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

clarity-wasm merge develop #5239

Merged
merged 522 commits into from
Oct 7, 2024

Conversation

csgui
Copy link

@csgui csgui commented Sep 25, 2024

Merge develop into feat/clarity-wasm-develop branch.

jferrant and others added 30 commits September 12, 2024 19:41
This matches the actual timeout that was hard-coded before this change.
…xes-jude

Feat/more multi miner fixes jude
fix: Improve DB deadlock detection/logging
merge 2.5.0.0.7 release branch to develop
chore: add info to signature gathering failure logs
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
jcnelson and others added 18 commits September 23, 2024 17:38
…acks-core into feat/signature-count-endpoint
…-command

feat/monitor-signers CLI command to poll signer stackerdb messages
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
test: add `BITCOIND_TEST=1` for running tests in VSCode
@csgui csgui requested review from a team as code owners September 25, 2024 08:19
@csgui csgui requested a review from obycode September 25, 2024 08:20
Copy link
Contributor

@obycode obycode left a 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?

@csgui
Copy link
Author

csgui commented Oct 7, 2024

No tricky conflicts were present. Most of them, if I recall correctly, were related to dependencies on a Cargo.toml.

@csgui csgui merged commit 9c83c35 into feat/clarity-wasm-develop Oct 7, 2024
1 check passed
@csgui csgui deleted the chore/clarity-wasm-merge-develop branch October 7, 2024 16:16
@blockstack-devops
Copy link
Contributor

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.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Oct 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.