vscode-github-actions icon indicating copy to clipboard operation
vscode-github-actions copied to clipboard

Resource not accessible by integration (textDocument/hover and expand repository secrets)

Open savannahostrowski opened this issue 1 year ago • 7 comments

Describe the bug A clear and concise description of what the bug is.

To Reproduce I get the same error when I 1) try to view repo secrets/variables and 2) hover on environment variables referenced in my workflow file

  1. Open "Settings pane"
  2. Expand "Secrets" > "Repository Secrets"

OR

  1. Hover an environment variable in my workflow file

Expected behavior Expect to see repo secrets/variables set.

Screenshots image image

Extension Version v0.25.7

Additional context I'm working in Codespaces

savannahostrowski avatar May 19 '23 19:05 savannahostrowski

I'll also add that all the icons sporadically disappear for running pipelines (e.g. spinners, refresh icon etc.)

savannahostrowski avatar May 22 '23 19:05 savannahostrowski

textDocument/completion also trigger this error when completing actions context. Tested in codespaces with original settings.

I am only able to reproduce the error in the codespaces.

memchr avatar Jul 29 '23 08:07 memchr

This may be a problem with the universal devcontainer used as the default codespace container. I haven't been able to reproduce the problem with the custom devcontainer

memchr avatar Jul 29 '23 18:07 memchr

I have a very similar error, but for me it's the organisational secrets, while using GHE

  request: {
    method: 'GET',
    url: 'https://xxxxxxxxx/api/v3/repos/xxxxx/xxxxxx/actions/organization-variables?per_page=100',
    headers: {
      accept: 'application/vnd.github.v3+json',
      'user-agent': 'VS Code GitHub Actions (0.26.2) octokit-rest.js/19.0.7 octokit-core.js/4.1.0 Node.js/18.15.0 (linux; x64)',
      authorization: 'token [REDACTED]'
    },
    request: { hook: [Function: bound bound e] }
  }
}
Failure to retrieve organization secrets:  Cs [HttpError]: Not Found

ragchuck avatar Sep 13 '23 07:09 ragchuck

A workaround is to open up the Command Palette, type "secret", and follow the prompts there. @memchr what do you mean by the custom dev container? Can you provide the container configuration file?

sgbaird avatar Nov 23 '23 15:11 sgbaird

I'm dealing with the same issue - what prompt are we talking about here? The only option I get from the command pallet when I type "secret" is to manage my codespaces secrets

lemisieur avatar May 22 '24 11:05 lemisieur

@sgbaird I'm also interested in knowing what prompts you're referring to. I get an option to manage my codespaces secrets, but I'm not sure in what way I'm supposed to manage them in order to make this work.

odonnellmichael avatar Jun 04 '24 13:06 odonnellmichael

Have the same issue on codespaces and it is becoming increasing annoying... The response code 403 suggest that the codespace is using token without the necessary rights. Simple test confirms that: image

However neither overwriting the token in devcontainer json (terminal.integrated.env.linux and runArgs) nor setting additional permissions for the repository seems to be working.... image

marcin-sg avatar Oct 17 '24 15:10 marcin-sg