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.
Fix invalid JSON escapes in GitHub remote MCP gateway config generation #41864
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Fix invalid JSON escapes in GitHub remote MCP gateway config generation #41864
Changes from all commits
08c4cbbba71ed7File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/diagnose]
safePosclipspostojsonText.length - 1when the parse error position equals the string length (EOF). This shifts the reportedcolumnone character back, which could mislead debugging for truncated or unterminated-string errors. A brief comment explaining the intent would help future readers.💡 Suggested clarification
Alternatively, special-case
pos >= lengthto reportline: <last line>, column: <EOL+1>for a more accurate EOF diagnosis.@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/diagnose]
keyMatchscans all oflineTextfor the first"key":pattern, regardless of where in the line the errorposfalls. For prettified JSON (one key per line) this works fine, but for minified or compacted JSON it could report a key that precedes the actual error position.💡 Improvement suggestion
Consider searching only within the substring up to
columnso the match is anchored to the error site:The fallback preserves the existing behaviour when no key appears before the error column (e.g., the error is inside a key name itself).
@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] The assertions only verify
keyandlineText—lineandcolumnare part of the returned contract but are unchecked, so regressions in position arithmetic would silently pass.💡 Suggested additions
Pinning at least
lineturns this into a real specification and catches off-by-one regressions ingetJSONParseErrorContext.@copilot please address this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/tdd] No test covers the
nullreturn path — whenparseErrorMessagecontains no"position N"substring the function silently returnsnull, but that branch is never exercised.💡 Suggested test
This matters because different JS engines (or future Node.js versions) may not include
"position N"in their error messages, and the calling code inmain()already guards onif (parseContext)— so the null path is a real production path that should be tested.@copilot please address this.
Uh oh!
There was an error while loading. Please reload this page.