-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
feat: FC-0012 - add atlas pull behind a flag #33502
feat: FC-0012 - add atlas pull behind a flag #33502
Conversation
Thanks for the pull request, @shadinaif! Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
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.
@OmarIthawi , do we need all steps when pulling using Atlas? or we should keep only generate?
@shadinaif I'm not sure, but it's probably a good idea to keep backward compatibility of the workflow.
I've added a suggestion to do that, please let me know what do you think.
a337379
to
76550c2
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.
Looks great now. Thanks @shadinaif!
76550c2
to
9e7d444
Compare
9e7d444
to
addfd6e
Compare
addfd6e
to
e00d1c3
Compare
@shadinaif please add the keyword OEP-58 somewhere in the description so this pull request appears in GitHub search. |
1c33ed5
to
b6ce92b
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.
It looks good! @shadinaif I've added few notes regarding the segmented dummy
.
Please let me know if you have any questions.
b6ce92b
to
f32ecd4
Compare
9d67cb7
to
09cc6be
Compare
Hi @OmarIthawi , please check this out, I believe this is the best way to keep maximum compatibility without TODOs |
@shadinaif I've tested it locally and found this strange error: Error details
This error is intermittent and don't occur all the time. So, I'm proposing a change to this pull request which I've tested: Please check it out and let me know if the 79e6c71 commit looks good to you. Of course the other tests PR should be discarded. |
Makefile
Outdated
# Calling extract_translations in way compatibile with openedx-translations workflow which | ||
# ensures having only two translation files in conf/locale/en/LC_MESSAGES directory (django.po and djangojs.po) | ||
$(MAKE) IS_OPENEDX_TRANSLATIONS_WORKFLOW=yes extract_translations |
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.
usemanage.py lms compilemessages
instead.
1c7828b
to
7a2516b
Compare
7a2516b
to
9affcd5
Compare
9affcd5
to
7a2516b
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.
Looks great! Thanks @shadinaif!!
Do you think we need to add the git config --global --add safe.directory /edx/app/edxapp/edx-platform
in the Dockerfile to save some steps for the engineers using devstack?
cc: @feanil this is ready to go. |
7a2516b
to
0130d4a
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.
Generally looks good to me, What's the reason for the git safe.directory
setting? Is it because the user that's pulling the translations in docker different from the user that checked out the repo? Also I don't see any dockerfile related changes here, should there be some?
@shadinaif would you mind checking Feanil's questions? |
@shadinaif please add the |
(atlas pull) will be performed only if OPENEDX_ATLAS_PULL environment variable is set Refs: FC-0012 OEP-58
0130d4a
to
a6b180c
Compare
Hi @feanil. when using cc:/ @OmarIthawi |
I think this issue is fine within the context of this image. Sometimes the check valid, but it's used in another context that makes it redaudant. Thanks @shadinaif for the update. I think this pull request is ready to be merged. cc: @feanil. |
@feanil @brian-smith-tcril @mphilbrick211 would you mind merging this pull request? It's fairly backward compatible and I'd like to rebase the other pull request: |
@shadinaif 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
2U Release Notice: This PR has been deployed to the edX production environment. |
(atlas pull) will be performed only if
OPENEDX_ATLAS_PULL
environment variable is setTests:
OPENEDX_ATLAS_PULL=yes make pull_translations
is working fineOPENEDX_ATLAS_PULL=yes make pull_translations
is deleting old translations and pulling the latest translationsNote:
I had to run the following command in the container before the test
References
This pull request is part of the FC-0012 project which is sparked by the Translation Infrastructure update OEP-58.
Check the links above for full information about the overall project.
Internalization is being rearchitected in Open edX Python, XBlock, Micro-frontend, and other projects. There are a number of immediately visible changes:
.json
,.po
or.mo
files will be committed into the repos.make extract_translations
in all repositoriesBreaking Changes
One of the primary goals of the project is to avoid breaking changes. If you noticed any suspicious code, please raise your concern. But before that, please know the strategy we're following to avoid breaking changes
For XBlocks:
conf/locale
. Therefore, we are creating a link fromconf/locale
totranslations
so Atlas can find the path without disrupting the current way of having translations locally within the XBlocks