-
Notifications
You must be signed in to change notification settings - Fork 280
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
Additions structure field tx changed to txs #972
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.
Can you squash all the commits into one?
@Shourya742 I think you merged your changes into upstream/master instead of rebasing your changes on it. That is what is stopping you from squashing these changes. You have to do an interactive rebase where you get rid of that merge commit. You can read more about rebase here: https://www.youtube.com/watch?v=7Mh259hfxJg. Let me know how it goes. |
Thank you @vladimirfomene for your assistance, I gained a lot of knowledge from this experience. Could you kindly review the branch and provide any suggestions for changes? I appreciate your help! |
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.
Review ACK 0026848. You might want to read this article: https://danielabrozzoni.com/posts/contributing_to_oss/. It will help you on your journey as you strive to make progress as a contributor.
@vladimirfomene Thanks, will go through the article. |
@vladimirfomene Hello, may I inquire if there is any particular issue concerning the pull request? I'm curious as to why it has not yet been merged. |
@evanlinjin, can you look into merging 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.
utACK 0026848 - looks good to me
I can't merge as your commits aren't signed, can you fix? https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits |
Thank you, @evanlinjin, for your assistance. There are no problems at the moment. I will patiently wait until #976 is merged. Once it is, I will update the commit and request a review. I am hopeful that my first contribution will be merged. In the meantime, I will explore other issues. |
This is to make it easier for chain source crates to formulate updates.
This allows us to skip adding an extra input to `Wallet::insert_tx`. Also remove redundant logic.
There are a number of improvements that can be done, but it is in a decent state to be usable. Possible improvements: * Remove requirement to retry obtaining ALL data after reorg is detected. Transactions can be anchored to a lower block (not block tip), and an `assume_final_depth` value can be used. * The logic to finalize an update with confirmation time can be improved during reorgs to not require returning an error.
This is the equivalent of `keychain_tracker_example_cli` that works with the redesigned structures.
This is a version of `keychain_tracker_electrum` that uses the redesigned structures instead.
This corresponds to `keychain::KeychainChangeSet` but for the redesigned structures with `LocalChain`. This structure is now used in `Wallet` as well as the examples.
As per reviews by @danielabrozzoni and @LLFourn
* `ElectrumUpdate::missing_full_txs` now returns a `Vec<Txid>` so we don't keep a reference to the passed-in `graph`. * `ElectrumUpdate::finalize*` methods now takes in `missing` txids instead of `full_txs`. `Client::batch_transaction_get` is called within the methods. Other changes: * `wallet::ChangeSet` is now made public externally. This is required as a wallet db should implement `PersistBackend<wallet::ChangeSet>`.
All associated examples are also updated.
Other changes: * The `async-https` feature of `bdk_esplora` is no longer default. * Rename `ObservedAs` to `ChainPosition`. * Set temporary MSRV to 1.60.0 to compile all workspace members will all features.
@Shourya742 because #976 is basically ready to be merged (waiting on reviews by others). I suggest that we rebase this work on top of that PR. I can cherry-pick that commit to be part of #976. Remember that we need a signed commit. |
Hello @evanlinjin, I have rebased my local issue branch onto your wallet_redesign branch. It is possible that I may have misunderstood the instruction to "rebase this work on top of that PR." Please find attached the current commit graph for your reference. Moreover, I have resolved all merge conflicts encountered during the rebase and have made necessary changes to electrum_ext.rs. |
@Shourya742 where did you push it? I don't have access to your local branches. The commit I see in this PR is 0026848 which is different to that in the image. |
@evanlinjin No, I haven't pushed the code yet. I was just hoping to ensure that I handled the rebase correctly or if I may have made any errors. If everything is in order, I would proceed with pushing the code. |
@Shourya742 the commit history looks good. Please make sure tests pass, clippy is happy and everything compiles before pushing. |
@evanlinjin I have completed running the tests, and Clippy appears to be good. I have also signed the commit. Kindly review it, please. |
Changed txout to txouts field in Addition Structure Some more changes Changes made after rebasing to wallet_redesign branch Removed chain_graphs
@evanlinjin have a look... |
Description
This PR solves the issue : #954
Notes to the reviewers
Additions structure field "tx" is changed to "txs" and relevant changes are made to all files using it.
Changelog notice
Checklists
All Submissions:
cargo fmt
andcargo clippy
before committingBugfixes: