Labels API does not work #2899

New Issue

GiteaMirror · 2025-11-02T04:53:07-06:00

GiteaMirror commented

2025-11-02 04:53:07 -06:00

Originally created by @rayitopy on GitHub (Feb 12, 2019).

Gitea version (or commit ref): Go1.11.5
Database (use [x]):
- [] PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

Description

The labels endpoints are not working as expected
GET /repos/{owner}/{repo}/issues/{index}/labels
Always return an epmty array
POST, PUT, DELETE /repos/{owner}/{repo}/issues/{index}/labels
Always returns a 401 status code, but I correctly setted the credentials

Originally created by @rayitopy on GitHub (Feb 12, 2019).  - Gitea version (or commit ref): Go1.11.5 - Database (use `[x]`): - [] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) - [ ] No - [ ] Not relevant ## Description The labels endpoints are not working as expected ` GET /repos/{owner}/{repo}/issues/{index}/labels` Always return an epmty array `POST, PUT, DELETE /repos/{owner}/{repo}/issues/{index}/labels` Always returns a 401 status code, but I correctly setted the credentials

GiteaMirror added the type/bug label 2025-11-02 04:53:07 -06:00

GiteaMirror closed this issue

2025-11-02 04:53:07 -06:00

GiteaMirror commented

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

@Larivact commented on GitHub (Feb 13, 2019):

Link to reproduce: https://try.gitea.io/api/v1/repos/ttttttttttttttt/ttttttttttttttt/issues/1/labels

@Larivact commented on GitHub (Feb 13, 2019): Link to reproduce: https://try.gitea.io/api/v1/repos/ttttttttttttttt/ttttttttttttttt/issues/1/labels

GiteaMirror commented

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

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

Yes, there is actually a bug with fetching labels of an issue. I have sent PR https://github.com/go-gitea/gitea/pull/6053 for that

I cannot replicate the 401 as it goes through on my end here.
Can I see how you are authorizing the request?

@adelowo commented on GitHub (Feb 13, 2019): Yes, there is actually a bug with fetching labels of an issue. I have sent PR https://github.com/go-gitea/gitea/pull/6053 for that I cannot replicate the 401 as it goes through on my end here. Can I see how you are authorizing the request?

GiteaMirror commented

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

@rayitopy commented on GitHub (Feb 13, 2019):

I was using basic authorization header in the swagger UI, with token authentication seems to work.
Maybe I'm misspelling the password or something. 🤷‍♂️

@rayitopy commented on GitHub (Feb 13, 2019): I was using basic authorization header in the swagger UI, with token authentication seems to work. Maybe I'm misspelling the password or something. :man_shrugging:

GiteaMirror commented

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

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

@rayitopy I will guess it's your password that is wrong:). Since #6053 has been merged, is there any more thing to do on this issue?

@adelowo commented on GitHub (Feb 13, 2019): @rayitopy I will guess it's your password that is wrong:). Since #6053 has been merged, is there any more thing to do on this issue?

GiteaMirror commented

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

@techknowlogick commented on GitHub (Feb 13, 2019):

closing as resolved. please re-open if needed.

@techknowlogick commented on GitHub (Feb 13, 2019): closing as resolved. please re-open if needed.

GiteaMirror referenced this issue

2025-11-02 12:15:34 -06:00

[PR #2899] [MERGED] Update swagger documentation #16652

Sign in to join this conversation.