[bitcoin] practicalswift opened pull request #18299: tests: Update FUZZERS_MISSING_CORPORA to enable regression fuzzing for all harnesses in master (master...FUZZERS_MISSING_CORPORA) https://github.com/bitcoin/bitcoin/pull/18299
As i can see on the issues page that there aren't much good first issues available. I want to ask whether there is any mechanism in bitcoin dev community to assign specific issues to someone or it's chaos !!!
you should head over to #bitcoin though (unless you want to improve the rpc :P), this is for bitcoin-core development
Stealthy: zmq works reasonably well, but i hear you. I wouldn't be surprised if there was a nodejs lib out there that does what you want, but most of us here are focused on bitcoin core, as the name of the channel implies.
[bitcoin] kallewoof opened pull request #18275: wallet: error if an explicit fee rate was given but the needed fee rate differed (master...2003-wallet-error-on-feechange) https://github.com/bitcoin/bitcoin/pull/18275
[bitcoin] practicalswift opened pull request #18270: util: Fail to parse space-only strings in ParseMoney(...) (instead of parsing as zero) (master...parsemoney-followup) https://github.com/bitcoin/bitcoin/pull/18270
[bitcoin] MarcoFalke merged pull request #17996: tests: Add fuzzing harness for serialization/deserialization of floating-points and integrals (master...fuzzers-float) https://github.com/bitcoin/bitcoin/pull/17996
bitcoin/master 8f6fb0a practicalswift: tests: Add serialization/deserialization fuzzing for integral types
bitcoin/master 3c82b92 practicalswift: tests: Add fuzzing harness for functions taking floating-point types as in...
bitcoin/master c2bd588 practicalswift: Add missing includes
luke-jr: bitcoin core, as a project, maintains packaging scripts for fetching official release binaries and suggests users run those. if you disagree and want to start suggesting users run packages linked against os libs that have a long history of only half-working, its probably something that needs to be discussed as a project, not the two of us.
luke-jr: if someone wants to replace the ppa with something that checks gitian signatures and downloads official binaries, as I've been saying needs to happen ~forever, then maybe its worth maintinaing again. but no one has ever shown a desire to do that, and the ppa has had many issues due to ubuntu insanity. its definitely a bad idea to use those build scripts for bitcoin nodes.
BlueMatt: there's been some interest in keeping the PPA using the bitcoin/bitcoin URI; can you add me to the org?
If anyone has topics they wanna talk about, we could gather those and bring them up after the next PR review, assuming people are up for doing more. I'm not actually sure how #bitcoin-core-dev maintains meeting topic proposals tho.
[bitcoin] luke-jr reopened pull request #15600: lockedpool: When possible, use madvise to avoid including sensitive information in core dumps or forked process memory spaces (master...lockedpool_dontdump) https://github.com/bitcoin/bitcoin/pull/15600
So, bitcoin core right now seems to lean towards constant func/method parameters to pointers in the form "type* const" (55 instances of "CWallet* const pwallet") over "const type*" (15 instances of "const CWallet*"), but from what I understand, "type* const" means the pointer itself is const (i.e. "pwallet = blarf" is illegal) but the pointed to instance is not const (i.e. pwallet->MutableThing() is legal). I tested this