-
Notifications
You must be signed in to change notification settings - Fork 420
fix(idempotency): validate before saving to cache #3822
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(idempotency): validate before saving to cache #3822
Conversation
Signed-off-by: heitorlessa <[email protected]>
Signed-off-by: heitorlessa <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## develop #3822 +/- ##
===========================================
+ Coverage 96.38% 96.42% +0.04%
===========================================
Files 214 214
Lines 10030 10093 +63
Branches 1846 1866 +20
===========================================
+ Hits 9667 9732 +65
+ Misses 259 258 -1
+ Partials 104 103 -1 ☔ View full report in Codecov by Sentry. |
@roger-zhangg and @leandrodamascena unrelated to this PR, Redis race condition tests were failing due to serialization in multi-processing -- only on M1, but not on CI. Diving into this I found that the issue is due to the standard library To fix it, I've added
![]() |
Signed-off-by: heitorlessa <[email protected]>
|
Thanks @heitorlessa , for the finding and fix. I wasn't aware of this M1 behavior difference before |
Issue number: #3821
Summary
As recently fixed in TS, we should be validating (payload tampering) before saving to cache.
Changes
Unrelated changes
multiprocess
dev dependency to usedill
overpickle
for multi-process serializationUser 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.