fix: skip score for workflows unexpected situations#92
Merged
Conversation
vtnphan
approved these changes
Jun 26, 2026
vtnphan
left a comment
Collaborator
There was a problem hiding this comment.
Looks like a nice short term fix! Liftoff
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.
Pull Request
Summary
Fix score for runs without a workflow (due to previous database schema missing the
workflowfield)Changes
job_utils.pycatches theValueErrorfromget_output_spec, logs a warning, and returnsNonefor that run's score instead of crashing.Score is best-effort metadata and shouldn't be able to 500 the page. All other jobs will now render; the orphaned run will appear without a score.
How to Test
CI Tests shall pass
Type of change
Checklist