-
Notifications
You must be signed in to change notification settings - Fork 27
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
♻️🔨 Unexpected mypy
upgrade revealed configuration and code failures
#6527
♻️🔨 Unexpected mypy
upgrade revealed configuration and code failures
#6527
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6527 +/- ##
=========================================
+ Coverage 84.5% 88.1% +3.5%
=========================================
Files 10 1548 +1538
Lines 214 63351 +63137
Branches 25 2059 +2034
=========================================
+ Hits 181 55845 +55664
- Misses 23 7188 +7165
- Partials 10 318 +308
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
👍
mypy
upgrade revealed configuration and code failures
|
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.
👍
What do these changes do?
The issue was caused by our CI pipeline not using a pinned version of
mypy
; instead, it was always fetching the latest version. This happened becauserequirements/ci.txt
did not includerequirements/tools.txt
, which specifies the version formypy
.As a result,
mypy
was updated between the CI passing for this PR and its merge into the master branch (commit da15add).The new version of
mypy
introduced additional type checks that uncovered issues in some parts of the code. Specifically, we had to make further changes to the section handling invoice attachments in emails to resolve these newly identified issues.Highlights
payments
service:-
services/payments/src/simcore_service_payments/services/notifier_email.py
-
services/payments/tests/unit/test_services_notifier_email.py
create_troubleshotting_log_message
does not raiseuv
run to run scriptRelated issue/s
How to test
Dev-ops checklist
NOne