💬 theuni commented on pull request "build: use macOS 14 SDK (Xcode 15.0)":
(https://github.com/bitcoin/bitcoin/pull/28622#issuecomment-1839051585)
> c0c2e7bb92c1fee0c4e9f3a485e4530786732d6c6dd9e9f418c282aa6892f55d Xcode-15.0-15A240d-extracted-SDK-with-libcxx-headers.tar.gz
Has been generated and is ready for use now by c-i.
(https://github.com/bitcoin/bitcoin/pull/28622#issuecomment-1839051585)
> c0c2e7bb92c1fee0c4e9f3a485e4530786732d6c6dd9e9f418c282aa6892f55d Xcode-15.0-15A240d-extracted-SDK-with-libcxx-headers.tar.gz
Has been generated and is ready for use now by c-i.
💬 fanquake commented on pull request "build: use macOS 14 SDK (Xcode 15.0)":
(https://github.com/bitcoin/bitcoin/pull/28622#issuecomment-1839054583)
> Has been generated and is ready for use now by c-i.
Force pushed for a CI run.
(https://github.com/bitcoin/bitcoin/pull/28622#issuecomment-1839054583)
> Has been generated and is ready for use now by c-i.
Force pushed for a CI run.
🤔 Sjors reviewed a pull request: "build: use macOS 14 SDK (Xcode 15.0)"
(https://github.com/bitcoin/bitcoin/pull/28622#pullrequestreview-1762543137)
Guix hashes:
```
fedbab3012043b4277a19fbd0a1abdb5d8e895446bba470981cef361064cdba6 guix-build-984cbe4f84a6/output/arm64-apple-darwin/SHA256SUMS.part
e40c88780560f4aa1e15657373cf6e6149878c90c1acb2980a6015c368378485 guix-build-984cbe4f84a6/output/arm64-apple-darwin/bitcoin-984cbe4f84a6-arm64-apple-darwin-unsigned.tar.gz
795221e68c86cb46684dcb80e729e6dd887402930bc8f911b97840f563c4fab8 guix-build-984cbe4f84a6/output/arm64-apple-darwin/bitcoin-984cbe4f84a6-arm64-apple-darwin-unsigned.zip
079
...
(https://github.com/bitcoin/bitcoin/pull/28622#pullrequestreview-1762543137)
Guix hashes:
```
fedbab3012043b4277a19fbd0a1abdb5d8e895446bba470981cef361064cdba6 guix-build-984cbe4f84a6/output/arm64-apple-darwin/SHA256SUMS.part
e40c88780560f4aa1e15657373cf6e6149878c90c1acb2980a6015c368378485 guix-build-984cbe4f84a6/output/arm64-apple-darwin/bitcoin-984cbe4f84a6-arm64-apple-darwin-unsigned.tar.gz
795221e68c86cb46684dcb80e729e6dd887402930bc8f911b97840f563c4fab8 guix-build-984cbe4f84a6/output/arm64-apple-darwin/bitcoin-984cbe4f84a6-arm64-apple-darwin-unsigned.zip
079
...
💬 Sjors commented on pull request "build: use macOS 14 SDK (Xcode 15.0)":
(https://github.com/bitcoin/bitcoin/pull/28622#discussion_r1414183497)
This matches for me, as of 984cbe4f84a6eb32153f7fc46c220a0ccb2746f9
(https://github.com/bitcoin/bitcoin/pull/28622#discussion_r1414183497)
This matches for me, as of 984cbe4f84a6eb32153f7fc46c220a0ccb2746f9
💬 theuni commented on pull request "build: use macOS 14 SDK (Xcode 15.0)":
(https://github.com/bitcoin/bitcoin/pull/28622#discussion_r1414202624)
Does this obsolete/interact with mlinker-version at all?
(https://github.com/bitcoin/bitcoin/pull/28622#discussion_r1414202624)
Does this obsolete/interact with mlinker-version at all?
🤔 theuni reviewed a pull request: "build: use macOS 14 SDK (Xcode 15.0)"
(https://github.com/bitcoin/bitcoin/pull/28622#pullrequestreview-1762939462)
Concept ACK. My generated tarball hash matches @fanquake's.
(https://github.com/bitcoin/bitcoin/pull/28622#pullrequestreview-1762939462)
Concept ACK. My generated tarball hash matches @fanquake's.
💬 fanquake commented on pull request "build: use macOS 14 SDK (Xcode 15.0)":
(https://github.com/bitcoin/bitcoin/pull/28622#issuecomment-1839077604)
Guix build (aarch64):
```bash
fedbab3012043b4277a19fbd0a1abdb5d8e895446bba470981cef361064cdba6 guix-build-984cbe4f84a6/output/arm64-apple-darwin/SHA256SUMS.part
e40c88780560f4aa1e15657373cf6e6149878c90c1acb2980a6015c368378485 guix-build-984cbe4f84a6/output/arm64-apple-darwin/bitcoin-984cbe4f84a6-arm64-apple-darwin-unsigned.tar.gz
795221e68c86cb46684dcb80e729e6dd887402930bc8f911b97840f563c4fab8 guix-build-984cbe4f84a6/output/arm64-apple-darwin/bitcoin-984cbe4f84a6-arm64-apple-darwin-unsign
...
(https://github.com/bitcoin/bitcoin/pull/28622#issuecomment-1839077604)
Guix build (aarch64):
```bash
fedbab3012043b4277a19fbd0a1abdb5d8e895446bba470981cef361064cdba6 guix-build-984cbe4f84a6/output/arm64-apple-darwin/SHA256SUMS.part
e40c88780560f4aa1e15657373cf6e6149878c90c1acb2980a6015c368378485 guix-build-984cbe4f84a6/output/arm64-apple-darwin/bitcoin-984cbe4f84a6-arm64-apple-darwin-unsigned.tar.gz
795221e68c86cb46684dcb80e729e6dd887402930bc8f911b97840f563c4fab8 guix-build-984cbe4f84a6/output/arm64-apple-darwin/bitcoin-984cbe4f84a6-arm64-apple-darwin-unsign
...
👍 andrewtoth approved a pull request: "init: don't delete PID file if it was not generated"
(https://github.com/bitcoin/bitcoin/pull/28946#pullrequestreview-1762959130)
ACK 8f6ab318635d823a7e6ad9020ac17b8d2dd0e91b
(https://github.com/bitcoin/bitcoin/pull/28946#pullrequestreview-1762959130)
ACK 8f6ab318635d823a7e6ad9020ac17b8d2dd0e91b
💬 achow101 commented on pull request "wallet: skip BnB when SFFO is enabled":
(https://github.com/bitcoin/bitcoin/pull/28994#discussion_r1414228551)
For unit tests, having the information in a struct is fine. However I'm not sure that it is really useful information to return in the RPC. IIRC my suggestion for searching the debug log is for functional tests since those already have an `assert_debug_log` helper.
(https://github.com/bitcoin/bitcoin/pull/28994#discussion_r1414228551)
For unit tests, having the information in a struct is fine. However I'm not sure that it is really useful information to return in the RPC. IIRC my suggestion for searching the debug log is for functional tests since those already have an `assert_debug_log` helper.
💬 fanquake commented on pull request "build: use macOS 14 SDK (Xcode 15.0)":
(https://github.com/bitcoin/bitcoin/pull/28622#discussion_r1414229876)
From having another look now, Clang still uses `-mlinker-version`, in it's decision making about whether to use `-platform_version` (by default), which it does if the linker version is > 520. If we are passing `-platform_version` ourselves, then maybe we can drop `-mlinker-version`, but I would have to look again, to see if there are other side effects, and this is probably ok to leave for now, and revisit when we do the lld switch, as I assume more flags are going to change there as well.
(https://github.com/bitcoin/bitcoin/pull/28622#discussion_r1414229876)
From having another look now, Clang still uses `-mlinker-version`, in it's decision making about whether to use `-platform_version` (by default), which it does if the linker version is > 520. If we are passing `-platform_version` ourselves, then maybe we can drop `-mlinker-version`, but I would have to look again, to see if there are other side effects, and this is probably ok to leave for now, and revisit when we do the lld switch, as I assume more flags are going to change there as well.
💬 maflcko commented on pull request "build: use macOS 14 SDK (Xcode 15.0)":
(https://github.com/bitcoin/bitcoin/pull/28622#issuecomment-1839131640)
https://cirrus-ci.com/task/4855730595954688?logs=ci#L8068
```
configure:33916: error: External signing is not supported for this Boost version
(https://github.com/bitcoin/bitcoin/pull/28622#issuecomment-1839131640)
https://cirrus-ci.com/task/4855730595954688?logs=ci#L8068
```
configure:33916: error: External signing is not supported for this Boost version
⚠️ FU3X opened an issue: "are there any plans to deal with fees?"
(https://github.com/bitcoin/bitcoin/issues/28995)
like a future update or eta?
(https://github.com/bitcoin/bitcoin/issues/28995)
like a future update or eta?
💬 fanquake commented on pull request "build: use macOS 14 SDK (Xcode 15.0)":
(https://github.com/bitcoin/bitcoin/pull/28622#issuecomment-1839158062)
> https://cirrus-ci.com/task/4855730595954688?logs=ci#L8068
> configure:33916: error: External signing is not supported for this Boost version
Nice. It's this issue https://github.com/boostorg/process/issues/342 & change https://github.com/boostorg/process/pull/343 from upstream Boost Process.
(https://github.com/bitcoin/bitcoin/pull/28622#issuecomment-1839158062)
> https://cirrus-ci.com/task/4855730595954688?logs=ci#L8068
> configure:33916: error: External signing is not supported for this Boost version
Nice. It's this issue https://github.com/boostorg/process/issues/342 & change https://github.com/boostorg/process/pull/343 from upstream Boost Process.
✅ fanquake closed an issue: "are there any plans to deal with fees?"
(https://github.com/bitcoin/bitcoin/issues/28995)
(https://github.com/bitcoin/bitcoin/issues/28995)
💬 ryanofsky commented on issue "`capnp` fails when cross-compiling":
(https://github.com/bitcoin/bitcoin/issues/28993#issuecomment-1839184118)
I'm struggling to get darwin build working locally, but I will try docker to reproduce this. Do you know if this might be a recent regression, or when was the last time it might have worked?
(https://github.com/bitcoin/bitcoin/issues/28993#issuecomment-1839184118)
I'm struggling to get darwin build working locally, but I will try docker to reproduce this. Do you know if this might be a recent regression, or when was the last time it might have worked?
📝 theStack opened a pull request: "test: maxuploadtarget: check for mempool msg disconnect if limit is reached, improve existing test coverage"
(https://github.com/bitcoin/bitcoin/pull/28996)
This PR improves existing and adds new test coverage for the `-maxuploadtarget` mechanism (feature_maxuploadtarget.py) in the following ways, one commit each:
* verify the uploadtarget state via the `getnettotals` RPC (`uploadtarget` result field):
https://github.com/bitcoin/bitcoin/blob/160d23677ad799cf9b493eaa923b2ac080c3fb8e/src/rpc/net.cpp#L581-L582
Note that reaching the total limit (`target_reached` == True) always implies that the historical blocks serving limits is also reached (`serv
...
(https://github.com/bitcoin/bitcoin/pull/28996)
This PR improves existing and adds new test coverage for the `-maxuploadtarget` mechanism (feature_maxuploadtarget.py) in the following ways, one commit each:
* verify the uploadtarget state via the `getnettotals` RPC (`uploadtarget` result field):
https://github.com/bitcoin/bitcoin/blob/160d23677ad799cf9b493eaa923b2ac080c3fb8e/src/rpc/net.cpp#L581-L582
Note that reaching the total limit (`target_reached` == True) always implies that the historical blocks serving limits is also reached (`serv
...
🤔 mzumsande reviewed a pull request: "net: Continuous ASMap health check"
(https://github.com/bitcoin/bitcoin/pull/27581#pullrequestreview-1763108020)
ACK 3ea54e5db7d53da5afa321e1800c29aa269dd3b3
(https://github.com/bitcoin/bitcoin/pull/27581#pullrequestreview-1763108020)
ACK 3ea54e5db7d53da5afa321e1800c29aa269dd3b3
🤔 jonatack reviewed a pull request: "rpc: encryptwallet help, mention HD seed rotation and backup requirement"
(https://github.com/bitcoin/bitcoin/pull/28980#pullrequestreview-1763137265)
Concept ACK
(https://github.com/bitcoin/bitcoin/pull/28980#pullrequestreview-1763137265)
Concept ACK
💬 jonatack commented on pull request "rpc: encryptwallet help, mention HD seed rotation and backup requirement":
(https://github.com/bitcoin/bitcoin/pull/28980#discussion_r1414333653)
s/file, containing/file that contains/
Suggest:
"Therefore, it is crucial to make a fresh backup of the newly generated wallet file."
(https://github.com/bitcoin/bitcoin/pull/28980#discussion_r1414333653)
s/file, containing/file that contains/
Suggest:
"Therefore, it is crucial to make a fresh backup of the newly generated wallet file."
💬 jonatack commented on pull request "rpc: encryptwallet help, mention HD seed rotation and backup requirement":
(https://github.com/bitcoin/bitcoin/pull/28980#discussion_r1414328971)
"backup" is a noun spelled as a single word, while "back up" is a verb spelled as 2 words
```suggestion
"Please exercise caution and ensure that you securely back up the updated wallet file to safeguard your funds and wallet information.\n",
```
(https://github.com/bitcoin/bitcoin/pull/28980#discussion_r1414328971)
"backup" is a noun spelled as a single word, while "back up" is a verb spelled as 2 words
```suggestion
"Please exercise caution and ensure that you securely back up the updated wallet file to safeguard your funds and wallet information.\n",
```