Thomas Eizinger 81da120c17 fix(phoenix-channel): report connection hiccups to upper layer (#8203) ...

The WebSocket connection to the portal from within the Clients, Gateways
and Relays may be temporarily interrupted by IO errors. In such cases we
simply reconnect to it. This isn't as much of a problem for Clients and
Gateways. For Relays however, a disconnect can be disruptive for
customers because the portal will send `relays_presence` events to all
Clients and Gateways. Any relayed connection will therefore be
interrupted. See #8177.

Relays run on our own infrastructure and we want to be notified if their
connection flaps.

In order to differentiate between these scenarios, we remove the logging
from within `phoenix-channel` and report these connection hiccups one
layer up. This allows Clients and Gateways to log them on DEBUG whereas
the Relay can log them on WARN.

Related: #8177 
Related: #7004

2025-02-20 00:54:43 +00:00

..

server

feat(relay): add SOFTWARE attribute (#8076)

2025-02-11 03:34:38 +00:00

auth.rs

refactor(relay): improve error messages on failed requests (#7405)

2024-11-28 22:12:27 +00:00

lib.rs

feat(relay): add SOFTWARE attribute (#8076)

2025-02-11 03:34:38 +00:00

main.rs

fix(phoenix-channel): report connection hiccups to upper layer (#8203)

2025-02-20 00:54:43 +00:00

net_ext.rs

fix(relay): correctly separate channel state for different peers (#3472)

2024-02-01 01:53:54 +00:00

proptest.rs

test(connlib): introduce routing table to tunnel_test (#5786)

2024-07-09 01:48:54 +00:00

server.rs

feat(relay): add SOFTWARE attribute (#8076)

2025-02-11 03:34:38 +00:00

sleep.rs

refactor(relay): favor Instant over SystemTime (#4468)

2024-04-08 23:37:19 +00:00

sockets.rs

fix(relay): buffer packets in case IO is busy (#7536)

2024-12-18 17:01:24 +00:00