-
Notifications
You must be signed in to change notification settings - Fork 639
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
ungit throws error at startup and quits #1130
Comments
I get the same error ([email protected]) |
Which version of node/npm are you using? Please refer to https://github.com/FredrikNoren/ungit/blob/master/CONTRIBUTING.md
|
getmac and editions are my packages. Could the author please try updating getmac to 1.4.4 as the debugging info users have provided is for getmac 1.4.1 |
I've updated getmac to 1.4.4. Probem is still here. |
Mind if I remote in and debug it with you? Not sure the issue is on my side, but happy to look into it as it is my package after all. |
Ok. I think I miss configured something with editions. Let me push up a fix. One moment. Strange errors are now only coming in, as the version is a few weeks old. |
v1.4.5 of getmac will be published as soon as https://travis-ci.org/bevry/getmac/builds/419868038 passes - let me know if that resolves the issue edit, now published |
I've updated getmac to 1.4.5. But the problem still exists. |
I will need to remote into your machine to debug, as I am unable to reproduce. Grab a time on https://balupton.com/meet and we’ll work it out |
Also interesting that all reports are for windows. Is anyone encountering this not on windows? Will try and get a windows VM going. Perhaps it is an issue with using colon in directory names, affecting the node resolution system or the npm bundles. |
I tried on ubuntu 18.04 with the exact same versions and I didn't had problems |
So turns out it is because Windows doesn't support I can work around this issue by not using |
Crossposted on the npm forum for advice |
I'll see what they say. Regardless, I'll push up a workaround (using underscores instead of colons) tomorrow. Sorry for the stuff up everyone. |
Thanks for diving into this issue in details, and this seems like a tricky issue. Considering [email protected] is still having some issue I will not cut the new version with this yet. Once again, thanks for the prompt response! |
(and sorry I've been unresponsive as this is a very busy week for my company... :( ) |
Came off my motorbike today and got a bit scraped up. So will get to this in a day or two. Sorry for the delay. In the meantime, you can pin getmac to an earlier version, perhaps 1.4.4 or 1.4.3 |
Hand got infected and had to return to Australia for treatment. Will be another day or so. I'm really sorry for the delays. |
+1 facing the same issue |
Also facing the same issue since many days (weeks?). |
Correct. I will get to it when I can, so far I have been too injured. Things are finally getting better though. For the meantime, pin getmac to an earlier version. |
@balupton Will downgrading to [email protected] and locking it to that version work? |
getmac 1.4.6 is incoming which will resolve this issue if you experience it again, clear your npm cache and try again |
Looks like |
I haven't been able to run
ungit
since the last update. I get the following error:The module
editions
is installed globally, and so isungit
.The text was updated successfully, but these errors were encountered: