Release menu #3949

New Issue

GiteaMirror · 2025-11-02T05:31:27-06:00

GiteaMirror commented

2025-11-02 05:31:27 -06:00

Originally created by @marknovem on GitHub (Sep 13, 2019).

big 500 error code displayed when accessing "Release" menu. Below are the sample logs on the server during the operation:

 []interface {}{1, 3}
2019/09/13 16:48:18 .../xorm/session_get.go:99:nocacheGet() [I] [SQL] SELECT "id", "uid", "repo_id" FROM "star" WHERE "uid"=$1 AND "repo_id"=$2 LIMIT 1 []interface {}{1, 3}
2019/09/13 16:48:18 ...xorm/session_find.go:199:noCacheFind() [I] [SQL] SELECT "id", "repo_id", "publisher_id", "tag_name", "lower_tag_name", "target", "title", "sha1", "num_commits", "note", "is_draft", "is_prerelease", "is_tag", "created_unix" FROM "release" WHERE repo_id=$1 ORDER BY "created_unix" DESC, "id" DESC LIMIT 10 []interface {}{3}
2019/09/13 16:48:18 .../xorm/session_raw.go:87:queryRow() [I] [SQL] SELECT count(*) FROM "release" WHERE repo_id=$1 []interface {}{3}
2019/09/13 16:48:18 ...xorm/session_find.go:199:noCacheFind() [I] [SQL] SELECT "id", "uuid", "issue_id", "release_id", "uploader_id", "comment_id", "name", "download_count", "size", "created_unix" FROM "attachment" WHERE "release_id" IN ($1) ORDER BY "release_id" ASC []interface {}{1}
2019/09/13 16:48:18 .../xorm/session_get.go:99:nocacheGet() [I] [SQL] SELECT "id", "lower_name", "name", "full_name", "email", "keep_email_private", "passwd", "must_change_password", "login_type", "login_source", "login_name", "type", "location", "website", "rands", "salt", "language", "description", "created_unix", "updated_unix", "last_login_unix", "last_repo_visibility", "max_repo_creation", "is_active", "is_admin", "allow_git_hook", "allow_import_local", "allow_create_organization", "prohibit_login", "avatar", "avatar_email", "use_custom_avatar", "num_followers", "num_following", "num_stars", "num_repos", "num_teams", "num_members", "visibility", "diff_view_style", "theme" FROM "user" WHERE "id"=$1 LIMIT 1 []interface {}{0}
2019/09/13 16:48:18 ...ters/repo/release.go:115:Releases() [E] calReleaseNumCommitsBehind: GetBranchCommit: object not found

Is there anything i missed to configured or missed to perform? please help me solve this problem. Thanks.

