"Failed to call GitHub Status API" with blank errors.

[Zee2]

Describe the bug

Trying to setup super-linter and I can't get it to report statuses correctly, and I'm also getting these mysterious status API failures.

2022-07-11 23:53:51 [INFO]   ERROR! Failed to call GitHub Status API!
2022-07-11 23:53:51 [INFO]   ERROR:[]
2022-07-11 23:53:51 [INFO]   ERROR! Failed to call GitHub Status API!
2022-07-11 23:53:51 [INFO]   ERROR:[]
2022-07-11 23:53:52 [INFO]   ERROR! Failed to call GitHub Status API!
2022-07-11 23:53:52 [INFO]   ERROR:[]
2022-07-11 23:53:52 [INFO]   ERROR! Failed to call GitHub Status API!
2022-07-11 23:53:52 [INFO]   ERROR:[]
2022-07-11 23:53:52 [INFO]   ERROR! Failed to call GitHub Status API!
2022-07-11 23:53:52 [INFO]   ERROR:[]

I am passing in the token correctly with GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}.

Expected behavior

The status is set correctly and no Status API errors appear.

Steps to Reproduce

My workflow file looks like:

name: Lint
on:
  push:
    branches: ["foobar"]
  pull_request:
    branches: ["foobar"]

jobs:
  lint:
    runs-on: ubuntu-latest

    steps:
    - name: Checkout
      uses: actions/checkout@v3
      with:
        # Full git history is needed to get a proper list of changed files within `super-linter`
        fetch-depth: 0
    
    - name: Lint
      uses: github/super-linter@v4
      env:
        VALIDATE_ALL_CODEBASE: false
        DEFAULT_BRANCH: foobar
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Additional context

Possibly related to #556?

[Zee2]

Ah, same as #2641, too!

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

If you're a maintainer, you can stop the bot to mark this issue as stale in the future by adding the O: backlog 🤖 label`.

[Zee2]

This is still an issue for us :(

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

If you're a maintainer, you can stop the bot to mark this issue as stale in the future by adding the O: backlog 🤖 label`.

[Zee2]

Still an issue....

[sid-am-ahd935]

Any workarounds for this??

[ferrarimarco]

Hi! To troubleshoot this issue, we need to be able to reproduce it. Can you please provide an example of a source file that triggers this?

[eitsupi]

I have been using supler-linter for the past several months and have rarely seen this error not occur and occur in most cases.
rocker-org/rocker-versioned2#516

The source code being linted did not appear to be related to the error (i.e., the error may or may not have occurred in the same PR).
(That is, there were cases where the error did not occur within the same PR, but the cases where the error did not occur were so rare that I forgot which PR it was.)

[ferrarimarco]

I suspect it's some kind of transient error. Given that we didn't enable --show-error but we did enable silent mode when using cURL to call the status API, we aren't going to get any output to investigate. I'm going to add the --show-error in #3367 with the hope that the curl error output gives us some hints about what went wrong.

[ferrarimarco]

@Zee2 now that we merged #3367, we're going to get more detailed output. I'm going to close this one, but please open a new issue once you're able to reproduce this, or to get any output. I'll keep an eye on this as well.

[Zee2]

@ferrarimarco , thanks so much for taking a look at this and responding. I'll give it another whirl and see what happens.

[eitsupi]

https://github.com/rocker-org/website/pull/72/checks#step:4:122

It doesn't look like anything has changed to me.

Edit: These haven't been shipped yet, have they?

[Zee2]

Alrighty! @ferrarimarco , it's failing w/ an HTTP 403.

[Zee2]

@ferrarimarco followup is here: https://github.com/github/super-linter/issues/3419

[shaneholloman]

still an issue in v5

name: superlint

'on':
  workflow_dispatch:
  push:
    branches: ["main"]
  pull_request:
    branches: ["main"]
jobs:
  run-lint:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Lint Code Base
        uses: github/super-linter@v5
        env:
          VALIDATE_ALL_CODEBASE: true
          VALIDATE_JSCPD: false
          VALIDATE_POWERSHELL: false
          DEFAULT_BRANCH: "main"
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          LINTER_RULES_PATH: .github/linters
          FILTER_REGEX_EXCLUDE: docker-compose/.env
          # This excludes the .env file from being linted on purpose since it is an example file only

2024-02-05 05:04:05 [INFO]   File:[/github/workspace/templates/unpackerr.yml]
2024-02-05 05:04:05 [INFO]    - File:[unpackerr.yml] was linted with [yamllint] successfully
2024-02-05 05:04:05 [INFO]   ----------------------------------------------
2024-02-05 05:04:05 [INFO]   ----------------------------------------------
2024-02-05 05:04:05 [INFO]   The script has completed
2024-02-05 05:04:05 [INFO]   ----------------------------------------------
2024-02-05 05:04:05 [INFO]   ----------------------------------------------
2024-02-05 05:04:06 [INFO]   ERROR! Failed to call GitHub Status API!
2024-02-05 05:04:06 [INFO]   ERROR:[curl: (22) The requested URL returned error: 403]
2024-02-05 05:04:06 [INFO]   ERROR! Failed to call GitHub Status API!
2024-02-05 05:04:06 [INFO]   ERROR:[curl: (22) The requested URL returned error: 403]
2024-02-05 05:04:06 [INFO]   ERROR! Failed to call GitHub Status API!
2024-02-05 05:04:06 [INFO]   ERROR:[curl: (22) The requested URL returned error: 403]
2024-02-05 05:04:06 [INFO]   ERROR! Failed to call GitHub Status API!
2024-02-05 05:04:06 [INFO]   ERROR:[curl: (22) The requested URL returned error: 403]
2024-02-05 05:04:06 [INFO]   ERROR! Failed to call GitHub Status API!
2024-02-05 05:04:06 [INFO]   ERROR:[curl: (22) The requested URL returned error: 403]
2024-02-05 05:04:06 [INFO]   ERROR! Failed to call GitHub Status API!
2024-02-05 05:04:06 [INFO]   ERROR:[curl: (22) The requested URL returned error: 403]
2024-02-05 05:04:06 [INFO]   ERROR! Failed to call GitHub Status API!
2024-02-05 05:04:06 [INFO]   ERROR:[curl: (22) The requested URL returned error: 403]

[jasonkarns]

And v6 (statuses: write permission is granted but still every few runs fails to report statuses)