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.

Sign up for GitHub

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

Jump to bottom

fix(am-dbg): disconnect events not visible in forwarded instances #195

Open
pancsta opened this issue Dec 15, 2024 · 0 comments
Open

fix(am-dbg): disconnect events not visible in forwarded instances #195

pancsta opened this issue Dec 15, 2024 · 0 comments
Labels
am-dbg tools/am-dbg bug Something isn't working good first issue Good for newcomers p:2 Medium priority

Comments

@pancsta
Copy link
Owner

pancsta commented Dec 15, 2024

With the new --fwd-data param from #191, chained instances have a persistent connection from a source instance. This breaks disconnect events, which now need to be pushed manually as a new msg type (for each indirect client disconn).
@pancsta pancsta added bug Something isn't working good first issue Good for newcomers p:2 Medium priority am-dbg tools/am-dbg labels Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
am-dbg tools/am-dbg bug Something isn't working good first issue Good for newcomers p:2 Medium priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pancsta