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

Disable rate limitting for snark works #14174

Merged
merged 1 commit into from
Sep 21, 2023
Merged

Disable rate limitting for snark works #14174

merged 1 commit into from
Sep 21, 2023

Conversation

georgeee
Copy link
Member

@georgeee georgeee commented Sep 21, 2023 •
edited
Loading

Disable rate limitting for snark works

Explain how you tested your changes:

  • Tested on a cluster

Checklist:

  • Dependency versions are unchanged
    • Notify Velocity team if dependencies must change in CI
  • Modified the current draft of release notes with details on what is completed or incomplete within this project
  • Document code purpose, how to use it
    • Mention expected invariants, implicit constraints
  • Tests were added for the new behavior
    • Document test purpose, significance of failures
    • Test names should reflect their purpose
  • All tests pass (CI will check this if you didn't)
  • Serialized types are in stable-versioned modules
  • Does this close issues?

@georgeee georgeee requested a review from a team as a code owner September 21, 2023 15:34
@georgeee
Copy link
Member Author

!ci-build-me

@deepthiskumar
Copy link
Member

!approved-for-mainnet

@georgeee georgeee merged commit de03589 into berkeley Sep 21, 2023
2 checks passed
@georgeee georgeee deleted the georgeee/disable-snark-work-rate-limiting branch September 21, 2023 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@deepthiskumar deepthiskumar deepthiskumar approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@georgeee @deepthiskumar