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

ParserError when running on Windows #7

Open
jpsim opened this issue Nov 3, 2020 · 5 comments
Open

ParserError when running on Windows #7

jpsim opened this issue Nov 3, 2020 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@jpsim
Copy link

jpsim commented Nov 3, 2020

Thanks for publishing such a useful project! I'm trying to SSH into a Windows actions runner using this project, but there appears to be a parser error:

ParserError: D:\a\_temp\d0f821d0-9ab8-4cb8-8d5e-c5eafef37d6a.ps1:54
Line |
  54 |      net user $env:UserName ***
     |                                                 ~
     | Missing closing ')' in expression.

Here's a permalink to the CI job where this is happening: https://github.com/jpsim/Yams/pull/282/checks?check_run_id=1348666021

I'll see if setting a Username env variable in my action fixes this and report back.

@jpsim
Copy link
Author

jpsim commented Nov 3, 2020

I'll see if setting a Username env variable in my action fixes this and report back.

This didn't help.

@luchihoratiu
Copy link
Owner

luchihoratiu commented Nov 4, 2020

Hi @jpsim, thank you for trying out the action and raising this issue!
I will take a closer look at this later on today but until then I think I have an idea: trying a different password in your secrets.SSH_PASS as it might have special characters interfering with the command (like a ( and now it's expecting a ) also).
Please let me know if by any chance that would be a good workaround 😄

@luchihoratiu luchihoratiu self-assigned this Nov 4, 2020
@luchihoratiu luchihoratiu added the bug Something isn't working label Nov 4, 2020
@jpsim
Copy link
Author

jpsim commented Nov 4, 2020

You got it, my password had a (. Changing it to something without parentheses worked! Thanks for the quick reply.

@jpsim
Copy link
Author

jpsim commented Nov 4, 2020

For anyone else landing here, the next password I tried after removing the parentheses didn't fail the ngrok setup but I still couldn't use it to SSH to the runner. It had a $ character which may have been the culprit. The third password I tried fully worked. Once I'm done debugging I'll post the working version here.

@jpsim
Copy link
Author

jpsim commented Nov 4, 2020

Alright you shouldn't use this exact password, but it might help to see what worked for me if you're having trouble getting something with a format that works for you: ZZFR2_QvYM466wREnRu~.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants