fix(idempotency): idempotent_function should support standalone falsy values#1669
Merged
leandrodamascena merged 2 commits intoOct 28, 2022
Conversation
2 tasks
Codecov ReportBase: 99.35% // Head: 99.35% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## develop #1669 +/- ##
========================================
Coverage 99.35% 99.35%
========================================
Files 128 128
Lines 5908 5908
Branches 373 373
========================================
Hits 5870 5870
Misses 18 18
Partials 20 20
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
leandrodamascena
approved these changes
Oct 28, 2022
Contributor
leandrodamascena
left a comment
There was a problem hiding this comment.
Nothing to change! LGTM!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue number: #1663
Summary
When using
idempotent_functionfor any synchronous Python function (different from Lambda Handler), customers set which keyword argument we should use to hash data as an idempotency key.We raise
RuntimeErrorfor cases where the keyword argument wasn't used correctly to prevent hashing the incorrect data. For example, function was called without the keyword argument (function(), instead offunction(data=data)).However, the current logic incorrectly checks the value available in the keyword argument, rather than the keyword argument was used. The following code leads to a
RuntimeErrorwhen we should be serializingNone->nulljust fine.Changes
This PR corrects the logic and only raises
RuntimeErrorif the keyword argument specified for hashing isn't in the list of keyword arguments available at the function call.User experience
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.