fix: OPTIC-574: Inconsistent behavior on Create Annotations From Predictions #5631
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.
PR fulfills these requirements
[fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made
ex.fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
Change has impacts in these area(s)
(check all that apply)
Describe the reason for change
With the changes to ML Backends, the logic in the retrieval of model versions caused a workflow regression in DataManager. The reason was because the default value of a project model version is an empty string, and all subsequent checks on retrieval of the model versions were considering strictly None to represent the absence. This fix loosens the checks to look for falsey/truthy instead which fixes the observed regressions.
Which logical domain(s) does this change affect?
Predictions, ModelVersions, DataManager