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

Depending on the event ordering, the completion might be sent twice for awakeables #1972

Closed
slinkydeveloper opened this issue Sep 18, 2024 · 0 comments · Fixed by #1973
Closed
Assignees
Labels
bug Something isn't working partition-processor

Comments

@slinkydeveloper
Copy link
Contributor

This can happen when the invocation is in invoked state, and the user sends twice the completion.

@slinkydeveloper slinkydeveloper added bug Something isn't working partition-processor labels Sep 18, 2024
@slinkydeveloper slinkydeveloper self-assigned this Sep 18, 2024
slinkydeveloper added a commit to slinkydeveloper/restate that referenced this issue Sep 18, 2024
slinkydeveloper added a commit to slinkydeveloper/restate that referenced this issue Sep 18, 2024
I shuffled around the code of store_completion (there was an indirection not needed)
slinkydeveloper added a commit to slinkydeveloper/restate that referenced this issue Sep 18, 2024
I shuffled around the code of store_completion (there was an indirection not needed)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working partition-processor
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant