Repository navigation
fix: preserve scheduled test defaults and show proxy disconnect causes - #187
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
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.
Scheduled account tests were resolving an absent prompt to
hibefore provider dispatch. Antigravity consequently treated that default as custom input and raised its output budget. Preserve the raw optional prompt, keep scheduled Antigravity requests at their original./ one-token defaults, and keep blank interactive tests athi/ one token.Proxy connection tests also expose a bounded, credential-redacted transport detail when a connection fails. EOF and connection resets have explicit messages, so a failure after a successful CONNECT/TLS handshake is distinguishable from authentication or certificate rejection.
Validation: targeted Gemini and Claude payload tests cover scheduled defaults, blank manual input and custom manual input; Go and Vue tests cover redacted disconnect causes and their display. The existing successful production BestProxy HTTP CONNECT and pinned-certificate check remains applicable because the proxy handshake and trust policy are unchanged.