powerlevel10k: bad file descriptor console output from _p9k_worker_start

I just updated and now I am getting a warning with the instant prompt, and I am on macOS. I think this is related to source ~/.p10k.zsh because if I commented that out, there is no warnings anymore. I am not sure if this is a problem because of the recent changes in this repo.

console output produced during zsh initialization follows

_p9k_worker_start:8: failed to close file descriptor 13: bad file descriptor
_p9k_worker_start:9: failed to close file descriptor 14: bad file descriptor
_p9k_worker_start:10: failed to close file descriptor 15: bad file descriptor

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 26 (9 by maintainers)

Most upvoted comments

Thanks for the reports, everyone. I’ve reverted the bad commit. Sorry for the breakage. Never a good idea to push late at night.

romkatv on May 20, 2020

I reverted the change for now by going into ~/.zinit/plugins/romkatv---powerlevel10k and do a git checkout fb9bc2d3.

stevenguh on May 19, 2020

If you care about interactive zsh performance, check out https://github.com/romkatv/zsh-bench.

romkatv on Oct 25, 2023

Had the same issue since moving my plugins to https://github.com/rossmacarthur/sheldon.

Turns out it had to do with the defer mechanism from romkatv/zsh-defer that delays loading of plugins.

So, after I changed the following line in my sheldon config from:

# Fish history search (up arrow).
[plugins.zsh-history-substring-search]
github = "zsh-users/zsh-history-substring-search"
apply = ["defer"]

# Fish history search (up arrow).
[plugins.zsh-history-substring-search]
github = "zsh-users/zsh-history-substring-search"

Everything worked as expected again.

ret2src on Oct 25, 2023

Its happening again now 😕 2022-02-15_22-09

JDeepD on Feb 15, 2022