Bug fix in EvaluationManager - #748
Merged
Merged
Conversation
… that submit_tasks() can be called asynchronously with retrieve_results().
thartland
approved these changes
Sep 12, 2025
thartland
left a comment
Collaborator
There was a problem hiding this comment.
Looks great. I tested this on an example problem. Thanks Wessley!
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.
Sorry that I missed the release by a few hours. I saw this bug yesterday, I think. This PR fixes the logic in
EvaluationManager.retrieve_results().EvaluationManager.retrieve_results(), and an inconsistency insubmit_tasks()(*argscan't come after keyword argument).EvaluationManager. This is made so thatsubmit_tasks()can be called in parallel withretrieve_results(). Not necessarily needed now, but I can think on workflows that do need that.Here follows the tests that I used that can reproduce the issue in the version of the code in the current develop branch. Please, I would recommend that you include such tests in future releases: