✅ RomanBelkov closed an issue: "large wallet: Bitcoind freezes"
(https://github.com/bitcoin/bitcoin/issues/15148)

💬 TheCharlatan commented on pull request "refactor: Extract common/args from util/system":
(https://github.com/bitcoin/bitcoin/pull/27419#issuecomment-1514467370)
Thank you for the reviews, decided to address the left over nits here:

Updated ec51c252de42e11906f114ac05e476fd88ca2176 -> be55f545d53d44fdcf2d8ae802e9eae551d120c6 ([splitSystemArgs_3](https://github.com/TheCharlatan/bitcoin/commits/splitSystemArgs_3) -> [splitSystemArgs_4](https://github.com/TheCharlatan/bitcoin/commits/splitSystemArgs_4), [compare](https://github.com/TheCharlatan/bitcoin/compare/splitSystemArgs_3..splitSystemArgs_4)):
* Addressed @ryanofsky's [comment](https://github.com/b
...

⚠️ batriskaweb3 opened an issue: "Compiling a bitcoin core version that accepts transactions over 100vkb"
(https://github.com/bitcoin/bitcoin/issues/27490)
### Please describe the feature you'd like to see added.

i couldnt manage to find any label that fits this,
when people try to inscribe ordinals that are bigger than 400kb they can not be able to because bitcoin core doesnt allow transactions over 100kvb
even though that would require the person to be a miner or pay miners for it but it still would be nice to guide us on how to compile such bitcoin core version

### Is your feature related to a problem, if so please describe it.

_No response
...

📝 TheCharlatan opened a pull request: "Kernel chain type"
(https://github.com/bitcoin/bitcoin/pull/27491)
This pull request is part of the `libbitcoinkernel` project https://github.com/bitcoin/bitcoin/issues/24303 https://github.com/bitcoin/bitcoin/projects/18 and more specifically its "Step 2: Decouple most non-consensus code from libbitcoinkernel". It is also a follow up to #26177.

It replaces pull request https://github.com/bitcoin/bitcoin/pull/27294, which just moved the constants to a new file, but did not re-declare them as enums.

The code move of the chain name constants out of the `cha
...

💬 TheCharlatan commented on pull request "refactor: Move chain names to the util library":
(https://github.com/bitcoin/bitcoin/pull/27294#issuecomment-1514490390)
Re https://github.com/bitcoin/bitcoin/pull/27294#pullrequestreview-1376476610
> However I think as long as every usage of the constants is changing anyway, it would be better to turn this into to enum and not introduce an odd namespace with string symbols. Suggestion would be to add a new `src/util/chain_types.h` file with:

I initially wanted to implement the constants as an enum, but then saw in the git history, that they were originally an enum and converted to string constants in https://
...

✅ TheCharlatan closed a pull request: "refactor: Move chain names to the util library"
(https://github.com/bitcoin/bitcoin/pull/27294)

💬 fanquake commented on issue "Compiling a bitcoin core version that accepts transactions over 100vkb":
(https://github.com/bitcoin/bitcoin/issues/27490#issuecomment-1514490496)
> a guide on what code changes should be done to compile such version

💬 fanquake commented on pull request "refactor: Move chain constants to the util library":
(https://github.com/bitcoin/bitcoin/pull/27491#issuecomment-1514492185)
```bash
7ea09dd60 scripted-diff: Remove unused chainparamsbase includes
d99bd93e0 Add missing definitions in prep for scripted diff
5589a4b0d refactor: Replace string chain name constants with ChainTypes
bd6493bf3 refactor: Create chaintype files

Error: script block marker but no scripted-diff in title of commit 7ea09dd60cd43e943f9910c950b05dda89ef3725
Failed
```

💬 TheCharlatan commented on pull request "refactor: Move chain constants to the util library":
(https://github.com/bitcoin/bitcoin/pull/27491#issuecomment-1514503368)
Re https://github.com/bitcoin/bitcoin/pull/27491#issuecomment-1514492185

> 7ea09dd60 scripted-diff: Remove unused chainparamsbase includes

Seems like the trailing whitespace in the commit mesasge header was tripping it up?

💬 fanquake commented on pull request "depends: fix compiling bdb with clang-16 on aarch64":
(https://github.com/bitcoin/bitcoin/pull/27462#issuecomment-1514514571)
@theuni Thanks for following up. Hopefully we'll be able to avoid the route of having to do even more invasive patching.

💬 fanquake commented on pull request "p2p: update hardcoded mainnet seeds for 25.x":
(https://github.com/bitcoin/bitcoin/pull/27488#issuecomment-1514526711)
cc @wiz

🚀 fanquake merged a pull request: "depends: Remove `_LIBCPP_DEBUG` from depends DEBUG mode"
(https://github.com/bitcoin/bitcoin/pull/27447)

👋 fanquake's pull request is ready for review: "ci: build libc++ in DEBUG mode in MSAN jobs"
(https://github.com/bitcoin/bitcoin/pull/27448)

💬 fanquake commented on pull request "ci: build libc++ in DEBUG mode in MSAN jobs":
(https://github.com/bitcoin/bitcoin/pull/27448#issuecomment-1514531348)
Rebased post #27447.

💬 ryanofsky commented on pull request "refactor: Move chain constants to the util library":
(https://github.com/bitcoin/bitcoin/pull/27491#discussion_r1171175379)
In commit "refactor: Replace string chain name constants with ChainTypes" (5589a4b0dd5b25017299f666127b7537f5f7a4c1)

Maybe replace `const ChainType&` with `ChainType` everywhere since it's an enum and probably more efficient to pass by value instead of by reference

💬 MarcoFalke commented on pull request "ci: build libc++ in DEBUG mode in MSAN jobs":
(https://github.com/bitcoin/bitcoin/pull/27448#issuecomment-1514559389)
is DEBUG=1 enabled for them as well in depends?

💬 MarcoFalke commented on issue "Feature request: alert PR author in case of CI failure":
(https://github.com/bitcoin/bitcoin/issues/27178#issuecomment-1514674473)
Ok, I found a hacky way to implement this:

GitHub check_suite event -> list check runs via GitHub API -> call cirrus CI API to get the task's build's pullRequest :smiling_face_with_tear:


Let me know if there are any bugs, questions or feature requests. Other than that, I think this can be closed?

💬 jonatack commented on pull request "p2p: update hardcoded mainnet seeds for 25.x":
(https://github.com/bitcoin/bitcoin/pull/27488#issuecomment-1514683900)
Pushed an update that adds seeds from @Wiz and colleagues. I was having issues connecting to some of them yesterday, but infra is being updated, and I was able to connect to all of them now.

✅ stickies-v closed an issue: "Feature request: alert PR author in case of CI failure"
(https://github.com/bitcoin/bitcoin/issues/27178)

💬 stickies-v commented on issue "Feature request: alert PR author in case of CI failure":
(https://github.com/bitcoin/bitcoin/issues/27178#issuecomment-1514706017)
Nice! Thank you for adding this to Drahtbot. Looks good, just looked at a PR with a recent CI failure and seeing this:

<img width="329" alt="image" src="https://user-images.githubusercontent.com/69010457/233084088-76c05ac7-6e0a-4da1-b3ec-cb1efe82a945.png">

Don't think this needs anything more - closing.

⚠️ fanquake opened an issue: "ci: failure in Docker build step"
(https://github.com/bitcoin/bitcoin/issues/27492)
Failure here: https://cirrus-ci.com/task/4581145136857088 in #27479. Does this just need a rebase? cc @MarcoFalke
```bash
docker build --tag gcr.io/cirrus-ci-community/bitcoin/bitcoin/ci/test_imagefile:d050f5b1ebc8c0ebdf779e9eda85ea03bfd0fca46391a14e57fbe478652e6623 --file ci/test_imagefile --build-arg CI_IMAGE_NAME_TAG="ubuntu:focal" --build-arg FILE_ENV="./ci/test/00_setup_env_native_nowallet_libbitcoinkernel.sh" ${CIRRUS_DOCKER_CONTEXT:-$CIRRUS_WORKING_DIR}
Sending build context to Docker
...