Issues · ably/specification

`connection_failures_test.md`'s RTN14a and RTN14g are the same provocation, so the revoked-key spec point has no coverage

ably/specification#554 · opened

on Sep 25, 2026

`proxy/heartbeat.md`'s RTN23a test closes the WebSocket two seconds in, thirteen seconds inside the idle window, so nothing in it exercises heartbeat starvation

ably/specification#553 · opened

on Sep 25, 2026

`proxy/connection_resume.md`: RTN15h1 asserts a status code neither SDK returns, RTN14h asks uts-proxy for a `PASSTHROUGH` substitution it does not make, and RTN19a reads event-log fields the proxy does not emit

ably/specification#552 · opened

on Sep 25, 2026

Three `realtime/integration` sections contradict themselves: RTN4b's fixture, RSA7's `EXPECT THROW`, and RTL14's FAILED heading

ably/specification#551 · opened

on Sep 25, 2026

Three small faults in `uts/rest/integration`: two short `Spec points` headers, a JWT fixture that fails the wrong way, and an empty `presence` array the server does not send

ably/specification#550 · opened

on Sep 24, 2026

`history.md`'s time-range test passes when `start` and `end` are ignored — and the three `RSL2b` sections are each filed under the wrong point

ably/specification#549 · opened

on Sep 24, 2026

`batch_presence.md`'s restricted-key test closes the connection that owns the presence member it then asserts on

ably/specification#548 · opened

on Sep 24, 2026

`push_channels.md`'s device identity token is a literal the server rejects, contradicting the comment directly above it

ably/specification#547 · opened

on Sep 24, 2026

Three `realtime/unit/connection` tests assert two token requests for a basic-auth client that makes one, and a fourth never establishes its transport

ably/specification#546 · opened

on Sep 24, 2026

`helpers/mock_websocket.md` does not declare `active_connection`, which the suite uses 193 times across 28 files — plus eight tests calling five members that do not exist

ably/specification#545 · opened

on Sep 24, 2026

Ten `realtime/unit` fixtures cannot produce the condition they set up — six of them treat `connectionStateTtl` as something a test can set, and four attach channels on clients that never connect

ably/specification#544 · opened

on Sep 24, 2026

Four `realtime/unit` tests pass whether or not the SDK implements the spec point they test — RTP18a is currently passing against an SDK that does not implement it

ably/specification#543 · opened

on Sep 24, 2026

Three `realtime/unit/presence` tests hold a clientId that `features.md` forbids, and the file asks SDKs to skip the RTP15f check rather than fixing the fixtures

ably/specification#542 · opened

on Sep 24, 2026

`uts/rest/unit` housekeeping: a leaked local path, six untitled sections, a duplicated test, three misfiled Realtime tests, and three header/spec-point claims that do not hold

ably/specification#532 · opened

on Sep 18, 2026

1

RSA10i/authorize-preserves-key-0 has an empty assertions block, and its premise — that a constructor key survives an authOptions argument — is not backed by any features.md point

ably/specification#531 · opened

on Sep 18, 2026

RSA4b/renewal-msgpack-response-4 drives token renewal through /time, which the time suite explicitly forbids and whose own test asserts /time sends no credentials

ably/specification#530 · opened

on Sep 18, 2026

Two REST unit tests demand local token-expiry detection that RSA4b1 makes optional and conditional — already documented as a known UTS error but never fixed

ably/specification#529 · opened

on Sep 18, 2026

Four broken fixtures in `uts/rest/unit` — two make their tests unsatisfiable, two encode superseded specification text

ably/specification#528 · opened

on Sep 18, 2026

Three REST publish-body assertions contradict `features.md` (RSL4c3/RSL4d3, RSL1k1, RSL1k3), and eight unit specs read the request body without pinning the protocol

ably/specification#527 · opened

on Sep 18, 2026

1

Presence actions on the wire: `rest_presence.md` asserts wire action 4 is LEAVE, and two `presence_message_types.md` tests assert an outgoing action as the string "enter"

ably/specification#526 · opened

on Sep 18, 2026

uts/rest/unit: tests filed under spec point ids that name the wrong requirement or do not exist, and completion-status.md inherits the error

ably/specification#525 · opened

on Sep 18, 2026

`/time` is mocked as `{"time": N}` in 48 places across six `rest/unit` specs; the endpoint returns `[server_time_ms]`, so a typed SDK cannot derive those tests as written

ably/specification#524 · opened

on Sep 18, 2026

`rest/unit/fallback.md` is half-migrated: it uses a `queue_response` mock API that `helpers/mock_http.md` does not define and `writing-test-specs.md` bans, which makes four of its tests unsatisfiable

ably/specification#523 · opened

on Sep 18, 2026

OBJECT_SYNC channelSerial: clarify sequence-id opacity (RTO5a1/RTO5a6) and close the UTS coverage gap that hides a cross-SDK parsing bug

ably/specification#520 · opened

on Aug 28, 2026

LiveObjects: consider how to handle backslashes in path segments

ably/specification#481 · opened

on May 25, 2026