Fix community manage requests #1287
Merged
Conversation
This file contains hidden or 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
* Fixes a bug where the expiration logic for "community manage record" requests failed because they were running in a Celery task without request context. * User is deduced from the request receiver now.
* Instead of working with specific records, the scripts accepts a community, for which then it creates requests (if not already created) for users with legacy records in the community. * For records that are owned by community members, the flags are automatically removed (since there is no sense to create requests). * Also persists the results in a JSON file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
fix(legacy): stop using
current_useroutisde request contextrequests failed because they were running in a Celery task without
request context.
fix(scripts): adjust community manage requests script
community, for which then it creates requests (if not already created)
for users with legacy records in the community.
automatically removed (since there is no sense to create requests).