-
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
🐛 Bug/autoscaling datetime failure #3976
🐛 Bug/autoscaling datetime failure #3976
Conversation
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.
thanks a lot!
Codecov Report
@@ Coverage Diff @@
## master #3976 +/- ##
=========================================
- Coverage 84.5% 79.7% -4.9%
=========================================
Files 943 625 -318
Lines 40665 26408 -14257
Branches 848 447 -401
=========================================
- Hits 34383 21053 -13330
+ Misses 6072 5223 -849
+ Partials 210 132 -78
Flags with carried forward coverage won't be shown. Click here to find out more.
|
30bd84f
to
b2fdf73
Compare
services/autoscaling/src/simcore_service_autoscaling/utils/utils_docker.py
Show resolved
Hide resolved
Code Climate has analyzed commit 6eee91e and detected 0 issues on this pull request. View more on Code Climate. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
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.
thanks for fixing this one. pretty nasty. still I wonder why this happened now and not before
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.
thanks for fixing this one. pretty nasty. still I wonder why this happened now and not before
What do these changes do?
Fixes unhandled exception in the sort predicate when autoscaling services is sorting tasks. This issue was found in production AWS logs
Once merged, i will prepare a hotfix to production ASAP
Related issue/s
How to test