-
Notifications
You must be signed in to change notification settings - Fork 671
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
clarity-wasm merge develop #5239
clarity-wasm merge develop #5239
Conversation
Test partial tenure fork
… into feat/use-burnchain-timeout
This matches the actual timeout that was hard-coded before this change.
…xes-jude Feat/more multi miner fixes jude
…diately on burncahin tip change
…achine Fix/signer block state machine
fix: Improve DB deadlock detection/logging
merge 2.5.0.0.7 release branch to develop
chore: add info to signature gathering failure logs
… into feat/use-burnchain-timeout
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
…acks-core into feat/signature-count-endpoint
…erence Fix/5193 stackerdb decoherence
…-command feat/monitor-signers CLI command to poll signer stackerdb messages
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
feat: Signer signature count endpoint
test: add `BITCOIND_TEST=1` for running tests in VSCode
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems okay to me. Were there any tricky conflicts that could use a closer look?
No tricky conflicts were present. Most of them, if I recall correctly, were related to dependencies on a Cargo.toml. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Merge
develop
intofeat/clarity-wasm-develop
branch.