error: "failed to check application" and "failed to clean partially cloned repository"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened:
The following errors appear when a piped ends:
The error failed to clean partially cloned repository seems related to the process implemented in the pull request below. The content of the error field is err: context canceled, out: .
The error failed to check application: ... has two possible forms:
- error: failed to load new manifests: unable to run kustomize template: signal: killed
- error: failed to load new manifests: unable to run kustomize template: context canceled
What you expected to happen:
A piped completes shutdown without those errors.
How to reproduce it:
Environment:
pipedversion: v0.49.0 (at least) to v0.49.3control-planeversion:- Others:
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
No source files or tests are named. Start by tracing piped shutdown handling and the process from pull request #5312, then reproduce the reported cancellation and signal errors; done means shutdown completes without the application-check or partial-clone cleanup errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100