-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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: Add -chainlocknotify
cmd-line option, update -instantsendnotify
#5522
Conversation
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.
why do we need to create a brand new functional test with mostly copy-paste code?
It seems as possible to extend old test test/functional/feature_notifications.py
with manageable amount of efforts, or do I miss some important difference?
This pull request has conflicts, please rebase. |
Execute command when the best chainlock changes (%s in cmd is replaced by chainlocked block hash).
4b03189
to
e24b102
Compare
719d4d9
to
d1461b0
Compare
I wouldn't agree with
That's how it would look like d1461b0. Had to implement a few workarounds to make it work, will most likely cause merge conflicts in the future. |
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.
That's how it would look like d1461b0. Had to implement a few workarounds to make it work,
yes, indeed, I counted 3 of them:
self.nodes[1]
->rpc
- different
extra_args
logic (because we have non-empty args by default) - different way to create wallets & removing files
Despite that I think it is still better that own file for feature_notifications_dash.py by 2 reasons:
- potential conflicts don't look as really difficult to resolve in this particular case because the overall architecture and logic is not changed: all changes are in details of implementation
- if it would be separate script
feature_nofications_dash.py
then no any changes from originalfeature_notifications.py
would be ever backported tofeature_nofications_dash.py
-> over time difference between these scripts would be bigger and bigger and potentially it increase complexity of support over time.
Anyway, I am not strongly against of separate script, but I'd prefer having them together.
Btw, why do we need to mine 4 quorums here? It works even with one quorum (as I tested locally). Otherwise LGTM now.
d1461b0
to
e7236f0
Compare
Dropped |
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.
utACK
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.
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.
utACK for squash merge
…nd related fixes 7c6c93d fix: remove missing comment to follow-up for bitcoin#15864 (Konstantin Akimov) 65226da Merge bitcoin#22229: test: consolidate to f-strings (part 1) (MarcoFalke) ad2c5a5 refactor: unify feature_notifications.py after #5522 with bitcoin's codebase (Konstantin Akimov) Pull request description: ## Issue being fixed or feature implemented Just one backport bitcoin#22229 because it is a big size, even though there's nothing non-trivial in it. Though, even it is called as part I, there has not been part II yet. ## What was done? Some preparation, code unifications to make bitcoin#22229 with less conflicts and finally backport of itselfl. ## How Has This Been Tested? Run unit & functional test ## Breaking Changes N/A ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone ACKs for top commit: UdjinM6: utACK 7c6c93d PastaPastaPasta: utACK 7c6c93d Tree-SHA512: fe296e3255d45a7a1924bd1e5e21634b3cd36ea3f71cf5e8684b54336771665ea7758de7bfc78721669a928f967e7d4db7b1da0a5cd275feb1a2ec0df841ad5c
Issue being fixed or feature implemented
Execute command when the best chainlock changes (
%s
in cmd is replaced by chainlocked block hash). Same as-blocknotify
but for chainlocks. Let-instantsendnotify
replace%w
with wallet name like-walletnotify
does.What was done?
How Has This Been Tested?
run tests
Breaking Changes
n/a
Checklist: