{"version":"2.1.242","anchor":"half-open-cross-session-connections-are-dropped-on-a-deadlin","canonical_anchor":"half-open-cross-session-connections-are-dropped-on-a-deadlin","heading":"Half-open cross-session connections are dropped on a deadline","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/half-open-cross-session-connections-are-dropped-on-a-deadlin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Half-open cross-session connections are dropped on a deadline\n\nCross-session connections that never send a full line are closed on a deadline.\n\n**What**\n\nThe local socket that carries messages between sessions now closes any connection that fails to send a complete line within a configured first-line deadline, so a stalled or probing peer no longer holds a slot open.\n\n**Details**\n\n- Each connection arms a timer on accept, cleared on close or error; the timer does not keep the process alive.\n- The drop is logged, and the first one in a session reports a cross-session inbox auth telemetry value.\n\n**Evidence**\n\n`[uds-messaging] Closing a connection that sent no complete line within `\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}