Skip to content

Conversation

mstoykov
Copy link
Contributor

What?

Why?

Checklist

  • I have performed a self-review of my code.
  • I have added tests for my changes.
  • I have run linter locally (make lint) and all checks pass.
  • I have run tests locally (make tests) and all tests pass.
  • I have commented on my code, particularly in hard-to-understand areas.

Related PR(s)/Issue(s)

@mstoykov mstoykov requested a review from a team as a code owner November 29, 2024 15:51
@mstoykov mstoykov requested review from olegbespalov and oleiade and removed request for a team November 29, 2024 15:51
Copy link
Contributor

@oleiade oleiade left a comment

Choose a reason for hiding this comment

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

Nice catch! 🚀

Copy link
Contributor

@olegbespalov olegbespalov left a comment

Choose a reason for hiding this comment

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

Waiting for actual fix, or closing the PR

Copy link
Contributor

@ankur22 ankur22 left a comment

Choose a reason for hiding this comment

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

LGTM 🚀

@mstoykov
Copy link
Contributor Author

This was a PR to illustrate that there is no way for the current PushIfNotDOne to not race with the context done and channel close.

The thing is that in the current code there is no place where the channel gets closed before every VU has returned so nothing should be using this - which is signaled with the context close.

The "real" fix for this will be to not use close the channel, but that is already used in some places, so it is way more involved.

Again in practice this should never happen - if it does it is a bug in the other code.

@mstoykov mstoykov closed this Dec 16, 2024
@mstoykov mstoykov deleted the pushIfNotDoneRace branch January 22, 2025 16:40
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.

4 participants