< gmaxwell>
sipa: it's not clear to me how it's possible to implement the policy to remove floods sent by the far side. You can tell that you already have the txn when you recieve the flood, so presumably you would have put it to be recon .. but it might have already been reconed and not part of your current recon set?
< sipa>
gmaxwell: in that case you don't remove it?
< sipa>
i believe the set is kept explicitly, not just in sketch form
< gmaxwell>
ah
< gmaxwell>
that works then.
< bitcoin-git>
[bitcoin] sipa opened pull request #21859: Add minisketch subtree and integrate in build/test (master...202105_minisketch) https://github.com/bitcoin/bitcoin/pull/21859
< sipa>
... 7712 lines
< sipa>
really?
< fanquake>
That's a lot of lines
< sipa>
it seems correct
< bitcoin-git>
[bitcoin] fanquake opened pull request #21860: [0.21] Backport update to Boost download URL (0.21...backport_boost_download) https://github.com/bitcoin/bitcoin/pull/21860
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #21862: test: Set regtest.BIP65Height = 112 to speed up tests (master...2105-testFasterBip65) https://github.com/bitcoin/bitcoin/pull/21862
< aj>
jnewbery: a class keeps the lock and locked data structure together so EXC_LOCKS_REQ(!mutex) works and doesn't need to be downgraded to LOCKS_EXCLUDED(mutex), but *shrug*
< jnewbery>
is the difference between EXC_LOCKS_REQ(!mutex) and LOCKS_EXCLUDED(mutex) documented somewhere?
< aj>
jnewbery: REQ(!x) fails unless the compiler is sure x is not held, EXLCUDED(x) only fails if the compiler is sure x is held; but what the compiler is sure about is a bit weird
< bitcoin-git>
[bitcoin] jonatack closed pull request #21855: fuzz: enable passing a max value to FuzzedDataProvider::ConsumeEnum() (master...ConsumeEnum-enable-passing-max-value) https://github.com/bitcoin/bitcoin/pull/21855
< bitcoin-git>
bitcoin/master 7e7eae7 fanquake: contrib: use f strings in security-check.py
< bitcoin-git>
[bitcoin] laanwj merged pull request #21664: contrib: use LIEF for macOS and Windows symbol & security checks (master...macos_win_lief) https://github.com/bitcoin/bitcoin/pull/21664
< bitcoin-git>
bitcoin/master 931684b James O'Beirne: validation: fix ActivateSnapshot to use hardcoded nChainTx
< bitcoin-git>
bitcoin/master 91d93aa James O'Beirne: validation: remove nchaintx from assumeutxo metadata
< bitcoin-git>
bitcoin/master 128b98f MarcoFalke: Merge bitcoin/bitcoin#21681: validation: fix ActivateSnapshot to use hardc...
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #21681: validation: fix ActivateSnapshot to use hardcoded nChainTx (master...2021-04-au-nchaintx-fix) https://github.com/bitcoin/bitcoin/pull/21681
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #21863: ci: Set depends DEBUG=1 for msan tasks to get line numbers (master...2105-ciMsanDebug) https://github.com/bitcoin/bitcoin/pull/21863
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #21863: ci: Set depends DEBUG=1 for msan tasks to get line numbers (master...2105-ciMsanDebug) https://github.com/bitcoin/bitcoin/pull/21863
< bitcoin-git>
[bitcoin] glozow opened pull request #21864: fix permissions on 00_setup_env_native_fuzz_with_msan.sh (master...2021-05-lint) https://github.com/bitcoin/bitcoin/pull/21864