Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[CI] The release API rate limit #619

Closed
Aisuko opened this issue Sep 12, 2023 · 5 comments
Closed

[CI] The release API rate limit #619

Aisuko opened this issue Sep 12, 2023 · 5 comments
Assignees
@leecalcote
Labels
area/ci Continuous integration | Build and release issue/stale Issue has not had any activity for an extended period of time

Comments

@Aisuko
Copy link
Member

Aisuko commented Sep 12, 2023

Current Behavior

Run pozetroninc/github-action-get-latest-release@master
  with:
    repository: istio/istio
    excludes: prerelease, draft, edge
  env:
    version: edge
Error: API rate limit exceeded for [1](https://github.com/meshery/meshery-linkerd/actions/runs/6151256549/job/16690944472?pr=544#step:4:1)7[2](https://github.com/meshery/meshery-linkerd/actions/runs/6151256549/job/16690944472?pr=544#step:4:2).176.205.12[3](https://github.com/meshery/meshery-linkerd/actions/runs/6151256549/job/16690944472?pr=544#step:4:3). (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)

Desired Behavior

Shall we increase the API rate limit or remove this step? The CI failed makes the PR hard to get to merge.

Implementation

Acceptance Tests

Contributor Guides and Resources
@Aisuko Aisuko added the area/ci Continuous integration | Build and release label Sep 12, 2023
@welcome
Copy link

welcome bot commented Sep 12, 2023

Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Contributors' Welcome Guide and sure to join the community Slack.

@stale
Copy link

stale bot commented Oct 17, 2023

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

@stale stale bot added the issue/stale Issue has not had any activity for an extended period of time label Oct 17, 2023
@stale
Copy link

stale bot commented Oct 28, 2023

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

@stale stale bot closed this as completed Oct 28, 2023
@Aisuko Aisuko reopened this Oct 29, 2023
@stale stale bot removed the issue/stale Issue has not had any activity for an extended period of time label Oct 29, 2023
@stale Stale
Copy link

stale bot commented Dec 3, 2023

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

@stale stale bot added the issue/stale Issue has not had any activity for an extended period of time label Dec 3, 2023
@stale Stale
Copy link

stale bot commented Dec 13, 2023

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

@stale stale bot closed this as completed Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@leecalcote leecalcote

Labels
area/ci Continuous integration | Build and release issue/stale Issue has not had any activity for an extended period of time
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@leecalcote @Aisuko