-
Notifications
You must be signed in to change notification settings - Fork 44
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
docker, core, editoast: add mode single-worker for all infra #9166
Conversation
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## dev #9166 +/- ##
============================================
- Coverage 39.15% 39.12% -0.03%
Complexity 2245 2245
============================================
Files 1290 1289 -1
Lines 97316 97269 -47
Branches 3280 3280
============================================
- Hits 38100 38061 -39
+ Misses 57277 57269 -8
Partials 1939 1939
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
I did not reviewed it yet but I have a small question. This features seems useful for debuging purpose (see #8599). I believe we're talking of core? If so I don't see why we should handle this feature using docker compose. |
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.
LGTM for core with one minor comment.
Not tested yet, I'll probably come back to it later.
Compose file here is more of a helper/documentation to plug all together, as |
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.
LGTM ! Didn't tested it yet. I'm waiting for your rebase to do so and then I'll approve the PR👍🏽
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.
Looks good although, as discussed, it will make us not really use the full complexity of osrdyne
on local, might not help to detect possible bugs in it. That said, all for making the developer experience smoother.
osrdyne
that depends on a Docker daemon that I don't have (using podman, daemon less).
c23a2d7
to
e7b8258
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.
Lgtm, not tested
I do not have anything to say about the PR per se, but I'm curious on why we would want to make this change the default behavior ? What's the rationale behind this ? |
@ElysaSrc there is a bit more info in the related issue #8599 but you may already have had a look and I'm not sure about your question. The main purpose is to ease debug of core (mainly without having to spawn a new core and track the id of the infra which can be painful, like for integration tests). Then the rationale of changing the noopdyne compose file is to consider that using dyne as noop is (almost?) only for that use case, so we might as well add the "changes" to editoast and core conf on the way to ease/document that case.
Hope that it answers your question, and maybe it's worth adding a bit of doc and a bit of description (will try to after more test, but any suggestion is welcome). |
Thanks for the detailed response ! |
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.
Tested for core debug purposes. Works as intended. Good job :)
302e4ef
to
56cee29
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.
Great work!
Should we also rename noopdyne
as single-worker
? It wasn't a great name, and I mostly named it that way because it wasn't a single-worker mode ^^'
56cee29
to
d60f674
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.
LGTM (README change)
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.
Gj again :) The scale option is a huge plus :)
Also cleanup unavailable envvar OSRD_BACKEND_URL Signed-off-by: Pierre-Etienne Bougué <bougue.pe@proton.me>
Signed-off-by: Pierre-Etienne Bougué <bougue.pe@proton.me>
d60f674
to
14eb514
Compare
target ~1 min 30 s for each deps and 30 s for editoast and front Signed-off-by: Pierre-Etienne Bougué <bougue.pe@proton.me>
d7c749a
to
7f4c167
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.
front/
changes LGTM (not tested)
In general huge +1 on the idea, although I haven't looked at all at the impl :P
Also:
OSRD_BACKEND_URL
🔍 please review by commit + one more developper should test it (integration + e2e + regular use)
This work may probably be improved (doc, script, etc.) any suggestion is welcome.
Fix: #8599