💬 russeree commented on pull request "CONTRIBUTING: Caution against using AI/LLMs (ChatGPT, Copilot, etc)":
(https://github.com/bitcoin/bitcoin/pull/28175#issuecomment-1654866248)
Concept ACK.

The two thoughts that come to mind are that

1. This section could become a cat and mouse game between the various models. ```but not limited to, ChatGPT, GitHub Copilot, and Meta LLaMA``` which ones of these will still have relevance in the future.

2. LLMs right now are the benchmark for text to text models but there are other types of models as well example NLP and RNN models. So this language could become obsolete overtime.

This post was written by GPT4 ... Just K
...

💬 jonatack commented on pull request " test: Extend stale_tip_peer_management test ":
(https://github.com/bitcoin/bitcoin/pull/23352#issuecomment-1654878558)
> > I wonder if it's possible (and worth it) to tweak the test such that it would have caught #26172.
>
> I have a [test](https://github.com/LarryRuane/bitcoin/commit/3f847e4c4e5f89f812407eef39d421f45b0eea02) for that but haven't made the PR yet (I'll do that this week). I'll compare what I have to this PR since there's likely some overlap.

@LarryRuane any update on the test?

💬 russeree commented on pull request "docs: Rewrite README to make it more appealing":
(https://github.com/bitcoin/bitcoin/pull/28174#issuecomment-1654878736)
My technical objection is that emoji illustrations vary between browsers, devices, and browser versions. The use of emojis would create an inconsistent experience between platforms.

My emotional and personal objection is and I mean this in the nicest way possible. I don't like the 'vibe' the changes to more informal language creates. It also makes the document less concise.

- The phrase ```Curious to know more? Find further details``` feels like a pitch almost as compared to the current `
...

💬 jonatack commented on pull request "net: Use serialization parameters for CAddress serialization":
(https://github.com/bitcoin/bitcoin/pull/25284#issuecomment-1654879568)
Concept ACK, will have a look.

💬 ariard commented on pull request "docs: Rewrite README to make it more appealing":
(https://github.com/bitcoin/bitcoin/pull/28174#issuecomment-1654897482)
I’m not sure keeping the project documentation as easy-to-read and engaging with emojis is that much a goal in itself considering Bitcoin Core is a security-first project underpinning a $567 billions ecosystem, where contributors would be rather invited to run their workflow on attack-surface minimized workstation. Rich graphical rendering requires lengthier and more opaque software supply chain.

Not a strong opinion, though there has been a [talk at DEFCON 30](https://media.defcon.org/DEF%20
...

💬 kevkevinpal commented on pull request "init: changing -torcontrol help to specify that a default port is used":
(https://github.com/bitcoin/bitcoin/pull/28101#discussion_r1277044095)
Valid point will change to the following

`"Tor control host and port to use if onion listening enabled (default: %s). If no port is specified, the default port will be used (default: %s)."`

💬 kevkevinpal commented on pull request "CONTRIBUTING: Caution against using AI/LLMs (ChatGPT, Copilot, etc)":
(https://github.com/bitcoin/bitcoin/pull/28175#issuecomment-1654947763)
ACK [08f9f62](https://github.com/bitcoin/bitcoin/pull/28175/commits/08f9f62dc4c1f2b2864d9a5f78b4f490b0debe87)

I was one of the mentioned PR's https://github.com/bitcoin/bitcoin/pull/28101

Would make sense to have this in the CONTRIBUTING.md

🤔 ariard reviewed a pull request: "CONTRIBUTING: Caution against using AI/LLMs (ChatGPT, Copilot, etc)"
(https://github.com/bitcoin/bitcoin/pull/28175#pullrequestreview-1551270145)
To be honest, and after looking on some LLM-term of service and in basic knowledge of copyright law, there is an uncertainty on the status of LLM output. It sounds LLM or AI operating platforms in their terms of service do no make the claim they own the intellectual property of the LLM output, and if even if they do so it’s probably an unfounded claim. A user might mix an “original” or “creative” element by sending an individual prompt request, a determining factor in any matter of intellectual
...

💬 ariard commented on pull request "CONTRIBUTING: Caution against using AI/LLMs (ChatGPT, Copilot, etc)":
(https://github.com/bitcoin/bitcoin/pull/28175#discussion_r1277040875)
I would recommend to drop any reference to a corporate entity, or one of its product in Bitcoin Core documentation, to avoid a mischaracterization of what they’re doing (whatever one personal opinion).

We already mentioned Github a lot in the contributing.md, though only as the technical platform where contributions are happening, not taking a stance on one of their product.

📝 kevkevinpal opened a pull request: "tests: add coverage to feature_addrman.py"
(https://github.com/bitcoin/bitcoin/pull/28176)
I added two new tests that will cover the nNew and nTried tests which add coverage to the if block by checking values larger than our range since we only check for negative values now

adding coverage to these lines
https://github.com/bitcoin/bitcoin/blob/master/src/addrman.cpp#L273
https://github.com/bitcoin/bitcoin/blob/master/src/addrman.cpp#L280

our test seem to only cover the `nTried < 0` and `nNew < 0` scenarios
<!--
*** Please remove the following help text before submitting: ***
...

💬 MarcoFalke commented on pull request "ci: Run Windows native task on GitHub Actions":
(https://github.com/bitcoin/bitcoin/pull/28173#issuecomment-1655060132)
Can you remove the Windows Cirrus task here, as it will need to be removed either way? Also, a link to a build would be nice, before this is enabled here.

💬 MarcoFalke commented on pull request "ci: Run Windows native task on GitHub Actions":
(https://github.com/bitcoin/bitcoin/pull/28173#issuecomment-1655061310)
Maybe also print the `GITHUB_TOKEN` permissions at every start of the task, just to double check they are read-only?

💬 MarcoFalke commented on pull request "ci: Run Windows native task on GitHub Actions":
(https://github.com/bitcoin/bitcoin/pull/28173#discussion_r1277118408)
```suggestion
on: [pull_request, push] # https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore
```

👍 MarcoFalke approved a pull request: "fuzz: add target for `ScriptPubKeyMan` (legacy)"
(https://github.com/bitcoin/bitcoin/pull/28153#pullrequestreview-1551387955)
lgtm

💬 MarcoFalke commented on pull request "fuzz: add target for `ScriptPubKeyMan` (legacy)":
(https://github.com/bitcoin/bitcoin/pull/28153#discussion_r1277122561)
nit: Could use `PickValue`?

🤔 MarcoFalke requested changes to a pull request: "rpc, util: avoid string copies in ParseHash/ParseHex functions"
(https://github.com/bitcoin/bitcoin/pull/28172#pullrequestreview-1551412773)
Not sure. This has no effect on the compiled binary and is only changing the style of the code.

💬 MarcoFalke commented on pull request "rpc, util: avoid string copies in ParseHash/ParseHex functions":
(https://github.com/bitcoin/bitcoin/pull/28172#discussion_r1277134227)
The names are short, so a copy or reference should make no difference. Also, a copy is still done when the input is a c-string, which is the case here for all call sites.

🤔 MarcoFalke requested changes to a pull request: "test: blockstore test with chattr instead of chmod"
(https://github.com/bitcoin/bitcoin/pull/28171#pullrequestreview-1551429665)
I think you can just use the existing pull request to push the changes. It is clear that this approach will be working. Just pay attention to the details and make sure you are confident in your diff before you push, if possible.

✅ MarcoFalke closed a pull request: "test: blockstore test with chattr instead of chmod"
(https://github.com/bitcoin/bitcoin/pull/28171)

💬 MarcoFalke commented on pull request "test: blockstore test with chattr instead of chmod":
(https://github.com/bitcoin/bitcoin/pull/28171#discussion_r1277145643)
This has nothing to do with asan, you will have to add it to all created containers.