Skip to content

fix(ui): one trail length for the bar, the store and /api/flow (#1976) - #2001

Merged
colbymchenry merged 1 commit into
mainfrom
fix/1976-trail-limits
Sep 27, 2026
Merged

colbymchenry merged 1 commit into
mainfrom
fix/1976-trail-limits

Conversation

@colbymchenry

Copy link
Copy Markdown
Owner

Carries @danusha2345's #1994 onto current main (their commits, authorship preserved; the CHANGELOG entry is collected separately to avoid conflicts between the fix PRs).

Validation

Fixes #1976

🤖 Generated with Claude Code

The trail store saves up to 64 hops, /api/flow read at most 24, the
in-memory trail had no limit, and /api/nodes answers 60 ids per request.
So "Read as flow" failed on any walk of 25 or more hops, including trails
the store had just saved, and a cold load of a 61-64 hop link never got its
names back.

/api/flow now reads up to the store's MAX_TRAIL_HOPS. The trail keeps the
same 64 hops, dropping the oldest on push and on hydrate. resolveTrailNames
asks /api/nodes in batches of 60 and merges the answers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 4da4540)
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.

Viewer: trails of 25+ hops fail "Read as flow"; trail limits disagree (store 64, flow 24, nodes 60)

1 participant