Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

connlib: surface interrupted portal connection to user #5557

Open
thomaseizinger opened this issue Jun 26, 2024 · 0 comments
Open

connlib: surface interrupted portal connection to user #5557

thomaseizinger opened this issue Jun 26, 2024 · 0 comments
Labels
area/connlib Firezone's core connectivity library kind/UX/user Issues related to end-user UX (Clients)

Comments

@thomaseizinger
Copy link
Member

Currently, phoenix-channel will reconnect in the background if the portal connection fails and there is no way for the client application to known that we aren't connected to the portal. This results in weird behaviour where everything appears to hang.

It also does! Without a portal connection, messages like connection intents are just buffered and never sent so we can't make new connections.

Connlib should emit some kind of event to the application to inform it that the portal connection is interrupted so that something isn't working.

@thomaseizinger thomaseizinger added area/connlib Firezone's core connectivity library kind/UX/admin Issues related to admin UX (portal, Gateways) labels Jun 26, 2024
@thomaseizinger thomaseizinger changed the title connlib: surface interrupted connection portal to user connlib: surface interrupted portal connection to user Jun 26, 2024
@jamilbk jamilbk added kind/UX/user Issues related to end-user UX (Clients) and removed kind/UX/admin Issues related to admin UX (portal, Gateways) labels Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connlib Firezone's core connectivity library kind/UX/user Issues related to end-user UX (Clients)
Projects
None yet
Development

No branches or pull requests

2 participants