🚀 achow101 merged a pull request: "refactor: Allow `CScript`'s `operator<<` to accept spans, not just vectors"
(https://github.com/bitcoin/bitcoin/pull/30765)

💬 brunoerg commented on pull request "fuzz: wallet: add target for `CreateTransaction`":
(https://github.com/bitcoin/bitcoin/pull/29936#issuecomment-2364509676)
ping review @maflcko @marcofleon

💬 glozow commented on pull request "refactor: TxDownloadManager + fuzzing":
(https://github.com/bitcoin/bitcoin/pull/30110#discussion_r1769185572)
Ugh yes, a bad rebase sorry. I've been using a new setup and haven't perfected my diff-viewing yet.

I don't understand how 0 tests failed, though 😬 gotta look into that

💬 mzumsande commented on issue "Intermittent failure in p2p_1p1c_network.py", line 58, in raise_network_minfee assert_greater_than(node.getmempoolinfo()['mempoolminfee'], FEERATE_1SAT_VB) ; AssertionError: 0.00001000 <= 0.00001000":
(https://github.com/bitcoin/bitcoin/issues/30922#issuecomment-2364529013)
I think that the problem is in how `fill_mempool` works with multiple nodes: If `node0` submits transactions so fast that they are being evicted from the mempool before they could be sent out to other peers, then the other peers will never see them, admit (and later remove) them from their mempool and therefore won't raise their minfee.

Not sure if this can be fixed within `p2p_1p1c_network.py` or if some sort of intermediate sync_mempool calls would need to be added to `fill_mempool` after
...

⚠️ kegdeg opened an issue: "rpc auth fails 'Error parsing command line arguments: Invalid parameter -rpcpasssword=password"
(https://github.com/bitcoin/bitcoin/issues/30939)
### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

After providing rpc credentials using bitcoin-cli, the following error appears:

'Error parsing command line arguments: Invalid parameter -rpcpasssword=password'

telnet to localhost connects with bitcoind running

### Expected behaviour

no error

### Steps to reproduce

This is how the bitcoin.conf looks like:

# Enable RPC server
server=1

# RPC settings
rpcuser=user
rpcpassw
...

💬 fjahr commented on pull request "wallet: Write best block to disk before backup":
(https://github.com/bitcoin/bitcoin/pull/30678#issuecomment-2364572949)
Addressed feedback from @ismaelsadeeq and @furszy , fixing logs and adding more test coverage.

💬 pinheadmz commented on issue "rpc auth fails 'Error parsing command line arguments: Invalid parameter -rpcpasssword=password":
(https://github.com/bitcoin/bitcoin/issues/30939#issuecomment-2364602199)
"rpcpasssword" with 3 S's or 2?

💬 bitcoin-tools commented on issue "`test_bitcoin` from pre-built 28.0rc2 tarball is failing for JSON parsing":
(https://github.com/bitcoin/bitcoin/issues/30938#issuecomment-2364612659)
Researching it deeper, it may be better to wrap the command in `sh -c '...'`, since that would run `echo` and `false` as shell built-ins, rather than depending on coreutils binaries. But I agree with your reasoning regarding `ls`.

🤔 glozow reviewed a pull request: "cluster mempool: extend DepGraph functionality"
(https://github.com/bitcoin/bitcoin/pull/30857#pullrequestreview-2317959224)
Read through the code and it makes sense to me, but haven't tested much. It would be nice to have a fuzz coverage report? @dergoegge

💬 glozow commented on pull request "cluster mempool: extend DepGraph functionality":
(https://github.com/bitcoin/bitcoin/pull/30857#discussion_r1768420948)
nit in 40224019cd6e8259118412529c554d8b4a260130
```suggestion
// Parents of a transaction do not have ancestors inside those parents (except itself).
```

💬 glozow commented on pull request "cluster mempool: extend DepGraph functionality":
(https://github.com/bitcoin/bitcoin/pull/30857#discussion_r1769251003)
Ok, so iiuc, if you add + remove + add + remove the same number of transactions, the depgraph isn't going to get larger and larger; the new transactions can take the place of the holes.

💬 kegdeg commented on issue "rpc auth fails 'Error parsing command line arguments: Invalid parameter -rpcpasssword=password":
(https://github.com/bitcoin/bitcoin/issues/30939#issuecomment-2364630756)
Oh wow, it should be 2 's'. Although I also had that error when using another password which I copy/pasted (maybe there was a spacing error cannot check now), just used password for the example. Those commands and bitcoin.conf are the correct ones, right? Will check it back again when I am back in front of the terminal.

💬 fjahr commented on pull request "Embed default ASMap as binary dump header file":
(https://github.com/bitcoin/bitcoin/pull/28792#issuecomment-2364675182)
CI failures (timeouts) seem unrelated, should be ready for review as I am hoping https://github.com/bitcoin/bitcoin/pull/30901 will get merged quickly.

💬 sipa commented on pull request "cluster mempool: extend DepGraph functionality":
(https://github.com/bitcoin/bitcoin/pull/30857#discussion_r1769352568)
Fixed.

💬 sipa commented on pull request "cluster mempool: extend DepGraph functionality":
(https://github.com/bitcoin/bitcoin/pull/30857#discussion_r1769352792)
Indeed, and `DepGraph` itself is responsible for allocating available positions.

💬 sipa commented on pull request "cluster mempool: extend DepGraph functionality":
(https://github.com/bitcoin/bitcoin/pull/30857#issuecomment-2364749507)
@instagibbs I deleted by build directory, redid the `cmake` generation, recompiled, and the slowdown was gone. Weird.

💬 kegdeg commented on issue "rpc auth fails 'Error parsing command line arguments: Invalid parameter -rpcpasssword=password":
(https://github.com/bitcoin/bitcoin/issues/30939#issuecomment-2364772586)
This is the bitcoin.conf

I removed the triple S, now getting the following error from the following command:

bitcoin-cli -rpcuser=user -rpcpassword -stdinrpcpass start

RPC password>
error: Authorization failed: Incorrect rpcuser or rpcpassword

(i type password)

💬 ryanofsky commented on issue "cmake: multiprocess guix build broken":
(https://github.com/bitcoin/bitcoin/issues/30931#issuecomment-2364790354)
From the log it looks like the failing line is [`CMakeLists.txt:177`](https://github.com/bitcoin/bitcoin/blob/e821f0a37a026fa0480c7f6f6c938da7c77e0d52/CMakeLists.txt#L177):

```cmake
find_package(Libmultiprocess COMPONENTS Lib)
```

which fails in [`LibmultiprocessConfig.cmake:46`](https://github.com/chaincodelabs/libmultiprocess/blob/6aca5f389bacf2942394b8738bbe15d6c9edfb9b/cmake/Config.cmake.in#L29):

```cmake
include("${CMAKE_CURRENT_LIST_DIR}/${_comp}Targets.cmake")
```

wit
...

💬 hebasto commented on issue "cmake: multiprocess guix build broken":
(https://github.com/bitcoin/bitcoin/issues/30931#issuecomment-2365135973)
I found three flaws in the build system. Fixing any one of them resolves the issue. Currently working on a PR.

📝 hebasto opened a pull request: "depends: Fix build with `MULTIPROCESS=1` in Guix environment"
(https://github.com/bitcoin/bitcoin/pull/30940)
In the Guix environment, `${BASEPREFIX}/${HOST}/native/bin` is added to the `PATH` environment variable:https://github.com/bitcoin/bitcoin/blob/33adc7521cc8bb24b941d959022b084002ba7c60/contrib/guix/libexec/build.sh#L233-L234

This causes CMake to search for package configurations in the `native` subdirectory first.

Explicitly specifying the top-priority search prefixes for the `Libmultiprocess` and `LibmultiprocessNative` packages resolves https://github.com/bitcoin/bitcoin/issues/30931.

...