fix: handle truncated JSON and unescaped quotes in community labels#1311
Open
matiasduartee wants to merge 6 commits into
Open
fix: handle truncated JSON and unescaped quotes in community labels#1311matiasduartee wants to merge 6 commits into
matiasduartee wants to merge 6 commits into
Conversation
…ills/ instead of ~/.agents/ or ~/.gemini/skills/
…usively use global config path
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.
This PR adds a regex fallback in _parse_label_response\ so that if the LLM output is truncated (Unterminated string) or contains unescaped quotes inside community names, the parser can salvage the valid name pairs instead of discarding the entire batch of communities.