eval-exec has quit [Remote host closed the connection]
eval-exec has joined #bitcoin-core-dev
saturday- has joined #bitcoin-core-dev
Saturday7 has quit [Ping timeout: 252 seconds]
eval-exec has quit [Remote host closed the connection]
eval-exec has joined #bitcoin-core-dev
mcey_ has joined #bitcoin-core-dev
mcey has quit [Read error: Connection reset by peer]
saturday- has quit [Ping timeout: 252 seconds]
Saturday7 has joined #bitcoin-core-dev
Saturday7 has quit [Ping timeout: 252 seconds]
szkl has quit [Quit: Connection closed for inactivity]
PaperSword1 has joined #bitcoin-core-dev
PaperSword has quit [Ping timeout: 252 seconds]
PaperSword1 is now known as PaperSword
PaperSword1 has joined #bitcoin-core-dev
PaperSword has quit [Ping timeout: 276 seconds]
PaperSword1 is now known as PaperSword
PaperSword1 has joined #bitcoin-core-dev
PaperSword has quit [Ping timeout: 264 seconds]
PaperSword1 is now known as PaperSword
<bitcoin-git>
[bitcoin] Sjors closed pull request #28616: Show transactions as not fully confirmed during background validation (master...2023/10/assume-unconfirmed) https://github.com/bitcoin/bitcoin/pull/28616
Saturday7 has joined #bitcoin-core-dev
PaperSword has quit [Ping timeout: 264 seconds]
Guyver2 has joined #bitcoin-core-dev
PaperSword has joined #bitcoin-core-dev
eval-exec has quit [Ping timeout: 264 seconds]
bitdex has joined #bitcoin-core-dev
Guyver2 has left #bitcoin-core-dev [Closing Window]
greypw149508 has quit [Quit: Connection reset by beer]
eval-exec has quit [Remote host closed the connection]
eval-exec has joined #bitcoin-core-dev
nanotube has joined #bitcoin-core-dev
abubakarsadiq has joined #bitcoin-core-dev
<vasild>
"< darosior> Does anyone have data on the number of RPCs per release by any chance?" -- Maybe "git grep '^static RPCHelpMan ' tagname |wc -l"? E.g. https://0bin.net/paste/Rlv1Xz26#zMuxVDaLjCgSgfrgOB7ddKC+k9bwQjyP4iTBvtrutdg
<vasild>
(plus minus a few false positives or negatives)
<bitcoin-git>
[bitcoin] l0rinc opened pull request #31730: build: add `bitcoind-release` preset with only `BUILD_DAEMON` enabled with `release` build type (master...l0rinc/bitcoind-release-cmake-preset) https://github.com/bitcoin/bitcoin/pull/31730
pyth has quit [Ping timeout: 260 seconds]
Saturday7 has joined #bitcoin-core-dev
Saturday7 has quit [Ping timeout: 252 seconds]
<bitcoin-git>
[bitcoin] l0rinc opened pull request #31731: doc: update translation generation cmake example (master...l0rinc/dev-mode-translation-doc-fix) https://github.com/bitcoin/bitcoin/pull/31731
jespada has joined #bitcoin-core-dev
pyth has joined #bitcoin-core-dev
Saturday7 has joined #bitcoin-core-dev
Saturday7 has quit [Ping timeout: 264 seconds]
Saturday7 has joined #bitcoin-core-dev
PaperSword1 has joined #bitcoin-core-dev
PaperSword has quit [Ping timeout: 252 seconds]
PaperSword1 is now known as PaperSword
<brunoerg>
#proposedmeetingtopic mutation testing
eval-exec has quit [Ping timeout: 245 seconds]
<bitcoin-git>
[bitcoin] l0rinc closed pull request #31730: build: add `bitcoind-release` preset with only `BUILD_DAEMON` enabled with `release` build type (master...l0rinc/bitcoind-release-cmake-preset) https://github.com/bitcoin/bitcoin/pull/31730
eval-exec has joined #bitcoin-core-dev
<darosior>
vasild: thanks. But some of the results you share strongly suggest it's missing a lot of the picture. For instance we didn't drop 40 commands from 22 to 23. Tried to modify the pattern matching a bit, can't find a portable way across versions. I'll stick with Pieter's suggestion.
<darosior>
For anyone interested, this is the data i get $ for version_folder in $(find _doc/en/ -mindepth 1 -maxdepth 1 -type d | grep '0$' |sort); do printf "$(basename $version_folder), "; find "$version_folder/rpc/" -mindepth 1 -type d -exec ls {} \; | wc -w ; done
<bitcoin-git>
[bitcoin] pythcoiner opened pull request #31734: Miniscriptdescriptor to string (master...miniscriptdescriptor_to_string) https://github.com/bitcoin/bitcoin/pull/31734
Cory93 has quit [Quit: Client closed]
Cory93 has joined #bitcoin-core-dev
Saturday7 has quit [Ping timeout: 252 seconds]
pyth has quit [Ping timeout: 248 seconds]
pyth has joined #bitcoin-core-dev
pyth has quit [Ping timeout: 252 seconds]
pyth has joined #bitcoin-core-dev
preimage has joined #bitcoin-core-dev
eval-exec has quit [Ping timeout: 264 seconds]
jespada has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
zeropoint has joined #bitcoin-core-dev
emcy__ has joined #bitcoin-core-dev
mcey_ has quit [Ping timeout: 264 seconds]
Saturday7 has joined #bitcoin-core-dev
mudsip has joined #bitcoin-core-dev
mudsip has quit [Client Quit]
LainExperiments has joined #bitcoin-core-dev
nanotube has quit [Ping timeout: 252 seconds]
Guest133 has joined #bitcoin-core-dev
Guest133 has quit [Client Quit]
<abubakarsadiq>
I've searched but did not see guidelines on how long will a deprecated feature (e.g) RPC will take for it to be removed! I've seen an example from d4cdbd6fb6ac3663d069307c4fd0078f4ecf0245 that the RPC will be removed in the next release. Is that the case? if so @tbd3 maybe document that as well in #30142
<sipa>
abubakarsadiq: generally, one major release (so marked deprecated in version N.0, removed in (N+1).0)
<sipa>
but of course, because it requires actual work (a PR being written and reviewed) during the N+1 release cycle, that may not happen, either because it's forgotten, or because people worry that too many users rely on it still
<abubakarsadiq>
Thanks so it's a case by case basis, I see the reason why having an estimate maybe an issue
SCR4MBL3 has joined #bitcoin-core-dev
<SCR4MBL3>
hi
SCR4MBL3 has quit [Quit: Leaving]
maflcko has quit [Read error: Connection reset by peer]
maflcko has joined #bitcoin-core-dev
mudsip has joined #bitcoin-core-dev
mudsip has quit [Client Quit]
PaperSword1 has joined #bitcoin-core-dev
PaperSword has quit [Ping timeout: 252 seconds]
PaperSword1 is now known as PaperSword
PaperSword1 has joined #bitcoin-core-dev
PaperSword has quit [Ping timeout: 252 seconds]
PaperSword1 is now known as PaperSword
LainExperiments has quit [Ping timeout: 240 seconds]
Saturday7 has joined #bitcoin-core-dev
<darosior>
Hey, the discussion from yesterday about multiprocess prompted me to write down my thoughts about a larger issue, that of setting ourselves long term goals as a project. Although uncomfortable i believe it's really important for us to talk about it. I think it makes sense to start discussing it during a meeting and we can hash it further at
<darosior>
CoreDev. Starting to write down an intro for the meeting topic i ended up writing a whole blog post. Here it is: https://antoinep.com/posts/core_project_direction . I'm curious to learn what others think about this.
<darosior>
#proposedmeetingtopic What should be the mid to long term goals of the project?
<bitcoin-git>
bitcoin/master f6e8893 ismaelsadeeq: test: test that `create_self_transfer_multi` respects `target_vsize`
<bitcoin-git>
bitcoin/master a8780c9 ismaelsadeeq: test: raise an error if output value is <= 0 in `create_self_transfer`
<bitcoin-git>
bitcoin/master 92787dd ismaelsadeeq: test: raise an error when target_vsize is below tx virtual size
<bitcoin-git>
[bitcoin] achow101 merged pull request #30322: test: raise an error in `_bulk_tx_` when `target_vsize` is too low (master...06-2024-fix_bulk_tx-with-low-weight) https://github.com/bitcoin/bitcoin/pull/30322