Thomas Eizinger ae872980ae refactor(gui-client): scope telemetry sessions to GUI client (#9179) ...

For our telemetry sessions with Sentry, we need to know which
environment we are running in, i.e. staging, production or on-prem. The
GUI client's tunnel service doesn't have a concept of an environment
until a GUI connects and sends the `StartTelemetry` message. Therefore,
we should scope a telemetry session to a GUI being connected over IPC.

Any errors around setting up / tearing down the background service are a
catch-22. Until a GUI connects, we can't initialise the telemetry
connection but if we fail to set up the background service, no GUI can
ever connect. Hence, the current setup and tear down of the `Telemetry`
module around the `ipc_listen` calls can safely be removed as they are
effectively no-ops anyway.

2025-05-20 23:18:18 +00:00

..

src

refactor(gui-client): scope telemetry sessions to GUI client (#9179)

2025-05-20 23:18:18 +00:00

tests

refactor(rust): move dns-control to bin-shared (#9023)

2025-05-06 01:29:09 +00:00

Cargo.toml

chore(rust): fix features in bin-shared (#9094)

2025-05-13 03:12:59 +00:00