Skip to content
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

[Attempt 2] refactor: Clean up lms/envs/production.py cruft #36131

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

kdmccormick
Copy link
Member

@kdmccormick kdmccormick commented Jan 17, 2025

Supporting information

Re-introdues #36115, which was reverted by #36129 due to a typo.

The typo fix is included as a separate commit.

Other information

There is an ongoing discussion of how to better safeguard against bugs like the one that led to the revert: #36129 (comment)

Merge considerations

I will wait until Tuesday Jan 21 to merge this.

kdmccormick and others added 2 commits January 17, 2025 14:36
This reintroduces commit 1593923,
which was reverted due to a typo.

The typo is fixed in the commit immediately following this one.

Co-Authored-By: Feanil Patel <[email protected]>
@kdmccormick kdmccormick force-pushed the kdmccormick/lms-envs-production-cleanup-2 branch from b70d54a to c0cb126 Compare January 17, 2025 19:40
@kdmccormick kdmccormick requested review from feanil and robrap January 17, 2025 19:42
@robrap
Copy link
Contributor

robrap commented Jan 17, 2025

Note: Test plan being discussed in Slack, with request not to merge without a plan.

Copy link
Contributor

@feanil feanil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took a look through again with a finer view of the additions to make sure there weren't any typos and I was able to bring up the LMS and CMS from this version of the settings file and the minimal.yaml locally so I think it's good to go but I'll wait till we add the unit test that we were discussing in slack before providing the final approval.

@kdmccormick kdmccormick added the create-sandbox open-craft-grove should create a sandbox environment from this PR label Jan 23, 2025
@kdmccormick
Copy link
Member Author

(rephrasing from Slack) I don't see any way to unit test this PR, since unit tests use lms/envs/test.py, which is based directly on lms/envs/common.py, not lms/envs/production.py. I think we will have to rely on code review, manual testing, and the PR sandbox for verification.

@open-craft-grove
Copy link

Sandbox deployment failed 💥
Please check the settings and requirements.
Retry deployment by pushing a new commit or updating the requirements/settings in the pull request's description.
📜 Failure Logs
ℹ️ Grove Config, Tutor Config, Tutor Requirements

@0x29a 0x29a added create-sandbox open-craft-grove should create a sandbox environment from this PR and removed create-sandbox open-craft-grove should create a sandbox environment from this PR labels Jan 24, 2025
@open-craft-grove
Copy link

Sandbox deployment successful 🚀
🎓 LMS
📝 Studio
ℹ️ Grove Config, Tutor Config, Tutor Requirements

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
create-sandbox open-craft-grove should create a sandbox environment from this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants