Cancelling build should not erase the step output
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.3k
- Forks
- 1.5k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 48
Description
Cancelling a build with ctrl-c should not erase the step output.
I was building an image docker buildx build ... and while watching the output I noticed an error that I knew would result in the image failing later on. I wanted to copy that error I saw so I hit ctrl-c to stop the build. The output that I wanted to preserve (so that I could copy and paste specifics of the error) got erased from my terminal and replaced with the following:
=> CANCELED [5/8] RUN [...redacted build step...] 72.3s
error: failed to solve: rpc error: code = Canceled desc = context canceled
😠
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the cancellation with a docker buildx build that emits a visible step error, then trace how ctrl-c cancellation replaces terminal output. Done means the output produced before cancellation remains available for copying while the build still reports that it was canceled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100