Repository navigation
fix: restore job filters by resolving tags once - #205
Merged
Merged
Conversation
|
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.
The jobs filter endpoint returned HTTP 500 after the popular-tag query hit its 30-second timeout. Resolve canonical tags once instead of repeating an ordered graph lookup for every tag. If popularity lookup fails, keep the valid tags already returned with the other filter values so all filters remain usable.
Validation: the corrected query returned 100 tags against production data in 779 ms using a read-only connection and a five-second timeout. TypeScript, lint, and the existing filter-cache and tag repository suites pass.