Unstable on Mac due to GitHub API restrictions

[xaviergmail]

I have been consistently running across this error when trying to use tmate on a macos-10.15 runner:

==> Installing dependencies for tmate: libssh and msgpack
==> Installing tmate dependency: libssh
==> Pouring libssh-0.9.5_1.catalina.bottle.tar.gz
🍺  /usr/local/Cellar/libssh/0.9.5_1: 23 files, 1.2MB
==> Installing tmate dependency: msgpack
==> Pouring msgpack-3.3.0.catalina.bottle.tar.gz
🍺  /usr/local/Cellar/msgpack/3.3.0: 757 files, 5.2MB
==> Installing tmate
==> Pouring tmate-2.4.0.catalina.bottle.tar.gz
🍺  /usr/local/Cellar/tmate/2.4.0: 9 files, 660.9KB
Error: HttpError: API rate limit exceeded for 199.19.85.34. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)

I'm not sure what exactly is triggering this, but I am in fact using limit-access-to-actor which relies on octokit

      - name: Setup tmate session
        uses: mxschmitt/action-tmate@v3
        with:
          limit-access-to-actor: true

It seems to be related to this: actions/runner-images/issues/602

Looking at octokit's documentation, it seems setting the GITHUB_TOKEN environment variable might be enough to authenticate the user. I will try that and report back with anything I find. Edit: I have yet again come across the same error with the GITHUB_TOKEN environment variable set

[obraunsdorf]

Same issue for me

[andreineculau]

As per https://github.com/octokit/rest.js/blob/master/docs/src/pages/api/01_authentication.md and https://github.com/octokit/auth-action.js

It does not require any configuration, but instead reads the GITHUB_TOKEN environment variable that is provided to GitHub Actions.

That doesn't seem to be the case though, exposing env: {GITHUB_TOKEN: {{ secrets.GITHUB_TOKEN }} } in my yaml workflow, hits the same issue.

[norm]

It's a limit enforced by tmate.io, not a GitHub thing. I've fixed this in one of my workflows by getting an API key from tmate, and setting it up:

  - name: Add tmate API key
    env:
      TMATE_API_KEY: ${{ secrets.TMATE_API_KEY }}
    run: |
      echo "set tmate-api-key '$TMATE_API_KEY'" > ~/.tmate.conf

... but it would be nice if that was done through a with option in this Action.

[mxschmitt]

Closing, since multiple different issues are mixed here.

HttpError: API rate limit exceeded for 199.19.85.34. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)

This is about the GitHub API, this has nothing to do with tmate.

Closing for now, for further issues please open new issues, thanks!

[rfay]

Github seems to have started limiting things far more in recent days, is there a way we could make it use GITHUB_TOKEN?

I'm getting this every single attempt today (and seeing it on unrelated tests that use github api as well):

Error: HttpError: API rate limit exceeded for 199.19.85.26. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)

[rfay]

Could we please reopen this and see if there's a way to get a token in there?

==> Running brew cleanup tmate...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see man brew).
Error: HttpError: API rate limit exceeded for 199.7.166.17. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)

[rfay]

I see this gist that may help here: https://gist.github.com/willgarcia/7347306870779bfa664e

[rfay]

It looks like just adding this to the test yml file:

    env:
      HOMEBREW_GITHUB_API_TOKEN: ${{ secrets.GITHUB_TOKEN }}