Topics created by mayorovp_3701

Hi @mayorovp_3701 Actually zero byte in position 1 looks like attempt to read UTF16-LE-encoded json as UTF8 Oh that's a great observation! Yeah that sounds like a reasonable explanation. But still... how could that even be possible? It's not like ProGet is going to randomly swap an encoding like that, and it's not like NuGet is going to store .json files incorrectly. As for experimentation, next time it happens: remove one of the connectors from the feed to which one navigate to the JSON endpoints of the connector in question, to see if you see the bad JSON try to identify a pattern of behavior that causes this watch for HTTP access logs to see if you can find the exact URL that's being accessed at the time of the connector failure (assuming it's a self-connector) be prepared to attach a MITM proxy to ProGet (Admin > Proxy) Thanks, Alana

Hi @mayorovp_3701, This is a bug you should definitely report to GitLab -- it's clearly required by the API and all other registries support it. Without that API defined, we have to "make guesses" based on undocumented conventions (i.e. /v3-flatcontainer/{id}), which causes headaches down the line. That's why there's an API contract :) I don't know how/why it works with dotnet sdk -- perhaps it's using a different endpoint, or maybe it's not actually working and just going to NuGet.org. Whatever the case, it doesn't make sense for us to build workarounds for easily-fixable bugs on GitLab when other vendors seem to follow the API contract. -- Dean

Hi @mayorovp_3701 , Thanks for confirming; we can will try to get this fixed in the next maintenance release via PG-3139 -- the underlying issue is most likely a race condition on that trigger I mentioned, so we're going to fix it by adding an advisory lock. It will not remove the duplicate content, but in theory deleting the image will. Thanks, Alana