Repository navigation
Conversation
6006175 to
2a84069
Compare
|
@codex review |
There was a problem hiding this comment.
🟢 Approval recommended
The focused logging and message changes have targeted test coverage and no identified blocking issues.
0 open findings
What changed in this PR
Improves visibility of rejected requests to the apps plugin’s Vite dev-server routes without flooding default logs.
Changes:
- Warns once per Host/reason pair, with a per-server cap and debug logging afterward.
- Adds stable rejection reasons and upgrade guidance for older Vite versions.
- Tests deduplication, warning limits, instance isolation, and credential exclusion.
| File | Description |
|---|---|
| packages/plugins/apps/src/vite/dev-server.ts | Adds bounded, per-server refusal warnings. |
| packages/plugins/apps/src/vite/dev-server.test.ts | Tests refusal logging and deduplication. |
| packages/plugins/apps/src/vite/dev-server-request-guard.ts | Adds rejection reasons, shared Host extraction, and upgrade guidance. |
| packages/plugins/apps/src/vite/dev-server-request-guard.test.ts | Verifies rejection reasons and guidance. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
22c3417 to
3db0670
Compare
🎉 All green!🧪 All tests passed 🔗 Commit SHA: d8a533d | Docs | View more details | Give us feedback! |
6d804f4 to
f35b888
Compare
Live Debugger Runtime BenchmarkSDK-loaded dormant-probe runtime overhead, measured against an uninstrumented bundle in the same browser session.
What do the Tiny and Hot workloads represent? Browser Debugger SDK: Full diagnosticsRaw samples are in the |
66c1dde to
fca924d
Compare
f35b888 to
025a10b
Compare
A refused /__dd request now logs at warn the first time a dev server logs that refusal's message, and at debug after that, so a developer behind a tunnel or LAN hostname sees why the request failed. The set of warned messages is capped per dev server, with one notice once the cap is reached. A refused hostname's non-ASCII characters are escaped, since the message now reaches the terminal by default. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fca924d to
6c87182
Compare
025a10b to
d8a533d
Compare
Motivation
debug, below the defaultlogLevelofwarn, so a developer behind a tunnel or LAN hostname sees a 403 and nothing in the terminal.Changes
7 changes across dev-server.ts, dev-server-request-guard.ts, README.md and their tests
debug.dev-server.tsMAX_WARNED_REJECTIONS(32) per dev server, with one notice.dev-server.tsdev-server-request-guard.tsserver.allowedHostsadvice intoALLOWED_HOSTS_HINT.dev-server-request-guard.tsdev-server.test.tsALLOWED_HOSTS_HINT.dev-server-request-guard.test.tsREADME.mdQA Instructions
6d804f4a. Setup: the build-plugins: Testing and QA Guide.vite devrun (Vite 6.4.3) of the request guard, with outbound sockets blocked and no Datadog credentials:server.allowedHostshint; onewarn, the 3 repeats atdebugonlyqa-guard-logging.sh\uescape, with no raw non-ASCII byte in the terminalqa-guard-logging.shlocalhostand once via127.0.0.1warn, the 2 repeats atdebugonlyqa-guard-logging.shContent-Typeqa-guard-logging.sh/__dd/debugBundlecallqa-guard-logging.shwarns, the last (cap-28) with the cap notice; the other 5 atdebugonlyqa-guard-logging.sh, both log levelsReal
vite devrun: script, app files and outputqa-guard-logging.sh:app/index.html:app/main.js:app/backend/greet.backend.ts:app/vite.config.mjs:loopback-only.cjs:\u:QA_LOG_LEVEL=debug, the responses and cap notice match the default run; the terminal and counts become:cap-28carries the notice.Blast Radius
/__ddroutes change.warnline, at most 33 per dev server.Documentation
server.allowedHosts🤖 Generated with Claude Code