-
Notifications
You must be signed in to change notification settings - Fork 59
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
Fails on Windows Github CI with powershell #50
Comments
Also, looks like the python version is wrong for windows:
But then it also looks like these binaries are missing: I guess it should be .exe? failing CD: Once I do that though I still get the issue above. Hrm that might be it, however when I use windows powershell on both sides it just hangs. |
Hi @madhavajay, Thanks for the detailed issue. Honestly I didn't put much time into windows support for tunshell so I don't believe that it is going to be an easy solve and may require updates to how the shell pty is handled on windows. Also would welcome any PR's which improve platform support :) |
It seems that the problem is happening on the connection client side (i.e. L side) With L side logs:
With debugger, I'm able to decrypt a sample last message:
Easy to guess it's type_id 3, 0x1d4 length, message, which I believe it's the old Stdout message of ShellServerMessage, which is updated to RemotePtyData message in aa7a3b7 So how on earth you only updated the Linux client but not the windows one? I strongly suggest you to release the client binary in Github Release for a better version tracking EDIT: I know why you deployed half of them: Because you wrote GitHub Actions script in an unsafe & inconsistent way.. |
Thanks for the detailed bug report @NyaMisty, feel free to submit a PR with the fixes! |
project new titel : DEAD |
Hi,
I have tried a task like this:
And I also tried
shell: pwsh
but they both give the following error on my side or the web browser version.Any ideas why?
The text was updated successfully, but these errors were encountered: