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

Optional feature: crash started task on timeout instead of deleting #264

Conversation

rakovskij-stanislav
Copy link
Contributor

Hello!

This PR introduces alternative behavior for STARTED tasks on their timeout.

For now karton deletes such tasks, but in certain scenarios it's preferable to crash them.

Also this PR shows effective config applied on karton dispatcher to ease testing with mixed parameter sources (command-line args, karton.ini, default values).

@rakovskij-stanislav
Copy link
Contributor Author

Related issue: #250

@rakovskij-stanislav
Copy link
Contributor Author

@psrok1 @nazywam @msm-code Hello! Just a gentle ping regarding this and other PRs. Thanks for your work!)

Copy link
Member

@psrok1 psrok1 left a comment

Choose a reason for hiding this comment

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

Looks good, thanks! I've made a small change and moved "Effective config" banner from SystemService constructor to the _log_config method that is called in loop.

I have also reverted comment on self.log.info("[%s] Processing task %s", ...), I guess it was leftover from testing.

@psrok1
Copy link
Member

psrok1 commented Jan 22, 2025

Ah, tests failed due to EOL of Python 3.7/3.8 - these version were removed from setup-python. Let me fix that.

@psrok1 psrok1 force-pushed the feature/crash-started-tasks-on-timeout branch from 0a4fe5f to 04b47cc Compare January 22, 2025 13:17
@psrok1 psrok1 merged commit 4cbb5ce into CERT-Polska:master Jan 22, 2025
7 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.

2 participants