Skip to content

issues: capture #024 (WebKit _rsc-prefetch e2e errors); annotate #023 repro#1066

Merged
BigSimmo merged 3 commits into
mainfrom
codex/issues-webkit-e2e-capture
Jul 22, 2026
Merged

issues: capture #024 (WebKit _rsc-prefetch e2e errors); annotate #023 repro#1066
BigSimmo merged 3 commits into
mainfrom
codex/issues-webkit-e2e-capture

Conversation

@BigSimmo

@BigSimmo BigSimmo commented Jul 22, 2026

Copy link
Copy Markdown
Owner

Summary

Docs-only ledger update. A full npm run verify:release:offline on main (ce32fe170) reproduced the webkit browser-matrix failure that #23 was waiting on ("diagnose only if reproduced"), so this records the diagnosis now rather than deferring it to the Sunday 2026-07-26 scheduled run.

  • New chore: pin esbuild to latest stable 0.28.1 #24 (P3 / issue) — 6/6 deterministic failures in tests/ui-route-coverage.spec.ts under the webkit project, each a pageerror … ?_rsc=… due to access control checks on Next.js RSC prefetch. Chromium and Firefox are clean. Not merge-blocking: the required gate test:e2e:pr is chromium-only, and the full webkit matrix is advisory/release-time. Most likely a Playwright route-interception x WebKit interaction rather than a Safari user defect; the row carries the open decision — (a) allow/mock _rsc for the webkit e2e project, or (b) confirm real Safari impact before trusting the full-matrix webkit gate at release.
  • fix: reconcile redesign and restore lint #23 annotated — its webkit clause now points at chore: pin esbuild to latest stable 0.28.1 #24; firefox ui-formulation:91 still awaits its own datapoint.
  • issues:next-id bumped 024 -> 025.

The two other webkit failures from the same run (ui-stress:412, ui-universal-search:210) passed on an isolated re-run and are recorded inline as true flake rather than tracked separately.

Diff-size note: the +22/-21 is almost entirely Prettier re-padding the markdown table (the new row's Detail cell widened a column). Only 3 lines are content.

Verification

Verification not run: docs-only ledger row — no code, config, links, or test paths changed, and prettier --check passes on the file. The finding recorded here came from a full npm run verify:release:offline on main ce32fe170 (every stage green except the webkit e2e described above), plus a targeted webkit re-run that separated the 2 flakes from the 6 deterministic failures.

RAG impact: no retrieval behaviour change — docs-only ledger row.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated the outstanding issues tracker with a new WebKit end-to-end testing issue related to _rsc prefetch access-control checks.
    • Added verification notes, decision steps, and cross-references for the newly tracked issue.

…epro

verify:release:offline on main ce32fe1 reproduced #23's webkit
browser-matrix clause: 6/6 deterministic ui-route-coverage failures,
root-caused to WebKit "access control checks" pageerrors on Next.js
RSC (_rsc) prefetch (Chromium+Firefox clean). Non-blocking — required
PR gate is chromium-only. Docs-only ledger update.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@supabase

supabase Bot commented Jul 22, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7fec82d8-17ee-4214-bcf8-7de584ea5c1b

📥 Commits

Reviewing files that changed from the base of the PR and between 658bd4d and 2c2f670.

📒 Files selected for processing (1)
  • docs/outstanding-issues.md

📝 Walkthrough

Walkthrough

The open-items ledger increments its next issue identifier, updates issue #023, and adds issue #024 covering WebKit _rsc prefetch access-control-check failures, verification details, and next-step options.

Changes

Outstanding issues ledger

Layer / File(s) Summary
Update open-items ledger
docs/outstanding-issues.md
Advances the issue counter from 024 to 025, revises issue #023, and appends issue #024 with WebKit verification and decision notes.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title is concise and accurately describes the new issue entry and annotation updates.
Description check ✅ Passed The description covers Summary and Verification, and the missing risk/governance sections are non-critical for this docs-only change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/issues-webkit-e2e-capture

Comment @coderabbitai help to get the list of available commands.

BigSimmo pushed a commit that referenced this pull request Jul 22, 2026
- Managed-alternative setup now says scope to UPDATE events only (do not tick
  INSERT) in the concrete instruction, not just a later warning — an INSERT
  webhook re-introduces the upload race.
- outstanding-issues #25: the base-URL GUC is mandatory per environment, not
  optional (the trigger no-ops without it), so the activation checklist can't
  leave the trigger inert.

Both are consistency fixes for earlier changes; neither touches the #24 row or
next-id marker (the ledger-collision surface vs #1066).

Docs-only.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BHMgBiXbH4Q5tUC7WxoyaX
@BigSimmo
BigSimmo enabled auto-merge (squash) July 22, 2026 04:58
@BigSimmo
BigSimmo merged commit 7dcf514 into main Jul 22, 2026
17 checks passed
@BigSimmo
BigSimmo deleted the codex/issues-webkit-e2e-capture branch July 22, 2026 05:00
BigSimmo pushed a commit that referenced this pull request Jul 22, 2026
- Renumber the webhook ledger rows #24-#27 -> #25-#28 (next-id 029) so they
  no longer collide with #1066's #24 (WebKit e2e). Per the consolidation
  decision, #1065 lands and the duplicate Codex webhook-doc PRs are closed;
  #1066 stays as a separate item.
- Scope the "receiver 500 -> retries" claim in the receiver-behaviour bullet:
  it only holds for a caller that actually retries, and neither documented path
  (raw net.http_post trigger or UPDATE-only managed webhook) does, so a failed
  clear can leave reindex_requested stuck true; recover via clear-then-flip.

Docs-only.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BHMgBiXbH4Q5tUC7WxoyaX
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