fix: log first-attempt revalidation failure before retry#151
Merged
Conversation
Previously the outer catch discarded the error silently — transient revalidation failures were invisible unless both attempts failed. Now logs at console.debug so operators can spot intermittent issues.
ESLint only allows console.warn and console.error — console.debug is not in the allowed list.
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
1 participant
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.
Summary
Context
Identified during PR #144 review by the silent-failure-hunter agent. The revalidateSafely helper retries once on failure, but only logged when the retry also failed — making transient issues completely invisible.
Test plan