Milos Gajdos

@javisabalete can you verify if this still happens on the latest `2.8.x` release?

Closing for the lack of noise. If you manage to reproduce it in `2.8.x` feel free to reopen.

In the past a few folks asked about this hence why this is in the v3 milestone.

@steve-taylor I believe these two merges addressed the woes on the `main` branch: * https://github.com/distribution/distribution/pull/2926 * https://github.com/distribution/distribution/pull/3942 Do you mind verifying and/or closing?

Agreed, closing. If the issue hasnt been fixed @steve-taylor, feel free to reopen.

> @milosgajdos Do you think we could open the discussion to having this target a 2.9 release branch? There will be no `2.9` release. All the effort should go into...

With https://github.com/distribution/distribution/releases/tag/v3.0.0-alpha.1 out now, I'm closing this PR as it won't be merged into `2.x` branch. I'd strongly recommend using the new release as all the further development is going...

ping @sargun re: https://github.com/distribution/distribution/pull/3360#issuecomment-1722461356

Closing due to inactivity. Feel free to reopen if you believe #3685 is insufficient.

I believe it is. Equally, I'd love if `distribution-spec` defined these [reference] limits, but it's a major gotcha for folks unfamiliar with this.