💬 MarcoFalke commented on issue "Permission to comment on closed PRs":
(https://github.com/bitcoin/bitcoin/issues/27234#issuecomment-1462229567)
I think you can just leave a comment on the open pull to refer to the closed one. Generally, after a long time (1 year) of being closed the discussion is locked to avoid notification of people who left the project or otherwise open the door widely for drive-by spammers.

If you really need or want to comment on a locked pull, my recommendation would be to unlock it first. Otherwise there is no way for someone else to reply.

💬 dergoegge commented on pull request "refactor: Replace GetTimeMicros by SystemClock":
(https://github.com/bitcoin/bitcoin/pull/27233#issuecomment-1462236593)
Concept ACK

📝 fanquake unlocked a pull request: "Blockstorage: Dont access gArgs to get blocks_dir"
(https://github.com/bitcoin/bitcoin/pull/27103)
<!--
*** 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
...

💬 fanquake commented on issue "Permission to comment on closed PRs":
(https://github.com/bitcoin/bitcoin/issues/27234#issuecomment-1462228887)
Yea. Threads are locked to combat spam (and/or when it's clear that the PRs are accidental, wrong repo etc). I've unlocked both now, if you'd like to comment. We can look at if there is some permissions change we can make.

💬 dhruv commented on pull request "BIP324: Enable v2 P2P encrypted transport":
(https://github.com/bitcoin/bitcoin/pull/24545#issuecomment-1462232617)
@vostrnad this is expected because the breaking change is in the p2p layer and not the transport. So a v2 connection is successfully established, and likely the inbound peer (not updated) never sees something that it interprets as the VERSION message. It should have timed out/failed eventually though. Did it do that? This isn't currently considered a downgrade scenario because a v2 transport connection was established. If we downgrade to v1 on p2p unresponsiveness, my thinking is that would lead
...

💬 jamesob commented on pull request "assumeutxo: net_processing changes":
(https://github.com/bitcoin/bitcoin/pull/24008#issuecomment-1462344633)
> Also, as far as I understand it, AssumeUTXO will mess up the order of the blocks stored on disk - the first blockfiles would have the blocks between the AssumeUTXO block and the tip, and the subsequent blockfiles would have the blocks between Genesis and the AssumeUTXO block. I wonder if that could break or slow down something, have you tried a reindex for example?

This is certainly worth addressing. My inclination is to say that given there are only 6925 separate block files on my mainnet
...

👍 kristapsk approved a pull request: "Use string interpolation for default value of -listen"
(https://github.com/bitcoin/bitcoin/pull/27232)
cr utACK 5c938e74cfdf6b89c6c4d5cce2fd07cbfc8b29c2

💬 kristapsk commented on pull request "p2p: set `-dnsseed` and `-listen` false if `maxconnections=0`":
(https://github.com/bitcoin/bitcoin/pull/26899#issuecomment-1462350149)
Concept ACK

💬 achow101 commented on issue "Permission to comment on closed PRs":
(https://github.com/bitcoin/bitcoin/issues/27234#issuecomment-1462349727)
> We can look at if there is some permissions change we can make.

IIRC it requires the "write" permission, which only maintainers have.

💬 achow101 commented on pull request "github: Switch to yaml issue templates":
(https://github.com/bitcoin/bitcoin/pull/27025#issuecomment-1462378021)
ACK 3fa1185dda3b000b9c3956422fd2351e40969dec

💬 dergoegge commented on pull request "tracing: network connection tracepoints":
(https://github.com/bitcoin/bitcoin/pull/25832#issuecomment-1462378467)
Concept ACK

💬 ryanofsky commented on pull request "refactor: Remove CAddressBookData::destdata":
(https://github.com/bitcoin/bitcoin/pull/18608#issuecomment-1462387666)
#27224 is the rebased version of this PR. (I would have reopened this one but ran into github permission issues)

💬 ryanofsky commented on pull request "Blockstorage: Dont access gArgs to get blocks_dir":
(https://github.com/bitcoin/bitcoin/pull/27103#issuecomment-1462391839)
@TheCharlatan

Curious why this PR was closed, and what is its relationship to #27125? Is that a PR a replacement or superset or a different approach?

💬 ryanofsky commented on issue "Permission to comment on closed PRs":
(https://github.com/bitcoin/bitcoin/issues/27234#issuecomment-1462409614)
Thanks for unlocking the PRs.

That is a good point that ability to comment on a locked PR is not really useful because relevant people won't be able to respond. Maybe ideally there would be a way to request that DrahtBot unlocks the PR, and then subsequently relocks it after a period of idle time (like a week or month).

Meantime, I guess I can use this issue to request things to be unlocked if the need arises. (At least until this issue itself is locked :grin:)

✅ ryanofsky closed an issue: "Permission to comment on closed PRs"
(https://github.com/bitcoin/bitcoin/issues/27234)

💬 TheCharlatan commented on pull request "Blockstorage: Dont access gArgs to get blocks_dir":
(https://github.com/bitcoin/bitcoin/pull/27103#issuecomment-1462411439)
> Curious why this PR was closed, and what is its relationship to https://github.com/bitcoin/bitcoin/pull/27125? Is that a PR a replacement or superset or a different approach?

I hit the wrong button by mistake :) - I should have left a comment, or better re-opened as a draft. The approach started here is the same though as in #27125.

🚀 glozow merged a pull request: "github: Switch to yaml issue templates"
(https://github.com/bitcoin/bitcoin/pull/27025)

💬 Sjors commented on pull request "Add test and docs for getblockfrompeer with pruning":
(https://github.com/bitcoin/bitcoin/pull/23813#issuecomment-1462438231)
re-utACK fe329dc936d1e02da406345e4223e11d1fa6fb38

💬 Sjors commented on pull request "assumeutxo":
(https://github.com/bitcoin/bitcoin/pull/15606#issuecomment-1462444460)
CI trips over:

```
src/validation.cpp:5721:1:
error:
return type 'const ChainstateRole' is 'const'-qualified at the top level, which may reduce code readability without improving const correctness [readability-const-return-type,-warnings-as-errors]
```

💬 TheCharlatan commented on pull request "refactor, kernel: Decouple ArgsManager from blockstorage":
(https://github.com/bitcoin/bitcoin/pull/27125#issuecomment-1462445136)
Updated f87c39399823e22c553b797cc66fa4063462a32b -> 6d9826f182d9122d4464d35d6682dc6fb4b1116e ([removeBlockstorageArgs_6](https://github.com/TheCharlatan/bitcoin/tree/removeBlockstorageArgs_6) -> [removeBlockstorageArgs_7](https://github.com/TheCharlatan/bitcoin/tree/removeBlockstorageArgs_7), [compare](https://github.com/TheCharlatan/bitcoin/compare/removeBlockstorageArgs_6..removeBlockstorageArgs_7)) addressing https://github.com/bitcoin/bitcoin/pull/27125#pullrequestreview-1317942691 by insta
...