# fix\(server\): drop the traceId from the websocket close line · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/bef882cfef03c071e116be78287ba203ad46d5ff)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: bef882cfef03c071e116be78287ba203ad46d5ff

Requested commit: bef882cfef03c071e116be78287ba203ad46d5ff

Commit: bef882cfef03c071e116be78287ba203ad46d5ff

Tree: 3850ba5c950172c429ba27a3c384b72efd870754

Author: Victor Vogel

Committer: Victor Vogel

## Message

```
fix(server): drop the traceId from the websocket close line

The /ws request span is a child of the server-lifetime span, so every
connection's close line carried the same traceId and could not be joined
to one connection or its stall candidates. Stop logging it, drop the
docs' join claims, and say in the handler that the t3.connection
attributes are what tell connections apart.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [7d3175980e29e62575c62e98aef2c0bbd22acd14](https://git.cafe/pingdotgg/t3code/commit/7d3175980e29e62575c62e98aef2c0bbd22acd14?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/bef882cfef03c071e116be78287ba203ad46d5ff?format=markdown)