Update Tahoe Nutmeg upgrade branch with changes from main
#1288
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…ificate-bugfix fix: empty signature added after every certificate saving (openedx#30912)
github-actions
bot
requested review from
OmarIthawi,
melvinsoft,
thraxil and
shadinaif
as code owners
It's still used by EdxRestAPIClient which is used for PS integrations
…ect-allowlist Add legacy /user_api/ prefix to MAIN_SITE_REDIRECT_ALLOWLIST
Add TahoeCourseAuthor role with Studio access
OmarIthawi
approved these changes
Oct 10, 2022
remove_site: fix CMS role IntegrityError + refactoring
don't report conflicts for releases before nutmeg
remove_site: also remove models with LearningContextKeyField
it's fast: 52.0nanosec
remove beeline logs from site config get_value
add beeline tracing for site config service usage
allow lint specific directory e.g. `tox -e pep8 openedx/`
``` django.db.utils.IntegrityError: (1451, 'Cannot delete or update a parent row: a foreign key constraint fails (`edxapp`.`user_tasks_usertaskstatus`, CONSTRAINT `user_tasks_usertaskstat_user_id_5ceae753d027017b_fk_auth_user_id` FOREIGN KEY (`user_id`) REFERENCES `auth_user` (`id`))') ```
SAMLConfiguration will be deleted with `site.delete()`
delete multiple sites at once; fixes for CMS-modules
…holder fix: Arabic translation placeholders in progress page
official py2neo is EOL and releases are gone from GitHub and PyPI
overhangio fork is too recent
use py2neo-history for access to older release gone from py2neo
Sync Dockerfile.tutor with latest server-vars.yml for Tahoe prod
…-support feat: Add Mandrill Subaccount support
Fix workflow configurations
…parameter-helper Add sanitize function for redirect parameter next
…rl-method Improve the sanitize_next_parameter method with handling new cases
…-in-iframe Hide site elements if render in iframe
…l elements after finish auth process
…-in-iframe Hide html elements if the parameter is set
…-in-iframe Set cookie value ror hideElements before redirect
…-in-iframe Hide html elements by parameter
… cookie on the backend side
…-in-iframe Add function to set hideElements cookie
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated pull request from branch Juniper
mainintoshadinaif/upgrade-to-nutmeg(Nutmeg upgrade).This is meant for making sure all of our Juniper changes gets merge into Nutmeg otherwise Juniper would stall. If tests passes merge this pull request.
If there are merge conflicts, it needs to be resolved manually as descriped in the following Runbook:
Fixing the conflicts via GitHub UI is usually a bad idea due to over simplified UX that makes the process less predictable.