search

github / vscode-github-actions

GitHub Actions extension for VS Code
https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-github-actions
MIT License
476 stars 72 forks source link

Unable to connect to the GitHub API, please check your internet connection. #295

Closed Nheverest closed 5 months ago

Nheverest commented 5 months ago

Describe the bug GitHub Actions extension displays: 'Unable to connect to the GitHub API, please check your internet connection.'

To Reproduce Follow the 'Getting started' documentation of the extension

  1. Install the extension from the Marketplace => OK
  2. Sign in with your GitHub account and when prompted allow GitHub Actions access to your GitHub account => OK
  3. Open a GitHub repository => OK
  4. You will be able to utilize the syntax features in Workflow files => OK
  5. and you can find the GitHub Actions icon on the left navigation to manage your Workflows => The icon only diplays the message 'Unable to connect to the GitHub API'

Expected behavior The extension should enable workflow management, and should be able to connect to Github.

Screenshots n.a.

Extension Version v0.26.2

Additional context VS Code 1.86.2, behing a proxy set in VS Code.

CoPilot extension works fine.

Python extension works fine.

Installing, re-installing the GitHub Actions extension, signing out/in, etc. nothing helped.

Output extract:

Activating GitHub Actions extension...
Error getting GitHub context
fetch failed
HttpError: fetch failed
impks27 commented 5 months ago

Facing the same issue. What has changed? The same plugin version used to work before. Did any of the dependent plugins change?

krisdehe commented 5 months ago

Hi, same issue but not the same error message image

Cannot fetch github context
Error: Cannot fetch github context
    at vt (c:\Users\user\.vscode\extensions\github.vscode-github-actions-0.26.2\dist\extension-node.js:2:1444927)
    at c:\Users\user\.vscode\extensions\github.vscode-github-actions-0.26.2\dist\extension-node.js:2:1626446
    at s.h (c:\Users\user\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:150:175235)
lfvdaniel commented 5 months ago

We are also seeing this issue.

impks27 commented 5 months ago

Was anybody able to fix this? This definitely seems to be a bug.

AaronMT commented 5 months ago

First time user of this extension and am seeing this too. Not the best experience off the bat.

KetchupOnMyKetchup commented 5 months ago

Hi there, I am so sorry about this experience. We currently don't support proxies but have plans to and understand that it is important for our customers and that it is frustrating to not be able to use the extension and that Copilot does have this feature. I just added a note in the README.md so it can be publicly documented: https://github.com/github/vscode-github-actions?tab=readme-ov-file#supported-features

@impks27 - There haven't been any recent changes. Are you using a proxy or was one added? Here are some troubleshooting steps in case you aren't using a proxy, and please reach out if these don't help. Sometimes re-installing the extension and reloading will help get it working (without a proxy):

I would like to close this issue in favor of this one (to avoid dupes and easier tracking) which has already been opened and is tracked and triaged on our project board once I get more information about the above issue with it having worked in the past but not anymore.
https://github.com/github/vscode-github-actions/issues/189

The above issue are important and tracked in our triaged section of our backlog along with the OS certificates which is related - https://github.com/orgs/github/projects/9557/views/1

Nheverest commented 5 months ago

Hello,

I am ok with closing this issue in favour of #189, though the title is a little bit misleading. I have subscribed to #189. I let you close this one.

Thanks!

KetchupOnMyKetchup commented 5 months ago

Thank you so much for being understanding. I changed the name of it to "Proxy Support for VS Code Actions Extension" to make it more clear so that it doesn't sound specific to language server since the overall goal is to get it working for the extension in general. You are right it is confusing, I appreciate you pointing that out. Ok, closing this one in favor of #189