users/search API results appear to be incorrectly limited by ui/EXPLORE_PAGING_NUM value #1658

New Issue

GiteaMirror · 2025-11-02T04:08:41-06:00

GiteaMirror commented

2025-11-02 04:08:41 -06:00

Originally created by @ag-wood on GitHub (Mar 28, 2018).

Gitea version (or commit ref): 1.3.2
Git version: 1.8.3.1
Operating system: RedHat Enterprise Linux 7.4
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No - don't know how to/access is an issue.
- Not relevant
Log gist:

ISSUE:

Using the users/search API with a limit option that is greater than the value configured for ui/EXPLORE_PAGING_NUM in app.ini results in the limit that is passed being ignored.

Originally created by @ag-wood on GitHub (Mar 28, 2018). - Gitea version (or commit ref): 1.3.2 - Git version: 1.8.3.1 - Operating system: RedHat Enterprise Linux 7.4 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [X] No - don't know how to/access is an issue. - [ ] Not relevant - Log gist: ## ISSUE: Using the users/search API with a limit option that is greater than the value configured for ui/EXPLORE_PAGING_NUM in app.ini results in the limit that is passed being ignored.

GiteaMirror added the type/bug label 2025-11-02 04:08:41 -06:00

GiteaMirror closed this issue

2025-11-02 04:08:41 -06:00

GiteaMirror commented

2025-11-02 04:08:42 -06:00

@stale[bot] commented on GitHub (Feb 4, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 4, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:08:42 -06:00

@adelowo commented on GitHub (Feb 4, 2019):

Un-stale

@adelowo commented on GitHub (Feb 4, 2019): ___Un-stale___

GiteaMirror commented

2025-11-02 04:08:42 -06:00

@lafriks commented on GitHub (Feb 4, 2019):

wasn't this fixed recently?

@lafriks commented on GitHub (Feb 4, 2019): wasn't this fixed recently?

GiteaMirror commented

2025-11-02 04:08:43 -06:00

@adelowo commented on GitHub (Feb 4, 2019):

I believe it was but I cannot find the PR.

Once I get home, I can properly for it :)

@adelowo commented on GitHub (Feb 4, 2019): I believe it was but I cannot find the PR. Once I get home, I can properly for it :)

GiteaMirror commented

2025-11-02 04:08:43 -06:00

@stale[bot] commented on GitHub (Apr 5, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 5, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:08:43 -06:00

@lunny commented on GitHub (Apr 11, 2019):

@lafriks I think it's not, see #6579

@lunny commented on GitHub (Apr 11, 2019): @lafriks I think it's not, see #6579

GiteaMirror referenced this issue

2025-11-02 11:59:26 -06:00

[PR #1658] [MERGED] fix multiple readme file rendering and fix #1657 #15978

Sign in to join this conversation.