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

fix: update muxer behavior #1289

Merged
merged 2 commits into from
Jul 14, 2022
Merged

fix: update muxer behavior #1289

merged 2 commits into from
Jul 14, 2022

Conversation

wemeetagain
Copy link
Member

  • use direction in muxerFactory.createStreamMuxer
  • use muxer.close instead of muxer.streams.forEach(s => s.close())

- use `direction` in `muxerFactory.createStreamMuxer`
- use `muxer.close` instead of `muxer.streams.forEach(s => s.close())`
@mpetrunic
Copy link
Member

that ci seems to be consistent in failing ^^

@wemeetagain
Copy link
Member Author

aww seemingly unrelated test?

@wemeetagain
Copy link
Member Author

Ok it looks like the test is relying on an identify/push being sent after the connection is closed to update the autorelay? I'd think that a peer:disconnect would suffice to trigger a similar path? But maybe the event isn't being dispatched since its shutting down?

@achingbrain achingbrain changed the title feat: update muxer behavior fix: update muxer behavior Jul 14, 2022
@achingbrain achingbrain merged commit b1b9139 into master Jul 14, 2022
@achingbrain achingbrain deleted the feat/update-muxer-behavior branch July 14, 2022 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants