-
Notifications
You must be signed in to change notification settings - Fork 221
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 context to ffi callbacks #6608
feat!: add context to ffi callbacks #6608
Conversation
integration test
Test Results (CI) 3 files 129 suites 37m 7s ⏱️ Results for commit ff494bd. ♻️ This comment has been updated with latest results. |
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.
On the client side what's being used as the context? Any pointer I assume, but specifically, they've decided to use? The wallet pointer?
yeah its any pointer, but I dont think you can choose the wallet pointer in the way its constructed. As you need to provide the pointer before you get the wallet? |
* development: chore(ci): remove ledger nanos and update ledger key gif resources (tari-project#6617) feat: improve mempool error msg when mempool out of sync (tari-project#6618) feat: exit logic for pre-mine spend (tari-project#6615) chore: new release esme v1.6.0-pre.0 (tari-project#6614) feat: enable identity grpc method by default (tari-project#6613) feat: pre-mine introduce temp ban and add counters (tari-project#6612) chore: changes mainnet default network (tari-project#6610) chore(ci): add riscv64 builds and misc script fixes (tari-project#6611) feat!: esme test pre-mine with immediate spend (tari-project#6609) feat!: add context to ffi callbacks (tari-project#6608) feat: add default exclude dial (tari-project#6607) feat!: add input mr into genesis block (tari-project#6601) feat: update pre_mine specification (tari-project#6606)
Description
Adds c_void context pointer to all FFI callbacks
Splits get address functions into interactive and one-sided
Motivation and Context
By adding a c_void pointer to the all callbacks, each callback can be identified by the context to know from what wallet the callback comes from.
Identifying the callback becomes important if you are running more than one wallet and thus need to identify the calling wallet.
Allows the FFI to get both the interactive and one-sided addresses from the wallet.
Breaking Changes
Adds c_void context to all callbacks.
Renames get_wallet_address to get_wallet_interactive_addess and adds get_wallet_one_sided_address