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.

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

Fix snark pool long async cycles (merge into berkeley) #13556

Merged
merged 8 commits into from
Jul 12, 2023

Conversation

nholland94
Copy link
Member

Merges #13409 into berkeley.

@nholland94 nholland94 requested review from a team as code owners July 10, 2023 18:01
@nholland94
Copy link
Member Author

!ci-build-me

@nholland94 nholland94 changed the title Fix snark pool long async cycles (merge into berkeley) [DO NOT MERGE] Fix snark pool long async cycles (merge into berkeley) Jul 10, 2023
@nholland94
Copy link
Member Author

nholland94 commented Jul 10, 2023

I messed up the base of this PR, fixing now.

EDIT: fixed

@nholland94 nholland94 force-pushed the fix/snark-pool-long-async-cycles-berkeley branch from ca8bded to 1708deb Compare July 10, 2023 18:09
@nholland94 nholland94 changed the title [DO NOT MERGE] Fix snark pool long async cycles (merge into berkeley) Fix snark pool long async cycles (merge into berkeley) Jul 10, 2023
@nholland94
Copy link
Member Author

!ci-build-me

@nholland94 nholland94 force-pushed the fix/snark-pool-long-async-cycles-berkeley branch from 1708deb to 689faea Compare July 10, 2023 18:28
@nholland94
Copy link
Member Author

!ci-build-me

@nholland94
Copy link
Member Author

!ci-build-me

@deepthiskumar
Copy link
Member

!approved-for-mainnet

@nholland94
Copy link
Member Author

!ci-build-me

@nholland94 nholland94 merged commit 6fbd330 into berkeley Jul 12, 2023
45 checks passed
@nholland94 nholland94 deleted the fix/snark-pool-long-async-cycles-berkeley branch July 12, 2023 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants