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

chore: add TRANSCRIPT_LANG_CACHE_TIMEOUT setting variable in common setting envs #36296

Merged
merged 3 commits into from
Feb 25, 2025

Conversation

AfaqShuaib09
Copy link
Contributor

This PR adds the TRANSCRIPT_LANG_CACHE_TIMEOUT settings variable to the common setting environments of LMS and CMS so that it won't cause the requirements upgrade to fail. Because App settings carry over to main project

See Current Reqs PR: https://github.com/openedx/edx-platform/actions/runs/13512360677/job/37754856463?pr=36294

Description

Describe what this pull request changes, and why. Include implications for people using this change.
Design decisions and their rationales should be documented in the repo (docstring / ADR), per
OEP-19, and can be
linked here.

Useful information to include:

  • Which edX user roles will this change impact? Common user roles are "Learner", "Course Author",
    "Developer", and "Operator".
  • Include screenshots for changes to the UI (ideally, both "before" and "after" screenshots, if applicable).
  • Provide links to the description of corresponding configuration changes. Remember to correctly annotate these
    changes.

Supporting information

Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.
Be sure to check they are publicly readable, or if not, repeat the information here.

Testing instructions

Please provide detailed step-by-step instructions for testing this change.

Deadline

"None" if there's no rush, or provide a specific date or event (and reason) if there is one.

Other information

Include anything else that will help reviewers and consumers understand the change.

  • Does this change depend on other changes elsewhere?
  • Any special concerns or limitations? For example: deprecations, migrations, security, or accessibility.
  • If your database migration can't be rolled back easily.

@AfaqShuaib09 AfaqShuaib09 force-pushed the afaq/prod-4305 branch 2 times, most recently from 1ec6497 to 6a2e9c0 Compare February 25, 2025 13:43
@UsamaSadiq UsamaSadiq merged commit b83c849 into openedx:master Feb 25, 2025
49 checks passed
@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

1 similar comment
@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

jciasenza pushed a commit to jciasenza/edx-platform that referenced this pull request Feb 25, 2025
…etting envs (openedx#36296)

* chore: add TRANSCRIPT_LANG_CACHE_TIMEOUT setting variable in common setting envs
* chore: bump edx-val version

fix: enzyme testing replaced by react tester

fix: enzyme testing replaced by react tester

fix: enzyme testing replaced by react tester

fix: enzyme testing replaced by react tester

fix: enzyme testing replaced by react tester
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants