-
Notifications
You must be signed in to change notification settings - Fork 4
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
[bug]: (eval):ZIModule_:1: can't write zwc file: /proc/self/fd/15.zwc #31
Comments
Hi @amogus07 👋 I need to be able reproduce the issue, here are some tips to narrow it down: Load only |
@ss-o It seems starship is the culprit |
So, is there anything I can do about it? |
I am guessing that Starhip or its related files are located where |
tried that, didn't work |
@amogus07 have you tried to profile/debug the Place the following at the top of [[ $ZSHRC_PROFILE -gt 0 ]] && zmodload zsh/zprof Then execute If you have no luck identifying the issue, you can try benchmark#method-1 or similar methods to pinpoint the issue. Finally, you can run the docker container re-produce the issue, and share the instructions. |
Could you explain how to set up the docker container for testing or provide some resources? I'm no familiar with docker. |
You can use https://github.com/z-shell/playground as an example, if you need additional support let me know 🎯 |
I don't use starship and am also running into this.
How can I verify that only the zpmod module is loaded? Use an empty zshrc/zprofile? That said AFAIK that's all that is loaded and it occurs. zsh 5.9 via linuxbrew on ubuntu 22.04; if that helps / is needed. |
Environment
Fedora Workstation 39
Reproduction steps
Expected behavior
zpmod operates normally according to README.md
Current behavior
Upon opening a new terminal session, the following message appears: "(eval):ZIModule_:1: can't write zwc file: /proc/self/fd/15.zwc"
Code snippet
Additional information
I don't use Zi
Self-service
Have you read the Contributing Guidelines?
Are you familiar with the Contributor Covenant Code of Conduct?
Contact Details
No response
The text was updated successfully, but these errors were encountered: