Skip to content

v0.12.0

Latest

Choose a tag to compare

@github-actions github-actions released this 31 Oct 04:58
· 177 commits to main since this release
9284240

Added

  • Add native reference-client channel selection that stops new sends on failed links (#1291).
  • Add an experimental native reference-client profile for Godot negotiated channels with exact binary packet events (#1240).
  • Relay live room events and gameplay to read-only spectators (#1137).
  • Add attributed opaque relay probes for v2 and mixed v2/v3 reference-client runs (#678).
  • Add browser reference-client MessagePack relay support for protocol v2 and v3 (#678).
  • Find a published live room by application, game, and room code beyond the session-list limit (#992).
  • Report reference-client peer and channel state at P2P timeouts, incomplete gameplay exchange timeouts,
    and before failed links are removed, including bounded browser state history and SDP, ICE, and DTLS progress
    plus native and browser receipt admission counts and browser SCTP error details (#853, #889, #1019).

Changed

  • Reduce room-join allocations when checking ASCII player names (#636).
  • Reduce temporary allocations during room checks and expiration (#636).
  • Reduce memory allocation when checking room members before game start (#636).
  • Reduce dashboard refresh copies and keep history storage within its sample limit (#636).
  • Reduce memory allocation when reading room state and publishing lobby readiness snapshots (#636).
  • Reduce spectator admission copies while preserving room and spectator snapshots (#636).
  • Reduce allocations when selecting a session host and publishing session peer lists (#636).
  • Reduce server latency metric memory and keep routine timing updates free of allocations (#1285, #636).
  • Reduce room-event copies when no player needs reconnect replay (#636, #1277).
  • Breaking: Native reference-client consumers must set channel_profile in settings literals
    and handle binary channel events, the receive-rejection failure field, channel-close observations,
    and generation fields on connection, channel-open, and received-message output events.
  • Bound active-session response storage and reduce room percentile query memory and dashboard-history sizing work (#636).
  • Reduce capacity-run send preparation, receipt collection, analysis work, replay allocations, churn index size, and retained
    stream, recipient, sender-identity, sparse-latency, and unused record storage (#636, #775).
  • Add clock anchors to capacity generator lag reports (#1009).
  • Add native SCTP, transport, and actual channel settings to gameplay diagnostics, with bounded waits and explicit partial
    results on busy links (#1240, #1244, #1287).
  • Reduce native gameplay send allocations by reserving the required fragment count (#636).
  • Reduce native gameplay receive copies and retained storage for small messages and reordered packets (#636, #1229).
  • Reduce delivery-report and retained-gap lookup work in both reference clients (#1192, #1194).
  • Reduce native recovery work when partial-reliability messages leave large sequence gaps (#1187).
  • Reduce native receive work when partial-reliability recovery discards fragmented gameplay (#1182).
  • Reduce native gameplay fragment insertion work for ordered and unordered messages (#636, #1191).
  • Reduce native gameplay completion work for fragmented unordered messages (#1175).
  • Reduce native gameplay receive work for complete unordered messages and packet-limited acknowledgments (#1171, #1172).
  • Breaking: Rust callers that construct ServerMessage::PlayerReconnected must set its optional player field.
  • Reduce native gameplay fragment completeness work for delayed or reordered packets (#1168).
  • Reduce native gameplay queue work for packets received or sent in order (#1164).
  • Reduce reliable relay deadline lookup work for queued gameplay (#1160).
  • Reuse the browser binary gameplay decoder across messages (#636).
  • Reduce browser gameplay receive allocations with reusable bounded storage (#1157).
  • Reduce relay queue scan work when batching is enabled (#1155).
  • Breaking: Custom message coordinators must support explicit spectator lifecycle frames and observer publication.
  • Expose native reference-client channel receipt diagnostics through the engine API.
  • Preserve native reference-client receive-limit, channel-closure, and first terminal connection observations (#1264).
  • Show which native peer channels retain application messages in shared receive-budget diagnostics (#1264).
  • Include browser channel totals and probe validation counts in exchange timeout diagnostics (#889).
  • Reduce memory and lookup work in capacity collection, delivery validation, churn schedules, artifact export, and replay
    (#636, #775).
  • Update Tokio to 1.54.1 after 1.54.0 was withdrawn.
  • Update Unicode normalization to 0.1.26.
  • Remove temporary payload allocation when measuring JSON gameplay, signaling, and peer metadata bytes (#636).
  • Reduce dashboard room-query allocations and release room locks before percentile sorting (#636).
  • Reduce the cost of average timing queries in the Rust library (#636).
  • Reduce memory allocation when recording server response and WebSocket round-trip timings (#636).
  • Breaking: Require Rust 1.94.0 or newer to build from source with the current dependencies.
  • Breaking: Rust library callers using EncryptionError::Base64Decode must use base64 0.23.
  • Breaking: Opaque reference-client sends now include an application sender header; upgrade both probe clients (#678).
  • Breaking: Native MessagePack runs now encode valid payloads and emit decoded receipt values
    instead of base64 wrappers (#678).
  • Refresh running Direct session plans immediately when the host changes or loses its endpoint (#947).
    Breaking: Rust library callers must use handle_provide_connection_info through Arc<EnhancedGameServer>.

Fixed

  • Repair repeated readiness on restored public Rust rooms so duplicate ready entries do not block game start (#1320).
  • Keep public Rust Room authority flags consistent after restoring room state (#1317).
  • Require complete, consistent member readiness before public Rust Room game starts (#1315).
  • Keep active rooms alive after player metadata changes through Rust storage APIs (#1309).
  • Keep rooms alive after lobby, ready, authority, and game-start changes through Rust Room and storage APIs (#1306).
  • Refuse overlapping player and spectator roles in public Rust room admission (#1304).
  • Refresh public Rust room activity after successful player joins and departures so expiry starts from that change (#1302).
  • Keep public room admission readiness and authority consistent, and refuse ready toggles for absent members (#1300).
  • Reject absent-player authority assignments without changing the room (#1298).
  • Reject duplicate player and spectator admissions without replacing members or inflating session join counts (#1296).
  • Preserve server shutdown close reasons while inbound traffic is still arriving (#1295).
  • Preserve player readiness when the public room API enters the lobby (#1293).
  • Keep the original physical generation on native gameplay and connection output after link rebuilds (#1283).
  • Wait for the requested native P2P rebuild before reporting success after relay fallback (#1282).
  • Keep native gameplay charged to the receive budget until its output is flushed or discarded (#1280).
  • Exclude terminal native reference-client links from the connected-pair count (#1276).
  • Preserve reliable and ordered native gameplay after large expiry backlogs (#1271).
  • Report native associations as drained only after shutdown work and unread gameplay finish (#1272).
  • Stop expired ordered native gameplay before its first transmission (#1269).
  • Clear native graceful-shutdown reset state after final reads and stops (#1263).
  • Apply native send-buffer limits to empty text and binary messages (#1260).
  • Keep capacity missing-delivery counts within recorded sends when a receipt has an out-of-range sequence (#1252).
  • Preserve native negotiated-channel reliable packets that arrive during startup (#1250).
  • Count every misrouted delivery from unexpected senders in capacity reports (#1243).
  • Preserve unread native gameplay between shutdown acknowledgment and final completion (#1239).
  • Complete native graceful shutdown before queued shutdown retries (#1237).
  • Preserve native graceful shutdown retry deadlines when a peer repeats its shutdown request (#1235).
  • Preserve native channel reset retry limits and deadlines when a peer reports a busy request (#1233).
  • Release native sent gameplay storage after selective acknowledgment or abandonment (#1230).
  • Keep native receive credit correct when accepted gameplay crosses full-width limits (#1231).
  • Keep native gameplay sending after messages are abandoned at a closed receive window (#1227).
  • Keep native receive-byte accounting exact when ordered reassembly rejects duplicate fragments (#1223).
  • Count empty native data-channel messages as zero application bytes in traffic statistics (#1219).
  • Disable Nagle on native reference-client sockets so small relay frames can send promptly (#1217).
  • Preserve leading BOM characters in browser MessagePack gameplay strings (#1215).
  • Keep repeated native data-channel close successful after completed reset (#1214).
  • Bound native chunk-cursor reads by the remaining message size (#1213).
  • Apply native chunk-array message limits to each message instead of the whole array (#1210).
  • Close late browser data-channel announcements after their peer link retires (#1211).
  • Keep native gameplay fragments within custom packet and chunk sizes (#1205, #1206).
  • Preserve native gameplay retransmission with full-width packet settings (#1208).
  • Include the next browser relay frame in the local send-buffer limit (#1207).
  • Preserve streams on small reset budgets and reject zero-budget writes before consuming gameplay (#1201, #1203).
  • Recover native incoming gameplay after fragment loss independently of local send ordering (#1199).
  • Split native stream-reset requests to fit supported packet and chunk sizes (#1200).
  • Retain selected ICE route details, transport transitions, and ICE errors in browser diagnostics (#853, #889).
  • Reject reference-client gameplay that an earlier exact report already marks as dropped (#1196).
  • Keep native recovery packets within the transport size when losses span many ordered streams (#1197).
  • Retain browser connection details when initial offer creation fails (#853).
  • Keep empty native SCTP writes from blocking later ordered messages (#1190).
  • Preserve native channel close notifications when remote admission waits until channel retirement (#1188).
  • Release browser negotiation backlog when peer links retire so repeated replacements keep gameplay active (#1183).
  • Preserve native ordered gameplay sequence progress when stream reset completes during graceful shutdown (#1184).
  • Refuse new native streams when graceful shutdown starts (#1145).
  • Preserve unread native ordered gameplay across stream sequence wrap (#1178).
  • Report exact remaining bytes for native chunk-array sources (#1177).
  • Report native streams as unwritable when graceful shutdown starts (#1145).
  • Preserve native message completion order when ordered fragments arrive late (#1170).
  • Restore current peer metadata to room observers in reconnect notifications (#1167).
  • Acknowledge duplicate native gameplay packets immediately after lost acknowledgments (#1165).
  • Keep native gameplay acknowledgments within the transport packet size during heavy reordering (#1163).
  • Preserve native gameplay acknowledgments across packet sequence wrap and large sequence gaps (#1158).
  • Reject capacity replay sends before their schedule or outside their recorded connection lifetime (#1159, #1162).
  • End retained native channel streams when peer close is canceled (#1156).
  • Keep native peer close responsive when its command queue is full (#1154).
  • Close reference-client gameplay links and cancel pending room sends when the client leaves a room (#1150).
  • Close retained native data-channel handles and release their send capacity when the peer connection closes (#1151).
  • Recover native graceful shutdown after the final completion packet is lost (#1147).
  • Drain admitted native gameplay during graceful shutdown and release receive space when applications read or stop
    streams (#1145).
  • Complete native graceful shutdown when the final gameplay acknowledgment arrives in SHUTDOWN (#1143).
  • Resolve browser relay fallback immediately when remote SDP setup fails (#1144).
  • Close native gameplay channels and release blocked sends when DATA or shutdown recovery reaches its retry limit (#1140).
  • Restore browser exchange error reports after a peer link restarts (#1141).
  • Prevent delayed packets from reopening closed native gameplay transports (#1138).
  • Enforce workload, planned raw event bytes, retained event, and archive replay budgets for capacity runs (#775).
  • Close native gameplay channels when stream reset retries expire (#1133).
  • Report native peer closure after a fatal socket error, including before channel admission (#1134).
  • Reject native sends after shutdown and return blocked-send closure errors without a polling delay (#1135).
  • Report native gameplay link failure when handshake retries expire before channel admission (#1131).
  • Close pending native gameplay channels when the SCTP handshake fails (#1128).
  • Release native channel send capacity when unreliable gameplay is abandoned (#1124).
  • Preserve native gameplay backpressure across repeated reads (#1125).
  • Reject queued gameplay after room leave without charging relay bytes (#1119).
  • Preserve native gameplay during peer resets and first sends on negotiated channels (#1121).
  • Keep embedded-server gameplay in its original connection when a player reconnects (#1117).
  • Keep v3 peer transport updates off v2 connections after a concurrent reconnect (#1108).
  • Preserve admitted browser gameplay payloads when a peer-link timeout occurs while output waits (#1099).
  • Hold queued native gameplay probes when a returning peer re-arms the exchange release gates (#1097).
  • Keep native send-buffer counts correct when setup or empty messages are acknowledged (#1095).
  • Deliver accepted native gameplay before reporting transport-driven data-channel closure (#1093).
  • Reject native gameplay sends until the data-channel handshake completes (#1091).
  • Release blocked native sends when their data channel closes and report closure before buffer pressure (#1088).
  • Preserve existing native gameplay channels when a new channel requests an occupied stream ID (#1085).
  • Open native channels created after connection and close stalled handshakes at the configured deadline (#1086).
  • Report reference-client relay fallback immediately when initial peer negotiation fails (#1087).
  • Keep valid native channels opening when another deferred channel fails or closes before connection (#1081).
  • Allow native data channels to use the last valid stream ID within the negotiated limit (#1079).
  • Release failed native channel creations so a later channel can reuse a free stream (#1080).
  • Send accepted native gameplay input before closing its data channel (#1076).
  • Preserve timely reference-client gameplay receipts when payload decoding or receive admission crosses the deadline
    (#1073, #1074).
  • Deliver final native gameplay input before reporting a remote data-channel reset (#1075).
  • Preserve timely native gameplay receipts through link loss, negotiation timeout, and ordinary retry (#1070).
  • Report native channel loss before a remote reset completes so relay fallback can proceed (#1071).
  • Preserve server transport-status order when library callers report concurrent changes (#1068).
  • Keep timely browser gameplay receipts when a peer-link timeout occurs while output waits (#1066).
  • Read queued native keepalive replies before a slow peer retry causes a false connection timeout (#1067).
  • Keep browser reference-client sessions connected when timely server replies wait behind gameplay output (#1062).
  • Stop browser reference-client gameplay when live channel or peer state closes before its callback (#1055).
  • Stop native reference-client gameplay after pair loss or live sibling-channel closure
    while preserving input queued before its own graceful channel close (#1053, #1059).
  • Switch browser reference-client pairs to relay fallback when a required data channel starts closing (#1051).
  • Stop native reference-client deferred gameplay probes after observed channel or peer-connection loss (#1049).
  • Prevent reference clients from forming WebRTC pairs after they observe a required-channel or peer-connection failure (#1046).
  • Apply queued reference-client room updates before reporting success so new peers and restored links
    are not skipped (#1041).
  • Keep reference-client relay sends and receipts within the run window, including slow payload preparation
    and socket writes (#1037, #1039).
  • Resend reference-client gameplay probes on replacement peer links so lost old-link probes can recover (#1035).
  • Count timely queued reference-client receipts and valid pending sends within their exchange windows,
    including after room restore (#1031, #1033, #1034).
  • Keep late browser reference-client exchange receipts from reporting success after the run deadline (#1029).
  • Stop browser reference-client exchange retries at the run deadline so late sends cannot report success (#1027).
  • Breaking: Keep old signaling from disrupting reference-client peer retries; upgrade both retry-enabled endpoints
    together (#1022).
  • Stop retired browser reference-client signals from reaching replacement peer links (#1015).
  • Let browser reference-client pair retries recover from stalled negotiation before the connection deadline (#1013).
  • Keep browser reference-client relay traffic and other peers moving during stalled negotiation,
    and prevent false run failures and false fallback reports at the run deadline (#1011).
  • Discard native reference-client deferred connections when peers leave or session plans remove them (#1010).
  • Keep native reference-client relay sessions responsive when data-channel exchange sends fail or stall across peers
    (#1000, #1002, #1003, #1025).
  • Keep browser crippled-ICE runs on relay fallback when peer SDP includes ICE candidates (#999).
  • Preserve JSON object keys and numeric key conversion in browser MessagePack relay payloads on v2 and v3 (#996).
  • Keep browser opaque relay sessions connected when mixed-room senders use JSON fallback (#994).
  • Retry native and browser reference-client game starts when players become ready again (#990).
  • Give native reference clients the full Pong response window after a slow successful Ping write (#987).
  • Reject native reference-client WebSocket writes that finish after their write or handshake window expires (#985).
  • Keep native reference-client handshake deadlines active while reading buffered WebSocket control frames (#983).
  • Reject native and browser reference-client WebSocket connections once the connection wait expires (#981).
  • Discard late reference-client peer setup results without disconnecting working peer links (#979).
  • End native and browser sessions after failed signaling writes, and stop stalled native WebSocket writes (#976).
  • Keep reference-client handshakes and browser output within one 20-second window per command (#974).
  • Keep native and browser peer setup within one connection window per session plan (#972).
  • Keep native relay traffic, retries, and run deadlines working after stalled WebRTC negotiation (#961).
  • Keep browser relay traffic, retries, late connections, and run deadlines working during stalled negotiation (#960, #969).
  • Use rustls 0.23.46 for corrected TLS session handling in the server and native reference client.
  • Report browser reference-client channel closure immediately when the channel closes before handler registration (#955).
  • Fix the library starter so applications can compile it, drain on Ctrl+C, and report signal setup failures (#951).
  • Fix false native peer connection reports from delayed data-channel open events (#948).
  • Discard old native and browser peer-link traffic when a fresh room membership arrives (#937).
  • Report native and browser reference-client recovery when new session plans
    replace established peer links, even after the connection wait expires (#930).
  • Keep browser reference-client connection and run deadlines stable when the system clock changes (#929).
  • Keep browser reference clients running until replacement peer links connect or time out (#925).
  • Restore native peer links through opt-in remote retries after the original connection wait expires (#923).
  • Restore browser/native peer links through opt-in retries without early fallback or lost close events (#921).
  • Bound native closed-channel memory and preserve messages queued before channel registration (#919).

Container image

ghcr.io/ambiguous-interactive/signal-fish-server:0.12.0

Multi-architecture manifest digest: sha256:68dff60c493f202b0ad445cebe80d9e3e28e08383c8f03b945b1ef1ba055ab86

Source revision: 92842406fbd3ef94f933fe0a40702fdfb5d3670f