MAINT: Improving JSON parsing logic to raise JSONException on empty required strings - #2567
Merged
varunj-msft merged 1 commit intoSep 3, 2026
Conversation
…equired strings Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8533014c-f354-4b22-b283-a374843aa006
varunj-msft
approved these changes
Sep 3, 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.
Description
Reject blank
next_messagevalues while parsing adversarial-chat responses. This causes the existing JSON retry path to run before an empty user message reaches the objective target.Tests and Documentation
Added unit coverage for empty and whitespace-only values and for retrying after an empty value. Documentation changes are not applicable.
Full pre-commit was run. Code-quality hooks passed. The memory migration and type-check hooks could not run successfully because the local environment could not resolve the locked project dependencies from the configured package index.