Originally created by @marknovem on GitHub (Sep 13, 2019). big 500 error code displayed when accessing "Release" menu. Below are the sample logs on the server during the operation: ``` []interface {}{1, 3} 2019/09/13 16:48:18 .../xorm/session_get.go:99:nocacheGet() [I] [SQL] SELECT "id", "uid", "repo_id" FROM "star" WHERE "uid"=$1 AND "repo_id"=$2 LIMIT 1 []interface {}{1, 3} 2019/09/13 16:48:18 ...xorm/session_find.go:199:noCacheFind() [I] [SQL] SELECT "id", "repo_id", "publisher_id", "tag_name", "lower_tag_name", "target", "title", "sha1", "num_commits", "note", "is_draft", "is_prerelease", "is_tag", "created_unix" FROM "release" WHERE repo_id=$1 ORDER BY "created_unix" DESC, "id" DESC LIMIT 10 []interface {}{3} 2019/09/13 16:48:18 .../xorm/session_raw.go:87:queryRow() [I] [SQL] SELECT count(*) FROM "release" WHERE repo_id=$1 []interface {}{3} 2019/09/13 16:48:18 ...xorm/session_find.go:199:noCacheFind() [I] [SQL] SELECT "id", "uuid", "issue_id", "release_id", "uploader_id", "comment_id", "name", "download_count", "size", "created_unix" FROM "attachment" WHERE "release_id" IN ($1) ORDER BY "release_id" ASC []interface {}{1} 2019/09/13 16:48:18 .../xorm/session_get.go:99:nocacheGet() [I] [SQL] SELECT "id", "lower_name", "name", "full_name", "email", "keep_email_private", "passwd", "must_change_password", "login_type", "login_source", "login_name", "type", "location", "website", "rands", "salt", "language", "description", "created_unix", "updated_unix", "last_login_unix", "last_repo_visibility", "max_repo_creation", "is_active", "is_admin", "allow_git_hook", "allow_import_local", "allow_create_organization", "prohibit_login", "avatar", "avatar_email", "use_custom_avatar", "num_followers", "num_following", "num_stars", "num_repos", "num_teams", "num_members", "visibility", "diff_view_style", "theme" FROM "user" WHERE "id"=$1 LIMIT 1 []interface {}{0} 2019/09/13 16:48:18 ...ters/repo/release.go:115:Releases() [E] calReleaseNumCommitsBehind: GetBranchCommit: object not found ``` Is there anything i missed to configured or missed to perform? please help me solve this problem. Thanks.

GiteaMirror added the issue/needs-feedback label 2025-11-02 05:31:27 -06:00

GiteaMirror closed this issue

2025-11-02 05:31:27 -06:00

GiteaMirror commented

2025-11-02 05:31:28 -06:00

@lunny commented on GitHub (Sep 13, 2019):

Have you force push to remove some commits?

@lunny commented on GitHub (Sep 13, 2019): Have you force push to remove some commits?

GiteaMirror commented

2025-11-02 05:31:28 -06:00

@marknovem commented on GitHub (Sep 14, 2019):

Nope.. i just perform normal 3 successive commits and push respectively and then create 1 tag. After that i notice that the "Releases" menu has a suffix value of "1" (e.g. 'Releases 1' ) so when i click it, the 500 error was displayed.

@marknovem commented on GitHub (Sep 14, 2019): Nope.. i just perform normal 3 successive commits and push respectively and then create 1 tag. After that i notice that the "Releases" menu has a suffix value of "1" (e.g. 'Releases 1' ) so when i click it, the 500 error was displayed.

GiteaMirror commented

2025-11-02 05:31:28 -06:00

@JakobR commented on GitHub (Sep 27, 2019):

I'm having the same issue, with the same error message in the logs (calReleaseNumCommitsBehind: GetBranchCommit: object not found).

Versions:

gitea 1.9.3 built with go1.13
git 2.23.0

I have not force-pushed either, but I have pushed the commits and tag separately, if that makes any difference (i.e., something like git commit; git push; git tag v1-xyz; git push --tags).

@JakobR commented on GitHub (Sep 27, 2019): I'm having the same issue, with the same error message in the logs (`calReleaseNumCommitsBehind: GetBranchCommit: object not found`). Versions: - gitea 1.9.3 built with go1.13 - git 2.23.0 I have not force-pushed either, but I have pushed the commits and tag separately, if that makes any difference (i.e., something like `git commit; git push; git tag v1-xyz; git push --tags`).

GiteaMirror commented

2025-11-02 05:31:28 -06:00

@lunny commented on GitHub (Sep 30, 2019):

@JakobR did your tag name has a space on middle?

@lunny commented on GitHub (Sep 30, 2019): @JakobR did your tag name has a space on middle?

GiteaMirror commented

2025-11-02 05:31:28 -06:00

@JakobR commented on GitHub (Sep 30, 2019):

No, it was just lowercase letters with a hyphen (-) in the middle.

@JakobR commented on GitHub (Sep 30, 2019): No, it was just lowercase letters with a hyphen (`-`) in the middle.

GiteaMirror commented

2025-11-02 05:31:29 -06:00