Skip to content

spec/ait: add error handling spec points - #447

Merged
lawrence-forooghian merged 1 commit into
ai-transport-featuresfrom
AIT-597-error-handling-spec-points
Apr 15, 2026
Merged

spec/ait: add error handling spec points#447
lawrence-forooghian merged 1 commit into
ai-transport-featuresfrom
AIT-597-error-handling-spec-points

Conversation

@lawrence-forooghian

Copy link
Copy Markdown
Contributor

Summary

  • Amend AIT-CT3b: on POST failure the turn stream must be errored (not closed) with TransportSendFailed (104005), preserving the HTTP status or wrapping the network error as cause.
  • AIT-CT14c: errorStream() on the stream router.
  • AIT-CT19/CT19a: channel continuity loss detection — error active own-turn streams with ChannelContinuityLost (104006).
  • AIT-CT20: send() must reject with ChannelNotReady (104007) when the channel is not ATTACHED or ATTACHING.
  • Add ChannelContinuityLost (104006) and ChannelNotReady (104007) to the error codes section.

Companion SDK PR: ably/ably-ai-transport-js#32

🤖 Generated with Claude Code

Add spec points for the new error handling behaviours introduced in the
SDK:
- Amend AIT-CT3b: on POST failure the turn stream must be errored (not
closed) with TransportSendFailed, preserving the HTTP status or
wrapping the network error as cause.
- AIT-CT14c: errorStream() on the stream router.
- AIT-CT19/CT19a: channel continuity loss detection — the transport
must monitor for FAILED, SUSPENDED, DETACHED, or non-resumed
re-attach and error active own-turn streams with
ChannelContinuityLost (104006).
- AIT-CT20: send() must reject with ChannelNotReady (104007) when the
channel is not ATTACHED or ATTACHING.
- Add ChannelContinuityLost (104006) and ChannelNotReady (104007) to
the error codes section.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lawrence-forooghian
lawrence-forooghian merged commit dea9e85 into ai-transport-featuresApr 15, 2026
2 checks passed
@lawrence-forooghian
lawrence-forooghian deleted the AIT-597-error-handling-spec-points branch April 15, 2026 14:39
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@lawrence-forooghian@JoaoDiasAbly