💬 BrandonOdiwuor commented on pull request "Wallet: (Refactor) GetBalance to calculate used balance":
(https://github.com/bitcoin/bitcoin/pull/29062#discussion_r1574895998)
Fixed: updated `GetBalance` to include `m_mine_used`
(https://github.com/bitcoin/bitcoin/pull/29062#discussion_r1574895998)
Fixed: updated `GetBalance` to include `m_mine_used`
💬 maflcko commented on pull request "test: Fix intermittent timeout in p2p_tx_download.py":
(https://github.com/bitcoin/bitcoin/pull/29933#discussion_r1574896587)
I think the real reason would be "because they are not needed". The secondary reason would be that the test will be faster on slower hardware. The final reason would be that this avoids intermittent test failures/timeouts. However, there are other ways to avoid the intermittent test failures, so I am not sure if this is the right place to document it.
Should I just put a comment here `# Avoid inbounds because they are not needed and slow down the test`?
(https://github.com/bitcoin/bitcoin/pull/29933#discussion_r1574896587)
I think the real reason would be "because they are not needed". The secondary reason would be that the test will be faster on slower hardware. The final reason would be that this avoids intermittent test failures/timeouts. However, there are other ways to avoid the intermittent test failures, so I am not sure if this is the right place to document it.
Should I just put a comment here `# Avoid inbounds because they are not needed and slow down the test`?
👍 maflcko approved a pull request: "doc: add LLVM instruction for macOS < 13"
(https://github.com/bitcoin/bitcoin/pull/29934#pullrequestreview-2015004975)
lgtm
(https://github.com/bitcoin/bitcoin/pull/29934#pullrequestreview-2015004975)
lgtm
💬 maflcko commented on pull request "doc: add LLVM instruction for macOS < 13":
(https://github.com/bitcoin/bitcoin/pull/29934#discussion_r1574898821)
I'd say to use the latest llvm. However, I presume you wanted to avoid a too recent llvm breaking on the old operating systems? Seems fine either way.
(https://github.com/bitcoin/bitcoin/pull/29934#discussion_r1574898821)
I'd say to use the latest llvm. However, I presume you wanted to avoid a too recent llvm breaking on the old operating systems? Seems fine either way.
💬 Sjors commented on pull request "doc: add LLVM instruction for macOS < 13":
(https://github.com/bitcoin/bitcoin/pull/29934#discussion_r1574902679)
> a too recent llvm breaking on the old operating systems
Exactly. Either llvm itself or Homebrew's build scripts might not work for some reason, so this seems safer.
(https://github.com/bitcoin/bitcoin/pull/29934#discussion_r1574902679)
> a too recent llvm breaking on the old operating systems
Exactly. Either llvm itself or Homebrew's build scripts might not work for some reason, so this seems safer.
💬 TheCharlatan commented on pull request "doc: add LLVM instruction for macOS < 13":
(https://github.com/bitcoin/bitcoin/pull/29934#issuecomment-2069769652)
Will test shortly.
(https://github.com/bitcoin/bitcoin/pull/29934#issuecomment-2069769652)
Will test shortly.
💬 ismaelsadeeq commented on pull request "doc: add LLVM instruction for macOS < 13":
(https://github.com/bitcoin/bitcoin/pull/29934#issuecomment-2069796578)
Concept ACK, I ran into this issue sometime ago
(https://github.com/bitcoin/bitcoin/pull/29934#issuecomment-2069796578)
Concept ACK, I ran into this issue sometime ago
💬 BrandonOdiwuor commented on pull request "doc: explain what the wallet password does":
(https://github.com/bitcoin/bitcoin/pull/28974#discussion_r1574923164)
removed
(https://github.com/bitcoin/bitcoin/pull/28974#discussion_r1574923164)
removed
💬 BrandonOdiwuor commented on pull request "doc: explain what the wallet password does":
(https://github.com/bitcoin/bitcoin/pull/28974#discussion_r1574923762)
fixed:summarised further
(https://github.com/bitcoin/bitcoin/pull/28974#discussion_r1574923762)
fixed:summarised further
💬 maflcko commented on pull request "test: Fix multiprocess CI timeout in p2p_tx_download":
(https://github.com/bitcoin/bitcoin/pull/29926#issuecomment-2069822890)
See also the current test failure, which remains: https://github.com/bitcoin/bitcoin/pull/29926/checks?check_run_id=24105987877
(https://github.com/bitcoin/bitcoin/pull/29926#issuecomment-2069822890)
See also the current test failure, which remains: https://github.com/bitcoin/bitcoin/pull/29926/checks?check_run_id=24105987877
💬 achow101 commented on pull request "ZMQ: Support UNIX domain sockets":
(https://github.com/bitcoin/bitcoin/pull/27679#issuecomment-2069827639)
ACK 21d0e6c7b7c7af7f6e54a45829b4fbfba6923b86
(https://github.com/bitcoin/bitcoin/pull/27679#issuecomment-2069827639)
ACK 21d0e6c7b7c7af7f6e54a45829b4fbfba6923b86
💬 instagibbs commented on pull request "test: Fix intermittent timeout in p2p_tx_download.py":
(https://github.com/bitcoin/bitcoin/pull/29933#discussion_r1574936864)
> Should I just put a comment here # Avoid inbounds because they are not needed and slow down the test?
not really, doesn't add anything, so leave it as is
(https://github.com/bitcoin/bitcoin/pull/29933#discussion_r1574936864)
> Should I just put a comment here # Avoid inbounds because they are not needed and slow down the test?
not really, doesn't add anything, so leave it as is
💬 instagibbs commented on pull request "test: Fix intermittent timeout in p2p_tx_download.py":
(https://github.com/bitcoin/bitcoin/pull/29933#issuecomment-2069846036)
makes sense
ACK fa6c300a9926a1d35fdd0a80f59ea39769bd2596
(https://github.com/bitcoin/bitcoin/pull/29933#issuecomment-2069846036)
makes sense
ACK fa6c300a9926a1d35fdd0a80f59ea39769bd2596
💬 fjahr commented on pull request "test: Fix multiprocess CI timeout in p2p_tx_download":
(https://github.com/bitcoin/bitcoin/pull/29926#issuecomment-2069859823)
> Which indicates that the problem is during shutdown, _after_ the test, not in the test.
>
> So I don't think adding mocktime will fix it. Maybe you were running into a different issue, or are trying to fix a different bug?
Hm, I didn't see `Stopping nodes` being printed so I am not convinced it's during shutdown but maybe I am just not familiar enough with the test framework. I am closing since it seems even with the +30 it's still failing and it seems duplicate #29933 might have a bette
...
(https://github.com/bitcoin/bitcoin/pull/29926#issuecomment-2069859823)
> Which indicates that the problem is during shutdown, _after_ the test, not in the test.
>
> So I don't think adding mocktime will fix it. Maybe you were running into a different issue, or are trying to fix a different bug?
Hm, I didn't see `Stopping nodes` being printed so I am not convinced it's during shutdown but maybe I am just not familiar enough with the test framework. I am closing since it seems even with the +30 it's still failing and it seems duplicate #29933 might have a bette
...
✅ fjahr closed a pull request: "test: Fix multiprocess CI timeout in p2p_tx_download"
(https://github.com/bitcoin/bitcoin/pull/29926)
(https://github.com/bitcoin/bitcoin/pull/29926)
💬 instagibbs commented on pull request "test: Don't fetch orphan parent when parent is in orphanage":
(https://github.com/bitcoin/bitcoin/pull/29915#discussion_r1574948358)
hmm yeah this doesn't add anything *unless it was requested in a separate `getdata` which this check wouldn't ensure anyways.
(https://github.com/bitcoin/bitcoin/pull/29915#discussion_r1574948358)
hmm yeah this doesn't add anything *unless it was requested in a separate `getdata` which this check wouldn't ensure anyways.
✅ instagibbs closed a pull request: "test: Don't fetch orphan parent when parent is in orphanage"
(https://github.com/bitcoin/bitcoin/pull/29915)
(https://github.com/bitcoin/bitcoin/pull/29915)
💬 maflcko commented on pull request "test: Fix multiprocess CI timeout in p2p_tx_download":
(https://github.com/bitcoin/bitcoin/pull/29926#issuecomment-2069873791)
> Hm, I didn't see Stopping nodes being printed so I am not convinced it's during shutdown
This will be printed after the network thread is closed. However, the network thread not closing is the underlying bug.
You can see this in the traceback I posted above. (`self.network_thread.close()` is line 314, and "Stopping nodes" is line 316)
(https://github.com/bitcoin/bitcoin/pull/29926#issuecomment-2069873791)
> Hm, I didn't see Stopping nodes being printed so I am not convinced it's during shutdown
This will be printed after the network thread is closed. However, the network thread not closing is the underlying bug.
You can see this in the traceback I posted above. (`self.network_thread.close()` is line 314, and "Stopping nodes" is line 316)
🚀 achow101 merged a pull request: "ZMQ: Support UNIX domain sockets"
(https://github.com/bitcoin/bitcoin/pull/27679)
(https://github.com/bitcoin/bitcoin/pull/27679)
✅ achow101 closed an issue: "Invalid port specified in -zmqpubrawtx when using IPC"
(https://github.com/bitcoin/bitcoin/issues/29802)
(https://github.com/bitcoin/bitcoin/issues/29802)