-
Notifications
You must be signed in to change notification settings - Fork 107
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
Tracking: TODOs with closed tasks #6281
Comments
Copied from #6347 ➜ GITHUB_TOKEN=XXX cargo run --package zebra-utils --bin search-issue-refs --all-features --features search-issue-refs
Searching files in this repo with a ".rs", ".yml", ".yaml", or ".toml" file extension for issue references..
Found 209 possible references to 104 issues, checking statuses on Github..
{results - see below}
Confirmed 179 references to 91 closed issues. References to Closed Issues
zebra/zebra-consensus/src/error.rs Line 156 in 5db2243
see more:zebra/zebra-network/src/peer_set/set.rs Line 423 in 5db2243
zebra/zebra-network/src/config.rs Line 328 in 5db2243
zebra/zebra-network/src/policies.rs Line 39 in 5db2243
zebra/zebrad/src/components/sync.rs Line 1156 in 5db2243
Line 32 in 5db2243
zebra/zebrad/src/components/inbound.rs Line 301 in 5db2243
zebra/zebra-chain/src/block/header.rs Line 89 in 5db2243
zebra/zebra-chain/src/block/header.rs Line 104 in 5db2243
zebra/zebra-network/src/config.rs Line 46 in 5db2243
zebra/zebra-chain/src/block/serialize.rs Line 134 in 5db2243
Line 91 in 5db2243
zebra/zebrad/tests/acceptance.rs Line 1936 in 5db2243
zebra/zebrad/src/components/sync.rs Line 644 in 5db2243
zebra/zebrad/src/components/sync.rs Line 777 in 5db2243
zebra/zebra-network/src/constants.rs Line 189 in 5db2243
zebra/zebra-consensus/src/transaction.rs Line 716 in 5db2243
zebra/zebra-state/src/service.rs Line 171 in 5db2243
zebra/zebra-network/src/config.rs Line 47 in 5db2243
zebra/zebra-network/src/peer/handshake.rs Line 636 in 5db2243
zebra/zebra-network/src/peer_set/limit.rs Line 124 in 5db2243
zebra/zebra-chain/src/orchard/sinsemilla.rs Line 163 in 5db2243
zebra/zebra-state/src/service/arbitrary.rs Line 129 in 5db2243
zebra/zebra-chain/src/block/arbitrary.rs Line 292 in 5db2243
zebra/zebra-network/src/peer_set/set.rs Line 508 in 5db2243
zebra/zebra-network/src/peer/handshake.rs Line 1108 in 5db2243
zebra/zebra-network/src/peer_set/set.rs Line 737 in 5db2243
zebra/zebra-state/src/service.rs Line 1028 in 5db2243
zebra/zebra-network/src/peer/connection.rs Line 1206 in 5db2243
zebra/zebra-network/src/peer/client/tests.rs Line 379 in 5db2243
zebra/zebra-state/src/service/check/utxo.rs Line 238 in 5db2243
zebra/zebra-chain/src/sprout/keys.rs Line 3 in 5db2243
zebra/zebra-chain/src/orchard/keys.rs Line 3 in 5db2243
zebra/zebra-chain/src/sapling/keys.rs Line 3 in 5db2243
zebra/zebra-test/src/command.rs Line 222 in 5db2243
zebra/zebra-test/src/command.rs Line 809 in 5db2243
zebra/zebra-test/tests/command.rs Line 74 in 5db2243
zebra/zebra-test/tests/command.rs Line 101 in 5db2243
zebra/zebra-test/tests/command.rs Line 130 in 5db2243
zebra/zebra-test/tests/command.rs Line 157 in 5db2243
zebra/zebra-test/tests/command.rs Line 445 in 5db2243
zebra/zebra-network/src/constants.rs Line 191 in 5db2243
zebra/zebra-consensus/src/transaction.rs Line 717 in 5db2243
zebra/zebrad/src/components/sync/progress.rs Line 173 in 5db2243
zebra/zebra-rpc/src/methods.rs Line 377 in 5db2243
zebra/zebra-rpc/src/methods.rs Line 480 in 5db2243
zebra/zebra-rpc/src/methods.rs Line 508 in 5db2243
zebra/zebra-rpc/src/methods.rs Line 564 in 5db2243
zebra/zebra-rpc/src/methods.rs Line 754 in 5db2243
zebra/zebra-rpc/src/methods.rs Line 766 in 5db2243
zebra/zebra-rpc/src/methods.rs Line 841 in 5db2243
zebra/zebra-rpc/src/methods.rs Line 923 in 5db2243
zebra/zebra-rpc/src/methods.rs Line 1041 in 5db2243
zebra/zebra-rpc/src/methods.rs Line 1106 in 5db2243
zebra/zebra-network/src/isolated.rs Line 36 in 5db2243
zebra/zebra-network/src/peer/handshake.rs Line 1108 in 5db2243
zebra/zebra-network/src/meta_addr.rs Line 141 in 5db2243
zebra/zebrad/tests/acceptance.rs Line 1009 in 5db2243
zebra/zebra-chain/src/sprout/joinsplit.rs Line 174 in 5db2243
zebra/zebra-chain/src/sapling/output.rs Line 175 in 5db2243
zebra/zebra-chain/src/sapling/spend.rs Line 224 in 5db2243
zebra/zebrad/src/components/sync/downloads.rs Line 240 in 5db2243
zebra/zebrad/tests/acceptance.rs Line 2004 in 5db2243
zebra/zebra-test/src/command.rs Line 483 in 5db2243
zebra/zebra-test/src/command.rs Line 917 in 5db2243
zebra/zebra-chain/src/work/difficulty.rs Line 295 in 5db2243
zebra/zebra-chain/src/work/difficulty.rs Line 400 in 5db2243
zebra/zebrad/tests/acceptance.rs Line 1010 in 5db2243
zebra/zebra-network/src/peer_set/limit.rs Line 124 in 5db2243
zebra/zebra-state/src/config.rs Line 32 in 5db2243
zebra/zebrad/tests/acceptance.rs Line 1804 in 5db2243
zebra/zebrad/tests/acceptance.rs Line 1832 in 5db2243
zebra/zebrad/tests/acceptance.rs Line 1861 in 5db2243
zebra/zebrad/tests/acceptance.rs Line 1926 in 5db2243
zebra/zebra-network/src/peer_set/set.rs Line 737 in 5db2243
zebra/zebrad/src/components/sync.rs Line 72 in 5db2243
zebra/zebra-state/src/service/tests.rs Line 164 in 5db2243
zebra/zebra-state/src/service/chain_tip.rs Line 612 in 5db2243
zebra/zebra-state/src/tests/setup.rs Line 41 in 5db2243
zebra/zebra-state/src/tests/setup.rs Line 55 in 5db2243
zebra/zebrad/src/components/inbound.rs Line 305 in 5db2243
zebra/zebra-consensus/src/checkpoint.rs Line 990 in 5db2243
zebra/zebra-network/src/meta_addr.rs Line 160 in 5db2243
zebra/zebra-network/src/meta_addr.rs Line 617 in 5db2243
zebra/zebra-network/src/meta_addr.rs Line 681 in 5db2243
zebra/zebra-network/src/meta_addr.rs Line 684 in 5db2243
zebra/zebra-network/src/meta_addr.rs Line 933 in 5db2243
zebra/zebra-network/src/peer_set/limit.rs Line 124 in 5db2243
zebra/zebra-state/src/service/check/utxo.rs Line 238 in 5db2243
|
Do we need to have different labels for:
I think tickets and TODOs might move between the first two categories as our priorities change, or based on community feedback. But the last category won't change much, because it's usually about an engineering tradeoff where it's too much effort or too risky. |
As long as we keep the Also I wonder if we're all bikeshedding a bit too much with this one 😅 |
Finally started looking into this. In order for me to track this more easily I have started this spreadsheet and I'll be adding the various different issues reported by the tool and the action to take here. Once that's done I may create more issues to clean those up as necessary. |
I think we've done as much as we're going to do here for now |
Motivation
We want to track all of the findings from the zebra audit.
Details
There are a number of
TODO
s in the codebase that use task numbers that are already closed. For instance, issue #862 states that the Sync process’sstate_contains()
API only checks the best chain for a given block hash (zebrad/src/components/sync.rs), rather than checking all the available chains in the mempool. The audited version of the library still queries the best chain in state and the task is closed.Another example is issue #2214 which suggests that the fanout handling should be done by the
PeerSet
so that all the fanouts wouldn’t use the same peer and block themselves. This seems to only be an issue on testnet where nodes aren’t as well connected as mainnet and the task is closed. This issue is referenced in aTODO
in zebrad/src/components/sync.rs.
This issue will be used to track any further issues created to address
TODO
s which refer to issues which have already been closed.Scope
TODO
s with closed issues and identify:TODO
s can be removed because the issue is already closed as done, otherwise resolved, or no longer relevantTODO
s need to be updated with relevant contextTODO
s should be updated toWONTFIX
in the case the issue was closed as not planned or something that we will not fix.TODO
comment referring to Limit fanouts to the number of active peers, Credit: Equilibrium #2214The text was updated successfully, but these errors were encountered: