Skip to content

unable to PushUpdateAddTag to Repo: unable to get tag Commit: object does not exist #28843

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
yp05327 opened this issue Jan 18, 2024 · 2 comments · Fixed by #29295
Closed

unable to PushUpdateAddTag to Repo: unable to get tag Commit: object does not exist #28843

yp05327 opened this issue Jan 18, 2024 · 2 comments · Fixed by #29295
Labels
type/bug
Milestone
1.21.6

Comments

@yp05327
Copy link
Contributor

yp05327 commented Jan 18, 2024 •
edited
Loading

Description

image

Using gogit and migrate https://github.com/torvalds/linux with releases

https://github.com/torvalds/linux/tree/v2.6.11
image

not sure whether this is a bug

Gitea Version

latest

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

build

Database

None
@lunny
Copy link
Member

lunny commented Jan 18, 2024

Looks like the tag point to a tree. I remember I have read the code about the related problem.

@yp05327 yp05327 mentioned this issue Jan 18, 2024
Closed
@wxiaoguang wxiaoguang mentioned this issue Feb 4, 2024
Closed
@lunny
Copy link
Member

lunny commented Feb 6, 2024

I believe this is a git's edgecase which only happen on linux itself. Maybe we need some trick to ignore it to avoid failure on gitea.

objecttype tagrefname:short v2.6.11-treeobject c39ae07f393806ccf406ef966e9a15afc43cc36aobjectname 5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8ccreator contents This is the 2.6.11 tree object.

NOTE! There's no commit for this, since it happened before I started with git.
Eventually we'll import some sort of history, and that should tie this tree
object up to a real commit. In the meantime, this acts as an anchor point for
doing diffs etc under git.

@lunny lunny mentioned this issue Feb 21, 2024
Merged
@lunny lunny added this to the 1.21.6 milestone Feb 21, 2024
lunny added a commit that referenced this issue Feb 22, 2024
@lunny @wxiaoguang
Ignore the linux anchor point to avoid linux migrate failure (#29295)
5ed17d9 
Fix #28843

This PR will bypass the pushUpdateTag to database failure when
syncAllTags. An error log will be recorded.

---------

Co-authored-by: wxiaoguang <[email protected]>
GiteaBot pushed a commit to GiteaBot/gitea that referenced this issue Feb 22, 2024
@lunny @wxiaoguang @GiteaBot
Ignore the linux anchor point to avoid linux migrate failure (go-gite…
4a89820 
…a#29295)

Fix go-gitea#28843

This PR will bypass the pushUpdateTag to database failure when
syncAllTags. An error log will be recorded.

---------

Co-authored-by: wxiaoguang <[email protected]>
@GiteaBot GiteaBot mentioned this issue Feb 22, 2024
Merged
6543 pushed a commit that referenced this issue Feb 22, 2024
@GiteaBot @lunny @wxiaoguang
Only log error when tag sync fails (#29295) (#29327)
b78f5fc 
Backport #29295 by @lunny

Fix #28843

This PR will bypass the pushUpdateTag to database failure when
syncAllTags. An error log will be recorded.

Co-authored-by: Lunny Xiao <[email protected]>
Co-authored-by: wxiaoguang <[email protected]>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 4, 2024
project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue Jan 23, 2025
@GiteaBot @lunny
@wxiaoguang @earl-warren
Only log error when tag sync fails (go-gitea#29295) (go-gitea#29327)
c4ac72e 
Backport go-gitea#29295 by @lunny

Fix go-gitea#28843

This PR will bypass the pushUpdateTag to database failure when
syncAllTags. An error log will be recorded.

Co-authored-by: Lunny Xiao <[email protected]>
Co-authored-by: wxiaoguang <[email protected]>
(cherry picked from commit b78f5fc)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type/bug
Projects
None yet
Milestone
1.21.6
Development

Successfully merging a pull request may close this issue.

Only log error when tag sync fails lunny/gitea
2 participants
@lunny @yp05327