memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
w0xlt has quit [Ping timeout: 276 seconds]
w0xlt has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] Bortlesboat opened pull request #34737: test: replace bare asserts with assertion helpers in rpc_blockchain.py (master...test-replace-bare-asserts-rpc-blockchain) https://github.com/bitcoin/bitcoin/pull/34737
<bitcoin-git>
[bitcoin] DrahtBot closed pull request #34737: test: replace bare asserts with assertion helpers in rpc_blockchain.py (master...test-replace-bare-asserts-rpc-blockchain) https://github.com/bitcoin/bitcoin/pull/34737
w0xlt has quit [Ping timeout: 264 seconds]
w0xlt has joined #bitcoin-core-dev
memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
w0xlt has quit [Ping timeout: 245 seconds]
jonatack has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] Bortlesboat opened pull request #34738: test: replace bare asserts with assertion helpers in rpc_blockchain.py (master...test-replace-bare-asserts-rpc-blockchain) https://github.com/bitcoin/bitcoin/pull/34738
vasild has quit [Ping timeout: 258 seconds]
jonatack has quit [Ping timeout: 244 seconds]
vasild has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] Bortlesboat opened pull request #34739: test: replace bare asserts with assertion helpers in wallet_bumpfee.py (master...test-replace-bare-asserts-wallet-bumpfee) https://github.com/bitcoin/bitcoin/pull/34739
bytes1440000 has joined #bitcoin-core-dev
<bytes1440000>
Suggestion for the next coredev.tech: 18.300582537335316, -64.82567230391793
<bytes1440000>
Maybe kanzure could help in getting some sponsors as well
bytes1440000 has left #bitcoin-core-dev [#bitcoin-core-dev]
dzxzg has joined #bitcoin-core-dev
dzxzg has quit [Remote host closed the connection]
w0xlt has joined #bitcoin-core-dev
w0xlt has quit [Ping timeout: 245 seconds]
svanstaa_ has quit [Ping timeout: 264 seconds]
svanstaa has joined #bitcoin-core-dev
PaperSword has quit [Quit: PaperSword]
cmirror has quit [Remote host closed the connection]
cmirror has joined #bitcoin-core-dev
Artea has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
memset has quit [Ping timeout: 258 seconds]
memset has joined #bitcoin-core-dev
timbo_xyz has joined #bitcoin-core-dev
AaronvanW has quit [Remote host closed the connection]
memset has quit [Ping timeout: 258 seconds]
memset has joined #bitcoin-core-dev
ghost43 has quit [Ping timeout: 258 seconds]
w0xlt has joined #bitcoin-core-dev
ghost43 has joined #bitcoin-core-dev
w0xlt has quit [Ping timeout: 246 seconds]
ghost43 has quit [Remote host closed the connection]
ghost43 has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] maflcko closed pull request #34736: refactor: use explicit `&util::TraceThread` function pointer in thread spawns (master...tracethread-consistency) https://github.com/bitcoin/bitcoin/pull/34736
<dergoegge>
It would be cool have something like this for the qt gui
darosior9 is now known as darosior
<hebasto>
qml will be a new gui soon
<dergoegge>
If we're gonna keep maintaining it, it could be nice to increase our confidence with some fuzzing, which would be enabled by this approach
<willcl-ark>
hi
<dergoegge>
I'm not gonna work on it myself, but if someone is interested, I'd be willing to help with review or writing the fuzz tests
<fjahr>
dergoegge: that's it?
<dergoegge>
yes unless someone has something to add
<johnny9dev>
Hi. I can throw some tokens to research it for Qt widgets. I've built this same thing before in another qml project
<dergoegge>
Great! lmk how that goes!
<fjahr>
#topic Kernel WG Update (sedited)
<sedited>
don't have anything to share this week.
<fjahr>
#topic Benchmarking WG Update (l0rinc, andrewtoth)
<l0rinc>
nothing from me
sr_gi has quit [Quit: Client closed]
<andrewtoth_>
I opened #34692 based on feedback from last week's meeting and in #34641. Hopefully that is simple enough to get into v31. It would be a big UX improvement for our users. We can continue improving dbcaching in v32 afterwards.
<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.
sr_gi has joined #bitcoin-core-dev
<andrewtoth_>
That's it from me
Guest11 has joined #bitcoin-core-dev
<fjahr>
#topic Net Split WG Update (cfields)
<cfields>
Still no update, focus has been elsewhere. Really hoping to get going this week. Thanks for your patience :)
<fjahr>
Not seeing silent payments, but the k_max discussion is making progress afaict (bip change is merged I think) and the focus is again on the secp Pr that implements this.
<fjahr>
Anything else to discuss?
<sipa>
hi
<johnny9dev>
I would like to get the qml project back onto the weekly topic list. I've spent the last 2 weeks working on it again and I am not have full momentum again.
<johnny9dev>
I now have full momentum*
loungerry_ has quit [Quit: left]
loungerry_ has joined #bitcoin-core-dev
<fjahr>
#topic QML GUI WG Update (johnny9dev)
<fjahr>
:p
<johnny9dev>
I have another contributor helping me as well who will like to update their progress too
<willcl-ark>
nice!
<fjahr>
johnny9dev: You don't have to ask for permission IMO, just move it up in the wiki page
<johnny9dev>
My goal is feature parity and have setup the test automation frameworks and have done the decoupling from the original qt project. epcileafies has completed the features for peer disconnect/ban and completed a full e2e test for it using the gui test framework
<johnny9dev>
the list of features has been added to the issues of the project.
<johnny9dev>
thats all for this status i think
<fanquake>
johnny9dev: one thing I'm a bit unclear on, is, are you planning to replace widgets with qml, or you want both to exist going forward (was wondering after the fuzz topic, because porting that to widgets seems like a bit of a waste, if it's just going to be replaced with qml anyways)?
<hebasto>
yes, replace
<dergoegge>
it's not a waste if we still ship qt for a while
<darosior>
hebasto: so what's the plan? Replace regardless of IPC support? How does it fit with the topic you brought up a couple weeks ago?
<hebasto>
the plan is to replace qt -> qml first, then consider switching to IPC
eugenesiegel has quit [Quit: Client closed]
w0xlt has quit [Ping timeout: 264 seconds]
eugenesiegel has joined #bitcoin-core-dev
w0xlt has joined #bitcoin-core-dev
<fanquake>
I guess anything IPC is blocked on actually implementing IPC for Windows, otherwise the GUI wont support Windows
<dzxzg>
At localhost we've had some discussions recently about helping maintain/improve the qtwidgets gui, not opposed to qml replacing qtwidgets but I think while we are shipping qtwidgets we should be maintaining it and testing it
<johnny9dev>
I think that makes sense and I will be helping with bitcoin-core/gui reviews as well.
<johnny9dev>
eventhough my top priority will be gui-qml
<hodlinator>
are there any plans to support tests comparing the drawn GUI to checked-in screenshots?
<fanquake>
hebasto: That seems a bit tangential though? That could be a discussion, or happen, regardless of anything QML related (i.e we could switch widget to a wayland backend), or if we wanted to ship static bins.
<fanquake>
I posted that comment as a rough outline of what could happen, but I don't really know if it's a good idea, or what should happen. i.e, just because the guix build is split up, does that mean we ship/support/test apks for android? They seem like separate discussions, that could happen in any order.
<sedited>
johnny9dev, gui-qml is still pulling in a few of the existing qt/*.h headers. Is the plan to consolidate these?
<hebasto>
yes, it works for any extra dependencies, either widgets or QML
eugenesiegel has quit [Quit: Client closed]
<johnny9dev>
sedited: i did the work to remove all of those headers from the project and port over just what is needed
eugenesiegel has joined #bitcoin-core-dev
<fanquake>
hebasto: yea, my point is that, figuring out how to do a release build, is downstream of (and doesn't have to be blocking) of actually deciding the larger picture
<johnny9dev>
hodlinator: i added screenshot support to the qml test bridge but unsure what to do with it just yet. initially it will just be for capturing the state on failure
<fanquake>
i.e doing the GUI over IPC, is unrelated to wether you build bitcoin-qt in a different guix container to bitcoind
dzxzg has quit [Quit: Konversation terminated!]
<hebasto>
combining many goal simultaneously, such use IPC and QML, won't be productive; switching to QML has a significant drawback, which is bringing more deps for static builds; now we have a _good_ plan to mitigate it
dzxzg has joined #bitcoin-core-dev
<hebasto>
s/goal/goals/
<hodlinator>
johnny9dev: cool, will look into it some more
<darosior>
Agree re combining many goals, but i see the opposite. I hear some want to add features to qt widgets, others to QML, given the already low amount of dev resources on the GUI that seems.. surprising
<johnny9dev>
the productivity tools that are available now require us all to reevaluate scope/resources
<johnny9dev>
i did this last month and am shocked and very excited
<fjahr>
I agree that it doesn't feel like all the Gui resources are pulling in the same direction. But maybe it's hard to see the bigger picture from the outside. Great to hear there is momentum definitely!
w0xlt has quit [Ping timeout: 256 seconds]
<fjahr>
Well, sounds like johnny9dev will keep us updated and there may be a clearer picture emerging over time? Sounds like people would appreciate some better understanding of how the different work strings come together. Anything to add on this topic?
<fjahr>
Anything else to discuss?
<achow101>
31.0 milestone
<fjahr>
(asmap run is a nailbiter btw)
w0xlt has joined #bitcoin-core-dev
<sipa>
team luisschwab, hodlinator, sedited, fjahr, sr-gi is in the lead
sr_gi has quit [Quit: Client closed]
<achow101>
(you can #topic that for me)
bomb-on has quit [Read error: Connection reset by peer]
<fjahr>
oh sorry
<fjahr>
#topic 31.0 milestone
<achow101>
Btanching is scheuled for the 10th, which is in 5 days
<corebot>
https://github.com/bitcoin/bitcoin/issues/34735 | Intermittent failure in rpc_gettxspendingprevout.py, line 98, assert_equal(node0.gettxspendingprevout([..]), [..]), JSONRPCException: No spending tx for the outpoint :0 in mempool, and txospenderindex is unavailable · Issue #34735 · bitcoin/bitcoin · GitHub
<dergoegge>
Usually when I update the infra, i'll kill all the running campaigns, so they won't finish up
<andrewtoth_>
Ah manually stopping
<dergoegge>
I also had bugs in the infra at some point that prevented the coverage tooling from working
<dergoegge>
Or containers running out of memory due to /tmp filling up (this should be fixed now)
bomb-on has joined #bitcoin-core-dev
<dzxzg>
dergoegge: Have you thought about surfacing failing fuzz inputs? Or would that require review / intervention to make sure they weren't serious?
<dzxzg>
(also looks great!)
<andrewtoth_>
well, since you asked for ideas, maybe inform in the dashboard whether the stop was caused specifically by test harness failure, or by some other external reason.
<dergoegge>
dzxzg: yes, I might make a access restricted version of this that has more details for findings
<lightlike>
dergoegge: what is a campaign? a run of a target for a specified time? a set of multiple targets?
<dergoegge>
andrewtoth_: +1
<dergoegge>
lightlike: A run of one harness for a certain duration
dzxzg has quit [Quit: Konversation terminated!]
<andrewtoth_>
Is there a technical distinction between a fuzz harness vs fuzz target? Or same thing?
<dergoegge>
We tend to mix these terms. I think technically the "target" is the code you are testing and the harness is the test code you write to "harness" the target
<dergoegge>
forgot to mention that marcofleon is working automation for fuzzing PRs, and the results from that might also show up on the dashboard at some point
<marcofleon>
hype
<andrewtoth_>
Yeah I mix them too but what you describe makes sense.
memset_ has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
Guest11 has quit [Quit: Client closed]
memset has quit [Remote host closed the connection]
memset_ has joined #bitcoin-core-dev
memset_ has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
vasild has quit [Ping timeout: 258 seconds]
vasild has joined #bitcoin-core-dev
memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
durandal_ has quit [Read error: Connection reset by peer]
durandal_ has joined #bitcoin-core-dev
SpellChecker has quit [Remote host closed the connection]
SpellChecker has joined #bitcoin-core-dev
dzxzg has joined #bitcoin-core-dev
eugenesiegel has quit [Quit: Client closed]
musaHaruna has quit [Quit: Connection closed for inactivity]
dzxzg has quit [Remote host closed the connection]
naiyoma has quit [Quit: WeeChat 4.1.1]
musaHaruna has joined #bitcoin-core-dev
aleggg has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] achow101 opened pull request #34747: test: Sync mempools and wait for txospender index to be synced in rpc_gettxspendingprevout (master...txospenderindex-test-wait-index-synced) https://github.com/bitcoin/bitcoin/pull/34747
abubakarsadiq has quit [Quit: Connection closed for inactivity]
l0rinc has quit [Quit: l0rinc]
luke-jr has quit [Remote host closed the connection]
luke-jr has joined #bitcoin-core-dev
l0rinc has joined #bitcoin-core-dev
brunoerg_ has joined #bitcoin-core-dev
brunoerg has quit [Ping timeout: 268 seconds]
dzxzg has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] furszy opened pull request #34748: index: improve TxoSpenderIndex readability and documentation (master...2026_index_txospend_doc) https://github.com/bitcoin/bitcoin/pull/34748
afiore has quit [Remote host closed the connection]
musaHaruna has quit [Quit: Connection closed for inactivity]
eugenesiegel has joined #bitcoin-core-dev
memset has quit [Remote host closed the connection]
memset has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] fjahr opened pull request #34749: rpc: Refactor gettxspendingprevout to be easier to parse (master...2026-02-24539-refactor) https://github.com/bitcoin/bitcoin/pull/34749