Retry feedback callback failures caused by no DB rows found#782
Merged
Retry feedback callback failures caused by no DB rows found#782
Conversation
…ued to guard against database registration race conditions
tieneupin
added
bug
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #782 +/- ##
==========================================
- Coverage 49.62% 49.60% -0.03%
==========================================
Files 96 96
Lines 10130 10135 +5
Branches 1331 1332 +1
==========================================
Hits 5027 5027
- Misses 4846 4851 +5
Partials 257 257 🚀 New features to boost your workflow:
|
stephen-riggs
approved these changes
Apr 15, 2026
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.
These exceptions might be caused by race conditions due to querying a dataset before its registration in the database is complete. This is usually seen with the
tomography_processing_parametersmessages, where they pass after being reinjected.Such feedback callback errors should be retried until they hit the retry limit and get sent to the DLQ.