Robb Manes
Robb Manes
Linking to [Red Hat Bugzilla 1906849](https://bugzilla.redhat.com/show_bug.cgi?id=1906849)
Just letting you know I didn't forget about this, was on break and back today. Thank you everybody for testing this and working on it.
TL;DR: Let's try to catch `io.Reader` errors about `EOF` or maybe whenever we get a `nil` response of `http.Response` and tell the user during `skopeo copy` operations that one side...
It also appears that, depending on when and which side terminates the connection we *might not* see a the `http.Response` as nil, as that's a server-side behavior we can't necessarily...
Just noting we saw a new occurrence of this on the server-side; specifically we suspect TCP-KeepAlive was not tolerated by an AWS ELB so it gracefully shut down the TCP...
> It’s up to you whether to use this issue to track the “unexpected EOF due to different pipe speeds”, the “(not unexpected) EOF to different pipe speeds”, or the...
In our case here, the specific scenario we were debugging was not a failure scenario; skopeo/podman was uploading layers with a negative size value (`-1`), which is a different issue...
Cast as `string` and formatting with `%q` is squashed in.
This really should be `Trace`, it's very verbose but still greatly helpful. Tried my hand at adding `--log-level` to skopeo in https://github.com/containers/skopeo/pull/2514 if we want to wait on that, and...
First time actually pushing a cobra change and making sure a global log level is applied to the containers org, would appreciate fact-checking to make sure I didn't break anything.