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

Fix bug in IdempotencyId::combine that prevented correct storing of idempotency key in idempotency table #1723

Merged

Conversation

slinkydeveloper
Copy link
Contributor

No description provided.

@slinkydeveloper
Copy link
Contributor Author

slinkydeveloper commented Jul 18, 2024

Trying to evaluate the impact of this bug:

  • This came up as bug while adding a test to the e2e to get output/attach using idempotency key. Will post this test soon.

@slinkydeveloper
Copy link
Contributor Author

I tested with the linked e2e PR and it works fine.

Copy link
Contributor

@tillrohrmann tillrohrmann left a comment

Choose a reason for hiding this comment

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

Thanks a lot for discovering this issue and fixing it @slinkydeveloper. I had a question about the side effects of this change for our users.

crates/types/src/identifiers.rs Show resolved Hide resolved
…dempotency table.

BREAKING CHANGE: This commit changes the way idempotent invocations are queried. When upgrading from Restate 1.0 to 1.1 this commit will generate duplicated requests for idempotent invocations created ONLY during the 1.0 lifecycle. For new invocations, no duplicated requests will be generated.
@slinkydeveloper slinkydeveloper force-pushed the fix-bug-idempotency-key branch from 1d2577f to 6884454 Compare July 22, 2024 12:43
@slinkydeveloper slinkydeveloper merged commit bf9f0d1 into restatedev:main Jul 22, 2024
3 checks passed
@slinkydeveloper slinkydeveloper deleted the fix-bug-idempotency-key branch July 22, 2024 12:44
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