feat: update_voucher_names now can be run synchronously and can batch… #4137
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
julianajlk
approved these changes
Feb 26, 2024
ecommerce/extensions/voucher/management/commands/update_voucher_names.py
Outdated
Show resolved
Hide resolved
zubair-ce07
pushed a commit
that referenced
this pull request
Mar 1, 2024
#4137) * feat: update_voucher_names now can be run synchronously and can batch sleep * feat: update_voucher_name mgmt command can start at an offset * fix: split update logic from task for quality reasons
zubair-ce07
pushed a commit
that referenced
this pull request
Mar 1, 2024
#4137) * feat: update_voucher_names now can be run synchronously and can batch sleep * feat: update_voucher_name mgmt command can start at an offset * fix: split update logic from task for quality reasons
zubair-ce07
pushed a commit
that referenced
this pull request
Mar 1, 2024
#4137) * feat: update_voucher_names now can be run synchronously and can batch sleep * feat: update_voucher_name mgmt command can start at an offset * fix: split update logic from task for quality reasons
zubair-ce07
pushed a commit
that referenced
this pull request
Mar 1, 2024
#4137) * feat: update_voucher_names now can be run synchronously and can batch sleep * feat: update_voucher_name mgmt command can start at an offset * fix: split update logic from task for quality reasons
abdullahwaheed
pushed a commit
to abdullahwaheed/ecommerce
that referenced
this pull request
Mar 1, 2024
openedx#4137) * feat: update_voucher_names now can be run synchronously and can batch sleep * feat: update_voucher_name mgmt command can start at an offset * fix: split update logic from task for quality reasons
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.
… sleep
⛔️ MAIN BRANCH WARNING! 2U EMPLOYEES must make branches against the 2u/main BRANCH
⛔️ DEPRECATION WARNING
This repository is deprecated and in maintainence-only operation while we work on a replacement, please see this announcement for more information.
Although we have stopped integrating new contributions, we always appreciate security disclosures and patches sent to security@edx.org
Anyone internally merging to this repository is expected to release and monitor their changes; if you are not able to do this DO NOT MERGE, please coordinate with someone who can to ensure that the changes are released.
Required Testing
(^ We can remove that manual check once REV-2624 is done and the corresponding e2e test runs again)
Description
Describe what this pull request changes, and why these changes were made. How will these changes affect other people, installations of edx, etc.?
Please include links to any relevant ADRs, design artifacts, and decision documents. Make sure to document the rationale behind significant changes in the repo, per OEP-19, and can be
linked here.
Useful information to include:
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; how did YOU test this change?
Other information
Include anything else that will help reviewers and consumers understand the change.