-
Notifications
You must be signed in to change notification settings - Fork 113
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
bad packages/x86_64/APKINDEX can cause hang #1645
Comments
OK. Here is a simple recreate that throws out the red-herring of a self-dependent package or the bootstrap archive.
Then from the wolfi-dev/os tree (commit listed above)
|
I think the problem is https://github.com/chainguard-dev/apko/blob/b93f0a2bc55f4dc8a07c373fc338e37dec193a24/pkg/apk/apk/implementation.go#L703 . On error of expandPackage, no close is ever done and thus no signal communicated. |
This problem was found in melange chainguard-dev/melange#1645 Any time a download failed, we did not communicate the error up the stack. Signed-off-by: Scott Moser <[email protected]>
This problem was found in melange chainguard-dev/melange#1645 Any time a download failed, we did not communicate the error up the stack. Signed-off-by: Scott Moser <[email protected]>
This problem was found in melange chainguard-dev/melange#1645 Any time a download failed, we would hang waiting for a close that would never occur. Signed-off-by: Scott Moser <[email protected]>
Make sure to close channel in InstallPackages, cleanup in CalculateWorld This problem was found in melange chainguard-dev/melange#1645 Any time a download failed, we would hang waiting for a close that would never occur. Signed-off-by: Scott Moser <[email protected]>
This is quite possibly in the realm of user error or "don't do that".
I got my wolfi-dev/os tree into a state that would not build packages.
Here should be enough information to recreate.
Note: ncurses does depend on itself.
I prettied-up the output a bit of the final ERROR message (after the ctrl-c). It actually does give a reasonable error, but I dont' know that I've ever read error messages of a program after hitting ctrl-c, so I feel justified in my lost time debugging why it was hung.
The text was updated successfully, but these errors were encountered: