-
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
♻️ Update PROJECTS_INACTIVITY_INTERVAL
env var format
#6797
base: master
Are you sure you want to change the base?
♻️ Update PROJECTS_INACTIVITY_INTERVAL
env var format
#6797
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6797 +/- ##
==========================================
- Coverage 85.92% 85.53% -0.39%
==========================================
Files 1550 619 -931
Lines 61749 30919 -30830
Branches 2164 318 -1846
==========================================
- Hits 53058 26447 -26611
+ Misses 8362 4412 -3950
+ Partials 329 60 -269
Continue to review full report in Codecov by Sentry.
|
PROJECTS_INACTIVITY_INTERVAL
env var format
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.
Thx. Careful with the osparc-config MR!!! This is a breaking change so you need to create different branches for those deploys where these variables cannot be applied right away until this code is released there
Please, read the MR's description.
|
Quality Gate passedIssues Measures |
What do these changes do?
Adapt the
PROJECTS_INACTIVITY_INTERVAL
env var to be used with an interval inISO 8601
format.In Pydantic v1 numbers were considered seconds by default, but in Pydantic v2 they generate a
WARNING
.Related issue/s
How to test
Dev-ops checklist