Open sg- opened 3 years ago
The remote server includes several pieces of native code which would need us to produce and distribute builds for this architecture.
Hi, Is there any progress in the feature request? I am happy to help this if I can anything
Well, no one upvoted it so it was closed. The same problem applies for other architectures like s390x. I haven't checked ppc64.
Aha, and I noticed it is have been moved into Backlog milestone. Does it mean that is to develop this feature in the furture? If I am wrong please correct me.
Hello I am RISCV fan, Tell me where can i upvote the request. I will vote for it.
Here I share a WA solution before the request completely work. Mounting the RISCV filesystem to X86 ubuntu nfs server, And then using vscode remote-ssh connecting to the x86 ubuntu. It is same like working on riscv platform with vscode.
Is there any updates on this one?
This appears to be the case of a misleading error message. The ssh command I see that's used in the logging: Running script with connection command: "c:\windows\system32\openssh\ssh.exe" -T -D 30668 "192.168.1.45"
If I attempt to issue that command from my console, I type in my password and never get a response. If I drop the -T and -D parameters though, I successfully connect. It sounds like if the plugin doesn't get a response from the server after the password is entered, it gets interpreted as a not supported target. How an I tell the extension to not submit these two arguments?
any updates to connect risc-v arch
This feature would be much appreciated
"Could not establish connection to "riscv": The remote hosts' architecture is not supported."
Common Microsoft, provide RISC-V support!
"Could not establish connection to "riscv": The remote hosts' architecture is not supported."
Common Microsoft, drop RISC-V support!
I dont think you are using the word drop correctly.
also seems vscode is not so open source now that riscv64 comes into picture :DD, time to jump to vscodium
"Could not establish connection to "riscv": The remote hosts' architecture is not supported." Common Microsoft, drop RISC-V support!
I dont think you are using the word drop correctly.
also seems vscode is not so open source now that riscv64 comes into picture :DD, time to jump to vscodium
Oh, yeah. Release the RISC-V SSH functionality! I thought about the usage of drop like in "Dropped Release Date" :D
Maybe I will switch back to Emacs, I just moved back to VSCode because Lex Fridman also moved from Emacs to VSCode. But that it's not possible to use the SSH functionality with RISC-V machines, is frustrating.
I want to bump this issue. I am from RISC-V Lab Partners (an official subgroup of RISC-V international working on providing RISC-V instances). If you guys are low on bandwidth to spend on this project, we can port this extension to RISC-V using Cloud-V for you. Could you point me to the source code for adding the RISC-V support or the least you can do is inform us about the status of the RISC-V port of this extension?
You can also enroll yourself for Cloud-V to develop this using the RISC-V continuous integration service
I can provide free RISC-V servers & CI to test this on. Is anyone from Microsoft interested in porting this to RISC-V?
I have added riscv64 support to vscodium REH builds(you can expect the next release will include riscv64 support) and open-remote-ssh(not merged yet). Guess what? When proprietary fails to deliver, the solution is FLOSS!
I have added riscv64 support to vscodium REH builds(you can expect the next release will include riscv64 support) and open-remote-ssh(not merged yet). Guess what? When proprietary fails to deliver, the solution is FLOSS!
god bless open source
Steps to Reproduce:
uname -m