Nuget Package Explorer only loads several nuget packages

[pmandalka]

Description

I have uploaded about 2900 Nuget packages to a local installed gitea instance, which worked fine. I can see all packages in the package list of the organisation in the Web-UI an also search for specific Packages.
But if I try to load all Packages e.g. in Visual Studio or in nuget Packages Explorer, i only some several of these packages:

In gitea Web-UI it looks like this:

Anybody knows this issue?
I have not testet it on try.gitea.io.

Gitea Version

1.20.0+rc2-12-g102dcfa3a

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Docker on Debian

How are you running Gitea?

As docker image

Database

PostgreSQL

[DaKaLKa]

Cannot test on try.github.io - no Package support activated.

[KN4CK3R]

I was aware of that problem as it's related to #23191. The problem is the client calling the "list" endpoint with the parameters query?q=&skip=0&take=15. The take parameter specifies how many packages should be returned. Currently this count is passed into the function which queries the database for the package versions. This method finds take package versions while it should find take packages. I could not build a performant sql query which limits the count of packages but returns all available package versions of these packages.

[pmandalka]

Ok, I see the SetSessionPagination set the limit on the versions instead of the packages.

In SQLite the needed query with take = 1 and Skip = 0 would be - so that the limit is executed on the packages and not the pacakge_version table.
SELECT * FROM (SELECT * FROM package LIMIT 1 OFFSET 0) t1 INNER JOIN (SELECT * FROM package_version) t2 ON t1.id = t2.package_id

But I have no experience in xorm and if it's possible to build such a query with the engine.

[KN4CK3R]

I looked into the problem yesterday and will create a PR later which fixes the problem. 👍

I created 50 packages with 20 versions each and the NuGet Package Explorer works fine now: