Skip to content

Better handling of timeout errors with deployment of decomposed productions #690

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

Closed
isc-pbarton opened this issue Jan 17, 2025 · 0 comments · Fixed by #695
Closed

Better handling of timeout errors with deployment of decomposed productions #690

isc-pbarton opened this issue Jan 17, 2025 · 0 comments · Fixed by #695
Assignees

Comments

@isc-pbarton
Copy link
Collaborator

The following can occur in a large decomposed production with a lot of active development:

  • I try to get the latest and greatest code by using the Pull option in the Source Control menu. It times out, eventually just giving me an alert that says "null".
  • I pull changes through the terminal by running do ##class(SourceControl.Git.API).Pull(). It updates the local repository, but deployment fails because it claims there is an in progress deployment.
  • I go into the deployment history in the Management Portal and clear the failed deployment.
  • I deploy again by running do ##class(SourceControl.Git.API).ImportAll(). It takes a minute but finally succeeds.
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

Successfully merging a pull request may close this issue.

1 participant