GitHub Codespaces Feedback: FAILED to deploy IntelliJ, WebStorm 2022.2.3EAP

[zudsniper]

Description Failure to deploy Remote Backend due to "Permission Denied" on GitHub Codespaces instances (4 cores, 8gb ram, 64 gb disk) Steps to reproduce

1. Create a GitHub Codespace I used github.com.
2. Run Gateway Beta 2022.2.4
3. Use GitHub Codespaces Jetbrains Client plugin to access previously created GitHub Codespace => resulting in the crash.

WARNING -- sorta long, skip through

Gateway-Crash-94.webm

Impact I am not able to use my remote development tools for my projects on GitHub Codespaces effectively. TESTED ON IntelliJ 2022.2.3 EAP, WebStorm 2022.2.3.EAP Additional context Native OS: Windwos Target OS: idk whatever codespaces are in by default (maybe this is the issue somehow...)

OS Version: 10.0
OS Architecture: amd64
IDE Version: 2022.2.4
Plugin Version: 0.2.0.896
Plugin path: C:\Users\jason\AppData\Local\JetBrains\Toolbox\apps\Gateway\ch-0\222.4459.11.plugins\github-codespaces-gateway
Plugin ID: com.github.codespaces.jetbrains.gateway

deploy-text-output.log host-logs.tar.gz

[shayneburgess]

Hey @zudsniper can you confirm if this happens on every Codespace you create or did it happen just once?

[zudsniper]

I will check when I can -- sorry for the delay. I'm able to use the tools now, but it's in an interesting situation: If I start via ${IDE} > File > Remote Development, I will *always *fail. I believe this is because I downgraded back to the stable versions of the apps not the EAP versions, and the few jetbrains client backends that I've installed are EAP. With that said, if I simply always start *from Gateway Beta, *I do not have this issue -- SAVE with gh codespaces, which still aren't booting -- however I only had time to try once.

Thanks for the response! I'm loving Space for my team & Gateway for myself, I've never interacted with a VPS this effectively -- but with that said, does it need to be so damn (computationally & monetarily! haha) expensive? One instance will easily thrash a 4GB RAM VM from my experience, which seems like a bit much? maybe I'm wrong.

Thanks again! Jason

On Tue, Nov 15, 2022 at 2:04 PM Shayne Burgess @.***> wrote:

Hey @zudsniper https://github.com/zudsniper can you confirm if this happens on every Codespace you create or did it happen just once?

— Reply to this email directly, view it on GitHub https://github.com/github/codespaces-jetbrains-feedback/issues/26#issuecomment-1315803684, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2U6HMS5I4H7FJL7RCLUELWIPUDFANCNFSM6AAAAAASA6V5WU . You are receiving this because you were mentioned.Message ID: @.***>

[zudsniper]

Hey @zudsniper can you confirm if this happens on every Codespace you create or did it happen just once?

@shayneburgess

Here's this morning with WebStorm once again

[zudsniper]

Sorry to spam of sorts but I just realized that that crash was actually initiated from just JetBrains Gateway, so it seems there is no way in for me now with these EAP thinClients installed, heh

[cmuto09]

Hey @zudsniper- thanks for the detailed report! It looks like there are some permissions issues with the underlying filesystem in your container that are disallowing JetBrains from installing the IDE correctly.

Are you able to share your repository or some details about your devcontainer.json configuration? Otherwise you could try to open up permissions within the filesystem of your container to see if that resolves your issue