Worker check runner container status#1342
Merged
Merged
Conversation
…-runner-container-status
ritwik-g
reviewed
Jun 5, 2025
ritwik-g
reviewed
Jun 5, 2025
johnyrahul
reviewed
Jun 5, 2025
johnyrahul
reviewed
Jun 5, 2025
johnyrahul
approved these changes
Jun 5, 2025
ritwik-g
approved these changes
Jun 5, 2025
Contributor
|
|
pk-zipstack
pushed a commit
that referenced
this pull request
Aug 20, 2025
* splitting celery tasks for chord callbacks * add celery retry value as env * updated compose override file to easy to use of workers in single worker-callback * polling for container or pod status check from worker * minor change in sample env value * condition to avoid re processing the same file execution id * minor changes in sample env * fixed status updation of file execution tracker while duplicate task * removed duplicate service from docker compose
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



What
ToolExecutionTrackerstatus handling into the worker from runner.FileExecutionTrackerto track all stage and container namescallback-workerservice to the Docker Compose file (was missing earlier).Why
How
get_container_statusandremove_container_by_namemethods in the docker client.Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
Database Migrations
Env Config
backend
Runner
Relevant Docs
Related Issues or PRs
Dependencies Versions
Notes on Testing
Screenshots
Checklist
I have read and understood the Contribution Guidelines.