fix: read stacks-core http event POST payloads for ignored events #673
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rafaelcr
approved these changes
Oct 30, 2024
zone117x
had a problem deploying
to
Development-mainnet
GitHub Actions
Failure
zone117x
had a problem deploying
to
Development-testnet
GitHub Actions
Failure
github-actions bot
pushed a commit
that referenced
this pull request
Oct 31, 2024
## [1.9.0-stacks-signers.6](v1.9.0-stacks-signers.5...v1.9.0-stacks-signers.6) (2024-10-31) ### Bug Fixes * read stacks-core http event POST payloads for ignored events ([#673](#673)) ([a01470e](a01470e))
|
🎉 This PR is included in version 1.9.0-stacks-signers.6 🎉 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Workaround for bug in stacks-core event emitter http code. Regression in stacks-core where http requests must now have their POST body read before closing the connection.
Chainhook ignored some events by returning a 200 http response and closing the connection after reading the http request headers, and ignoring the request body.