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

Modify retrying of sync tasks to use resumesync command #9170

Closed

Conversation

bjester
Copy link
Member

@bjester bjester commented Mar 9, 2022

Summary

References

Addresses #7270

Reviewer guidance


Testing checklist

  • Contributor has fully tested the PR manually
  • If there are any front-end changes, before/after screenshots are included
  • Critical user journeys are covered by Gherkin stories
  • Critical and brittle code paths are covered by unit tests

PR process

  • PR has the correct target branch and milestone
  • PR has 'needs review' or 'work-in-progress' label
  • If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
  • If this is an important user-facing change, PR or related issue has a 'changelog' label
  • If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

  • Automated test coverage is satisfactory
  • PR is fully functional
  • PR has been tested for accessibility regressions
  • External dependency files were updated if necessary (yarn and pip)
  • Documentation is updated
  • Contributor is in AUTHORS.md

@bjester bjester added this to the 0.15.2 milestone Mar 9, 2022
@bjester bjester added the work-in-progress Not ready for review label Mar 9, 2022
@@ -111,12 +109,7 @@
if (this.taskInfo.canCancel) {
return 'cancel';
} else if (this.taskInfo.canClear) {
// Import tasks can't be retried since we don't save the username/password
Copy link
Member Author

Choose a reason for hiding this comment

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

This comment was incorrect. The credentials are validated prior to the creation of the task, and once validated, a certificate is created which facilitates authentication thereafter

@bjester bjester self-assigned this Apr 25, 2022
@marcellamaki marcellamaki modified the milestones: Planned Patch: "Clear the decks", Planned Patch 3: TBD Apr 26, 2022
@bjester bjester closed this Jun 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
work-in-progress Not ready for review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

extremely large database size when sync attempts are made but don’t complete
2 participants