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

ensures sourceMode is obtained with happens-before relationships #3518

Merged
merged 6 commits into from
Jul 4, 2023

Conversation

OlegDokuka
Copy link
Contributor

When the concurrent request call happens with an initial subscription to the initial source, the obtained sourceMode may indicate unset instead of none due to the nature of the given primitive

Signed-off-by: OlegDokuka odokuka@vmware.com

@OlegDokuka OlegDokuka added the type/bug A general bug label Jun 26, 2023
@OlegDokuka OlegDokuka added this to the 3.4.31 milestone Jun 26, 2023
@OlegDokuka OlegDokuka requested a review from a team as a code owner June 26, 2023 18:21
Base automatically changed from 3.4.x-3487-2 to 3.4.x July 4, 2023 10:52
Signed-off-by: OlegDokuka <odokuka@vmware.com>
Late subscribe may observe zero events when multiple inners subscribes to FluxRefCount simultaneously so the one which does not invoke connect method subscribes to the FluxPublish too late (e.g. the one which call connect subscribe faster and invoke connect method earlier)
```
 subscribe 1           subscriber 2
     |                      |
   count + 1 (1)            |
     |                 count + 1 (2)
     |                      |
     |                  subscribe
     |                      |
     |                   connect
     |                  onComplete
  subscribe
  (hanging)
```

to solve the problem subscribe should happen before count is incremented so we have strong ordering
Signed-off-by: OlegDokuka <odokuka@vmware.com>
Signed-off-by: OlegDokuka <odokuka@vmware.com>
Signed-off-by: OlegDokuka <odokuka@vmware.com>
Signed-off-by: OlegDokuka <odokuka@vmware.com>
Signed-off-by: OlegDokuka <odokuka@vmware.com>
@OlegDokuka OlegDokuka merged commit 19ba2f5 into 3.4.x Jul 4, 2023
7 checks passed
@reactorbot
Copy link

@OlegDokuka this PR seems to have been merged on a maintenance branch, please ensure the change is merge-forwarded to intermediate maintenance branches and up to main 🙇

OlegDokuka added a commit that referenced this pull request Jul 5, 2023
Signed-off-by: Oleh Dokuka <odokuka@vmware.com>
OlegDokuka added a commit that referenced this pull request Jul 5, 2023
Signed-off-by: Oleh Dokuka <odokuka@vmware.com>
@chemicL chemicL deleted the 3.4.x-3487-2-publish branch April 11, 2024 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug A general bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants