Skip to content

Fix channel BufferOverflow behavior #3331

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

Closed
wants to merge 1 commit into from
Closed

Fix channel BufferOverflow behavior #3331

wants to merge 1 commit into from

Conversation

artemkaxboy
Copy link

Fixes unexpected behavior #3330

@qwwdfsad qwwdfsad self-requested a review June 22, 2022 10:59
Copy link
Collaborator

@qwwdfsad qwwdfsad left a comment

Choose a reason for hiding this comment

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

Sorry, but I can neither accept this PR nor guide you through the whole contribution process here:

  • It will be postponed to 1.7.0, so we cannot merge it and have to keep it unmerged for a while, while keeping it in sync
  • It requires a lot of analysis to do (e.g. it doesn't work for capacity = 0 for now and probably there are other places that have to be thoughtfully checked)
  • More importantly, we are in the process of rewriting the core of our channels Introduce fast and scalable channels #3103. It's all in progress and it will be really tough to keep this work in sync with develop

Sorry for the inconvenience and thanks for the effort

@qwwdfsad qwwdfsad closed this Jun 22, 2022
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.

2 participants