IBM Blockchain Platform Extension for VS Code disconnects from WSL Ubuntu

[collaboration-tools]

(Moved to this repository by request of @cazfletch)

On opening the extension, for example by clicking where the icon should be, it shows the panels for the extension but at the bottom left hand side instead of "WSL: Ubuntu" it changes to "Disconnected from WSL: Ubuntu", and brings up a dialog "Attempting to reconnect..." which hangs.

Also, the Extension icon is not shown in the navigation bar, just a blank spot where it should be (still clickable to open the extension).

Prior to installing VS Code, Docker Desktop was running Hyperledger Fabric containers, i.e., Linux has the necessary Node packages installed. The same behaviour occurs in VS Code on removing the containers and quitting Docker.

Windows 10 Pro 10.0.18362
Visual Studio Code 1.37.1
IBM Blockchain Platform Extension for VS Code 1.0.8

[cazfletch]

Hi @keith-harrison-broninski i tried this out using ssh rather than wsl. I don't get exactly the same problem however i do get problems. For now the answer is that the extension doesn't work with remote development but we plan to make it work in the future.

[collaboration-tools]

@cazfletch Thanks.

Just as a note, I tried running VS Code from Windows rather than from WSL Ubuntu, and (although the extension icon then appears) get exactly the same behaviour.

Do you have a timeframe for fixing this? Seems like something a lot of people would find useful!

[mattcarp]

I can confirm that this extension also does not work using remote development via SSH on an EC2 Ubuntu server (18.04). However, error messages are of the type: command 'aPackagesExplorer.createSmartContractProjectEntry' not found (in other words, commands from the activationEvents key in package.json).

I've tried rebuilding grpc in the ~/.vscode-server/extensions/ibmblockchain.ibm-blockchain-platform-1.0.8 directory using the following:

npm rebuild grpc --target=4.2.5 --runtime=electron --dist-url=https://atom.io/download/electron --update-binary --fallback-to-build --target_arch=x64

But no luck.

Works well locally on my Mac though. Would be great to have this running for remote development since it would simplify setting up dev chains in the cloud.

Thanks.

[EdMoffatt]

Hey @bizbi - thank you for raising! @cazfletch 's looking into the fix for this :)

Not related to this issue specifically, but I was wondering if you would mind letting me know why you use Remote Development? I'd not heard of it until folks raised issues, so it wasn't a usage-pattern I'd thought of before. I'm a User Experience Designer working on this dev tooling, so I appreciate any chance to learn about how people want to use it!

GitHub reply is fine, or you could drop me an email edmoffat@uk.ibm.com if you prefer! Interested if you use Remote Dev to gain particular advantages for your workflow, or maybe to work around some restrictions you have? Cheers!

[collaboration-tools]

Hi Ed I am prototyping with fabric on a Windows laptop, so building a dev environment in WSL. Actually, now I've got further with it, I probably wouldn't run fabric in VS Code any more, since set up, test, and tear down of the environment is all scripted. But it would have been useful when doing the tutorial early on. Hope this helps, Best, Keith

…

On Tue, 15 Oct 2019 at 15:55, EdMoffatt ***@***.***> wrote: Hey @bizbi <https://github.com/bizbi> - thank you for raising! @cazfletch <https://github.com/cazfletch> 's looking into the fix for this :) Not related to this issue specifically, but I was wondering if you would mind letting me know why you use Remote Development? I'd not heard of it until folks raised issues, so it wasn't a usage-pattern I'd thought of before. I'm a User Experience Designer working on this dev tooling, so I appreciate any chance to learn about how people want to use it! GitHub reply is fine, or you could drop me an email ***@***.*** if you prefer! Interested if you use Remote Dev to gain particular advantages for your workflow, or maybe to work around some restrictions you have? Cheers! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1357?email_source=notifications&email_token=AAVKEJ5WKAQWXFSCGQVTRKDQOXKUFA5CNFSM4ISNHRV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBJCGTI#issuecomment-542253901>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAVKEJ2TK2P742ILF5OD3XDQOXKUFANCNFSM4ISNHRVQ> .

[cazfletch]

closing as not going to support WSL