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

Don't use Dispatcher for suspendReadableAndRead and TLS initialization on Node.js #3348

Merged
merged 4 commits into from
Dec 23, 2023

Conversation

armanbilge
Copy link
Member

Fixes errors reported in #3336 and #3338.

By introducing some custom concurrent data structures, we can completely avoid Dispatcher, the indirection and performance cost, and the dispatcher already shutdown errors that have been plaguing us.

@armanbilge armanbilge changed the title Don't use Dispatcher for suspendReadableAndRead and TLS init on Node.js Don't use Dispatcher for suspendReadableAndRead and TLS initialization on Node.js Nov 26, 2023
@armanbilge
Copy link
Member Author

@mikeshepherd @gvolpe Ok, here's another attempt 😅 I published 3.9.3-27-7874843-SNAPSHOT.

@mikeshepherd
Copy link

@mikeshepherd @gvolpe Ok, here's another attempt 😅 I published 3.9.3-27-7874843-SNAPSHOT.

Thanks @armanbilge, we'll give this a try and get back to you. But it looks good to me reading it 👍

private[this] var readableCounter = 0
private[this] var readable = false
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could have sworn this didn't work initially 🤔 but seems fine now.

@mpilquist mpilquist merged commit cc913dd into typelevel:main Dec 23, 2023
15 checks passed
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