Unable to connect to the GitHub API , Please check your internet connection. Installed in WSL

[0lzi]

Describe the bug
After installing this in WSL and logging in I receive the below message.

To Reproduce
Steps to reproduce the behavior:

1. Install extension in WSL workspace
2. Login to Github and authorise with org
3. See error

Expected behavior

1. Install extension in WSL workspace
2. Login to Github and authorise with org
3. It Works as expected

Screenshots

Extension Version
v0.25.3

Additional context
Add any other context about the problem here.

[briantist]

I have the same issue. When I click Refresh I get no error, only this message:

[areifert]

Clicking on the Refresh button (in the GitHub Actions tab) does nothing for me either. Checking the developer console in VS Code, I'm seeing the following error:

ERR command 'github-actions.explorer.refresh' not found: Error: command 'github-actions.explorer.refresh' not found
    at v.k (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1552:2618)
    at v.executeCommand (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1552:2534)
    at async i.open (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:615:42187)
    at async h.open (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:615:43698)

[0lzi]

I get this error in Console

  ERR Cannot get default system shell when there is no backend for remote authority 'wsl+ubuntu-22.04': Error: Cannot get default system shell when there is no backend for remote authority 'wsl+ubuntu-22.04'
    at Object.getDefaultSystemShell (vscode-file://vscode-app/c:/Users/user/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1702:6416)
    at async i.v (vscode-file://vscode-app/c:/Users/user/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1695:18520)
    at async i.r (vscode-file://vscode-app/c:/Users/user/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1695:17783)
    at async i.getDefaultProfile (vscode-file://vscode-app/c:/Users/user/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1695:17114)
    at async i.o (vscode-file://vscode-app/c:/Users/user/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1695:15825)

[KetchupOnMyKetchup]

I am investigating this bug now and was able to repro.

There are a couple of workarounds for now that worked for me using WSL Ubuntu 22.04 that you can try for now while I investigate:

1. Login to GitHub using VS Code on Windows without connecting to WSL, then connect to WSL
2. Login, see the failure, reload VS Code (Ctrl + Shift + P, then type in Developer: Reload Window)
   

[areifert]

I'm actually seeing this bug on a (M1) Mac rather than Windows. It seems to not be installing at all. The VS Code developer console shows the following after attempting to uninstall and reinstall the plugin:

Activating extension 'github.vscode-github-actions' failed: Not Found.

[KetchupOnMyKetchup]

@areifert Would you mind opening a separate issue for that issue with reinstalling the plugin with repro steps / screenshots so we can address that separately?

[areifert]

Created separate issue: #93

[KetchupOnMyKetchup]

This should be fixed in the newly released version 0.25.4

[0lzi]

Login to GitHub using VS Code on Windows without connecting to WSL, then connect to WSL
Login, see the failure, reload VS Code (Ctrl + Shift + P, then type in Developer: Reload Window)

This didnt fix it for me. It says Unable to find a Git executable I am guessing I would need to install Git in Windows first

[lebrice]

@KetchupOnMyKetchup This is still happening to me in v0.26.2

[scottco-slalom]

This fixed this issue for me:
#251 (comment)