--- Log opened Thu Jan 05 00:00:05 2023
00:21 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/360e047a7102...296e88225096
00:21 < bitcoin-git> bitcoin/master e6864fa fanquake: contrib: remove builder keys
00:21 < bitcoin-git> bitcoin/master 296e882 MarcoFalke: Merge bitcoin/bitcoin#26598: contrib: remove builder keys
00:43 < bitcoin-git> [bitcoin] zpv closed pull request #26815: builder-keys: remove luke-jr (master...patch-1) https://github.com/bitcoin/bitcoin/pull/26815
00:43 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #26598: contrib: remove builder keys (master...drop_non_guix_keys) https://github.com/bitcoin/bitcoin/pull/26598
00:50 -!- Guyver2 [~Guyver@77.174.98.73] has joined #bitcoin-core-dev
01:00 -!- jakwolf[m] [~jakwolfma@2001:470:69fc:105::2:acc8] has quit [Quit: You have been kicked for being idle]
01:04 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds]
01:06 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
01:26 -!- gossie [~gossie@2001:1c02:11e:3500:9941:94eb:7c34:cc0f] has joined #bitcoin-core-dev
01:27 -!- Guyver2 [~Guyver@77.174.98.73] has left #bitcoin-core-dev [Closing Window]
02:44 < p2plife> init message: messages are odd, in code they are _("foo_").translated - not sure why the final "_" nor why the .translated
02:45 < p2plife> the result is that these messaged (seen with grep "init message" ~/.bitcoin/debug.log) are all ending with bytes e2 80 a6, and then the newline 0a
02:45 < p2plife> I noticed since on screen these bytes looked like random characters. is that a known problem? I couldn't find it mentioned in Issues on github
02:55 < p2plife> ok nevermind. that's the ellipsis unicode. it looks weird on plain terminals,
03:01 < hebasto> p2plife: maybe open an issue to let others to reproduce the behaviour you mentioned?
03:02 < hebasto> oh, nm, you mentioned  the "ellipsis" unicode
03:19 -!- ___nick___ [~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net] has joined #bitcoin-core-dev
03:49 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
03:50 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #26817: doc: Remove copyright years  (master...2301-doc-copy-🍼) https://github.com/bitcoin/bitcoin/pull/26817
04:02 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:9cec:e75:2ae:365b] has joined #bitcoin-core-dev
05:07 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection]
05:12 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #26818: test: Fix feature_startupnotify intermittent issue (master...2301-test-fix-s-🐫) https://github.com/bitcoin/bitcoin/pull/26818
05:40 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
05:41 -!- vasild_ [~vd@user/vasild] has joined #bitcoin-core-dev
05:44 -!- vasild [~vd@user/vasild] has quit [Ping timeout: 255 seconds]
06:30 -!- jungly [~jungly@host-95-238-185-44.retail.telecomitalia.it] has joined #bitcoin-core-dev
06:37 -!- BUSY [~BUSY@user/busy] has quit [Ping timeout: 260 seconds]
06:50 -!- BUSY [~BUSY@user/busy] has joined #bitcoin-core-dev
06:58 -!- Guest39 [~Guest39@pool-96-241-171-211.washdc.fios.verizon.net] has joined #bitcoin-core-dev
07:09 -!- vasild_ [~vd@user/vasild] has quit [Quit: leaving]
07:12 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection]
07:34 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
07:43 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
07:43 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
07:48 -!- halosghost [~halosghos@user/halosghost] has joined #bitcoin-core-dev
08:02 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500:9f97:ce49:553a:6cb3] has joined #bitcoin-core-dev
08:17 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Ping timeout: 268 seconds]
08:20 -!- jungly [~jungly@host-95-238-185-44.retail.telecomitalia.it] has quit [Ping timeout: 260 seconds]
08:24 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/296e88225096...61f35159ffad
08:24 < bitcoin-git> bitcoin/master fac810b MarcoFalke: test: Fix feature_startupnotify intermittent issue
08:24 < bitcoin-git> bitcoin/master 61f3515 MarcoFalke: Merge bitcoin/bitcoin#26818: test: Fix feature_startupnotify intermittent ...
08:26 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #26818: test: Fix feature_startupnotify intermittent issue (master...2301-test-fix-s-🐫) https://github.com/bitcoin/bitcoin/pull/26818
08:33 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/61f35159ffad...3212d104f4ac
08:33 < bitcoin-git> bitcoin/master f2fc03e Pasta: refactor: use braced init for integer constants instead of c style casts
08:33 < bitcoin-git> bitcoin/master 3212d10 MarcoFalke: Merge bitcoin/bitcoin#23829: refactor: use braced init for integer literal...
08:33 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #23829: refactor: use braced init for integer literals instead of c style casts (master...use-braced-init) https://github.com/bitcoin/bitcoin/pull/23829
08:36 -!- kexkey [~kexkey@static-198-54-132-134.cust.tzulo.com] has quit [Ping timeout: 272 seconds]
08:39 -!- kexkey [~kexkey@static-198-54-132-141.cust.tzulo.com] has joined #bitcoin-core-dev
08:48 -!- ___nick___ [~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
08:50 -!- ___nick___ [~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net] has joined #bitcoin-core-dev
08:51 -!- ___nick___ [~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net] has quit [Client Quit]
08:53 -!- ___nick___ [~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net] has joined #bitcoin-core-dev
08:57 -!- SpellChecker_ [~SpellChec@user/SpellChecker] has joined #bitcoin-core-dev
09:02 -!- SpellChecker [~SpellChec@user/SpellChecker] has quit [Ping timeout: 255 seconds]
09:19 -!- b_101 [~robert@173.254.196.62.adsl.inet-telecom.org] has joined #bitcoin-core-dev
09:19 -!- as2333 [~as2333@host170.181-12-230.telecom.net.ar] has joined #bitcoin-core-dev
09:21 -!- b_101_ [~robert@173.254.196.62.adsl.inet-telecom.org] has quit [Quit: Lost terminal]
09:23 < bitcoin-git> [bitcoin] achow101 pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/3212d104f4ac...b4fb0a3255d3
09:23 < bitcoin-git> bitcoin/master d5f4ae7 Sebastian Falbesoner: wallet: fully migrate address book entries for watchonly/solvable wallets
09:23 < bitcoin-git> bitcoin/master 730e14a Sebastian Falbesoner: test: wallet: check that labels are migrated to watchonly wallet
09:23 < bitcoin-git> bitcoin/master b4fb0a3 Andrew Chow: Merge bitcoin/bitcoin#26761: wallet: fully migrate address book entries fo...
09:23 < bitcoin-git> [bitcoin] achow101 merged pull request #26761: wallet: fully migrate address book entries for watchonly/solvable wallets (master...202212-migratewallet_persist_addressbook) https://github.com/bitcoin/bitcoin/pull/26761
09:33 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 255 seconds]
09:33 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
09:36 < p2plife> will people be releasing statement regarding if commits and recent changes from luke-jr are "audited"? there are rumours or doubt arising that sources are "compromised" (yes I know there is a review process, but not everyone knows)
09:40 < achow101> p2plife: luke isn't a maintainer, he can't merge anything
09:55 < bitcoin-git> [bitcoin] hebasto opened pull request #26821: refactor: Make `ThreadHTTP` return void (master...220105-http) https://github.com/bitcoin/bitcoin/pull/26821
09:56 -!- cotsuka [~cotsuka@user/cotsuka] has quit [Quit: Bye!]
09:59 < halosghost> though, might be a different question about knots
09:59 -!- cotsuka [~cotsuka@user/cotsuka] has joined #bitcoin-core-dev
10:15 -!- Guest39 [~Guest39@pool-96-241-171-211.washdc.fios.verizon.net] has quit [Ping timeout: 260 seconds]
10:16 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
10:34 < jamesob> Surprising that this is dead code in the functional test suite: https://github.com/bitcoin/bitcoin/blob/master/test/functional/test_framework/script.py#L817-L820
10:34 < jamesob> Where are all the taproot spends?
10:34 < jamesob> Looks like they only happen in feature_taproot.py, which is horrifying
10:35 < sipa> Why?
10:35 < jamesob> I just mean it's a beastly functional test when attempting to read through and find a simple taproot spend
10:36 < sipa> If you mean that feature_taproot.py is horrifying in terms of readability, I agree (though I'm still quite proud of it...).
10:36 < jamesob> Yeah just in terms of readability. I'm sure it delivers a lot of functionality and coverage
10:37 < sipa> I thought you meant it's horrifying that that's the only thing testing it.
10:37 < jamesob> I'm just surprised - I thought P2TR spends were more common in the functional tests
10:38 < sipa> Well most tests involve directing bitcoind to do the spending; there are few uses for doing the spending on the functional test side (except when testing verification of the relevant rules).
10:43 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
10:45 < bitcoin-git> [bitcoin] brunoerg opened pull request #26822: p2p, rpc: don't allow past absolute timestamp in `setban` (master...2023-01-fix-ban-time) https://github.com/bitcoin/bitcoin/pull/26822
10:47 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Ping timeout: 264 seconds]
10:49 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #26823: refactor: Work around Werror=free-nonheap-object in AssumeCalculateMemPoolAncestors (master...2301-s390x-refactor-gcc-bug-📧) https://github.com/bitcoin/bitcoin/pull/26823
10:51 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
11:01 < achow101> meeting?
11:02 < Murch1> Hi
11:02 < brunoerg> Hi
11:02 < achow101> #startmeeting
11:02 <@core-meetingbot> Meeting started Thu Jan  5 19:02:41 2023 UTC.  The chair is achow101. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings.
11:02 <@core-meetingbot> Available commands: action commands idea info link nick
11:02 < achow101> #bitcoin-core-dev Meeting: achow101 aj amiti ariard b10c BlueMatt cfields Chris_Stewart_5 darosior digi_james dongcarl elichai2 emilengler fanquake fjahr gleb glozow gmaxwell gwillen hebasto instagibbs jamesob jarolrod jb55 jeremyrubin jl2012 jnewbery jonasschnelli jonatack jtimon kallewoof kanzure kvaciral laanwj larryruane lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball morcos nehan NicolasDorier paveljanik petertodd 
11:02 < achow101> phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild
11:03 < sipa> Hi
11:03 < jamesob> hi
11:03 < instagibbs> hi
11:03 < furszy> hi
11:03 < kvaciral> hi
11:03 < achow101> Welcome to the weekly general IRC meeting.
11:04 < achow101> There are no preproposed meeting topics this week, does anyone have any last minute topics to discuss?
11:04 < LarryRuane> hi
11:05 < achow101> #topic high priority for review
11:05 <@core-meetingbot> topic: high priority for review
11:05 < achow101> https://github.com/orgs/bitcoin/projects/1
11:05 < achow101> anything to add/remove/merge?
11:05 < jamesob> did the board get reset? I though I had an assumeutxo PR on there
11:06 < jamesob> can I add #25740?
11:06 <@gribble> https://github.com/bitcoin/bitcoin/issues/25740 | assumeutxo: background validation completion by jamesob · Pull Request #25740 · bitcoin/bitcoin · GitHub
11:06 < achow101> jamesob: I don't think it's been changed
11:07 < jamesob> that's weird... I definitely remember my AU PR being on there
11:07 < lightlike> maybe it was the one that got merged recently?
11:08 < jamesob> hmm, dunno.
11:08 < achow101> jamesob: added
11:08 < jamesob> thanks
11:10 < LarryRuane> I may as well ask here, anyone have a PR they'd like to be covered in review club? (I'm hosting on Feb 15)
11:10 < achow101> all of them :)
11:10 < LarryRuane> Also we're always welcome to have people host, if you'd like to try that
11:10 < LarryRuane> :)
11:12 -!- Guest96 [~Guest96@2605:8d80:682:dd56:dc84:f30d:5972:3964] has joined #bitcoin-core-dev
11:13 < achow101> LarryRuane: I think anything in the high prio board and the pr status board (https://github.com/orgs/bitcoin/projects/5/views/1)
11:15 < LarryRuane> achow101: +1 thanks
11:15 < achow101> anything else to discuss?
11:17 < achow101> #endmeeting
11:17 <@core-meetingbot> topic: Bitcoin Core development discussion and commit log | Feel free to watch, but please take commentary and usage questions to #bitcoin | Channel logs: http://www.erisian.com.au/bitcoin-core-dev/, http://gnusha.org/bitcoin-core-dev/ | Meeting topics http://gnusha.org/bitcoin-core-dev/proposedmeetingtopics.txt / http://gnusha.org/bitcoin-core-dev/proposedwalletmeetingtopics.txt
11:17 <@core-meetingbot> Meeting ended Thu Jan  5 19:17:29 2023 UTC.  
11:17 <@core-meetingbot> Minutes:        https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2023/bitcoin-core-dev.2023-01-05-19.02.moin.txt
11:18 < bitcoin-git> [bitcoin] fanquake opened pull request #26824: build: fix configuring with only bitcoin-util (master...fix_bitcoin_util_configure) https://github.com/bitcoin/bitcoin/pull/26824
11:18 < achow101> laanwj: I guess I should take over chairing the meetings permanently?
11:23 < jamesob> what's the policy on type hints in test_framework? are people amenable to those being added? I think generally it'd be a pretty big contributor to readability
11:24 < achow101> jamesob: we have type hints in some places, and the linter does run a type checker
11:25 < jamesob> e.g. in test_framework.key, test_framework.wallet, there are many places where the function has to be inspected to determine return type but just having that information accessible in the function signature would be convenient
11:26 < achow101> I would say add type hints as new stuff is added, kind of like how we do style stuff
11:28 < jamesob> I do think it would be beneficial if someone just started adding type information to signatures... because isn't it all trivially verifiable by the type checker? Like if someone adds incorrect annotations, that will be caught by CI, right?
11:29 < achow101> although test_framework is pretty low volume so blanket adding type annotations to all function signatures probably wouldn't cause too much rebasing?
11:29 < jamesob> yeah I wouldn't think so
11:29 < sipa> I think it may be helpful to do it for the few modules where it would actually have helped you in your work.
11:30 < jamesob> I think in individual tests would be too much churn, but for the framework I think adding annotations is reasonable; it's almost like scripted-diff in that it's CI enforced
11:30 < jamesob> sipa: yeah that's what I was thinking
11:30 < sipa> Given that we apparently already have annotations in some modules but not others, it doesn't seem like there is much of a need to do it over the entirety of the function test codebase at once.
11:30 < jamesob> (not to discourage adding type info in new tests...)
11:30 < bitcoin-git> [bitcoin] fanquake opened pull request #26825: build: remove already tested headers from AC_CHECK_HEADERS (master...remove_already_tested_headers) https://github.com/bitcoin/bitcoin/pull/26825
11:30 < jamesob> sipa: yeah and that'd be really tedious work anyway...
11:32 < sipa> And there isn't a strict separation between "having" and "not having" annotations; like you could go put "Any" on everything, and it wouldn't mean anything.
11:32 < sipa> (no pun intended)
11:32 -!- SpellChecker_ [~SpellChec@user/SpellChecker] has quit [Remote host closed the connection]
11:32 < jamesob> hah, right
11:32 -!- SpellChecker [~SpellChec@user/SpellChecker] has joined #bitcoin-core-dev
11:40 -!- Guest96 [~Guest96@2605:8d80:682:dd56:dc84:f30d:5972:3964] has quit [Quit: Client closed]
11:46 < bitcoin-git> [bitcoin] fanquake opened pull request #26826: refactor: remove windows-only compat.h usage in randomenv (master...windows_randomenv_compat_usage) https://github.com/bitcoin/bitcoin/pull/26826
11:57 < bitcoin-git> [bitcoin] fanquake opened pull request #26827: doc: use "std lib clock" over "C++11 clock" (master...doc_std_lib_clocks) https://github.com/bitcoin/bitcoin/pull/26827
11:57 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
11:57 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #bitcoin-core-dev
12:17 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection]
12:22 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
12:26 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
12:26 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
12:27 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #bitcoin-core-dev
13:04 -!- ___nick___ [~quassel@cpc68289-cdif17-2-0-cust317.5-1.cable.virginm.net] has quit [Ping timeout: 268 seconds]
13:44 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:9cec:e75:2ae:365b] has quit []
13:56 -!- lisper29 [~vibs29``@83-87-73-107.cable.dynamic.v4.ziggo.nl] has joined #bitcoin-core-dev
14:15 < lisper29> I'm learning to use BIP32 derived addresses in bitcoind. BIP32 4.3.2 (pub->pub) ends by specifying that when a derivation at index i is invalid "one should proceed with the next value for i". So if the deriveaddresses RPC returns an error, I'll try the next index. But I don't see the getnewaddress RPC or the Qt "create new receiving address" button's code trying the next index for this type of failed derivation. Do 
14:15 < lisper29> they have a bug in that they'll never get past that invalid index? (pubkey.cpp CPubKey::Derive is what I assume performs the BIP32 4.3.2 validation.)
14:20 < sipa> It's not a bug in that it cannot occur. I should perhaps explain that in the BIP.
14:21 -!- Guest57 [~Guest57@189.6.9.148] has joined #bitcoin-core-dev
14:21 < lisper29> sipa: I think you've just ended many weeks of my misery. thank you!
14:22 -!- Guest57 [~Guest57@189.6.9.148] has quit [Client Quit]
14:25 < sipa> "cannot" as in the probability of it ever occurring in our lifetimes is negligible
14:25 < bitcoin-git> [bitcoin] andrewtoth opened pull request #26828: assumeutxo: catch and log fs::remove error instead of two exist checks (master...assumeutxo-remove-fix) https://github.com/bitcoin/bitcoin/pull/26828
14:25 < lisper29> Do I understand correctly then that deriveaddresses also will always produce a valid address at every index in [0,2^31-1]?
14:27 < sipa> yes
14:28 < lisper29> Ah I see, it's low probability, got it. I did see the 2^-126 probability for another section of BIP32. This section didn't mention it. And anyway its specified algorithm says that if invalid then try the next. So not being cryptographer or mathematician, I figured I must follow prescribed algorithm.
14:30 < lisper29> Hurray, thank you. That's a huge weight off a programmer's shoulders.
14:39 < lisper29> Last question: If that low probability index occurs, does deriveaddresses return an error? Then I can write code to try next index. Or does deriveaddresses return an address that I won't know is dangerous to advertise?
14:40 -!- halosghost [~halosghos@user/halosghost] has quit [Quit: WeeChat 3.7.1]
14:42 < lisper29> If it's meaningless to reason at such low probabilities (e.g. because many other things can fail before then, such as hashes colliding), please ignore of course.
14:51 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window]
15:09 < sipa> Yeah, it's just practically impossible to hit, even if someone were to intentionally try to make it happen with all computational power in the world.
15:09 < sipa> We can't even write a test for it, because of that.
15:22 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection]
15:22 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
15:23 < lisper29> Right, I guessed that it was low from no test vectors and the 2^-126 mentioned elsewhere. I know what to do. Assuming CPubKey::Derive does properly return a failure, there's 0 (not just negligible) probability of deriveaddresses returning an address when it shouldn't. So I'll write client code to loop to next index. Regardless, client code will never see a bad address from deriveaddresses, even if it runs until the 
15:23 < lisper29> last table entry at: https://en.wikipedia.org/wiki/Timeline_of_the_far_future . And I'll tell all users of my program that in dealing with cryptography (which underlies bitcoin), there are these negligibly likely events. That's enough agonising for now :-)
15:23 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Client Quit]
15:42 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500:9f97:ce49:553a:6cb3] has quit [Ping timeout: 265 seconds]
16:07 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500:9f97:ce49:553a:6cb3] has joined #bitcoin-core-dev
16:45 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500:9f97:ce49:553a:6cb3] has quit [Ping timeout: 264 seconds]
17:13 -!- Saloframes [~Saloframe@user/Saloframes] has joined #bitcoin-core-dev
17:16 -!- boxframes_ [~Saloframe@user/Saloframes] has joined #bitcoin-core-dev
17:16 -!- boxframes_ [~Saloframe@user/Saloframes] has quit [Remote host closed the connection]
17:21 -!- boxframes_ [~Saloframe@user/Saloframes] has joined #bitcoin-core-dev
17:21 -!- boxframes_ [~Saloframe@user/Saloframes] has quit [Remote host closed the connection]
17:21 -!- lisper29 [~vibs29``@83-87-73-107.cable.dynamic.v4.ziggo.nl] has left #bitcoin-core-dev [Leaving]
17:27 -!- boxframes_ [~Saloframe@user/Saloframes] has joined #bitcoin-core-dev
17:27 -!- boxframes_ [~Saloframe@user/Saloframes] has quit [Remote host closed the connection]
17:53 -!- b_101_ [~robert@173.254.196.62.adsl.inet-telecom.org] has joined #bitcoin-core-dev
17:56 -!- b_101 [~robert@173.254.196.62.adsl.inet-telecom.org] has quit [Ping timeout: 260 seconds]
17:59 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500:9f97:ce49:553a:6cb3] has joined #bitcoin-core-dev
18:00 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500:9f97:ce49:553a:6cb3] has quit [Read error: Connection reset by peer]
18:48 -!- Saloframes [~Saloframe@user/Saloframes] has quit [Quit: Leaving]
19:39 < bitcoin-git> [bitcoin] achow101 opened pull request #26829: init: Remove unnecessary sensitive flag from rpcbind (master...dont-hide-rpcbind-log) https://github.com/bitcoin/bitcoin/pull/26829
20:12 -!- jonatack1 [~jonatack@user/jonatack] has joined #bitcoin-core-dev
20:13 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 260 seconds]
20:32 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 255 seconds]
20:43 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection]
21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev
23:08 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/b4fb0a3255d3...2cfe37962343
23:08 < bitcoin-git> bitcoin/master faa86ee MarcoFalke: refactor: Work around Werror=free-nonheap-object in AssumeCalculateMemPool...
23:08 < bitcoin-git> bitcoin/master 2cfe379 MarcoFalke: Merge bitcoin/bitcoin#26823: refactor: Work around Werror=free-nonheap-obj...
23:42 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #26823: refactor: Work around Werror=free-nonheap-object in AssumeCalculateMemPoolAncestors (master...2301-s390x-refactor-gcc-bug-📧) https://github.com/bitcoin/bitcoin/pull/26823
23:49 -!- NorrinRadd [~NorrinRad@gateway/tor-sasl/norrinradd] has joined #bitcoin-core-dev
--- Log closed Fri Jan 06 00:00:03 2023