-
Notifications
You must be signed in to change notification settings - Fork 678
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: event emitter will now emit new_txid in-case a tx replaces another #5381
Conversation
I could be wrong, but I think this may need to be opened against develop, not master. |
@jferrant yes didn't know it existed. |
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.
This LGTM, pending CI passes. Thanks @usagi32!
@usagi32 you'll have to fix some of the formatting errors before CI runs tests - you can see these by running |
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.
LGTM!
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.
LGTM. Thanks @usagi32!
Ah, unfortunately there's a new compilation error, assuming from after merging in develop. |
Fixed build errors and merged latest |
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.
LGTM!
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.
Could we add a changelog entry for this?
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.
LGTM!
Oh, it's not running the CI jobs because the last commit only changed a markdown file. Looks like we need some adjustments to the CI rules. |
@obycode I think it's something to do with me pushing to this forked branch, I'm not sure. Maybe I'll need to open a new PR... |
Looks like merging develop was enough to get it to trigger, so maybe my Markdown theory was correct? |
Closing, reoponed as #5605 |
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. |
This extra information is required by an issue in the blockchain-api here and here.
Event emitter will now give to the api node which transaction replaced another.