Skip to content
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

enter-grain error on Windows #264

Open
ocdtrekkie opened this issue Feb 20, 2020 · 3 comments
Open

enter-grain error on Windows #264

ocdtrekkie opened this issue Feb 20, 2020 · 3 comments
Labels

Comments

@ocdtrekkie
Copy link
Collaborator

I don't know what this means, but enter-grain did not work for me on my Windows machine.

PS C:\Users\ocdtr\Projects\Jupyter-Lab-Sandstorm> vagrant-spk enter-grain
Looking for apps in dev mode...
Looking for grains...

Error parsing line: 5037 ownership-correct c5Xv6FfWHKr9sGAbrP3hGd. Crashing.Traceback (most recent call last):
  File "<string>", line 1001, in <module>
  File "<string>", line 998, in main
  File "<string>", line 786, in shell
ValueError: need more than 3 values to unpack
vagrant-spk returned -1
@zenhack
Copy link
Collaborator

zenhack commented Feb 21, 2020

Looks like this line is returning something other than a 4-tuple:

supervisor_pid, ownership_check, grain_id, child_pid = line.split()

Maybe do some print debugging around there?

@ocdtrekkie
Copy link
Collaborator Author

Print debugging this on Windows is likely to be super difficult because packaging the EXE in the release script is a super pain in the rear. I probably should figure out how to set up a Python environment on my Windows PC such that I could play with the actual script file.

@ocdtrekkie
Copy link
Collaborator Author

It looks like 5037 ownership-correct c5Xv6FfWHKr9sGAbrP3hGd is missing the child_pid though, since it's looking for that after the grain_id, which we can see in that string.

@ocdtrekkie ocdtrekkie added the bug label Mar 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants