Move run finished status update to the end of the job#352
Merged
Conversation
cristian-tamblay
approved these changes
Oct 24, 2025
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
2 participants
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.
This pull request refactors the order of database operations in the
runfunction withinmodel_job.pyto improve error handling and ensure that the model evaluation step occurs before marking the job as finished. The main change is moving the code that sets the job status as finished and commits to the database after the model evaluation step, rather than before.Error handling and workflow improvements:
run.set_status_as_finished()anddb.commit()to occur after the model evaluation step, ensuring that the job is only marked as finished if evaluation succeeds. [1] [2]