Test: room for a giant thread's card on a busy runner #305
No reviewers
Labels
No labels
area/ci
area/desktop
area/packaging
area/protocol
area/reading
area/ui
area/web
area/writing
kind/bug
kind/feature
kind/infra
kind/request
needs/user
parked
perf
security
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
littlefox/neokom!305
Loading…
Reference in a new issue
No description provided.
Delete branch "fix-giant-list-timeout"
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?
Fixes main: run #502 (merge of #302) failed once on giant.spec list test on Android (no card within 15 s); the same test passed on the branch. Gives the first card the 60 s the rest of that test allows.
Refs #285
🤖 Generated with Claude Code
https://claude.ai/code/session_01XJW2ocwLunyaLiUwCBHEP8
Not just a slow runner: building a 3 000-long chain's index walked down a level (one text) per round trip, so with CI's (or any real server's) latency the card never came. Added prefetching the texts after a level in its channel (fetch_after), in the index walk and the chat's walks. Locally with 30 ms each way: the giant list test passes (card in ~20 s); devserver integration tests pass.
Merged; main run #533 green. Besides the fetch-ahead for walks down (giant thread card now ~20 s at 30 ms latency, not minutes): the channel chat stays at its end while its page comes in (any scroll but its own stops it), mute.spec waits for the thread before opening a menu, and time/channel-views retry what a redraw can undo.