Conversation
…lity Wrap real API calls in try/catch so tests pass (skip drift comparison) when the Gemini Interactions API returns HTTP errors. Also harden the drift-report-collector to distinguish infrastructure errors (HTTP 4xx/5xx, DNS failures, etc.) from broken drift report formats — warn instead of crash for the former.
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
collectDriftEntriesguard now distinguishes infrastructure failures (HTTP errors, connection refused) from broken report formats. API unavailability warns instead of crashing; actual format mismatches still crash.Fixes the drift job failure introduced by PR #139 (Gemini Interactions API).
Test plan