💬 glozow commented on pull request "p2p: track and use all potential peers for orphan resolution":
(https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1901887320)
deleted now that parent_txids is gone

💬 glozow commented on pull request "p2p: track and use all potential peers for orphan resolution":
(https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1901905478)
Fwiw makes sense, but this function doesn't exist anymore, so marking resolved

💬 glozow commented on pull request "p2p: track and use all potential peers for orphan resolution":
(https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1901882259)
Done

💬 glozow commented on pull request "p2p: track and use all potential peers for orphan resolution":
(https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1901891303)
added

💬 glozow commented on pull request "p2p: track and use all potential peers for orphan resolution":
(https://github.com/bitcoin/bitcoin/pull/31397#issuecomment-2569511364)
Thanks for the reviews @mzumsande @instagibbs! Just got back from holiday, addressed all the comments. Biggest change was recalculating missing parents each time we add a new orphan reso candidate. I also wrote a test for https://github.com/bitcoin/bitcoin/pull/31397#discussion_r1881018172

💬 ismaelsadeeq commented on pull request "BlockAssembler: return selected packages virtual size and fee":
(https://github.com/bitcoin/bitcoin/pull/30391#discussion_r1901970599)

> Is it really a histogram at this point or just a vector of fee rates/fracs?

It is a vector of package fee frac's, which can be used to build a histogram.

> Might be helpful to add a comment here telling that the values in this vector are sorted. That's what I assumed while going through the `CalculatePercentiles` function here.

Yes, it is sorted by the order in which the packages are selected in the block template. I believe this is obvious because we are emplacing the fee fr
...

✅ achow101 closed a pull request: "[28.x] Finalize 28.1"
(https://github.com/bitcoin/bitcoin/pull/31582)

💬 achow101 commented on pull request "[28.x] Finalize 28.1":
(https://github.com/bitcoin/bitcoin/pull/31582#issuecomment-2569523096)
Closing in favor of https://github.com/bitcoin/bitcoin/pull/31594

💬 ismaelsadeeq commented on pull request "BlockAssembler: return selected packages virtual size and fee":
(https://github.com/bitcoin/bitcoin/pull/30391#issuecomment-2569523210)
> Nit: In the PR description, a draft PR is mentioned as the project. Can add this link for project issue: #30392

Added, and addressed your comments!

💬 achow101 commented on pull request "[28.x] 28.1 backports (final?)":
(https://github.com/bitcoin/bitcoin/pull/31594#issuecomment-2569535615)
ACK 1451c56cce3e3df784e1dac969ffb0165df313c7

💬 l0rinc commented on pull request "doc: Clarify comments about endianness after #30526":
(https://github.com/bitcoin/bitcoin/pull/31596#discussion_r1901981925)
```suggestion
* treated as little-endian numbers and sorted in ascending numeric order.
```

💬 remcoros commented on pull request "doc: Clarify comments about endianness after #30526":
(https://github.com/bitcoin/bitcoin/pull/31596#discussion_r1901988639)
'can be used to used to display' -> 'can be used to display'

💬 l0rinc commented on pull request "refactor: Allow std::byte in (Read/Write)(LE/BE)":
(https://github.com/bitcoin/bitcoin/pull/31524#discussion_r1901989166)
I just haven't really seen this being used in the project, but I don't mind if we do.

💬 edilmedeiros commented on pull request "util: detect and warn when using exFAT on MacOS":
(https://github.com/bitcoin/bitcoin/pull/31453#discussion_r1901995035)
Agree with this, even though I have never encountered any problems with the wallet files on a Mac with a FAT formatted disk, only on the blocks dir.

💬 l0rinc commented on pull request "doc: Clarify comments about endianness after #30526":
(https://github.com/bitcoin/bitcoin/pull/31596#discussion_r1901996392)
This was already fixed [`13464c0c44645e0ed88d9d72c3ad697dca800e10..3e0a992a3f0f2b15b7be5049dc4f3134b4b0bc40`#diff-800776e2dd](https://github.com/bitcoin/bitcoin/compare/13464c0c44645e0ed88d9d72c3ad697dca800e10..3e0a992a3f0f2b15b7be5049dc4f3134b4b0bc40#diff-800776e2dda39116e889839f69409571a5d397de048a141da7e4003bc099e3e2)L88

💬 TheCharlatan commented on pull request "kernel: Move kernel-related cache constants to kernel cache":
(https://github.com/bitcoin/bitcoin/pull/31483#issuecomment-2569566280)
Thank you for the review and code suggestions @hodlinator,

Updated 7517126d9fd2c3e50dc95ce831bac6895b950e24 -> ad80e410b3bf8814cb5b997715ee8cb28f2a2a66 ([kernel_cache_sizes_4](https://github.com/TheCharlatan/bitcoin/tree/kernel_cache_sizes_4) -> [kernel_cache_sizes_5](https://github.com/TheCharlatan/bitcoin/tree/kernel_cache_sizes_5), [compare](https://github.com/TheCharlatan/bitcoin/compare/kernel_cache_sizes_4..kernel_cache_sizes_5))

* Add handling for dbcache sizes exceeding `size_t` si
...

💬 remcoros commented on pull request "doc: Clarify comments about endianness after #30526":
(https://github.com/bitcoin/bitcoin/pull/31596#discussion_r1901998957)
👍 my bad, github didn't show it as outdated and was looking at the convo tab.

💬 edilmedeiros commented on pull request "util: detect and warn when using exFAT on MacOS":
(https://github.com/bitcoin/bitcoin/pull/31453#issuecomment-2569575625)
Concept ACK.

Already lost many hours trying to debug this and my conclusion so far is that the FAT driver on macOS is flawed.
Also, it's quite difficult to reproduce this reliably, IBD will fail in a different point every time. Maybe we can detect a broken block in persistent memory and restart IBD from there?

💬 edilmedeiros commented on pull request "util: detect and warn when using exFAT on MacOS":
(https://github.com/bitcoin/bitcoin/pull/31453#discussion_r1902010252)
If my memory is not failing me, I have seem only macOS related issues reporting problems with exFAT external drivers. I tried exFAT on the internal drive of an old 2016 Intel Macbook Pro (original 1GB SSD, APFS on a primary partition and exFAT on a secondary partition for Bitcoin data) and IBD failed on v26. It was about a year ago, I was trying to understand if it was a problem with the external drive I was using at the time or a software problem. Unfortunately, I can't try that again with that
...

💬 mzumsande commented on issue "Assertion pindexPrev && pindexPrev == chainstate.m_chain.Tip() when running regtest":
(https://github.com/bitcoin/bitcoin/issues/31562#issuecomment-2569582744)
> Thx alot! so is this expected to reach the next release cycle? which version will it be included in?

Looks like it will already be fixed in 28.1 (backport PR #31594) which should be released soon.

💬 rkrux commented on pull request "BlockAssembler: return selected packages virtual size and fee":
(https://github.com/bitcoin/bitcoin/pull/30391#discussion_r1902019482)
> It is a vector of package fee frac's, which can be used to build a histogram.

Building a histogram seems to be one of the use cases of this field. I don't feel it should be called a histogram only because of this. Is there any other reason as well?
I hope I'm not missing any context here.