<bitcoin-git>
bitcoin/master 141df0a Cory Fields: crypto: disable asan for sha256_sse4 with clang and -O0
<bitcoin-git>
bitcoin/master ae2658c merge-script: Merge bitcoin/bitcoin#30097: crypto: disable asan for sha256_sse4 with cla...
<bitcoin-git>
[bitcoin] fanquake merged pull request #30097: crypto: disable asan for sha256_sse4 with clang and -O0 (master...sha2asan) https://github.com/bitcoin/bitcoin/pull/30097
<achow101>
There is one preproposed meeting topic this week. Any last minute ones to add to the list?
<sr_gi[m]>
hi
<b10c>
hi
Emc99 has joined #bitcoin-core-dev
<Murch[m]>
hi
<achow101>
#topic package relay updates (glozow)
<glozow>
#30000 was merged (yay!). The priority PR is still #28984. On the p2p side, I opened #30110 as the next step. #30111 splits out the first 4 commits which are concerned with thread safety and should be reviewed very carefully. The rest of #30110 consists of more mechanical refactoring + tests.
<sdaftuar>
hi -- so i think last week i mentioned i had been working on an esoteric issue. unfortunately i've still been working on it for the past week so i can just quickly update what that is
<sdaftuar>
one thing that sipa and i have been discussing is whether we cna come up with some sort of "quality metric" for linearizations. there are a couple of reasons you might want this:
pablomartin has joined #bitcoin-core-dev
<sdaftuar>
a) having tests to ensure that our code does what we expect (eg regression tests so we don't break things in the future)
<sdaftuar>
b) having an understanding of what guarantees we provide to users
<sdaftuar>
so as a natural place to start, we can think about guarantees ancestor feerate based mining provides. however, it turns out that it seems to guarantee surprisingly little, and coming up with general properties that should hold up is quite hard
<sdaftuar>
anyway, i don't have a good answer to this question yet but will continue to think about it, and probably set my sights lower for what tests we can include
<sdaftuar>
that's it from me
<stickies-v>
hi
<sipa>
i'll probably open a PR today with low-level cluster linearization code
<achow101>
yay
<sdaftuar>
\o/
<sdaftuar>
that would immediately become the PR to review please :)
<achow101>
#26606 has been getting plenty of review and seems to be close. there's a few residual comments that need to be addressed, but those should be fairly trivial
<achow101>
The proposed moderation guidelines have been public for a couple weeks now, and there's been a bit of feedback. I think it's at the point that we can move forward with putting them into effect and electing/appointing/volunteering some moderators
<achow101>
There is a meta repo where the guidelines will live, as well as any meta discussion: https://github.com/bitcoin-core/meta. the discussion about the guidelines has taken place there as well.
<achow101>
2 weeks ago, willcl-ark and pinheadmz volunteered to be moderators, and I think there was general agreement for them. I think we can start with them, if there are no objections?
<darosior>
hi
<darosior>
+1 for both
<cfields>
+1
<hebasto>
ACK on willcl-ark and pinheadmz
<brunoerg>
+1
<abubakarsadiq>
+1
<sipa>
+1
<ajonas>
+1
<dergoegge>
+1
<b10c>
+2
<josie>
+1
<josie>
b10c: lol
* pinheadmz
blushing
<pinheadmz>
json 2.0 merged too plenty of free time now
<vasild>
+1
<achow101>
as always, we can make changes if necessary, this isn't something that's set in stone
<sr_gi[m]>
ACK on both
Chris_Stewart_5 has quit [Ping timeout: 264 seconds]
<jonatack>
guidelines suggestion: "pull requests will be *aggressively* moderated" -> s/aggressively/actively/
<achow101>
Any other topics to discuss?
<jonatack>
+1 on willcl-ark and pinheadmz
Chris_Stewart_5 has joined #bitcoin-core-dev
<achow101>
#endmeeting
Emc99 has quit [Quit: Client closed]
<achow101>
jonatack: i believe the word choice was intentional, as in people shouldn't be surprised if their comment gets deleted
<jonatack>
achow101: I think "actively" suggests it too, just less aggressively :)
<_aj_>
could use "zealously", to be a bit less "let's have a fight about it"
<laanwj>
+1
bugs_ has joined #bitcoin-core-dev
<vasild>
to me that first paragraph about aggressive moderation brings some bitter/negative feelings, like "you are enering enemy territory here!"
<achow101>
jonatack: i suppose so. changed it
<jonatack>
achow101: ty
<jonatack>
thankfully on the bips repo it's been limited so far
<jonatack>
(the need for moderation)
<achow101>
jonatack: well there is still spam that we've been deleting
<achow101>
but not so much brigading currently, although the taproot assets and ordinals bips prs have attracted that in the past
<jonatack>
same, deleting. and twice reminded people to focus on technical review.
<jonatack>
perhaps reworking bip 2 will help clarify the repo scope.
Guyver2 has joined #bitcoin-core-dev
preimage has joined #bitcoin-core-dev
Emc99 has joined #bitcoin-core-dev
Emc99 has quit [Client Quit]
Guyver2 has left #bitcoin-core-dev [Closing Window]