github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

List a team's member API page parameter is 0-based (should be 1-based) #10854

New Issue
Closed
opened 2025-11-02 09:20:04 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 09:20:04 -06:00
Owner
Copy Link

Originally created by @yamadayutaka on GitHub (May 16, 2023).

Description

In the API specification, page is supposed to be specified as 1-based.

https://try.gitea.io/api/swagger#/organization/orgListTeamMembers

image

However, it seems to be implemented with 0-based. (Please see screenshots)

Gitea Version

1.19.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Target Organization/Team

image

Result when page=1 is specified

image

Result when page=0 is specified

image

Git Version

No response

Operating System

No response

How are you running Gitea?

Installed with Helm chart and running on Kubernetes.

Override values

service:
  http:
    type: LoadBalancer

Install command

helm install gitea gitea-charts/gitea --version 8.3.0 -f override-values.yaml

Database

None

Originally created by @yamadayutaka on GitHub (May 16, 2023). ### Description In the API specification, `page` is supposed to be specified as `1-based`. https://try.gitea.io/api/swagger#/organization/orgListTeamMembers ![image](https://github.com/go-gitea/gitea/assets/77612853/a9b71199-fc5e-429c-9635-437efbfdf1d1) However, it seems to be implemented with `0-based`. (Please see screenshots) ### Gitea Version 1.19.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ### Target Organization/Team ![image](https://github.com/go-gitea/gitea/assets/77612853/0c061646-cfb9-4579-8304-07623029587f) ### Result when `page=1` is specified ![image](https://github.com/go-gitea/gitea/assets/77612853/797a91bb-d97c-454c-a2ea-b2299e61ffe7) ### Result when `page=0` is specified ![image](https://github.com/go-gitea/gitea/assets/77612853/13e01c67-0a68-4413-8c06-d72fb14bfeeb) ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Installed with Helm chart and running on Kubernetes. ### Override values ```yaml service: http: type: LoadBalancer ``` ### Install command ``` helm install gitea gitea-charts/gitea --version 8.3.0 -f override-values.yaml ``` ### Database None
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 09:20:04 -06:00
GiteaMirror commented 2025-11-02 09:20:05 -06:00
Author
Owner
Copy Link

@yardenshoham commented on GitHub (May 16, 2023):

The fix would be a breaking change so this shouldn't go in 1.19.4

@yardenshoham commented on GitHub (May 16, 2023): The fix would be a breaking change so this shouldn't go in 1.19.4
GiteaMirror commented 2025-11-02 09:20:05 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 16, 2023):

It should be a bug, because the API documentation said it's 1 based.

@lunny commented on GitHub (May 16, 2023): It should be a bug, because the API documentation said it's 1 based.
GiteaMirror commented 2025-11-02 09:20:05 -06:00
Author
Owner
Copy Link

@yardenshoham commented on GitHub (May 16, 2023):

I agree it's a bug. The fix itself would be a breaking change so it should be fixed in 1.20

@yardenshoham commented on GitHub (May 16, 2023): I agree it's a bug. The fix itself would be a breaking change so it should be fixed in 1.20
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/confirmed type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10854
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?