💬 furszy commented on issue "wallets created on master get corrupted when processed with v25":
(https://github.com/bitcoin/bitcoin/issues/27915#issuecomment-1605559145)
> Maybe we should consider it an error to load a wallet if the descriptors can't all be round-tripped? (and consider it a bugfix for 25.x, while also trying to avoid triggering it for a while)

Yeah, that is already done in #27920 (fc5565eb). It will prevent ugly stuff from happening from now on.

💬 luke-jr commented on pull request "test: Fix intermittent issue in mining_getblocktemplate_longpoll.py":
(https://github.com/bitcoin/bitcoin/pull/27941#issuecomment-1605565551)
The longpoll request is supposed to return immediately if the conditions have been met. The token includes a reference to the transaction update state as a counter.

💬 hebasto commented on pull request "build: produce a .zip for macOS distribution":
(https://github.com/bitcoin/bitcoin/pull/27099#discussion_r1240844088)
8d8d4325fedad5c140ea1ad4568f19609c431e2e

The following diff is intended to fix the [reproducibility](reproducible) issue:
```suggestion
if [ -n "$(SOURCE_DATE_EPOCH)" ]; then find $(APP_DIST_DIR) -exec touch -d @$(SOURCE_DATE_EPOCH) {} +; fi
zip -X -r $@ $(APP_DIST_DIR)
```

💬 pinheadmz commented on issue "MSan CI failure in psbt_wallet_tests and feebumper_tests":
(https://github.com/bitcoin/bitcoin/issues/27001#issuecomment-1605791170)
Testing webhooks don't mind me

💬 amitiuttarwar commented on pull request "p2p: Diversify automatic outbound connections with respect to networks":
(https://github.com/bitcoin/bitcoin/pull/27213#discussion_r1241000169)
my latest thinking was to change this data struct to an array, add explicit numeric values to the `Network` enum (for index values) & then protect the array with `m_nodes_mutex` to keep the values consistent between the relevant data structures tracking node data. what do you think of this approach?

(I had coded it up, but then managed to spill liquid on my laptop which fried it as I was trying to push the changes. still working to get my current setup back to functional to make the changes
...

💬 besoeasy commented on pull request "Sanitizing ports of -rpcconnect and -rpcport.":
(https://github.com/bitcoin/bitcoin/pull/27820#issuecomment-1605833739)
@Brotcrunsher

Instead of checking if desiredRpcPort is less than or equal to zero and greater than 0xFFFF, you can use a single condition to check if it's outside the valid port range.

📝 Swallow094 opened a pull request: "Create FEWFEWF"
(https://github.com/bitcoin/bitcoin/pull/27960)
<!--
*** 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
...

💬 Swallow094 commented on pull request "Create FEWFEWF":
(https://github.com/bitcoin/bitcoin/pull/27960#issuecomment-1605860760)
GẺGRE

💬 Swallow094 commented on pull request "Create FEWFEWF":
(https://github.com/bitcoin/bitcoin/pull/27960#issuecomment-1605860773)
GFRGFG

✅ achow101 closed a pull request: "Create FEWFEWF"
(https://github.com/bitcoin/bitcoin/pull/27960)

📝 achow101 locked a pull request: "Create FEWFEWF"
(https://github.com/bitcoin/bitcoin/pull/27960)
<!--
*** 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
...

⚠️ FelixWeis opened an issue: "Assertion failed: (data.size() > node.nSendOffset), function SocketSendData, file net.cpp, line 837"
(https://github.com/bitcoin/bitcoin/issues/27963)
### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

crashed

### Expected behaviour

not crash

### Steps to reproduce

compiled master at d1ae96755a0f9d7e12c3f6741c030d8ea6d0416f, did mainnet IBD,
around 40 hours after IBD crashed with the asseration fail.

### Relevant log output

unclear if relevant but these are the final lines
```
2023-06-24T06:15:52Z Saw new header hash=00000000000000000000f72e1a37859593a848a2f9b88eb9e5c3f0d8c971d
...

💬 FelixWeis commented on issue "Assertion failed: (data.size() > node.nSendOffset), function SocketSendData, file net.cpp, line 837":
(https://github.com/bitcoin/bitcoin/issues/27963#issuecomment-1605906878)
```Build Options:
with external callbacks = no
with benchmarks = no
with tests = yes
with ctime tests = no
with coverage = no
with examples = no
module ecdh = no
module recovery = yes
module extrakeys = yes
module schnorrsig = yes

asm = no
ecmult window size = 15
ecmult gen prec. bits = 4

valgrind = no
CC
...

💬 MarcoFalke commented on issue "Assertion failed: (data.size() > node.nSendOffset), function SocketSendData, file net.cpp, line 837":
(https://github.com/bitcoin/bitcoin/issues/27963#issuecomment-1605939843)
> around 40 hours after IBD crashed with the asseration fail.

I guess this makes it hard to reproduce with gdb attached or with more logging enabled?

Glancing at the code, I don't see how this could happen unless macOS `send` returned a value larger than the `len` passed in?

https://github.com/bitcoin/bitcoin/blame/d1ae96755a0f9d7e12c3f6741c030d8ea6d0416f/src/net.cpp#L837

The last change in the function was https://github.com/bitcoin/bitcoin/commit/691eaf8873fe2f189153ca637506a02915
...

⚠️ Zencsy opened an issue: "Bitcoin Core not responding"
(https://github.com/bitcoin/bitcoin/issues/27964)
### Issues, reports or feature requests related to the GUI should be opened directly on the GUI repo

- [X] I still think this issue should be opened here

### Report

I've just started bitcoin mining a few months ago and I've chosen bitcoin core as the app to store my bitcoins, after 2 days of synchronizing with the network i've 18 weeks left and suddenly my bitcoin core application keeps freezing and not responding. I tried to look for solutions to fix the problem online but most of them said
...

💬 hebasto commented on issue "Bitcoin Core not responding":
(https://github.com/bitcoin/bitcoin/issues/27964#issuecomment-1606018490)
> Issues, reports or feature requests related to the GUI should be opened directly on the GUI repo

Mind moving this issue into the [GUI repo](https://github.com/bitcoin-core/gui) (closing this one and opening a new issue there)?

> my bitcoin core application keeps freezing and not responding.

If it keeps freezing after restarting, more details are welcome, for instance `debug.log` content (NOTE: make sure no private details will leaked).

✅ Zencsy closed an issue: "Bitcoin Core not responding"
(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?

⚠️ 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
...

🤔 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`