Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Caution Review failedAn error occurred during the review process. Please try again later.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
This branch has not been deployed
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.
What & why
Fixes #695
playwrightProxyOptionpassed the proxy username and password todecodeURIComponent. That throwsURIErroron a%that is not a valid escape (50%off,p%,%2). The URL parser keeps such a%as it is, so the error reached both browser launch paths and every browser fetch failed while that proxy was set.Changes
decodeUserinfoin src/fetch/proxy-credentials.ts decodes valid credentials exactly as before. IfdecodeURIComponentthrows, it decodes each valid escape sequence on its own and keeps a stray%as typed. Decoding sequence by sequence matters because the URL parser has already escaped characters such as", spaces and non-ASCII letters (pä%ssreaches us asp%C3%A4%ss). Returning that raw text would send the wrong password.%FFnext to a stray%), it is kept as typed and not replaced with U+FFFD.Testing
npm testpasses (not ticked: the full suite with a real browser has not run)npm run lintpassesLocal run 2026-11-12, Windows 11, Node 24.19.0, 2 workers:
npm run lintis clean.npx vitest run tests/unit: 8129 tests, 8083 passed, 20 failed, 19 skipped. tests/unit/fetch: 74 files, 961 tests, all passed. The 20 failures are in 7 files outside fetch (cli/agents/skills, tui propagation, warmup json contract, plugins loader, repl shell, research synthesis-local). The same 20 tests fail on unchanged main on this Windows machine (same 7 files). Fullnpm test(integration and e2e with a real browser) was not run locally.Checklist
CONTRIBUTING.mdand agree to its contribution termsValidated with Claude Opus 5.5.