Zowe Explorer is not working in Codespaces

[jellypuno]

Describe the bug

I am trying Github Codespaces and I installed Zowe Explorer. The extension loaded but I am not sure that it activated properly. There are no error message whatsoever. There are no buttons and if I try using the commands, it doesn't work.

To Reproduce

Activate Codespaces and Install ZE

Expected behavior

It should work similarly as the Desktop or theia

Screenshots

Desktop (please complete the following information):

• OS: Windows 11
• Zowe Explorer Version: latest
• (Optional) Zowe CLI Version: N/A
• (Optional) Are you using Secure Credential Store? none

Additional context

[github-actions]

Thank you for creating a bug report. If you haven't already, please ensure you have provided steps to reproduce it and as much context as possible.

[jellypuno]

I also don't know where to find the logs 😢

[jellypuno]

It works in Codespaces desktop

[traeok]

Wondering if this issue was specific to GitHub codespaces? I just tried installing Zowe Explorer in Codespaces (web) and it seems to be functional. The missing "+" button is now showing, the favorites nodes are back under each section. Will do some further testing and report back.

[JillieBeanSim]

I opened the web version of Github Codespaces and installed the Zowe Explorer extension and was able to create a v1 profile and team config but wasn't able to connect to the host with an ENOTFOUND error testing with multiple host connections (this could be due to firewall). Found where in the workspace we are storing the profile information
./home/codespace/.zowe

[JillieBeanSim]

we are seeing the same outcome as with #1798 @zFernand0 do we want to handle the same way? FYI @anaxceron

[zFernand0]

yeah, we should handle them the same way.
if we don't document unsupported ENVs then we should close both as not planned (for now) 😋

[zFernand0]

Given that we only document environments that we support...
Let's close this issue (as not planned - for now) since we can't claim we support this particular one yet.
We can revisit these connectivity/firewall challenges later on.