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

errror - did not send all necessary objects #142

Closed
tcurdt opened this issue May 1, 2023 · 5 comments
Closed

errror - did not send all necessary objects #142

tcurdt opened this issue May 1, 2023 · 5 comments

Comments

@tcurdt
Copy link

tcurdt commented May 1, 2023

While "Breaking-Move" gives an idea, I am a little lost on what happened here.

Last zgenom autoupdate log:
--------
fatal: bad object refs/remotes/origin/Breaking-Move-zgen-compatibility-into-zgen.zsh.zwc
error: https://github.com/jandamm/zgenom.git did not send all necessary objects


-- zgenom: Deleting `/Users/tcurdt/.zgenom/sources/init.zsh` ...
-- zgenom: Deleting `/Users/tcurdt/.zcompdump-shodan2` ...

Recreating init.zsh

not saved
-- zgenom: Creating `/Users/tcurdt/.zgenom/sources/init.zsh` ...
-- zgenom: Initializing completions ...
-- zgenom: Compiling files ...
--------

Any pointers on how to fix this?

@V4G4X
Copy link

V4G4X commented May 2, 2023

Facing the same issue recently. Get this in the console output on every new terminal.

@jandamm
Copy link
Owner

jandamm commented May 2, 2023

Hey @tcurdt, @V4G4X,

that issue isn't actually the Breaking change of #137.

The issue is that the branch of #137 ended in .zsh.
Git creates a file to keep track of that file .git/refs/remotes/origin/Breaking-Move-zgen-compatibility-into-zgen.zsh.
When zgenom compiles it sources the .git folder wasn't ignored. So zgenom created a .git/refs/remotes/origin/Breaking-Move-zgen-compatibility-into-zgen.zsh.zwc.
The next time Git checks for updates it cannot get an update on the branch Breaking-Move-zgen-compatibility-into-zgen.zsh.zwc.

I fixed this in #140.

In order to fix the current state you have to do the following:

cd $ZGEN_SOURCE
rm -f ".git/refs/remotes/origin/Breaking-Move-zgen-compatibility-into-zgen.zsh.zwc"
git fetch --prune
git rebase origin/main

This will remove the faulty file and update zgenom so it won't happen again.

Please let me know if this fixes your issue 👍

@jandamm jandamm pinned this issue May 2, 2023
@tcurdt
Copy link
Author

tcurdt commented May 2, 2023

Thank you so much, Jan.
That did the trick!

@tcurdt tcurdt closed this as completed May 2, 2023
@V4G4X
Copy link

V4G4X commented May 3, 2023

Thanks it fixes it for me too!

@jef
Copy link

jef commented May 9, 2023

Thank you for this and the hard work on zgenom 🙇

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

No branches or pull requests

4 participants