-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Deleting a FIFO message with an expired receipt handle should raise an error #12442
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
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 1h 13m 6s ⏱️ - 39m 58s Results for commit bf73c2c. ± Comparison against base commit 1005e96. This pull request removes 1262 and adds 4 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
gregfurman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have left some comments mostly related to snapshot testing. Feel free to ignore my nits 🙂
thrau
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! thanks for fixing this :-)
just two minor nits, nothing blocking
0ce4b09 to
bf73c2c
Compare
Motivation
As per title. FIFO messages should not be deleted if the provided receipt handle has expired, tests against AWS failed consistently. Reversely, the same test succeeded consistently on standard queues, making fifo specific code necessary.
fixes #12278
Changes
_pre_delete_checkshook when removing messages, because this behaviour is fifo specific, and a complete remodel of the delete method to separate standard and fifo behaviour to make this cleaner was out of scope for this PR.