β
Zencsy closed an issue: "Bitcoin Core not responding"
(https://github.com/bitcoin/bitcoin/issues/27964)
(https://github.com/bitcoin/bitcoin/issues/27964)
π¬ MarcoFalke commented on issue "Bitcoin Core not responding":
(https://github.com/bitcoin/bitcoin/issues/27964#issuecomment-1606024240)
Pretty sure it is just waiting for cs_main, which is needed in IBD. So this is expected, unless the GUI is made lock-free, for which there should already be an issue open?
(https://github.com/bitcoin/bitcoin/issues/27964#issuecomment-1606024240)
Pretty sure it is just waiting for cs_main, which is needed in IBD. So this is expected, unless the GUI is made lock-free, for which there should already be an issue open?
β οΈ dooglus opened an issue: "deadlock shutting down v25.0"
(https://github.com/bitcoin/bitcoin/issues/27965)
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behaviour
I ran "bitcoin-cli stop" and it didn't stop.
### Expected behaviour
I expect it to stop.
### Steps to reproduce
It usually works. Sometimes it doesn't. I don't know how to reproduce.
### Relevant log output
Here's the end of `debug.log`:
2023-06-25T12:55:49Z Saw new header hash=0000000000000000000375a71ccc0569c279dbb751bdbb70d86d983cd38eea68 height=795857
2023-06-25T12:55
...
(https://github.com/bitcoin/bitcoin/issues/27965)
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behaviour
I ran "bitcoin-cli stop" and it didn't stop.
### Expected behaviour
I expect it to stop.
### Steps to reproduce
It usually works. Sometimes it doesn't. I don't know how to reproduce.
### Relevant log output
Here's the end of `debug.log`:
2023-06-25T12:55:49Z Saw new header hash=0000000000000000000375a71ccc0569c279dbb751bdbb70d86d983cd38eea68 height=795857
2023-06-25T12:55
...
π€ pablomartin4btc reviewed a pull request: "fuzz: addrman, add coverage for `network` field in `Select()`, `Size()` and `GetAddr()`"
(https://github.com/bitcoin/bitcoin/pull/27549#pullrequestreview-1497037871)
Tested ACK: `FUZZ=addrman ./src/test/fuzz/fuzz`
Tried also with a few seeds added last month by @Xekyo:
e.g.: `FUZZ=addrman ./src/test/fuzz/fuzz ../qa-assets/fuzz_seed_corpus/addrman/1b02be22a08f8e28c192cb1c86f074158d18a691`
(https://github.com/bitcoin/bitcoin/pull/27549#pullrequestreview-1497037871)
Tested ACK: `FUZZ=addrman ./src/test/fuzz/fuzz`
Tried also with a few seeds added last month by @Xekyo:
e.g.: `FUZZ=addrman ./src/test/fuzz/fuzz ../qa-assets/fuzz_seed_corpus/addrman/1b02be22a08f8e28c192cb1c86f074158d18a691`
π¬ pablomartin4btc commented on pull request "fuzz: addrman, add coverage for `network` field in `Select()`, `Size()` and `GetAddr()`":
(https://github.com/bitcoin/bitcoin/pull/27549#discussion_r1241153134)
Do we really need this?
```suggestion
```
Next line calling `AddrMan::GetAddr()` function passes `std::nullopt` as the network argument (meaning ALL_NETWORKS), so as `AddrMan::Size()` also interprets the same for the network argument and since even `ConsumesBool()` when returns false it would be `std::nullopt` (meaning ALL_NETWORKS), why to bother with this, just pass std::nullopt below when you call `AddrMan::Size()`, unless I'm missing something here.
(https://github.com/bitcoin/bitcoin/pull/27549#discussion_r1241153134)
Do we really need this?
```suggestion
```
Next line calling `AddrMan::GetAddr()` function passes `std::nullopt` as the network argument (meaning ALL_NETWORKS), so as `AddrMan::Size()` also interprets the same for the network argument and since even `ConsumesBool()` when returns false it would be `std::nullopt` (meaning ALL_NETWORKS), why to bother with this, just pass std::nullopt below when you call `AddrMan::Size()`, unless I'm missing something here.
π¬ pablomartin4btc commented on pull request "fuzz: addrman, add coverage for `network` field in `Select()`, `Size()` and `GetAddr()`":
(https://github.com/bitcoin/bitcoin/pull/27549#discussion_r1241153526)
As I explained my reasoning of this above in my first comment on the initialisation of the network variable:
```suggestion
(void)const_addr_man.Size(/*network=*/std::nullopt, in_new);
```
(https://github.com/bitcoin/bitcoin/pull/27549#discussion_r1241153526)
As I explained my reasoning of this above in my first comment on the initialisation of the network variable:
```suggestion
(void)const_addr_man.Size(/*network=*/std::nullopt, in_new);
```
π¬ pablomartin4btc commented on pull request "fuzz: addrman, add coverage for `network` field in `Select()`, `Size()` and `GetAddr()`":
(https://github.com/bitcoin/bitcoin/pull/27549#discussion_r1241150445)
I was going to propose:
```suggestion
bool in_new{fuzzed_data_provider.ConsumeBool()};
```
``` ```
But then I checked also the definition of the`AddrMan::Size()`function consuming `in_new` as and argument and I see in the comments that it would interpret the 3 states:
```
/**
* Return size information about addrman.
*
* @param[in] net Select addresses only from specified network (nullopt = all)
* @param[in] in_new Select addresses only f
...
(https://github.com/bitcoin/bitcoin/pull/27549#discussion_r1241150445)
I was going to propose:
```suggestion
bool in_new{fuzzed_data_provider.ConsumeBool()};
```
``` ```
But then I checked also the definition of the`AddrMan::Size()`function consuming `in_new` as and argument and I see in the comments that it would interpret the 3 states:
```
/**
* Return size information about addrman.
*
* @param[in] net Select addresses only from specified network (nullopt = all)
* @param[in] in_new Select addresses only f
...
π¬ dooglus commented on issue "deadlock shutting down v25.0":
(https://github.com/bitcoin/bitcoin/issues/27965#issuecomment-1606094420)
Netstat tells me there's nothing listening on port 8332:
$ sudo netstat -plnt | grep 833
tcp 0 0 127.0.0.1:8333 0.0.0.0:* LISTEN 584775/bitcoin-qt-v
tcp 27 0 127.0.0.1:8334 0.0.0.0:* LISTEN 584775/bitcoin-qt-v
Detaching gdb and running `strace -f` on the process shows lots of activity:
[pid 584775] recvmsg(6, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
[pid 5847
...
(https://github.com/bitcoin/bitcoin/issues/27965#issuecomment-1606094420)
Netstat tells me there's nothing listening on port 8332:
$ sudo netstat -plnt | grep 833
tcp 0 0 127.0.0.1:8333 0.0.0.0:* LISTEN 584775/bitcoin-qt-v
tcp 27 0 127.0.0.1:8334 0.0.0.0:* LISTEN 584775/bitcoin-qt-v
Detaching gdb and running `strace -f` on the process shows lots of activity:
[pid 584775] recvmsg(6, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
[pid 5847
...
π¬ pablomartin4btc commented on issue "bitcoind hangs waiting for `g_requests.empty()`":
(https://github.com/bitcoin/bitcoin/issues/27722#issuecomment-1606107875)
As @willcl-ark, tried @theStack's method with no sucess, my libevent version is 2.1.7, I'll try to update it and retry again. Thanks.
@Crypt-iQ I did: Ctrl-C the waitforblockheight command before trying to stop bitcoind.
(https://github.com/bitcoin/bitcoin/issues/27722#issuecomment-1606107875)
As @willcl-ark, tried @theStack's method with no sucess, my libevent version is 2.1.7, I'll try to update it and retry again. Thanks.
@Crypt-iQ I did: Ctrl-C the waitforblockheight command before trying to stop bitcoind.
π furszy approved a pull request: "feerate: For GetFeePerK() return nSatoshisPerK instead of round trip through GetFee"
(https://github.com/bitcoin/bitcoin/pull/27914#pullrequestreview-1497104793)
Code ACK 11d65006
(https://github.com/bitcoin/bitcoin/pull/27914#pullrequestreview-1497104793)
Code ACK 11d65006
π maryinaurvina opened a pull request: "Create bitcoin56"
(https://github.com/bitcoin/bitcoin/pull/27966)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
(https://github.com/bitcoin/bitcoin/pull/27966)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
π¬ maryinaurvina commented on pull request "Create bitcoin56":
(https://github.com/bitcoin/bitcoin/pull/27966#issuecomment-1606138070)
[bitcoin](https://github.com/bitcoin/bitcoin/tree/master)
(https://github.com/bitcoin/bitcoin/pull/27966#issuecomment-1606138070)
[bitcoin](https://github.com/bitcoin/bitcoin/tree/master)
β
hebasto closed a pull request: "Create bitcoin56"
(https://github.com/bitcoin/bitcoin/pull/27966)
(https://github.com/bitcoin/bitcoin/pull/27966)
π fanquake locked a pull request: "Create bitcoin56"
(https://github.com/bitcoin/bitcoin/pull/27966)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
(https://github.com/bitcoin/bitcoin/pull/27966)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
π mohammadimtayaj052 opened a pull request: "Create bitcoinBTC"
(https://github.com/bitcoin/bitcoin/pull/27967)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
(https://github.com/bitcoin/bitcoin/pull/27967)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
π¬ mohammadimtayaj052 commented on pull request "Create bitcoinBTC":
(https://github.com/bitcoin/bitcoin/pull/27967#issuecomment-1606145315)
btcaa
(https://github.com/bitcoin/bitcoin/pull/27967#issuecomment-1606145315)
btcaa
β
hebasto closed a pull request: "Create bitcoinBTC"
(https://github.com/bitcoin/bitcoin/pull/27967)
(https://github.com/bitcoin/bitcoin/pull/27967)
π hebasto locked a pull request: "."
(https://github.com/bitcoin/bitcoin/pull/27967)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
(https://github.com/bitcoin/bitcoin/pull/27967)
<!--
*** Please remove the following help text before submitting: ***
Pull requests without a rationale and clear improvement may be closed
immediately.
GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->
<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:
* Any test improvements or new tests that improv
...
π¬ Macoophonic commented on pull request "feerate: For GetFeePerK() return nSatoshisPerK instead of round trip through GetFee":
(https://github.com/bitcoin/bitcoin/pull/27914#issuecomment-1606183319)
Guys, it's late, I'll send more tomorrow π€£π€£π€£π
Hey gold night
VΓ o 21:56, CN, 25 thg 6, 2023 Matias Furszyfer ***@***.***>
ΔΓ£ viαΊΏt:
> ***@***.**** approved this pull request.
>
> Code ACK 11d6500
> <https://github.com/bitcoin/bitcoin/commit/11d650060aed25273d860baa4e03168a778832bb>
>
> β
> Reply to this email directly, view it on GitHub
> <https://github.com/bitcoin/bitcoin/pull/27914#pullrequestreview-1497104793>,
> or unsubscribe
> <https://github.com/notifications/unsub
...
(https://github.com/bitcoin/bitcoin/pull/27914#issuecomment-1606183319)
Guys, it's late, I'll send more tomorrow π€£π€£π€£π
Hey gold night
VΓ o 21:56, CN, 25 thg 6, 2023 Matias Furszyfer ***@***.***>
ΔΓ£ viαΊΏt:
> ***@***.**** approved this pull request.
>
> Code ACK 11d6500
> <https://github.com/bitcoin/bitcoin/commit/11d650060aed25273d860baa4e03168a778832bb>
>
> β
> Reply to this email directly, view it on GitHub
> <https://github.com/bitcoin/bitcoin/pull/27914#pullrequestreview-1497104793>,
> or unsubscribe
> <https://github.com/notifications/unsub
...
π¬ Macoophonic commented on issue "bitcoind hangs waiting for `g_requests.empty()`":
(https://github.com/bitcoin/bitcoin/issues/27722#issuecomment-1606197612)
Guys, it's late, I'll send more tomorrow π€£π€£π€£π
Hey gold night
VΓ o 21:15, CN, 25 thg 6, 2023 pablomartin4btc ***@***.***> ΔΓ£
viαΊΏt:
> As @willcl-ark <https://github.com/willcl-ark>, tried @theStack
> <https://github.com/theStack>'s method with no sucess, my libevent
> version is 2.1.7, I'll try to update it and retry again. Thanks.
>
> @Crypt-iQ <https://github.com/Crypt-iQ> I did: Ctrl-C the
> waitforblockheight command before trying to stop bitcoind.
>
> β
> Reply to this em
...
(https://github.com/bitcoin/bitcoin/issues/27722#issuecomment-1606197612)
Guys, it's late, I'll send more tomorrow π€£π€£π€£π
Hey gold night
VΓ o 21:15, CN, 25 thg 6, 2023 pablomartin4btc ***@***.***> ΔΓ£
viαΊΏt:
> As @willcl-ark <https://github.com/willcl-ark>, tried @theStack
> <https://github.com/theStack>'s method with no sucess, my libevent
> version is 2.1.7, I'll try to update it and retry again. Thanks.
>
> @Crypt-iQ <https://github.com/Crypt-iQ> I did: Ctrl-C the
> waitforblockheight command before trying to stop bitcoind.
>
> β
> Reply to this em
...