💬 willcl-ark commented on issue "Simpler settings interpretation":
(https://github.com/bitcoin/bitcoin/issues/17508#issuecomment-3427148415)
Closing this as it hasn’t seen any activity for a while. If you’d like to continue the discussion or feel the topic is still important, please leave a comment and we can reopen it.
(https://github.com/bitcoin/bitcoin/issues/17508#issuecomment-3427148415)
Closing this as it hasn’t seen any activity for a while. If you’d like to continue the discussion or feel the topic is still important, please leave a comment and we can reopen it.
✅ willcl-ark closed an issue: "contrib: add symbol-check test for non-existence of `vmova` instructions in Windows build"
(https://github.com/bitcoin/bitcoin/issues/28413)
(https://github.com/bitcoin/bitcoin/issues/28413)
💬 willcl-ark commented on issue "contrib: add symbol-check test for non-existence of `vmova` instructions in Windows build":
(https://github.com/bitcoin/bitcoin/issues/28413#issuecomment-3427183919)
It looks like this issue has been resolved. If that’s not the case, please let us know by commenting here or opening a new issue.
(https://github.com/bitcoin/bitcoin/issues/28413#issuecomment-3427183919)
It looks like this issue has been resolved. If that’s not the case, please let us know by commenting here or opening a new issue.
✅ willcl-ark closed an issue: "Allow creating and injecting a custom coinbase into a block template"
(https://github.com/bitcoin/bitcoin/issues/28475)
(https://github.com/bitcoin/bitcoin/issues/28475)
💬 willcl-ark commented on issue "Allow creating and injecting a custom coinbase into a block template":
(https://github.com/bitcoin/bitcoin/issues/28475#issuecomment-3427198007)
This issue hasn’t attracted much interest from other contributors in quite some time.
Given that, it doesn’t seem important enough to keep open indefinitely. I’m going to close it for now due to lack of activity, but pull requests or renewed discussion are always welcome.
Comment here if you think this should be re-opened.
(https://github.com/bitcoin/bitcoin/issues/28475#issuecomment-3427198007)
This issue hasn’t attracted much interest from other contributors in quite some time.
Given that, it doesn’t seem important enough to keep open indefinitely. I’m going to close it for now due to lack of activity, but pull requests or renewed discussion are always welcome.
Comment here if you think this should be re-opened.
💬 maflcko commented on issue "ci: Where to run heavy and fragile CI tasks?":
(https://github.com/bitcoin/bitcoin/issues/33668#issuecomment-3427202876)
Good point that if the only issue is the CPU usage, it could be fixed by more CPU. Though, stuff like msan on -O0 is so heavy that it doesn't pass at all on the GHA provided VM after 6 hours, so it will likely be slow enough to not make sense on pull requests at all.
(https://github.com/bitcoin/bitcoin/issues/33668#issuecomment-3427202876)
Good point that if the only issue is the CPU usage, it could be fixed by more CPU. Though, stuff like msan on -O0 is so heavy that it doesn't pass at all on the GHA provided VM after 6 hours, so it will likely be slow enough to not make sense on pull requests at all.
✅ willcl-ark closed an issue: "Bitcoin OpenRPC Specification"
(https://github.com/bitcoin/bitcoin/issues/29477)
(https://github.com/bitcoin/bitcoin/issues/29477)
💬 willcl-ark commented on issue "Bitcoin OpenRPC Specification":
(https://github.com/bitcoin/bitcoin/issues/29477#issuecomment-3427216236)
Closing this one in favour of #29912. Please continue discussion of this topic there.
(https://github.com/bitcoin/bitcoin/issues/29477#issuecomment-3427216236)
Closing this one in favour of #29912. Please continue discussion of this topic there.
✅ willcl-ark closed an issue: "Porting bcc tools to libbpf"
(https://github.com/bitcoin/bitcoin/issues/30298)
(https://github.com/bitcoin/bitcoin/issues/30298)
💬 willcl-ark commented on issue "Porting bcc tools to libbpf":
(https://github.com/bitcoin/bitcoin/issues/30298#issuecomment-3427237510)
This issue hasn’t attracted much interest from other contributors in some time.
Given that, it doesn’t seem important enough to keep open indefinitely. I’m going to close it for now due to lack of activity, but pull requests or renewed discussion are always welcome.
Comment here if you think this should be re-opened.
(https://github.com/bitcoin/bitcoin/issues/30298#issuecomment-3427237510)
This issue hasn’t attracted much interest from other contributors in some time.
Given that, it doesn’t seem important enough to keep open indefinitely. I’m going to close it for now due to lack of activity, but pull requests or renewed discussion are always welcome.
Comment here if you think this should be re-opened.
✅ maflcko closed an issue: "Test Framework - test_framework.test_node.FailedToStartError: No RPC credentials"
(https://github.com/bitcoin/bitcoin/issues/30818)
(https://github.com/bitcoin/bitcoin/issues/30818)
💬 maflcko commented on issue "Test Framework - test_framework.test_node.FailedToStartError: No RPC credentials":
(https://github.com/bitcoin/bitcoin/issues/30818#issuecomment-3427239821)
> I presume adding support for tests directly on Windows is easier (or adding documentation on how to do it).
This is done in the CI now. See:
https://github.com/bitcoin/bitcoin/blob/c862936d16a640690ef4c89456738fe4bb99be54/.github/workflows/ci.yml#L382-L443
The basic idea is that you re-write the `test/config.ini` file.
(https://github.com/bitcoin/bitcoin/issues/30818#issuecomment-3427239821)
> I presume adding support for tests directly on Windows is easier (or adding documentation on how to do it).
This is done in the CI now. See:
https://github.com/bitcoin/bitcoin/blob/c862936d16a640690ef4c89456738fe4bb99be54/.github/workflows/ci.yml#L382-L443
The basic idea is that you re-write the `test/config.ini` file.
✅ willcl-ark closed an issue: "Doc: Consolidate documentation of functional test parameters."
(https://github.com/bitcoin/bitcoin/issues/17380)
(https://github.com/bitcoin/bitcoin/issues/17380)
💬 willcl-ark commented on issue "Doc: Consolidate documentation of functional test parameters.":
(https://github.com/bitcoin/bitcoin/issues/17380#issuecomment-3427241149)
This issue hasn’t attracted much interest from other contributors in quite some time.
Given that, it doesn’t seem important enough to keep open indefinitely. I’m going to close it for now due to lack of activity, but pull requests or renewed discussion are always welcome.
Comment here if you think this should be re-opened.
(https://github.com/bitcoin/bitcoin/issues/17380#issuecomment-3427241149)
This issue hasn’t attracted much interest from other contributors in quite some time.
Given that, it doesn’t seem important enough to keep open indefinitely. I’m going to close it for now due to lack of activity, but pull requests or renewed discussion are always welcome.
Comment here if you think this should be re-opened.
✅ willcl-ark closed an issue: "CI: Make failure message easier to spot"
(https://github.com/bitcoin/bitcoin/issues/31200)
(https://github.com/bitcoin/bitcoin/issues/31200)
💬 willcl-ark commented on issue "CI: Make failure message easier to spot":
(https://github.com/bitcoin/bitcoin/issues/31200#issuecomment-3427249269)
It looks like this issue has been resolved. If that’s not the case, please let us know by commenting here or opening a new issue.
(https://github.com/bitcoin/bitcoin/issues/31200#issuecomment-3427249269)
It looks like this issue has been resolved. If that’s not the case, please let us know by commenting here or opening a new issue.
✅ willcl-ark closed an issue: "qa: `PermissionError` in functional tests on Windows"
(https://github.com/bitcoin/bitcoin/issues/28529)
(https://github.com/bitcoin/bitcoin/issues/28529)
💬 willcl-ark commented on issue "qa: `PermissionError` in functional tests on Windows":
(https://github.com/bitcoin/bitcoin/issues/28529#issuecomment-3427255585)
Since the problem isn’t easily reproducible, I’m closing this for now. If it occurs again, please feel free to open a new issue or comment here so we can reopen it.
(https://github.com/bitcoin/bitcoin/issues/28529#issuecomment-3427255585)
Since the problem isn’t easily reproducible, I’m closing this for now. If it occurs again, please feel free to open a new issue or comment here so we can reopen it.
💬 TheCharlatan commented on pull request "Add libbitcoinkernel example files":
(https://github.com/bitcoin/bitcoin/pull/33669#issuecomment-3427265866)
Concept ACK
I have something similar over at http://thecharlatan.ch/kernel-docs/examples.html . Purplelkarrot also suggested to have code examples in the style of https://purplekarrot.github.io/btck/design/naming_conventions.html (at the bottom). The tabbed views between the languages look particularly nice imo. I am not sure if we should host this in this repo though. We discussed having a separate repo (under the bitcoin-core org) to host language bindings, examples, and docs in a coherent
...
(https://github.com/bitcoin/bitcoin/pull/33669#issuecomment-3427265866)
Concept ACK
I have something similar over at http://thecharlatan.ch/kernel-docs/examples.html . Purplelkarrot also suggested to have code examples in the style of https://purplekarrot.github.io/btck/design/naming_conventions.html (at the bottom). The tabbed views between the languages look particularly nice imo. I am not sure if we should host this in this repo though. We discussed having a separate repo (under the bitcoin-core org) to host language bindings, examples, and docs in a coherent
...
💬 BenWestgate commented on pull request "doc: update multisig tutorial to use multipath descriptors":
(https://github.com/bitcoin/bitcoin/pull/33286#issuecomment-3427270530)
> This isn't quite true for multipath descriptors:
>
> > The checksum for a descriptor without one...**
>
> We have to take the `checksum` field and append it to the multipath input descriptor, similar to private key descriptors.
>
> Do we need to document this?
Resolved my own concerns with: https://github.com/bitcoin/bitcoin/pull/33286/commits/de7c3587cd4586bbed94a4ea6eae4a252301daee
(https://github.com/bitcoin/bitcoin/pull/33286#issuecomment-3427270530)
> This isn't quite true for multipath descriptors:
>
> > The checksum for a descriptor without one...**
>
> We have to take the `checksum` field and append it to the multipath input descriptor, similar to private key descriptors.
>
> Do we need to document this?
Resolved my own concerns with: https://github.com/bitcoin/bitcoin/pull/33286/commits/de7c3587cd4586bbed94a4ea6eae4a252301daee