-
Notifications
You must be signed in to change notification settings - Fork 42
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
Error: spawn lsof ENOENT on snow init #247
Comments
Hey belkrax, thanks so much for your report! Interesting, it seems your Linux OS doesn't support lsof. If you change this line: to return Promise.resolve(); you should be more successful. Could you try this again and we go to the next step to find a solution for the missing |
I grabbed the lsof package (in hindsight the issue was obvious but I'm unused to node error messages) and everything works now. Thank you! |
I still think there is room for improvement in this code. We can either improve the error message, find an alternative on Linux, or skip |
Describe the bug
After compiling snow, if I try to run
snow init
(while in a newly created directory), node spits outThe
.snow
folder is still created, however if I try to runsnow add .
(and a few other snow commands), I get the errorIn
.snow/log/mainlog
, there is 1 line:1633564812686 -0700 $> init: initialized at /home/[filepath]/test_snow
, so the repo seems to have initialized successfully, but all other (non-log) folders in.snow
are empty.To Reproduce
Steps to reproduce the behavior:
[be using zsh/linux/ext4]
snow init
^ this will cause a node error
snow add .
^ this will raise a "no HEAD found" error
Expected behavior
snow init
shouldn't throw any errors, andsnow add .
shouldn't failDesktop (please complete the following information):
Additional context
I'm a node newbie so maybe I made some sort of obvious mistake ... if I did, I'm sorry for wasting your time
The text was updated successfully, but these errors were encountered: