Skip to content

Make PYTHON_ENV_INIT_TIMEOUT and PLUGIN_MAX_EXECUTION_TIMEOUT for plugin daemon customizable via .env file #15282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
5 tasks done
kurokobo opened this issue Mar 8, 2025 · 0 comments · Fixed by #15283
Closed
5 tasks done
Labels
💪 enhancement New feature or request

Comments

@kurokobo
Copy link
Contributor

kurokobo commented Mar 8, 2025

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

The following environment variables for plugin daemon are often suggested as workarounds in reported Issues.

  • PYTHON_ENV_INIT_TIMEOUT
  • PLUGIN_MAX_EXECUTION_TIMEOUT

However, in the current implementation, this requires editing of the docker-compose.yml directly. It would be convenient if these values could be modified through the .env file.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💪 enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant