Skip to content

Fix Validate: ignore optional precedent sidecar console errors - #13

Closed
MatthewPaver wants to merge 1 commit into
mainfrom
fix/ci-browser-console-errors
Closed

MatthewPaver wants to merge 1 commit into
mainfrom
fix/ci-browser-console-errors

Conversation

@MatthewPaver

Copy link
Copy Markdown
Owner

Why

Validate has failed since 2026-10-02 (run 36998319280). browser_change_assurance.py asserts no console errors, but Chromium logs the fetch to the optional precedent RAG sidecar (127.0.0.1:8787) as a console error when it is absent (ERR_CONNECTION_REFUSED in CI) or answers without CORS headers (local). The page already falls back to offline precedents, and the requestfailed listener already ignored the sidecar — the console listener didn't.

Change

One shared is_sidecar() check, applied to console errors (text and source URL) as well as failed requests. Every other console error still fails the test.

Verified

scripts/run_browser_tests.py — all 4 suites pass locally (failed before the change with the same assertion).

🤖 Generated with Claude Code

Validate failed on 2026-10-02 because Chromium logs refused (CI) or
CORS-blocked (local) fetches to the optional RAG sidecar on :8787 as
console errors. The page already falls back offline and requestfailed
already ignored the sidecar; apply the same rule to console errors.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@MatthewPaver

Copy link
Copy Markdown
Owner Author

Superseded by #14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant