• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

lsm / HyperNeo / 30283797683
83%

Build:
DEFAULT BRANCH: dev
Ran 27 Jul 2026 04:15PM UTC
Jobs 0
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
  cancel
30283797683

push

github

web-flow
test: add chat/thread lifecycle recovery regression suite (#2250)

* test: add chat/thread lifecycle recovery regression suite

Regression coverage for the lifecycle transitions that previously caused
sessions to appear stuck, locked, or mis-positioned:

- Router special-character contract (router-lifecycle-recovery): create ->
  parse round-trips, coordinator ids with colons resolve on the space-session
  route, plain /session/ rejects colon/non-hex/slash ids, raw-pathname
  matching (no percent-decoding).
- SessionStore cold mount + reconnect (session-store-lifecycle-recovery):
  cold-mount snapshot sorts + opens messagesLoaded, and on WebSocket
  reconnect the store re-subscribes with the same subscription id and
  re-applies the fresh snapshot; superseded subscriptions do not re-subscribe.
- shouldBlockForPendingQuestion edges (ChatContainer.test): only a trailing
  terminal result clears the waiting_for_input lock; non-waiting statuses
  never block.
- Daemon stale waiting_for_input (processing-state-lifecycle-recovery):
  real ProcessingStateManager preserves waiting_for_input across a restart,
  then the terminal-result setIdle() path clears it and persists idle so a
  second restart does not re-lock the composer.

* test: route stale waiting_for_input recovery through the result handler

Address review feedback on PR #2250: the prior test called
ProcessingStateManager.setIdle() directly, so it never exercised
SDKMessageHandler's terminal-result detection and would stay green if that
setIdle() call were deleted.

The test now wires a real ProcessingStateManager as the handler's state
manager and delivers a terminal ERROR result through
SDKMessageHandler.handleMessage(). An error result is isSDKResultMessage but
not isSDKResultSuccess, so it hits the handler's stale-clear at the top of
the result path without reaching handleResultMessage()/finishTurn() (which
also setIdle for success results) — isolating the fixed branch. Verified by
temporarily... (continued)
Source Files on build 30283797683
Detailed source file information is not available for this build.
  • Back to Repo
  • Github Actions Build #30283797683
  • e828b43e on github
  • Prev Build on dev (#30283662837)
  • Next Build on dev (#30283927832)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc