-
Notifications
You must be signed in to change notification settings - Fork 434
fix(parser): apigw wss validation check_message_id; housekeeping #553
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Changes: - Add some more unit tests - Fix bug with `check_message_id` not looking in the RequestContext - Add more mypy coverage - Add pragma: no cover
@risenberg-cyberark - can you check the apigw fix I made for the validation. |
Codecov Report
@@ Coverage Diff @@
## develop #553 +/- ##
===========================================
+ Coverage 99.86% 99.95% +0.08%
===========================================
Files 113 113
Lines 4485 4477 -8
Branches 243 243
===========================================
- Hits 4479 4475 -4
+ Misses 3 0 -3
+ Partials 3 2 -1
Continue to review full report at Codecov.
|
btw, the code coverage is insane :) @michaelbrewer |
@heitorlessa i will leave out the other possible type checking and validation checks for idempotent for another time |
if i < max_handler_retries: | ||
continue | ||
else: | ||
if i == max_handler_retries: |
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.
nice one!!
* develop: feat(params): expose high level max_age, raise_on_transform_error (#567) fix(parser): apigw wss validation check_message_id; housekeeping (#553) chore(deps-dev): bump isort from 5.9.2 to 5.9.3 (#574) feat(data-classes): decode json_body if based64 encoded (#560) chore(deps-dev): bump mkdocs-material from 7.2.0 to 7.2.1 (#566)
Issue #, if available:
Description of changes:
Various housekeeping, code coverage and mypy tasks
Changes:
check_message_id
not validating against the RequestContextcheck_message_id
pragma: no cover
idempotency.py
and remove unusedmax_handler_retries
propertyChecklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.