Powerlevel10k: gitstatus failed to initialize

[CNife]

When I updated powerlevel10k to 1.8.0, gitstatus starts to fail.

Error log:
https://paste.ofcode.org/5mXMwTmh6xM7RPjrwaznh8

[romkatv]

The log says that the following command hangs:

curl -fsSLo /home/cnife/.cache/gitstatus/gitstatusd-linux-x86_64.tmp.5140.tar.gz -- https://github.com/romkatv/gitstatus/releases/download/v1.0.0/gitstatusd-linux-x86_64.tar.gz

You need to have a working internet connection for powerlevel10k to download gitstatusd. If you want to, you can trigger this download manually after you update powerlevel10k:

git -C ~/.oh-my-zsh/custom/themes/powerlevel10k pull
~/.oh-my-zsh/custom/themes/powerlevel10k/gitstatus/install -f

[SebastianMuskalla]

I'm getting a similar problem.
When I try the manual install, I get the following error.

[gitstatus] error: failed to download gitstatusd: https://github.com/romkatv/gitstatus/releases/download/v1.0.0/gitstatusd-cygwin_nt-10.0-x86_64.tar.gz
curl: (23) Failed writing body (0 != 16384)

The file itself exists; when I paste the URL into a browser, I can download it.

[romkatv]

@SebastianMuskalla Please post the command that fails. It should start with curl.

[romkatv]

Oh, I see that curl is broken on Cygwin. I'll write a workaround.

This is not the same problem that @CNife is experiencing.

[knaeble]

I may also have a related issue. Please check https://paste.ofcode.org/JvdwQEJEXq3ZjUWaiRh8Gy for reference. It fails at an earlier stage than @CNife .

[romkatv]

@SebastianMuskalla Please update powerlevel10k and try again.

@knaeble Has powerlevel10k every work for you on the same machine or has it started happening recently?

[romkatv]

To clarify, the issue @knaeble is having is unrelated. I'd be surprised if powerlevel10k ever worked on iSH.

[knaeble]

Never tried it on this machine, only have been using it on others. Damn :/

[romkatv]

Never tried it on this machine, only have been using it on others.

Do any of those other machines run iSH? In other words, has powerlevel10k ever worked for you on iSH?

[knaeble]

None of them run iSH. So no, never. It’s flawless in WSL & native installations of course. Great work!

[romkatv]

OK, then iSH is simply not there yet. Lots and lots of things don't work in it. Zsh is apparently one of them.

[SebastianMuskalla]

@SebastianMuskalla Please update powerlevel10k and try again.

Fixed! Thanks a lot!

[romkatv]

Seems like everything is fixed. I assume the issue @CNife has posted was caused by not being connected to the internet. Please shout if not.

[Maryse47]

@romkatv why gitstatusd aren't bundled with powerlevel10k? I don't like my terminal downloading something over the web when I launch it.

[romkatv]

@romkatv why gitstatusd aren't bundled with powerlevel10k?

The size of the repo has been growing too large too quickly.

I don't like my terminal downloading something over the web when I launch it.

You can trigger this download manually after you update powerlevel10k:

git -C ~/.oh-my-zsh/custom/themes/powerlevel10k pull
~/.oh-my-zsh/custom/themes/powerlevel10k/gitstatus/install -f

git pull requires internet connection and the ability to read data from github.com. The second line is no different.

[Maryse47]

The size of the repo has been growing too large too quickly.

You could use submodule or just provide a way for downstream packagers to bundle it.

You can trigger this download manually after you update powerlevel10k:

git -C ~/.oh-my-zsh/custom/themes/powerlevel10k pull
~/.oh-my-zsh/custom/themes/powerlevel10k/gitstatus/install -f

I use powerlevel10k from Arch Linux package and don't use oh-my-zsh.

git pull requires internet connection and the ability to read data from github.com. The second line is no different.

I see gitstatus failed to initialize on every new shell I spawn and my working directory isn's a git repo so it shouldn't need to call git pull or anything.

[romkatv]

There are packaging instructions for distributions: https://github.com/romkatv/powerlevel10k/blob/master/README.md#how-to-package-powerlevel10k-for-distribution. Arch isn't following them yet. I don't know if they intend to.

[Maryse47]

cc : @shibumi ^

[romkatv]

cc : @shibumi ^

I've pinged @shibumi when I've made this change: https://github.com/romkatv/powerlevel10k/issues/392#issuecomment-626341555. You are experiencing issues because a new Arch Linux package was released without changes to it's packaging procedure. It's not broken per se but it requires internet connection to download gitstatusd (just once, not on every shell startup).

[shibumi]

Uff, I hoped it would just work. Looks like I need to have another look on this.

@romkatv I am actually not a big fan of the change, because your new build method is not reproducible. It's bad practice to download dependencies during the actual build process.

I need the libgit2 version before I download any software. I can't download the powerlevel10k stuff first and then parse it, because there should be no outgoing connection during the build process. This is for isolation proccess. It ensures that no remote source is tampering with the build process.

I will have a look and see how I get this working again, but it will need major work on the PKGBUILD and take some time.

[romkatv]

@romkatv I am actually not a big fan of the change, because your new build method is not reproducible. It's bad practice to download dependencies during the actual build process.

Is it possible you've misunderstood instructions?

[romkatv]

Specifically, this passage:

Depending on your workflow, it might be easier to store the URL to the libgit2 tarball in the same place where you are going to put the main powerlevel10k tarball URL. You'll need to update both URLs at the same time when bumping package version.

So you need two tarballs and then you run ./build. The latter doesn't download anything. The instructions show how to obtain the two tarballs.

[shibumi]

@romkatv yes, but the version info of your second tarball is hidden in the build info script that is in your first tarball. Do you see this dependency tree or am I misunderstanding something?

[romkatv]

You get the URL to the first tarball from a powerlevel10k release. That URL is fixed. Put that URL and the sha256 in your package definition.

Extract URL of the second tarball from the first. That URL is fixed because the first tarball is fixed. Put that URL and the sha256 in your package definition.

You start with a powerlevel10k release number and after that everything is reproducible. No hidden dependencies, nothing changing from underneath.

These steps can be done either manually or they can be automated. Up to you.

Does it make sense?

[romkatv]

I can attach libgit2 tarballs to powerlevel10k releases although it seems silly given that a powerlevel10k release unambiguously defines the libgit2 tarball by reference.

[shibumi]

@romkatv I really don't want to extract the tarball just for getting a second URL, doesn't matter if it's fixed. I still think you should provide the libgit2 URL somewhere else then only in the buildinfo file of the first release tarball. I maintain over 50 packages, I hope you understand the work load if every of these would start having such weird distribution methods.

No need to attach the libgit2 tarballs to the powerlevel10k release, it would be already enough if you could point via URL in the powerlevel10k release page on github to the corresponding libgit2 URL.

[romkatv]

Sure, I can add a link. Currently there is no link because no one has asked for it. I'm surprised that you prefer to manually extract technical data (such as URLs) from free-form release notes rather than from machine-readable metadata, but it's your time and your call.

Link added: https://github.com/romkatv/powerlevel10k/releases/tag/v1.8.2.

[shibumi]

@romkatv thanks.

[LimingFang]

The log says that the following command hangs:

curl -fsSLo /home/cnife/.cache/gitstatus/gitstatusd-linux-x86_64.tmp.5140.tar.gz -- https://github.com/romkatv/gitstatus/releases/download/v1.0.0/gitstatusd-linux-x86_64.tar.gz

You need to have a working internet connection for powerlevel10k to download gitstatusd. If you want to, you can trigger this download manually after you update powerlevel10k:

git -C ~/.oh-my-zsh/custom/themes/powerlevel10k pull
~/.oh-my-zsh/custom/themes/powerlevel10k/gitstatus/install -f

Thanks! It works.