Fix #460: GC probe cap #471
No reviewers
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub!471
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/issue-460"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Child of #449 (F7). Raises maxForkNetworkProbes 64->512 (two probes/child, so ~256 direct children + transitive subtrees per pass); exhaustion still fails closed with nothing deleted. Refreshes stale one-level-per-pass comments (forknet.go, pulls model, features/03 §7 — the walk is breadth-first transitive in one pass; the cap, not depth, bounds it). Tests: TestForkNetworkGCWideFanout (40 children compact, measured cost pinned at exactly 81 GETs) + TestForkNetworkGCCapExceeded reworked to 300 children aborting safely. Full maintain suite -race green, coverage 95.5% (>=95% gate), vet/fmt clean. No new deps. No browser check needed (no browser-facing change). Residual bound stated in code + Decisions: fan-outs beyond ~256 children still defer; durable paged cursor is follow-up (needs bucket-side cursor state, a schema decision). Fixes #460.