Repository navigation
fix: use upstream's bound in parse_workspace_id - #120
Merged
cameronsjo merged 2 commits intoOct 21, 2026
Merged
Conversation
Upstream fixed the out-of-range w_N / N panic with the same filter as fork PR #81 (herdrdev#5171). The 2026-10-12 sync kept the fork's copy of the line and its comment, so the function still diverged from upstream with no change in behavior. parse_workspace_id now matches upstream master exactly. The fork's request-path tests and the hand-rolled guards stay. The ledger marks the #81 entry retired for the parser filter. refs #77 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016MXBYW3meTL95gcAeo2HFm
|
Warning Review limit reached
This review includes 2 billable files and costs up to $0.50.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 53 minutes for your next included review. View limit details
Comment |
…workspace-id docs/fork/CHANGES.md conflict only: this branch and master (#115, #116, #117, #118, #119) each added a new section at the same spot. Kept all of them whole, this branch's section first because the ledger is newest first. The retired note on the #81 entry merged without a conflict. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016MXBYW3meTL95gcAeo2HFm
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
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.
Requested by Cameron · project thread
What
Upstream fixed the out-of-range
w_N/Nworkspace-id panic with the same filter as fork PR #81 (upstream herdrdev#5171). The 2026-10-12 sync kept the fork's copy of the line and its comment. Soparse_workspace_idstill diverged from upstream, with no difference in behavior.parse_workspace_idinsrc/app/ids.rsnow matches upstreammaster(143bf5f) exactly. The fork's.filter(|index| *index < len)and its four-line comment become upstream's.filter(|&index| index < len). The fork's request-path tests and the three hand-rolled< lenguards stay.In
docs/fork/CHANGES.md, the #81 entry is marked retired for the parser filter, like the 2026-09-17 retired entry. A short new entry records this PR.Check
masterbyte for byte (diffed againstraw.githubusercontent.com/herdrdev/herdr/master/src/app/ids.rs, master at143bf5f).cargo fmt --check: pass.cargo test. The vendored libghostty-vt build fetches its Zig packages fromdeps.files.ghostty.org, which this session's proxy blocks. I installed Zig 0.16.0 and seededuucodeby hand (hash verified), but zlib, highway, wuffs and the themes tarball also need that host. CI covers it:cargo nextest run --locked -E 'test(positional_workspace_id) + test(numeric_workspace_ids_beyond_the_last_workspace_are_not_found)'.Part of the owned-concessions sweep (cameronsjo/cadence-ecosystem#649).
Generated by Claude Code