github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 18:48:08 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

500/Runtime Error when getting tags via API #3393

New Issue
Closed
opened 2025-11-02 05:11:32 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 05:11:32 -06:00
Owner
Copy Link

Originally created by @philippbeckmann on GitHub (May 29, 2019).

Description

When calling /repos/{owner}/{repo}/tags via Swagger, the error runtime error: invalid memory address or nil pointer dereference occurs.

The tested repos were migrated from another git server.

Edit2: The error can be reproduced on try.gitea.io: curl -X GET "https://try.gitea.io/api/v1/repos/7073/gitea/tags" -H "accept: application/json" -H "authorization: Basic NzA3Mzp0ZXN0NzA3Mw=="

Originally created by @philippbeckmann on GitHub (May 29, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.8.1+6-g608f46e59 - Git version: git version 2.21.0.windows.1 - Operating system: Windows Server 2019 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [x] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: https://gist.github.com/philippbeckmann/ac66da04209ab9c6dc26c0c173ab6fe8 ## Description When calling `/repos/{owner}/{repo}/tags` via Swagger, the error `runtime error: invalid memory address or nil pointer dereference` occurs. The tested repos were migrated from another git server. Edit2: The error can be reproduced on try.gitea.io: `curl -X GET "https://try.gitea.io/api/v1/repos/7073/gitea/tags" -H "accept: application/json" -H "authorization: Basic NzA3Mzp0ZXN0NzA3Mw=="`
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 05:11:32 -06:00
GiteaMirror commented 2025-11-02 05:11:33 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jul 28, 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 (Jul 28, 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 05:11:33 -06:00
Author
Owner
Copy Link

@guillep2k commented on GitHub (Aug 16, 2019):

I can't reproduce it now. Has it been addressed?

@guillep2k commented on GitHub (Aug 16, 2019): I can't reproduce it now. Has it been addressed?
GiteaMirror commented 2025-11-02 05:11:33 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Aug 16, 2019):

Also am unable to reproduce. Will close, but @philippbeckmann please re-open if still an issue.

@techknowlogick commented on GitHub (Aug 16, 2019): Also am unable to reproduce. Will close, but @philippbeckmann please re-open if still an issue.
GiteaMirror commented 2025-11-02 05:11:33 -06:00
Author
Owner
Copy Link

@philippbeckmann commented on GitHub (Aug 16, 2019):

Hello, sorry for my late response. The issue can no longer be reproduced in version 1.9.0

@philippbeckmann commented on GitHub (Aug 16, 2019): Hello, sorry for my late response. The issue can no longer be reproduced in version 1.9.0
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#3393
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?