Skip to content

fix(cli): bound cold subscribe so large channels can post - #19

Open
femzyomos wants to merge 1 commit into
rjx18:mainfrom
femzyomos:fix/cli-cold-subscribe-hydrate-limit
Open

fix(cli): bound cold subscribe so large channels can post#19
femzyomos wants to merge 1 commit into
rjx18:mainfrom
femzyomos:fix/cli-cold-subscribe-hydrate-limit

Conversation

@femzyomos

Copy link
Copy Markdown

Summary

  • syncRoom cold-subscribes with since_seq: 0. On large channels, replaying full history can exceed ProtocolClient's default 5s inter-frame wait and fail codor post / status / inbox with timed out waiting for server frame.
  • Pass the existing protocol hydrate_limit on cold subscribe (500) and raise the sync frame wait to 60s so bounded cold snapshots finish reliably.

Why

Live dogfood: a channel with ~10k messages took ~8s to full-sync with inter-frame gaps >5s. codor post -r <that-channel> timed out; smaller channels posted fine. After this change, post succeeded in ~3–4s.

Test plan

  • pnpm --filter @codor/cli build
  • pnpm --filter @codor/cli exec vitest run src/index.spec.ts -t "post" (6 passed)
  • Maintainer: Harn plan for collaboration-room-sync if required (contributor path per CONTRIBUTING — describe intent here; did not edit .harn/)

Full-history syncRoom (since_seq 0) can exceed ProtocolClient's 5s
inter-frame wait on large channels, timing out post/status/inbox.
Pass hydrate_limit on cold subscribe and raise the sync frame wait.
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.

1 participant