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

Investigate potential catch-22 in revision auto pulling mechanism #63

Open
davidlatwe opened this issue Jan 16, 2022 · 0 comments
Open

Comments

@davidlatwe
Copy link
Owner

When calling rezup use {name}, the command checks remote container for new revision and pulls one if there is. This design might have a potential problem is that when the command fails to create the new revision, it will keep pulling next time and fails again, deadlock.

Improvement

  • Better to define a max pulling retry time in single command call, and fallback to old revision if failed.
  • When fallback to old revision, prompt warning every time it's being accessed by CLI.
  • Recipe should have entries to indicate who authored it, e.g. author, email, and these info could be used in warning message above.
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

No branches or pull requests

1 participant