Skip to content
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.

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

Error: object not found #69

Open
exalted opened this issue Jul 3, 2024 · 3 comments · May be fixed by #71
Open

Error: object not found #69

exalted opened this issue Jul 3, 2024 · 3 comments · May be fixed by #71

Comments

@exalted
Copy link

exalted commented Jul 3, 2024

Installed via Homebrew and running version 3.0.12. I am getting…

2024/07/03 12:15:56 object not found

… error when I run gibo update.

@exalted
Copy link
Author

exalted commented Aug 4, 2024

FWIW; rm -rf ~/Library/Caches/gibo/ solved it.

@singularitti
Copy link

Me, too! Can this bug be fixed?

@ijaureguialzo
Copy link

ijaureguialzo commented Oct 15, 2024

I seems that the Git library used by gibo is not able to update the repository because it's a shallow copy.

Using Gitkraken or the command line I was unable to update, getting this output for a git status:

git status

En la rama main
error: Could not read 3674ae092f8055c29ffac2066dce1ccd7f798891
error: no se pudo analizar commit 3674ae092f8055c29ffac2066dce1ccd7f798891
fatal: bad revision '5445a270254a0b4443b20ed0033c4094959f937e...53cf297127b8c4613f5f3331b55cd7f465581e53'

I don't have experience with go, so can't help much, but I've been able to "resurrect" the repo, without having to delete it and clone again.

Running these commands on the cached repo restored it to a working state:

git fetch --depth 1
git reset --hard origin/main
git clean -dfx

Maybe it gives some clue to a maintainer that understands what's going on and how the app can recover from the situation, probably doing that "reset" part if the repo gets corrupted.

Hope it helps solving this.

ijaureguialzo added a commit to ijaureguialzo/gibo that referenced this issue Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants