Skip to content

ci.yaml validation failing on You have exceeded a secondary rate limit #102402

Description

Activity

  1. CaseyHillers commented on Apr 22, 2022

    @CaseyHillers
    ContributorAuthor

    In the past, this happened as we were generating the github access token too frequently. Last time I added a cache handler around it so we only generate it every ~7 minutes. I'm not sure why this would happen again

  2. added
    in triagePresently being triaged by the triage team
    team-infraOwned by Infrastructure team
    and removed
    in triagePresently being triaged by the triage team
    on Apr 25, 2022
  3. keyonghan commented on May 13, 2022

    @keyonghan
    Contributor
  4. keyonghan commented on May 25, 2022

    @keyonghan
    Contributor

    This happens more frequently in flake bot when making github API calls more frequently within a short time:
    https://github.com/flutter/flutter/pull/104627/checks?check_run_id=6595824741
    https://github.com/flutter/flutter/pull/104624/checks?check_run_id=6595822201

  5. keyonghan commented on Jun 8, 2022

    @keyonghan
    Contributor

    This happened on multiple flake bot PRs. Will take a look.

  6. self-assigned this
    on Jun 8, 2022
  7. keyonghan commented on Jun 24, 2022

    @keyonghan
    Contributor

    This issue happens only when scheduling large numbers of check runs in pre-submit in a short time.

    Based on Dealing with secondary rate limits:

    If you're making a large number of POST, PATCH, PUT, or DELETE requests for a single user or client ID, wait at least one second between each request.
    

    I am adding some more logs in flutter/cocoon#1938 for validation.

  8. keyonghan commented on Jun 30, 2022

    @keyonghan
    Contributor

    Haven't seen this in the past week. Needs a further look when this repros.

  9. added
    P1High-priority issues at the top of the work list
    on Jul 12, 2022
  10. keyonghan commented on Jul 12, 2022

    @keyonghan
    Contributor

    Still no repros in past weeks. Moving this to TD with P3 for further monitoring.

  11. CaseyHillers commented on Jul 12, 2022

    @CaseyHillers
    ContributorAuthor

    \cc @XilaiZhang (for context about why Google Testing can't create a token for every request)

  12. keyonghan commented on Aug 15, 2022

    @keyonghan
    Contributor

    Another instance: https://github.com/flutter/flutter/pull/109540/checks?check_run_id=7842906196
    where multiple commits are pushed around the same time

  13. 25 remaining items

  14. keyonghan commented on Feb 1, 2024

    @keyonghan
    Contributor

    Reopening as this issue has most of related context.
    https://github.com/flutter/flutter/pull/142590/checks?check_run_id=21054601140.

    GitHub Error: You have exceeded a secondary rate limit. Please wait a few minutes before you try again. If you reach out to GitHub Support for help, please include the request ID D3D8:58A4:21BC33D:448A492:65BA10F7.
    
  15. moved this from To be archived to In progress in [DEPRECATED] Infra Ticket Queueon Feb 1, 2024
  16. keyonghan commented on Feb 1, 2024

    @keyonghan
    Contributor

    This happened only on flake/deflake PRs, and the flaky bot API seems broken this week and may have caused multiple PRs filed in a very short time.

  17. unlocked this conversation on Feb 2, 2024
  18. added
    P2Important issues not at the top of the work list
    and removed
    P1High-priority issues at the top of the work list
    on Mar 27, 2024
  19. github-actions commented on Jun 7, 2024

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  20. locked as resolved and limited conversation to collaborators on Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listteam-infraOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure team

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions