Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

HttpError: Resource not accessible by integration

See original GitHub issue

Error: HttpError: Resource not accessible by integration
Error: Resource not accessible by integration

This error always happened since yesterday (before yesterday, it works for many years):

https://github.com/apache/spark/actions/runs/3200342170/jobs/5227121801 https://github.com/apache/spark/actions/runs/3200342170/jobs/5227121801

Issue Analytics

State:
Created a year ago
Reactions:2
Comments:7 (2 by maintainers)

Top GitHub Comments

1reaction

Yikuncommented, Dec 20, 2022

@MaksimZhukov Thanks for your help and info!

0reactions

MaksimZhukovcommented, Dec 19, 2022

Here is the statement from the GitHub documentation:

The permissions for the GITHUB_TOKEN are initially set to the default setting for the enterprise, organization, or repository. If the default is set to the restricted permissions at any of these levels then this will apply to the relevant repositories. For example, if you choose the restricted default at the organization level then all repositories in that organization will use the restricted permissions as the default. The permissions are then adjusted based on any configuration within the workflow file, first at the workflow level and then at the job level.

I’ve created a workflow file without specifying the permissions key. Everything worked fine as long as my default permissions granted to GITHUB_TOKEN were permissive. It seems to me that your organization has restricted the default GITHUB_TOKEN permissions.

Also, I would like to mention that it is recommended to specify the permissions key in workflow file to configure the minimum required permissions for a workflow or job. This section was also included in the example in the README file in scope of the PR you mentioned.

I am closing the issue. Please contact us if you have any concerns.