Skip to content
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

Worker task execution timeout (global) #1951

Merged
merged 2 commits into from
Dec 19, 2023

Conversation

KLarpen
Copy link
Contributor

@KLarpen KLarpen commented Dec 19, 2023

The setting server.workers.timeout in application configuration is required but allows zero value to switch off the limit.

Closes: #1950

  • tests and linter show no problems (npm t)
  • tests are added/updated for bug fixes and new features
  • code is properly formatted (npm run fmt)
  • description of changes is added in CHANGELOG.md
  • update .d.ts typings

The setting server.workers.timeout in application configuration is required but allows zero value to switch off the limit.

Closes: metarhia#1950
Copy link
Member

@tshemsedinov tshemsedinov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use AbortSignal.timeout(msec)

@tshemsedinov tshemsedinov merged commit 1fd89f6 into metarhia:master Dec 19, 2023
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Configuration server.worker.timeout doesn't limit task execution time
2 participants