Repository navigation
docs: record #566–#572 follow-up merges, head 645abbb8 - #573
Conversation
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Update benchmark comparison and follow-up results docs/benchmarks/fork-vs-upstream-node-bun-2026-10-27.md, README.md |
The benchmark document adds results for PRs #566–#572 and updates the remaining-loss summary. The README updates the compared fork revision. |
Possibly related PRs
- bompus/codegraph#566: The benchmark update reports results for this PR’s JavaScript declaration-scope memoization.
- bompus/codegraph#570: The benchmark update reports results for this PR’s
bare_call_receiverand generated-path memoization.
Priority:
Merge Risk: 
Minimal · up to 73878
-
No actionable merge-blocking risk remains.
Pre-merge checks: 
6
-
Check name Status Explanation Description Check Check skipped - CodeRabbit’s high-level summary is enabled. Title check The title clearly and concisely describes the documentation changes: recording follow-up merges #566–#572 and updating the measured head to 645abbb.Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Suppressions Explained The pull request changes only README.md and a benchmark Markdown document. The added lines update revision text, benchmark rows, and result descriptions. No added line introduces a lint, type-check, c… User-Visible Changes Documented The pull request changes only README.md and a benchmark documentation page. The diff updates benchmark text, revisions, and follow-up rows. It does not add, remove, or rename a CLI command or flag, MC… Full details: Suppressions Explained
-
Explanation
The pull request changes only README.md and a benchmark Markdown document. The added lines update revision text, benchmark rows, and result descriptions. No added line introduces a lint, type-check, compiler suppression directive, or ignore configuration entry.
Full details: User-Visible Changes Documented
-
Explanation
The pull request changes only README.md and a benchmark documentation page. The diff updates benchmark text, revisions, and follow-up rows. It does not add, remove, or rename a CLI command or flag, MCP tool or argument, supported language or framework, agent target, or config key.
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
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.
Comment @coderabbitai help to get the list of available commands.
|
@coderabbitai review |
✅ Action performed
|
* docs: 2026-10-28 re-measure at de5a7b8 across all seven corpora Index and sync tables regenerated from the full 168-row re-run (upstream 69af19a, 4 arms x 2 mirrored passes). Fork now wins 6/7 Node index cells outright and 6/7 sync cells per runtime; pretix-Bun index resolves to a tie. New disclosed losses: gin index (~0.1s fixed overhead on a 119-file repo) and discourse sync (~0.5s). Follow-up table gains #573-#575 rows. * docs: regenerate scorecard, heatmap and README card from the 2026-10-28 run The "Every result at a glance" count, loss list, heatmap and README card still carried the earlier matrix: 57/10/9 with pretix-Bun index and sync listed as losses. Regenerated from the same raw run as the tables — adapt-flat-output + render-charts over the 2026-10-28 index-sync rows and the carried 2026-10-27 MCP/CLI data — the scorecard is 57/6/13, adds the gin index and discourse sync losses and the Alamofire index-memory loss, and drops the pretix-Bun cells (now inside spread). README card alt text and prose timings aligned to the generated figures (1.7x index, 3.5x sync, 30% memory; supabase 15.6 s, n8n 49.4 s, pretix +34% Bun).
Summary
d9bd974c→645abbb8in the doc and README.CODEGRAPH_RESOLVE_PROFILEindex runs, 3.2–3.7 s) across resolve: check js_decl_scope_memo before the file/tree loads #569–resolve: apply_language_gate filters in place #572, with exact graph parity (32,799 nodes / 73,404 edges).Test plan
Summary by CodeRabbit