16:00:01 <abubakarsadiq> #startmeeting 
16:00:01 <corebot> abubakarsadiq: Meeting started at 2026-10-01T16:00+0000
16:00:02 <corebot> abubakarsadiq: Current chairs: abubakarsadiq
16:00:03 <corebot> abubakarsadiq: Useful commands: #action #info #idea #link #topic #motion #vote #close #endmeeting
16:00:05 <corebot> abubakarsadiq: See also: https://hcoop-meetbot.readthedocs.io/en/stable/
16:00:06 <corebot> abubakarsadiq: Participants should now identify themselves with '#here' or with an alias like '#here FirstLast'
16:00:07 <brunoerg> hi
16:00:08 <stickies-v> hi
16:00:09 <abubakarsadiq> #bitcoin -core-dev Meeting: _aj_ abubakarsadiq achow101 andrewtoth b10c brunoerg cfields danielabrozzoni darosior dzxzg eugenesiegel fanquake fjahr furszy hebasto hodlinator instagibbs janb84 jarolrod johnny9dev jonatack josie jurraca kanzure kevkevin laanwj lightlike l0rinc maflcko marcofleon maxedw Murch pinheadmz provoostenator pseudoramdom ryanofsky sdaftuar sedited sipa sliv3r__ sr_gi stickies-v stringintech
16:00:09 <abubakarsadiq> theStack vasild willcl-ark
16:00:11 <janb84> hi
16:00:12 <eugenesiegel> hi
16:00:14 <cfields> hi
16:00:18 <hebasto> hi
16:00:18 <lightlike> hi
16:00:19 <instagibbs> hello
16:00:19 <dzxzg> hi
16:00:22 <pseudoramdom> hi
16:00:25 <maxedw> hi
16:00:27 <yancy> hi
16:00:37 <johnny9dev> Hi
16:00:37 <willcl-ark> hi
16:00:40 <l0rinc> hi
16:00:55 <abubakarsadiq> #topic Fuzzing WG Update (eugenesiegel, marcofleon)
16:00:59 <b10c> hi
16:01:24 <eugenesiegel> I'm not sure if marcofleon is here, but no update from my side
16:01:34 <abubakarsadiq> 👍
16:01:39 <abubakarsadiq> #topic Kernel WG Update (sedited)
16:01:40 <enochazariah> hi
16:01:46 <nervana21> hi
16:01:50 <andrewtoth_> hi
16:01:51 <marcofleon> no update this week
16:01:53 <marcofleon> possibly next
16:02:02 <theStack> hi
16:03:00 <abubakarsadiq> I think @sedited is not here, so I will move on.
16:03:01 <abubakarsadiq> #topic Benchmarking WG Update (l0rinc, andrewtoth)
16:03:18 <l0rinc> nothing from my side, but want to present something next week
16:03:26 <andrewtoth_> I haven't had an update in this WG in a while. I think I can be removed as lead.
16:03:32 <andrewtoth_> I will still actively review speedup PRs and benchmark, but I don't really have regular updates to give.
16:04:21 <abubakarsadiq> alright, if l0rinc also has no update, it can be archived.
16:04:25 <abubakarsadiq> #topic QML GUI WG Update (johnny9dev)
16:05:16 <johnny9dev> Pseudorandom has completed a comprehensive overhaul of the UX
16:05:33 <johnny9dev> Its looking good and were close to a design we think will work for release
16:05:45 <johnny9dev> Will start getting more feedback on it.
16:06:01 <johnny9dev> If anyone is interested in trying its in the qt6 branch of the project
16:06:10 <johnny9dev> That's all for this week
16:06:30 <abubakarsadiq> thanks @johnny9dev
16:06:32 <abubakarsadiq> #topic QML GUI WG Update (johnny9dev)
16:06:41 <abubakarsadiq> #topic QA WG Update (brunoerg)
16:07:03 <brunoerg> Hi, I've been working on a new project which is a collaborative mutation testing platform (https://mutanthub.space/). I've noticed that we have people using different tools and approaches to create mutants, different PRs addressing mutants (some overlaps), etc.
16:07:07 <willcl-ark> are there pre-built bins johnny9dev?
16:07:28 <brunoerg> So the idea of this new platform is that everything is centralized there and it becomes more collaborative.
16:07:46 <brunoerg> Anyone can submit surviving mutants, reproduce and evaluate them.
16:08:02 <brunoerg> For every surviving mutant, people can claim that a commit or PR kills it (so people can test it and/or avoid overlaps), as well as we can have discussions about mutants there.
16:08:15 <yuvicc> hi
16:08:33 <brunoerg> In the coming days, I will probably shutdown https://bitcoincore.space and https://secp256k1.space and centralize everything on mutanthub.
16:08:40 <johnny9dev> willcl-ark: by the end of the day bitcoincore.app will have them
16:09:01 <brunoerg> feedback is welcome
16:09:02 <sipa> hi
16:09:02 <brunoerg> that's all
16:09:13 <willcl-ark> 👍
16:09:58 <abubakarsadiq> @brunoerg  whats the process of submitting mutants?
16:12:34 <brunoerg> e.g. you can open any file from our source code (at https://mutanthub.space/projects/bitcoin/bitcoin/code), click on a specific line and suggest a mutant. Me as admin of the platform or any other people that wants to help in this process have to approve it (just to avoid trolls).
16:13:06 <brunoerg> we also have a feature that me and selected people can do bulk import from a json file.
16:13:45 <dzxzg> The killed mutants are the ones where a fix has been pushed to the project?
16:13:46 <abubakarsadiq> nice, thanks
16:14:20 <brunoerg> killed mutants are the ones that are detected by any of our tests
16:15:03 <brunoerg> considering the tests at the same commit point from where that mutant was created
16:15:51 <dzxzg> ah i see, thanks for sharing it looks awesome
16:17:27 <abubakarsadiq> Anything else to discuss?
16:17:55 <dzxzg> Maybe just an ask there's still some items on the 32.0 milestone, it would be helpful if anyone has extra hands to look thee
16:18:14 <abubakarsadiq> https://github.com/bitcoin/bitcoin/milestone/84
16:18:27 <eugenesiegel> would people find it helpful if they could tag some sort of bot or add a label that says they want a fuzzamoto build on their PR (assuming fuzzamoto covers the code in the first place)
16:19:02 <instagibbs> eugenesiegel remind me where is there a spot to look at scenarios covered
16:19:35 <willcl-ark> I have another bot-related topic, after eugenesiegel
16:19:52 <stickies-v> eugenesiegel: sounds useful to me
16:19:53 <eugenesiegel> instagibbs: scenarios here: https://github.com/oss-garage/fuzzamoto/tree/master/fuzzamoto-scenarios/bin   but the ir scenario covers most of the p2p stuff
16:21:36 <eugenesiegel> I can vibe-code a bot ppl can ping and make it as un-invasive as possible, that's all from me
16:22:53 <willcl-ark> I'm wondering if there'd be interest in a limited trial of automated AI reviews on PRs. I've already been testing this in my mirror of bitcoin/bitcoin, and I feel the results are useful enough. If there is interest, I think we could start on PRs coming from contibutors outside the frequent-contributor group.
16:23:57 <instagibbs> could we start with allowing people to call it in for their PR, so people can sample it
16:24:03 <willcl-ark> My suspicion is that some (or all) PRs arrive with LLM assistance or review in some capacity, and that human reviewers will then download the branch and make another llm-assisted first pass review. An automated review could do some of that initial work once and make the findings available to everyone/the original author.
16:24:18 <willcl-ark> instagibbs: that could also be an approach
16:25:08 <eugenesiegel> can we make it so that another person can't invoke it on your own PR if it's opt-in?
16:26:08 <willcl-ark> If you want to see what the reviews are like first, then you can check new/recently-synced PRs here: https://git.fish.foo/bitcoin/bitcoin there should be a comment from "ralph" after some time with a review
16:26:38 <yancy> I think that would be interesting upon request
16:27:02 <dzxzg> what model is it using?
16:27:10 <willcl-ark> I have to run out now, but will read all following messages when I get back (sorry about that). Happy to provide more details/links to bot code/prompts etc if folks want
16:27:57 <willcl-ark> I had codex make a crazy "how it works" chart which is here, and has the modesl in use for each agent/pass: https://github.com/willcl-ark/nix/blob/master/pkgs/forgejo-review-bot/README.md (it's a bit of a hectic document though)
16:28:03 <andrewtoth_> I think most of the value of LLM reviews is still having it be distilled by experienced contributors. So just posting the LLM output on a PR doesn't add much value IMO.
16:30:10 <abubakarsadiq> andrewtoth_: +1, I think it can be noise sometimes, so a dev should review the LLM reviews and post them.
16:31:43 <abubakarsadiq> #endmeeting