Repository navigation
fix: distinguish daily source read failures from absent runs - #485
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
What changed
When archive listing failed, reports could not be read, or the bounded read limit was exceeded, the daily publisher returned
no_attributable_runsif no attributable rows remained. Preserve fixed source-failure statuses instead; unknown source errors use a safe fallback without exposing provider text. Genuine empty or unmatched sources retainno_attributable_runs.All these paths still fail before POST. Partial projections with attributable runs, identity validation, exact acknowledgement matching and the single-request policy are unchanged. Add regression coverage and document the statuses.
This follows #484 and addresses a reproduced diagnostic defect. It does not establish or repair the original candidate-storage incident, and it does not recover live authentication. No deployment or live invocation was performed.
How verified
no_attributable_runsinstead ofsource_list_failed) and passed after the fix.Draft only. No labels, merge, deployment, IAM changes, candidate replay or trading.
AI assistance
OpenAI Codex. No delegated agents.