You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When connecting a resource via Github App and opening a PR, a preview deployment gets queued. If the PR is merged right after it is created (few seconds) the deployment stalls (I assume because there is nothing to pull from?), blocks the queue and the new docker container will not get cleaned up.
We are using the hosted interface at app.coolify.com, love this project so far! This is only a minor issue, not urgent for us at all!
All the best!
Minimal Reproduction (if possible, example repository)
Connect source as Github App, open Pull Request, wait only 2-3 seconds, close/merge the PR.
Exception or Error
No response
Version
v4.0.0-beta.297
The text was updated successfully, but these errors were encountered:
ity-alex
changed the title
[Bug]: Quickly opening and mergin a PR crashes deploys and leaves ghosts
[Bug]: Quickly opening and merging a PR crashes deploys and leaves ghosts
Jun 20, 2024
Maybe the deletion by webhook only removes the final container, while the cancelling of the deploy removes the currently building container. Possible solution would be to check for currently active deploys in the webhook handler?
Description
When connecting a resource via Github App and opening a PR, a preview deployment gets queued. If the PR is merged right after it is created (few seconds) the deployment stalls (I assume because there is nothing to pull from?), blocks the queue and the new docker container will not get cleaned up.
We are using the hosted interface at app.coolify.com, love this project so far! This is only a minor issue, not urgent for us at all!
All the best!
Minimal Reproduction (if possible, example repository)
Connect source as Github App, open Pull Request, wait only 2-3 seconds, close/merge the PR.
Exception or Error
No response
Version
v4.0.0-beta.297
The text was updated successfully, but these errors were encountered: