TanStackOSS
    ai
    fix(ai-client): restore pending interrupt on hydrate even when activeRun is reported hydrateFromServer chose between tailing an activeRun and restoring a pending interrupt with a mutually-exclusive if/else-if, tailing first. A run that just paused on an interrupt can momentarily still read as 'running' on the server, so a hydrate racing that window returns BOTH an activeRun cursor and the pending interrupt. The old order tailed the (paused) run and dropped the approval, so the interrupt card intermittently vanished on reload. Check pending interrupts first: a pending interrupt means the thread is paused, so restore the approval and never tail. Adds a regression test for the both-present hydrate result.
    nx run-many --targets=build --exclude=examples/**,testing/**
Succeeded
CI Pipeline Execution
Linux
4 CPU cores
read-write access token used
47e93acd984
80%

Cache hits

40 of 50 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

50 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools