-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
director.py: restore READTHEDOCS_VERSION_[TYPE|NAME] #9052
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
Conversation
These env vars were accidentally removed in readthedocs#9002. This commit naively restores the 2 missing env variables in the new get_rtd_env_vars() location. Signed-off-by: Jeff Squyres <[email protected]>
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.
Thanks, looks like we have a test, but it's marked as skip
readthedocs.org/readthedocs/projects/tests/test_build_tasks.py
Lines 186 to 189 in dd73d84
@mock.patch("readthedocs.doc_builder.director.load_yaml_config") | |
@pytest.mark.skip() | |
# NOTE: find a way to test we are passing all the environment variables to all the commands | |
def test_get_env_vars_default(self, load_yaml_config): |
I see that some of the CI failed. It looks like this may be something I just ran across in an entirely different context the other day:
The latest release of Jinja2 -- v3.1.0, released 24 May 2022 -- made a backwards-incompatible change. From https://jinja.palletsprojects.com/en/3.1.x/changes/#version-3-1-0:
If your CI environment restricts itself to the previous release of Jinja 2 (v3.0.3), it should work fine. That being said, I see several places in the code base where you already have |
@jsquyres the tests from tests-embedapi aren't related to this change and are failing on main, we can fix that later, don't worry about it. |
Great! Do you think that this is a sufficient fix for #9051? (I admit that I did a very little bit of grep'ing and git spelunking around the code base to come up with this fix) If so, is there a way to get this fix into production so that our RTD builds start working again? 😄 |
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 started digging in as well, and saw these were missing.
@stsewd Thank you! How long does it take for this change to get into production? |
@jsquyres we will try to deploy this change today |
These env vars were accidentally removed in #9002. This commit naively restores the 2 missing env variables in the new get_rtd_env_vars() location. Signed-off-by: Jeff Squyres <[email protected]>
These env vars were accidentally removed in #9002. This commit naively restores the 2 missing env variables in the new get_rtd_env_vars() location. Signed-off-by: Jeff Squyres <[email protected]>
@jsquyres |
@ericholscher Looks good -- many thanks! |
These env vars were accidentally removed in #9002. This commit naively restores the 2 missing env variables in the new
get_rtd_env_vars()
location.Signed-off-by: Jeff Squyres [email protected]
This commit is a potential naïve fix for #9051. I have no good way to test this, but it does restore the 2 env vars that were removed in #9002.