Repository navigation
Scale the edge budget with the page count - #75
Merged
Merged
Conversation
arberx
force-pushed
the
fix/scale-edge-budget
branch
from
August 28, 2026 18:05
f5f353c to
6345f0f
Compare
7.0.0 derived maxFetches, maxDurationMs and maxBytes from maxPages but left maxEdges at its flat 100,000 default, recreating the original defect one budget over: at the ~42 recorded edges per page measured on a production portfolio site, a 5,000-page request stops admitting pages near 2,400 with termination max-edges. An unset maxEdges now derives as maxPages x 50, floored at the flat default and clamped to a safe integer. An explicit maxEdges is honoured exactly and a call with no maxPages keeps the documented flat default. Engine 2.1.0 to 2.2.0: shape unchanged, semantics changed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
arberx
force-pushed
the
fix/scale-edge-budget
branch
from
August 28, 2026 18:05
6345f0f to
782afb9
Compare
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
1 participant
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.
7.0.0 made maxPages the budget that drives the others, but left maxEdges flat at 100,000. On link-dense sites that recreates the truncation one budget over: measured at ~42 recorded edges per page on a production portfolio site (navigation and footer templates repeat on every page), the flat default runs out near page 2,400 of a 5,000-page request and admission stops with termination max-edges.
An unset maxEdges now derives as maxPages x 50, floored at the flat default and clamped to a safe integer:
An explicit maxEdges is honoured exactly. The regression test fails with the scaling removed (verified by reverting). 625 tests pass; typecheck, lint, e2e clean.
Minor bump 7.0.0 to 7.1.0; crawl engine 2.1.0 to 2.2.0 (shape unchanged, semantics changed).
🤖 Generated with Claude Code