-
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
✨Saving volume stats inside the shared store volume #4267
✨Saving volume stats inside the shared store volume #4267
Conversation
…status-in-state-volume
Codecov Report
@@ Coverage Diff @@
## master #4267 +/- ##
========================================
+ Coverage 79.8% 86.9% +7.0%
========================================
Files 938 818 -120
Lines 39877 37622 -2255
Branches 965 456 -509
========================================
+ Hits 31860 32703 +843
+ Misses 7796 4810 -2986
+ Partials 221 109 -112
Flags with carried forward coverage won't be shown. Click here to find out more.
|
…status-in-state-volume
…status-in-state-volume
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! some comments
services/dynamic-sidecar/src/simcore_service_dynamic_sidecar/models/shared_store.py
Outdated
Show resolved
Hide resolved
Code Climate has analyzed commit 645369f and detected 0 issues on this pull request. View more on Code Climate. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
What do these changes do?
It is necessary to store the state of the volumes somewhere. Since the sidecar has exclusive access to the shared store volume, it will not have any permission or ownership issues when trying to write the states there.
Contents of the SharedStore (snapshot while outputs and state are being saved):
Bonus: minor
models-library
cleanupRelated issue/s
state volume
inside the dy-sidecar osparc-issues#962How to test
DevOps Checklist