-
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
🐛♻️ Is638/fixes docker-compose operations bursts and create containers call in dy-sidecar #3187
🐛♻️ Is638/fixes docker-compose operations bursts and create containers call in dy-sidecar #3187
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3187 +/- ##
========================================
+ Coverage 80.9% 82.0% +1.1%
========================================
Files 686 736 +50
Lines 30152 31528 +1376
Branches 3940 4079 +139
========================================
+ Hits 24400 25864 +1464
+ Misses 4920 4829 -91
- Partials 832 835 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
|
978b125
to
d2fd484
Compare
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.
I'm fine if this will improve the situation for now.
Please think about my note below.
services/dynamic-sidecar/src/simcore_service_dynamic_sidecar/core/docker_compose_utils.py
Show resolved
Hide resolved
31613d2
to
279a145
Compare
ensure_run_in_sequence_context_is_empty was wrong since ITISFoundation@c215bf9
a5fba4d
to
0b1ba85
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
What do these changes do?
POST /containers
we eliminateddocker-compose rm
beforeup
. The following was observedup
rm
followed byup
up
(not sure why? I guess it since sdc is taking too long ...)rm
(which probably removes those being created) then restart from stratchup
rm
is a close operations and typically takes a bit longerpytest_simcore/simcore_service_library_fixtures.py
for tests with co-routines decorated with@run_sequentially_in_context
docker_compose_utils
andsettings
docker_compose_utils
API run one at a time@run_sequentially_in_context
E.g. avoids running in parallel docker-compose up and config on the same service. I.e. implementsRelated issue/s
How to test
pytest services/dynamic-sidecar/tests/unit/test_core_docker_compose_utils.py::test_burst_calls_to_docker_compose_config
Checklist