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 I realize that a bundle is "hung" and won't finish, I would like to be able to use CTRL+C to stop porter AND the bundle from continuing to run.
To Reproduce
Create a bundle that just has a really long sleep in it
Run porter install
Use CTRL+C to abort porter install.
Only porter stops, the invocation image keeps going uninterrupted, and then the records aren't persisted for the run.
Expected behavior
The invocation image should stop too. If we can do anything to mark the run as failed that's great, but no one should be having to use docker rm to get rid of dangling invocation images.
Version
1.0.0-beta.1
The text was updated successfully, but these errors were encountered:
I'll bring this one up at the community meeting this week if I can. I've found where this is happening, but without some changes to the CNAB-go library we use, I'm not sure how we could get around this? (There might be some fancy tricks that @schristoff knows though, so I'll wait for feedback :))
Describe the bug
When I realize that a bundle is "hung" and won't finish, I would like to be able to use CTRL+C to stop porter AND the bundle from continuing to run.
To Reproduce
Only porter stops, the invocation image keeps going uninterrupted, and then the records aren't persisted for the run.
Expected behavior
The invocation image should stop too. If we can do anything to mark the run as failed that's great, but no one should be having to use docker rm to get rid of dangling invocation images.
Version
1.0.0-beta.1
The text was updated successfully, but these errors were encountered: