I tracked it down further today, accidentally finding a reproducer. In
methods/http.cc we check for Req.DownloadSize > Req.MaximumSize and fail
with an error if that's the case; hence ensuring our download was within
the allowed range for the request.
The issue is that Req.MaximumSize is calculate
We tracked this down to the Pulp repository not having Size fields.
While this is a broken repository, APT should also more gracefully
handle that situation, either by warning about missing Size values,
erroring out, disabling pipelining; or by fixing pipelining to behave if
we don't know the size
With help from @juliank, I was able to transfer the state from my bionic
box to focal, and hirsute. Issue reproduces on all of them. On hirsute,
apt is 2.2.1. Where do we go from here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
> I don't have that mirrored, but I have focal, and I could not
reproduce. Apt 2.0.2
There have been no relevant changes between 1.6.y and 2.0.y, so it
really should reproduce with both of them or none of them.
But you have to be careful that the download is _exactly_ the same,
usually by pointin
> I am also a bit worried about the screenshot in the referred bugreport
as that shows two different servers replying (Apache vs some python via
a proxy).
The saltstack repository is served by pulp, so client -> httpd -> pulp.
I've verified that httpd responds with correctly. Not sure why pulpcore
> I've attached an example log, where the error pops up for multiple
packages, and they all appear to be compared to one size (86464 bytes).
just for the record: This is a misunderstanding. If apt does pipelining
it searches in the requests it made for the file this response is for.
If no request
Please let me know if you can reproduce this with 2.2.2 in hirsute. No
changes can be made to the http method in stable releases, as it's super
fragile - Every time we make changes, something else breaks.
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notif
Managing to get a reproducer for HTTP issues more than a couple of hours
has not really worked so far, and most people's reproducers don't work.
It's highly subjective to network latency and MTU afaict.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
