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

feat: parse /stackerdb_chunks Stacks node event #653

Merged
merged 9 commits into from
Oct 16, 2024

Conversation

rafaelcr
Copy link
Collaborator

@rafaelcr rafaelcr commented Oct 14, 2024

Starts listening to the new /stackerdb_chunks Stacks node event and parses the incoming message. Parsers are taken from the stacks_codec crate, which has been updated with the latest serializers.

For future PRs:

  • Start integrating the signer messages into the predicates framework
  • Store signer messages in a local SQLite DB for replay
  • Expand unit tests to include full Stacks node integration tests

@rafaelcr
Copy link
Collaborator Author

Thanks for the comments @zone117x I'll be adding some unit tests today with your test payloads so we can merge this one ASAP

@rafaelcr rafaelcr marked this pull request as ready for review October 15, 2024 20:14
@rafaelcr rafaelcr requested a review from zone117x October 15, 2024 20:14
@rafaelcr
Copy link
Collaborator Author

@zone117x can you take a look? I added a unit test to check the parser behavior, but will expand the tests in a future PR. Right now, Chainhook has a strange way of depending on a local install of redis to run tests so it's tricky to run them in a local setup. I'll move that over to docker in the next PR and start adding some integration tests.

Copy link
Member

@zone117x zone117x left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@rafaelcr rafaelcr had a problem deploying to Development-mainnet October 16, 2024 14:46 — with GitHub Actions Failure
@rafaelcr rafaelcr had a problem deploying to Development-testnet October 16, 2024 14:46 — with GitHub Actions Failure
@rafaelcr rafaelcr merged commit e44d84a into stacks-signers Oct 16, 2024
10 of 12 checks passed
@rafaelcr rafaelcr deleted the feat/stacks-signers branch October 16, 2024 14:47
github-actions bot pushed a commit that referenced this pull request Oct 25, 2024
## [1.9.0-stacks-signers.1](v1.8.0...v1.9.0-stacks-signers.1) (2024-10-25)

### Features

* add various new nakamoto block fields to `/new_block` ingestion and `StacksPayload` ([#659](#659)) ([f48cda5](f48cda5))
* include recovered signer pubkeys in new block payload ([#662](#662)) ([b5ad4ba](b5ad4ba))
* include signer messages in Stacks predicate payloads ([#656](#656)) ([aee14bc](aee14bc))
* parse `/stackerdb_chunks` Stacks node event ([#653](#653)) ([e44d84a](e44d84a))
* store signer messages in local sqlite database ([#664](#664)) ([d12acd9](d12acd9))
* support tenure-height in block messages ([#661](#661)) ([99e5a61](99e5a61))
* **ts-client:** add persisted predicates and periodic health check ([#658](#658)) ([535226a](535226a))
* **ts-client:** add signer messages to stacks payloads ([#657](#657)) ([ff66bb2](ff66bb2))

### Bug Fixes

* add a configurable max timeout for outgoing predicate payload requests ([#642](#642)) ([6c1dfa9](6c1dfa9)), closes [#643](#643)
* increase stacks event server body size limit to 500MB ([#660](#660)) ([21234c9](21234c9))
* return 500 status code to Stacks node when event ingestion fails ([#648](#648)) ([63c753c](63c753c)), closes [#646](#646)
* signer pubkey calculation ([#665](#665)) ([cc93873](cc93873))
* update SignerMessage deserializing ([#663](#663)) ([71364c1](71364c1))
* validate ts client predicates before registering ([#639](#639)) ([2d08f72](2d08f72))
Copy link

🎉 This PR is included in version 1.9.0-stacks-signers.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants