💬 manfreddd commented on issue "Bitcoin Core v25.0 Crashes":
(https://github.com/bitcoin/bitcoin/issues/28119#issuecomment-1646284658)
Sure, enclosing the Task Manager window screenshot (in Portuguese).

💬 besoeasy commented on issue "Bitcoin Core v25.0 Crashes":
(https://github.com/bitcoin/bitcoin/issues/28119#issuecomment-1646325159)
@manfreddd you using SSD ? your disc seems slow

💬 besoeasy commented on issue "Bitcoin Core v25.0 Crashes":
(https://github.com/bitcoin/bitcoin/issues/28119#issuecomment-1646325611)

@manfreddd you using SSD ? your disc seems slow

+ your antivirus might be closing bitcoin process for p2p communication

💬 manfreddd commented on issue "Bitcoin Core v25.0 Crashes":
(https://github.com/bitcoin/bitcoin/issues/28119#issuecomment-1646337045)
Enclosing debug file from last Bitcoin Core run.
[debug.log](https://github.com/bitcoin/bitcoin/files/12135141/debug.log)

🤔 vostrnad reviewed a pull request: "script: add description for the functionality of each opcode"
(https://github.com/bitcoin/bitcoin/pull/27109#pullrequestreview-1541936673)
The more I look at this (and especially after the switch to notation), the more I think the descriptions should each be on a separate line above the opcode in a block comment (`/** ... */`). It would allow for longer descriptions where needed without ever exceeding the soft 100-per-line character limit.

The block comments could now include (where appropriate):
* Both a textual description and notation (frankly, I find the notation-only comments quite difficult to read).
* Historical context
...

📝 luke-jr opened a pull request: "Bugfix: RPC: Remove quotes from non-string oneline descriptions"
(https://github.com/bitcoin/bitcoin/pull/28123)
Various JSON Object parameters had a `oneline_description` with quote characters. Fix those, and extend `rpcdoccheck` to detect them.

Also, slightly improve GBT's oneline description for template_request.

💬 theStack commented on pull request "BIP324 ciphersuite":
(https://github.com/bitcoin/bitcoin/pull/28008#discussion_r1271193421)
off-by-one, the "message index wrong" kind of error type (error=12) is currently not tested:
```suggestion
for (unsigned error = 0; error <= 12; ++error) {
```
(to avoid issues like this, could add an enum with error types and give the highest error sth like ERROR_HIGHEST, to be used in the loop counter, but that's probably overkill)

👋 luke-jr's pull request is ready for review: "RPC/Wallet: Convert walletprocesspsbt to use options parameter"
(https://github.com/bitcoin/bitcoin/pull/24963)

💬 luke-jr commented on pull request "RPC/Wallet: Convert walletprocesspsbt to use options parameter":
(https://github.com/bitcoin/bitcoin/pull/24963#issuecomment-1646444551)
Rebased

👍 MarcoFalke approved a pull request: "Bugfix: RPC: Remove quotes from non-string oneline descriptions"
(https://github.com/bitcoin/bitcoin/pull/28123#pullrequestreview-1542053175)
review ACK 5e3e83b005518659a69916c373b808da27e51791

💬 MarcoFalke commented on pull request "Bugfix: RPC: Remove quotes from non-string oneline descriptions":
(https://github.com/bitcoin/bitcoin/pull/28123#discussion_r1271252144)
nit: Could use `STR_INTERNAL_BUG`?

```suggestion
STR_INTERNAL_BUG(strprintf("Internal bug detected: non-string RPC arg \"%s\" quotes oneline_description:\n%s\n",
m_names, m_opts.oneline_description,

)};
```

💬 MarcoFalke commented on pull request "Bugfix: RPC: Remove quotes from non-string oneline descriptions":
(https://github.com/bitcoin/bitcoin/pull/28123#discussion_r1271252337)
I think you can remove the IsNull check below? Also, does this need release notes?

💬 MarcoFalke commented on issue "Bitcoin Core v25.0 Crashes":
(https://github.com/bitcoin/bitcoin/issues/28119#issuecomment-1646498972)
Can you share the output of `gettxoutsetinfo muhash`, which would allow to compare the result to one on another machine to detect potential leveldb corruption.

💬 hebasto commented on pull request "kernel: Remove UniValue from kernel library":
(https://github.com/bitcoin/bitcoin/pull/28113#issuecomment-1646499733)
Suggesting an alternative implementation that is based on the following idea:
```diff
--- a/src/core_read.cpp
+++ b/src/core_read.cpp
@@ -242,10 +242,10 @@ bool ParseHashStr(const std::string& strHex, uint256& result)
return true;
}

-int ParseSighashString(const UniValue& sighash)
+int ParseSighashString(const std::optional<std::string>& sighash)
{
int hash_type = SIGHASH_DEFAULT;
- if (!sighash.isNull()) {
+ if (sighash.has_value()) {
static std::map<
...

📝 MarcoFalke opened a pull request: "fuzz: Re-enable symbolize=1 in ASAN_OPTIONS"
(https://github.com/bitcoin/bitcoin/pull/28124)
Looks like this fixed itself somehow and is no longer reproducible?

💬 hebasto commented on pull request "refactor: Make more transaction size variables signed":
(https://github.com/bitcoin/bitcoin/pull/28059#discussion_r1271259740)
Thanks! Updated.

💬 hebasto commented on issue "32-bit Linux: build flags lost with depends & overriden CC(X)":
(https://github.com/bitcoin/bitcoin/issues/28096#issuecomment-1646515246)
This issue seems related to another one with overridden `CC` and `CXX` -- https://github.com/bitcoin/bitcoin/pull/23571.

💬 MarcoFalke commented on pull request "build: pass sanitize flags to instrument libsecp256k1 code":
(https://github.com/bitcoin/bitcoin/pull/27991#issuecomment-1646529778)
Maybe mark as draft for as long as CI is red?

💬 MarcoFalke commented on pull request "fuzz: wallet, add target for `Crypter`":
(https://github.com/bitcoin/bitcoin/pull/28074#discussion_r1271271794)
That's a no-op assignment

💬 Ayush170-Future commented on pull request "fuzz: wallet, add target for `Crypter`":
(https://github.com/bitcoin/bitcoin/pull/28074#discussion_r1271273469)
Thank you so much for noticing this. I don't know how I missed this.