memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
S3RK_ has joined #bitcoin-core-dev
S3RK has quit [Ping timeout: 245 seconds]
w0xlt has quit [Ping timeout: 245 seconds]
<bitcoin-git>
[bitcoin] w0xlt opened pull request #34811: doc: update cjdns.md for current cjdns installation and peering (master...update-cjdns-doc) https://github.com/bitcoin/bitcoin/pull/34811
<bitcoin-git>
bitcoin/master b267efc Sebastian Falbesoner: rpc, net: completely remove `startingheight` field of `getpeerinfo` RPC
<bitcoin-git>
bitcoin/master 745ad94 Sebastian Falbesoner: p2p: remove m_starting_height field from node state (only show once in deb...
<bitcoin-git>
bitcoin/master 51a4dc5 merge-script: Merge bitcoin/bitcoin#34796: rpc, net: remove `startingheight` field of `g...
<bitcoin-git>
[bitcoin] sedited merged pull request #34796: rpc, net: remove `startingheight` field of `getpeerinfo` RPC and from node state (master...2026-remove-starting_height_field) https://github.com/bitcoin/bitcoin/pull/34796
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
ghost43 has quit [Remote host closed the connection]
ghost43_ has joined #bitcoin-core-dev
jerryf has quit [Remote host closed the connection]
<bitcoin-git>
bitcoin/master 2e8072e Sebastian Falbesoner: rpc: support writing UTXO set dump (`dumptxoutset`) to a named pipe
<bitcoin-git>
bitcoin/master 61a5460 Sebastian Falbesoner: test: add test for utxo-to-sqlite conversion using named pipe
<bitcoin-git>
bitcoin/master b19caee Sebastian Falbesoner: doc: add release note for #31560 (named pipe support for `dumptxoutset` RP...
<bitcoin-git>
[bitcoin] fanquake merged pull request #31560: rpc: allow writing UTXO set to a named pipe (master...202412-dumptxoutset-allow_write_to_named_pipe) https://github.com/bitcoin/bitcoin/pull/31560
pablomartin has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
<bitcoin-git>
bitcoin/master ecb5ce6 stratospher: test: fix addr relay test silent pass and wrong peerinfo index
<bitcoin-git>
bitcoin/master 7ee8c0a stratospher: test: protect outbound connection from eviction in getaddr_test
<bitcoin-git>
bitcoin/master 57bfa86 stratospher: test: use static methods and clarify comment in addr_relay
<bitcoin-git>
[bitcoin] fanquake merged pull request #34750: test: fix addr relay test silently passing and other improvements (master...2026_03_tests_addr_relay) https://github.com/bitcoin/bitcoin/pull/34750
<bitcoin-git>
[bitcoin] l0rinc closed pull request #33270: stabilize translations by reverting old ids by text content (master...l0rinc/stabilize-translations) https://github.com/bitcoin/bitcoin/pull/33270
<bitcoin-git>
[gui] johnny9 opened pull request #933: [DRAFT] Introduce Qt test automation bridge and gui functional tests (master...qt-test-bridge) https://github.com/bitcoin-core/gui/pull/933
luke-jr_ has quit [Ping timeout: 265 seconds]
w0xlt has joined #bitcoin-core-dev
w0xlt has quit [Ping timeout: 245 seconds]
dzxzg2 has joined #bitcoin-core-dev
sr_gi has joined #bitcoin-core-dev
<fjahr>
#startmeeting
<corebot>
fjahr: Meeting started at 2026-03-12T16:00+0000
<fjahr>
There is one pre-proposed meeting topic this week. Any last minute ones to add?
<brunoerg>
hi
<l0rinc>
hi
<theStack>
hi
<kanzure>
hi
<furszy>
hi
<andrewtoth_>
hi
<pinheadmz>
yo
<nymius>
hi
<fjahr>
Ok, starting with the WGs!
<fjahr>
#topic Fuzzing WG Update (dergoegge)
<hodlinator>
hi
<eugenesiegel>
hi
<dergoegge>
nothing from my side
kevkevin has joined #bitcoin-core-dev
<fjahr>
#topic Benchmarking WG Update (l0rinc, andrewtoth)
dzxzg2 has quit [Ping timeout: 255 seconds]
<l0rinc>
nothing urgent from my side
<andrewtoth_>
#34576 was merged. #31132 has been rebased with all split out PRs completed. Thanks everyone for your reviews and benchmarks!
dzxzg2 has joined #bitcoin-core-dev
<corebot>
andrewtoth_: Error: That URL appears to have no HTML title within the first 32KB.
<corebot>
andrewtoth_: Error: That URL appears to have no HTML title within the first 32KB.
<dzxzg2>
hi
sr_gi has quit [Client Quit]
<andrewtoth_>
I'm considering reopening #31132 as a fresh PR since there are over 500 comments and many are no longer relevant.
<corebot>
andrewtoth_: Error: That URL appears to have no HTML title within the first 32KB.
<andrewtoth_>
That's it from me.
sr_gi has joined #bitcoin-core-dev
epicleafies has quit [Changing host]
epicleafies has joined #bitcoin-core-dev
<andrewtoth_>
What's wrong with corebot?
<_aj_>
github rate limits probably?
<achow101>
It's not having a good day I guess
<_aj_>
(at least i'm constantly getting rate limits when not logged in, for no apparent reason)
<fjahr>
depressed from all the ai slop
<fjahr>
johnny9dev: you wanted yours reactivated, right? Please edit the WGs wiki page, thanks!
<fjahr>
#topic QML GUI WG Update (johnny9dev)
<johnny9dev>
yes
<johnny9dev>
For gui-qml I have been focused on cleaning up any dependency to the qt source code. I’ve also been working on the test coverage and automation frameworks. I am just about done with both and will be closing out the related issues on that. I will then begin PRing chunks of features next week along with Luke (epicleafies). The target features are all listed in the project’s Issues. I also plan on spending time to learn Figma Make
<johnny9dev>
and Figma’s MCP server. I’ve seen some real world cases of it being very effective the last two weeks and need to explore this for gui-qml.
<johnny9dev>
For gui, dergoegge asked if the test bridge would work for qt so I some time porting over the test automation bridge. It’s still a bit rough and needs some more validation/review but I started the draft on bitcoin-core/gui#933. Interested in what people think about this approach. Flakiness can be a problem initially with end to end tests so effort will need to be done to make sure it’s all solid before really moving forward with
<johnny9dev>
something like this. Animations, process initializing, and timings can be tricky but this shouldn’t be much worse than what y’all already deal with for the bitcoind functional tests.
<corebot>
johnny9dev: Error: That URL appears to have no HTML title within the first 32KB.
<kanzure>
does figma export to qml?
<johnny9dev>
you can use the mcp bridge to help translate figma to code
<dergoegge>
johnny9dev: cool, I'll have a look at that
<johnny9dev>
epicleafies has been helping with qml also
<johnny9dev>
epicleafies: can you give status?
w0xlt has joined #bitcoin-core-dev
<epicleafies>
Yeah, I've finished the debug log page and am working on the proxy settings to persist
<johnny9dev>
he also fully completed peers ban/disconnect including an end to end automated gui test with it
<johnny9dev>
i think that will probably be the most complicated one too
<johnny9dev>
with multiple nodes
<johnny9dev>
i think that is all
<fjahr>
I'm not seeing any of the other WG chairs.
<fjahr>
#proposedmeetingtopic logging system (_aj_)
<_aj_>
There's about a dozen open PRs/issues about changing the
<_aj_>
logging API, many of which have been open for almost two years now. Here's a table: https://gist.github.com/ajtowns/ff6247953437270ce81998bc0f7d6739 Many of these changes seem to me to make things substantially worse for working on bitcoin node software, and at this point it feels like a denial of service attack: "oh, you disagreed with this PR? well, we'll keep that one open as a sword of
<_aj_>
damocles, but also, how about this slightly different PR with slightly different motivations?" which just leaves me giving what feel like endless "Concept NACKs" and getting more frustrated. There are still a couple of followups to #28318 that I'd like to get in (namely #34038, and once that's done, switching the map of categories to an atomic bitfield), so I'd rather keep being somewhat involved,
<_aj_>
but this is pretty exhausting. So I'd really like it if folks who are a bit more dispassionate on the issue could get involved and express opinions on whether any of the proposed changes are actually valuable/desired, and ideally for the number of open proposals to get trimmed down a lot.
<corebot>
_aj_: Error: That URL appears to have no HTML title within the first 32KB.
<fjahr>
#topic logging system
<corebot>
_aj_: Error: That URL appears to have no HTML title within the first 32KB.
<achow101>
_aj_: how many major opinions on logging direction are there? 2?
<fanquake>
3 I think
<fjahr>
there seem to be three PR authors
<fanquake>
depending on the part of the codebase
<fjahr>
(of currently active prs)
<dzxzg2>
if it's possible to express succinctly, what are the different goals / usecases / motivations for changing the interface?
<_aj_>
i think there's a few different ones about the kernel (if you have multiple validation objects running, can their logs be separated; if you have multiple loggers and one validation state, can they get different info); there's a desire to pass different amounts of state to the Log*() functions (some or all of wallet name, category, level), and there's sometimes a desire to have all messages have a
<_aj_>
category (LogInfo(NET, "connected to new outbound"))
<fanquake>
Rough count but I think there's about ~15 different logging related refactors / PRs open at the moment
_flood has quit [Remote host closed the connection]
<dergoegge>
Some of the kernel related logging questions seem worthwhile solving but idk about the naming and calling conventions (that just seems like an endless pit to pour time into)
_flood has joined #bitcoin-core-dev
<_aj_>
the kernel stuff impacts the calling convention -- if you want logging from CheckBlock to go two different places, you have to pass in the two different logging systems into the LogDebug(..) call, eg
<sipa>
what does "two different places" mean?
<_aj_>
if you're running two different ChainstateManager's in the same process, and want to log the work they're doing / the failures they have independently
<l0rinc>
are these logging change suggestions fundamentally mutually exclusive?
<sipa>
i'm confused about why that would be the case, or why the code in question would know about it at all
<l0rinc>
is this related to different wallets and processes logging to different output files?
<sedited>
fwiw I think this is a nice to have, but the discussions and time sunk into logging as opposed to making things actually more useful seems skewed. I'd be happy with a simple albeit imperfect solution for now.
<sedited>
l0rinc I think that is orthogonal
<ryanofsky>
yeah i think we can easily make progress on this stuff, by just focusing on logging prs that are noncontroversial
<_aj_>
ryanofsky: closing the near-alternatives, and just keeping the "best" of them open would be a win in my view (best==your opinion after taking feedback into account, not necessarily least-controversial/most-likely-to-be-acceptable; imo anyway)
<l0rinc>
It seems to me the logging problems aren't obvious to most of us, it seems to be mostly working already - can we start with listing the exact problems?
<fjahr>
Maybe ask for review here again when there is a clear point were more feedback is needed. Hard to motivate yourself to go through the full list and find that for yourself, IMO.
<ryanofsky>
i guess my general feeling is it is not good to spend time have meta-debates about what code should be reviewed and generally peole should just review things they are interested, and maintain prs they are interested in maintaining
<ryanofsky>
if some progress is being blocked, but i am not aware of that happening
<fjahr>
Seems like the details of logging can continue to be discussed after the meeting. Is there anything else to discuss that should be in the meeting?
<_aj_>
fjahr: i think you could reasonably go through the gist above and say "this is ugly, is there really a big benefit?" or "this is much better than what we do now! i like it!" and have that be a useful contribution
<ryanofsky>
sgtm
<ryanofsky>
yeah i'll take a look at the gist
<achow101>
fjahr: topic for 31.0?
<fjahr>
#topic v31
<achow101>
we branched on tuesday night, tagged v31.0rc1 yesterday
<_aj_>
yay!
<achow101>
there's a backports pr and still a couple things in the milestone, so definitely will have a rc2
aleggg has quit [Remote host closed the connection]
<achow101>
any new issues to add to the milestone?
<achow101>
also release notes draft is in the wiki
<janb84>
Testing guide will be adressed by BOSS program / me
<fanquake>
I assume we'll fix all the multiprocess issues with another subtree pull?
<fanquake>
(once the rest of the issues there are fixed)
<maflcko>
Maybe let the functional tests run in a loop over night, this night, and see if it is still running the next morning. If not, leave an issue. (Make sure to increase --timeout-factor for smaller machines)
<fanquake>
I don't have a Windows machine, so someone on Windows will have to do that for that issue (maybe UCRT related)
<maflcko>
oh, I meant in general, to see if *all* dev machines and platforms can run the tests smoothly
<fanquake>
Yea sure, will be running
<maflcko>
nice, thx
<fjahr>
#endmeeting
<corebot>
fjahr: Meeting ended at 2026-03-12T16:41+0000
<darosior>
Agree on a special mention for the dbcache default change. I also think it's worth having one for the updates to mempool-replacement.md
dzxzg has quit [Quit: Konversation terminated!]
dzxzg has joined #bitcoin-core-dev
memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
nymius has joined #bitcoin-core-dev
nymius has quit [Client Quit]
memset has quit [Remote host closed the connection]
l0rinc has quit [Quit: l0rinc]
memset has joined #bitcoin-core-dev
eugenesiegel has quit [Quit: Client closed]
adys has quit [Ping timeout: 248 seconds]
<bitcoin-git>
[bitcoin] ViniciusCestarii opened pull request #34818: doc: fix process name typo in multiprocess.md (master...fix-multiprocess-doc-typo) https://github.com/bitcoin/bitcoin/pull/34818
svanstaa has quit [Ping timeout: 248 seconds]
svanstaa has joined #bitcoin-core-dev
Chris_Stewart_5 has quit [Quit: WeeChat 4.1.1]
brunoerg has joined #bitcoin-core-dev
musaHaruna has quit [Quit: Connection closed for inactivity]
jonatack has quit [Ping timeout: 272 seconds]
brunoerg has quit [Ping timeout: 244 seconds]
l0rinc has joined #bitcoin-core-dev
Setherson has quit [Quit: Setherson]
Setherson has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
w0xlt has joined #bitcoin-core-dev
jerryf_ has quit [Remote host closed the connection]
jerryf has joined #bitcoin-core-dev
brunoerg has quit [Remote host closed the connection]
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 245 seconds]
jonatack has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 268 seconds]
jonatack has joined #bitcoin-core-dev
darosior has quit [Quit: Ping timeout (120 seconds)]
darosior has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 244 seconds]
Artea has joined #bitcoin-core-dev
bugs_ has quit [Quit: Leaving]
kevkevin has quit [Remote host closed the connection]
eugenesiegel has joined #bitcoin-core-dev
w0xlt has quit [Quit: w0xlt]
eugenesiegel has quit [Ping timeout: 240 seconds]
jarthur has joined #bitcoin-core-dev
memset has quit [Remote host closed the connection]