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

notifyOnTransient also ignore disconnection events? #2369

Open
marcus-pousette opened this issue Jan 21, 2024 · 0 comments
Open

notifyOnTransient also ignore disconnection events? #2369

marcus-pousette opened this issue Jan 21, 2024 · 0 comments
Labels
need/triage Needs initial labeling and prioritization

Comments

@marcus-pousette
Copy link
Contributor

marcus-pousette commented Jan 21, 2024

  • Version:
    1.1.0

  • Subsystem:
    registrar

Severity:

Medium/low

Description:

It seems like onDisconnect events are still emitted from transient connections shutting down even if notifyOnTransient is false.

I am receiving onDisconnect events when failing to establish a WebRTC connection

Steps to reproduce the error:

The seems to be intended behaviour (judging by the code).

topology.onDisconnect?.(remotePeer)

Is it possible to fetch the closing connection here and skip if transient and notifyOnTransient is false ?

Feels more intuitive that connect and disconnect events are handled in the same way.

@marcus-pousette marcus-pousette added the need/triage Needs initial labeling and prioritization label Jan 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant