powerlevel10k: gitstatus_query write error: broken pipe

Hi,

I found that after I execute some commands in CLI (e.g., echo, vim <file>), it sometimes shows gitstatus_query:echo:32: write error: broken pipe, and it shows the error in every result of CLI commands later if it is triggered once. . 螢幕快照 2019-07-19 上午2 06 03

I install this theme by oh-my-zsh, and my os is MacOSX 10.14.5. I use iTerm2 as my terminal emulator.

This is a copy of my .zshrc file Hope to help you replicate the error.

Thanks.

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 55 (27 by maintainers)

Commits related to this issue

print a message when killing gitstatusd (for debugging https://github.com/romkatv/powerlevel10k/issues/123) — committed to romkatv/powerlevel10k by romkatv 5 years ago
daemonize gitstatusd in zsh bindings Fixes https://github.com/romkatv/powerlevel10k/issues/123 and https://github.com/romkatv/powerlevel10k/issues/97. — committed to romkatv/gitstatus by romkatv 5 years ago
Squashed 'gitstatus/' changes from d3bc3e34..901c366b 901c366b survive `cd` being a function that fails instead of doing its job; see #123 git-subtree-dir: gitstatus git-subtree-split: 901c366b8ecb7... — committed to romkatv/powerlevel10k by romkatv 4 years ago

Most upvoted comments

Thanks, the config the wizard suggested to me looks awesome!!

hsinyinfu on Aug 6, 2019

On master that job is disowned (started with &!), so it cannot be controlled with ZSH job control tools. On bg-zsh it’s not disowned (started with plain &), which is the reason you are seeing something like this when starting zsh:

[4] 21581

romkatv on Jul 21, 2019

Let’s try to figure out what’s going on. This must be something unusual as I’ve never seen reports of this kind. Please do the following.

Update powerlevel10k to the latest version. If you’ve installed at the standard location, you can update it like this:

( cd $ZSH_CUSTOM/themes/powerlevel10k && git pull )

Enable logging by adding GITSTATUS_LOG_LEVEL=DEBUG to your ~/.zshrc.

echo 'GITSTATUS_LOG_LEVEL=DEBUG' >>!~/.zshrc

Restart zsh and trigger the error the same way you did it before.
Type the following command and copy its output to this issue.

() {
  emulate -L zsh && setopt xtrace
  echo $ZSH_VERSION $ZSH_PATCHLEVEL
  uname -a
  ps --pid $GITSTATUS_DAEMON_PID_POWERLEVEL9K
  lsof -p $$
  lsof -p $GITSTATUS_DAEMON_PID_POWERLEVEL9K
  cat $GITSTATUS_DAEMON_LOG_POWERLEVEL9K
}

romkatv on Jul 19, 2019