[Bug]: API `models` endpoint drops first model on pagination about civitai HOT 1 CLOSED

This issue is still present when applying the following query parameters and utilizing nextCursor: username, limit, sort, nsfw

Example:

• First 50 models by the user, novowels:
  https://civitai.com/api/v1/models?username=novowels&limit=50&sort=Newest&nsfw=true

• Next 50 (nextCursor at the time of reporting):
  https://civitai.com/api/v1/models?limit=50&nsfw=true&sort=Newest&username=novowels&cursor=2024-03-10T21%3A35%3A22.332Z

• First 100 models by nochekaiser881:
  https://civitai.com/api/v1/models?username=novowels&limit=100&sort=Newest&nsfw=true

Utilizing the nextCursor on the API query with First 50 to retrieve the Next 50, the 51st model from the First 100 API query is missing from the Next 50. Exhausting the nextCursor function until completion, there are the same amount of missing models as there were nextCursors provided.

Additional troubleshooting...

Things get quite strange when troubleshooting this with another user, nochekaiser881:

• First 50 models by the user, nochekaiser881:
  https://civitai.com/api/v1/models?username=nochekaiser881&limit=50&sort=Newest&nsfw=true
• Next 50:
  https://civitai.com/api/v1/models?limit=50&nsfw=true&sort=Newest&username=nochekaiser881&cursor=2024-04-02T00%3A01%3A11.724Z
• First 100:
  https://civitai.com/api/v1/models?username=nochekaiser881&limit=100&sort=Newest&nsfw=true

The 51st model and ongoing from the Next 50 do not follow the same ordered listing as the First 100 API query, despite using the sort parameter. Nothing about this API query is different from the first example apart from the username (and nextCursor of course).

from civitai.