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
(wrong-type-argument stringp nil)
error when cloning a package during doom {install,upgrade}
#5918
Comments
With emacsPgtkGcc |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
Unfortunately, this is not a Doom issue. This is the error that straight throws when a connection times out due to internet downtime, prohibitive proxies (or ISPs), SSL verification issues, or the remote service being down. This causes a This is one of our more commonly reported issues, so I'll pin this and leave it open until it's addressed upstream, or I get around to writing an error handling layer over straight (which is a long term goal, given it's one of this project's biggest UX issues -- this is not the only error of its kind -- but it'll be some time until I get to it). Anyhow, the workaround is to simply try again after deleting the local package's repo:
Cycling a package's module (comment it out in Side note: please use the 👍 reaction to express that their advice worked for you, instead of spamming the thread with "worked for me too!" posts. |
(wrong-type-argument stringp nil)
error when cloning a package during doom {install,upgrade}
This comment was marked as outdated.
This comment was marked as outdated.
Is there any way to figure out what repo to delete? I ended up deleting the entire |
$ rg 'straight-vc-%S-%S' .local/straight/repos/
.local/straight/repos/straight.el/straight.el
1300: (let ((func (intern (format "straight-vc-%S-%S" |
I'll be deleting all the comments here that are related to #6960 and not to the issue here. It is quite messy to have people talking about another issue here, and that prevents following possible solutions to the issue here (which is related to network error handling during straight operations mostly). There are things happening in the background about #6960, it'll be fixed soon ™️ once maintainers have a bit more time, and the permanent fix to #6960 is modifying your own packages.el to repin straight (The other reason for deletion is that people using github search for the wrong issue will come here, and think that they are on topic while commenting here, on which they − unknowingly − are not) |
In case this information is useful for someone else:
That is, instead of |
What did you expect to happen?
When running
doom upgrade
, I'd expect my packages to be upgraded to the latest version.What actually happened?
Instead I receive the following error:
The error log can be found here: https://pastebin.com/VQQR8R0N
doom upgrade
works as expected when removing themagit
entry from init.elDescribe your attempts to resolve the issue
I tried removing repositories I assumed affected with
rm -rf ~/.emacs.d/.local/straight/repos/...
, but the error persisted.Reinstalling Doom Emacs entirely worked in the end.
Steps to reproduce
magit
entry ininit.el
doom upgrade
,doom sync
ordoom install
System Information
https://pastebin.com/4wRMAQJn
The text was updated successfully, but these errors were encountered: