Updated for pricing array length 0 check, diff summary and test plan.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 21 2023
Nov 20 2023
Note to myself: wait for the website to be deployed before landing (~10 minutes)
Please update your summary and test plan to match the last diff revision
Nov 19 2023
Tweak wording based on review comments
Updated array length checks, error message and price element index.
Minor wording/simplification suggestions
In D14818#332833, @bytesofman wrote:the problem is that the function does too many things. You should split it into logical pieces so you can bail early for coinbase txs without adding another nesting level that makes the code harder to follow.
similar to the tx functions, there is a lot of technical debt in parseChronikTx and it should be rewritten separately from this patch (which is needed to fix a critical issue for wallets with staking rewards).
Build Bitcoin ABC Diffs / Diff Testing (preview-e.cash) passed.
Preview is available at http://54.39.19.73:41821 for the next 60 minutes.
@bot preview-e.cash
Capitalize words in heading
Nov 18 2023
the problem is that the function does too many things. You should split it into logical pieces so you can bail early for coinbase txs without adding another nesting level that makes the code harder to follow.
add test for parsing coinbase tx
There is no test for the change.
If you have a coinbase tx, dont iterate through inputs at all
this fixes the bug but is not the right implementation
remove debug logging
Nov 17 2023
Per tg chat, disabling alias registration if the pricing array from API has more than one entry. I've kept the Alias component itself still accessible as the user should still be able to check their purchased aliases, which is separate from pricing matters.
In D14758#332754, @Fabien wrote:Rename NNG types that will conflict with ChronikClientNode (even though these types are in separate files, bc they are used by ChronikClient and ChronikClientNode, and both objects are exported, ts will not allow them to have the same name)
Is there no kind of namespace ? Or maybe make it a member of the ChronikClient
name the generated file specific to in-node chronik
Rename NNG types that will conflict with ChronikClientNode (even though these types are in separate files, bc they are used by ChronikClient and ChronikClientNode, and both objects are exported, ts will not allow them to have the same name)
In D14758#332748, @Fabien wrote:This could be split into several diffs, for example file/var renames could be their own diffs. Same for the @generated mark on the proto ts file. This makes it easier to spot the where the changes are.
This could be split into several diffs, for example file/var renames could be their own diffs. Same for the @generated mark on the proto ts file. This makes it easier to spot the where the changes are.
update: draft up for review.
sharing failoverProxy, support ws iterations for in-node
@bot build-linux-arm build-linux-aarch64
@bot build-linux-arm build-linux-aarch64