This is a continuation on this message. I'm not quite sure if closing the topic was the best option, but OK.
Is it possible to share access to your GitLab repository?
I'm afraid I won't be able to 'open up' our GitLab instance to the internet, corporate won't be too happy about that I'm afraid ;-)
That's the easiest thing of course, but you say "on-prem" so maybe not so easy.
Agreed, that would be easiest. But, indeed, not so easy.
As an alternative, can you create a simple reproduction case using a public GitLab repository? This way, we can plug ProGet into it, attach a debugger, and figure out what's going on.
I'm not sure how I would go about that; we have dozens of packages in our repository, it may be only one specific package that causes the issue?
I'll see if I can intercept the ProGet traffic and dump that and reconstruct the requested JSON's to some files or something. Maybe that will help? Let me see what I can do to get you the most information to (try to) repro the issue. Crap, it's SSL ofcourse... Hmm... let me think this through...
Edit: Ok. Best I can come up with currently is I dump the searchresults for the queries "a", "e", "i", "o" and "u" , all with a &take=1000, which should return all packages in any of the 5 files. Maybe you can find an issue that way?
I'll send the JSON files to support@inedo.com as previously. Let's see where that takes us and go from there?
Please not I will be on holiday for the next two weeks so it may take a while before I reply.
