--- Log opened Mon May 09 00:00:18 2022 00:05 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 00:10 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 252 seconds] 00:18 -!- csknk [~csknk@88.87.164.26] has joined #bitcoin-core-pr-reviews 00:29 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:907e:f927:5768:840] has quit [Ping timeout: 252 seconds] 00:39 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 00:43 -!- brunoerg [~brunoerg@187.183.43.40] has joined #bitcoin-core-pr-reviews 00:48 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection] 00:49 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews 00:56 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 01:21 -!- a1ph4byte [~a1ph4byte@adsl-70-228-72-132.dsl.akrnoh.ameritech.net] has quit [Ping timeout: 246 seconds] 01:21 -!- MarcoFalke [~none@198.12.116.246] has quit [Ping timeout: 240 seconds] 01:25 -!- a1ph4byte [~a1ph4byte@70.228.72.132] has joined #bitcoin-core-pr-reviews 01:30 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #bitcoin-core-pr-reviews 01:32 -!- david-bakin [~david-bak@c-174-61-163-5.hsd1.wa.comcast.net] has quit [Ping timeout: 252 seconds] 01:43 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 256 seconds] 01:55 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 02:00 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 250 seconds] 02:19 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 02:44 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 03:17 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 260 seconds] 03:18 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #bitcoin-core-pr-reviews 03:46 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 03:50 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 246 seconds] 04:03 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 04:04 -!- csknk [~csknk@88.87.164.26] has quit [Ping timeout: 252 seconds] 04:06 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #bitcoin-core-pr-reviews 04:18 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 04:20 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 04:34 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #bitcoin-core-pr-reviews 05:24 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 240 seconds] 05:36 -!- csknk [~csknk@88.87.164.26] has joined #bitcoin-core-pr-reviews 05:53 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 05:58 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 252 seconds] 06:18 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 06:21 -!- antonleviathan [~antonlevi@ec2-3-99-96-13.ca-central-1.compute.amazonaws.com] has joined #bitcoin-core-pr-reviews 07:07 < a1ph4byte> I have a question about my dev environment and I'm fairly new to using git at scale. I have forked bitcoin and pulled down a local copy. I have also set the original repo as my upstream. What I'm not quite sure is how to locally review a PR request on somebody elses fork. Is it as simply as setting their repo as a remote? and switching to their PR branch? 07:17 < sipa> that is one way 07:17 < sipa> there is another... github actually exports all PRs as branches of the main repository directly 07:18 < sipa> If you add this to your .git/config file: 07:18 < sipa> [remote "upstream-pull"] 07:18 < sipa> fetch = +refs/pull/*/head:refs/remotes/upstream-pull/* 07:18 < sipa> url = git@github.com:bitcoin/bitcoin.git 07:19 < sipa> And then `git fetch upstream-pull`, you get all pull requests locally; e.g. `git checkout upstream-pull/22914` will give you PR 22914. 07:21 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 240 seconds] 07:29 -!- antonleviathan [~antonlevi@ec2-3-99-96-13.ca-central-1.compute.amazonaws.com] has quit [Quit: Client closed] 07:38 -!- TheRec [~toto@user/therec] has quit [Read error: Connection reset by peer] 07:47 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 07:49 -!- TheRec [~toto@84-75-225-47.dclient.hispeed.ch] has joined #bitcoin-core-pr-reviews 07:49 -!- TheRec [~toto@84-75-225-47.dclient.hispeed.ch] has quit [Changing host] 07:49 -!- TheRec [~toto@user/therec] has joined #bitcoin-core-pr-reviews 07:52 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 246 seconds] 07:53 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 07:56 < a1ph4byte> sipa, thanks for the insight 07:57 < Murch> a1ph4byte: It's certainly a question of personal preference, but I like the following setup: 07:57 < Murch> The main project repository I always call `upstream`. My own fork of the repository is `origin`. When I regularly engage with PRs from a specific contributor, I will add their repository as an additional "remote" and name it after their Github handle. E.g. I have `achow101` as a remote for my Bitcoin Core repository, because I work a lot with his coin selection simulation branch. 07:57 < Murch> To check out pull requests, I use the same trick that sipa described 07:59 < Murch> Jon also has a nice write-up here that gives a more detailed description of that idea and some other hints: https://jonatack.github.io/articles/how-to-review-pull-requests-in-bitcoin-core 08:11 < lightlike> yes, it's a matter of taste - I like to have a separate folder for each PR I review, so I use from master (e.g. for PR 12345): 08:11 < lightlike> git fetch origin pull/12345/head:PR_12345 08:11 < lightlike> git worktree add --checkout ../PR_12345 PR_12345 08:11 < a1ph4byte> Yeah I was trying to follow this write up, but was getting a bit lost. For example, his option 1 for pulling down locally, adds some lines of code to .git/config, specifically it has you update the [remote "origin"] to be able to fetch remote pull requests, but I thinks this is assumping that the remote is the bitcion repo and not your own fork. Wasn't sure if I could just 08:11 < a1ph4byte> add those same config lines to a [remote "upsteam"] section. 08:12 < a1ph4byte> lightlike, does this work if my the origin in my personal fork, I imagine not 08:13 -!- david-bakin [~david-bak@c-174-61-163-5.hsd1.wa.comcast.net] has joined #bitcoin-core-pr-reviews 08:14 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 276 seconds] 08:14 < lightlike> a1ph4byte: I don't think so. 08:16 < a1ph4byte> I think I read in the dev notes that you should make your own fork, but a lot of the git explanations for pull remote PRs assumes that your working off the main repo... very confusing 08:17 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 08:19 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Read error: Connection reset by peer] 08:19 -!- Kaizen_K_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 08:23 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 08:24 -!- Kaizen_K_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 246 seconds] 08:24 < lightlike> yes, I have separated these, using the main repo for review and my fork for own branches. I'd guess that most contributors have their own special workflow - once you get accustomed to something you are unlikely to change. 08:25 -!- Kaizen_K_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 08:27 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 252 seconds] 08:40 < Murch> a1ph4byte: You'll just have to replace all the mentions of `origin` in the definition of the remote with upstream, then it'll work 08:47 -!- Kaizen_K_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Remote host closed the connection] 08:47 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 08:51 < a1ph4byte> ALCON, this is good info thanks! 09:26 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 10:02 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-pr-reviews 10:13 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has joined #bitcoin-core-pr-reviews 10:27 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.] 10:28 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has joined #bitcoin-core-pr-reviews 10:29 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has quit [Client Quit] 10:31 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has joined #bitcoin-core-pr-reviews 10:37 < laanwj> i usually do `git fetch upstream pull//head && git checkout FETCH_HEAD` where upstream is the bitcoin/bitcoin repo 10:38 < laanwj> that, or i use the bitcoin-maintainer-tools/github-merge.py script, it's really convenient (even if you don't intend to merge), but always works with the PR merged into master 10:39 < a1ph4byte> i'll have to check that script out 10:46 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Remote host closed the connection] 10:48 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 12:07 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Remote host closed the connection] 12:08 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 12:13 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 252 seconds] 12:25 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!] 12:34 -!- csknk [~csknk@88.87.164.26] has quit [Quit: leaving] 13:03 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has quit [Ping timeout: 240 seconds] 13:09 -!- hashfunc77a [~user@2601:5c0:c280:7090:7c25:cf68:625f:614f] has joined #bitcoin-core-pr-reviews 13:10 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 13:14 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Ping timeout: 240 seconds] 13:20 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has quit [Read error: Connection reset by peer] 13:22 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has joined #bitcoin-core-pr-reviews 13:37 -!- a1ph4byte [~a1ph4byte@70.228.72.132] has quit [Remote host closed the connection] 13:51 -!- a1ph4byte [~a1ph4byte@70.228.72.132] has joined #bitcoin-core-pr-reviews 14:01 -!- Hardcode [~Hardcode@190.62.9.248] has joined #bitcoin-core-pr-reviews 14:01 -!- Hardcode [~Hardcode@190.62.9.248] has quit [Client Quit] 14:05 -!- hashfunc77a [~user@2601:5c0:c280:7090:7c25:cf68:625f:614f] has quit [Remote host closed the connection] 14:30 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has joined #bitcoin-core-pr-reviews 14:36 -!- Kaizen_Kintsugi_ [Kaizen_Kin@gateway/vpn/protonvpn/kaizenkintsugi/x-74018745] has quit [Remote host closed the connection] 15:00 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@ip72-194-104-106.oc.oc.cox.net] has joined #bitcoin-core-pr-reviews 15:04 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@ip72-194-104-106.oc.oc.cox.net] has quit [Remote host closed the connection] 15:32 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:646b:743b:e0fe:3064] has joined #bitcoin-core-pr-reviews 16:07 -!- brunoerg [~brunoerg@187.183.43.40] has quit [Remote host closed the connection] 16:22 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:31ca:a77e:83ce:86f9] has joined #bitcoin-core-pr-reviews 16:27 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:31ca:a77e:83ce:86f9] has quit [Ping timeout: 248 seconds] 16:39 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:646b:743b:e0fe:3064] has quit [Remote host closed the connection] 16:39 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 16:42 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Remote host closed the connection] 16:42 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 16:52 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Remote host closed the connection] 16:53 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 16:58 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:31ca:a77e:83ce:86f9] has joined #bitcoin-core-pr-reviews 17:02 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Ping timeout: 252 seconds] 17:15 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 17:20 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Ping timeout: 260 seconds] 17:20 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 17:24 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Ping timeout: 250 seconds] 17:43 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 17:43 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Remote host closed the connection] 17:43 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 17:53 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Remote host closed the connection] 17:54 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 18:00 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Ping timeout: 240 seconds] 18:12 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:31ca:a77e:83ce:86f9] has quit [Ping timeout: 248 seconds] 18:17 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 18:27 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:31ca:a77e:83ce:86f9] has joined #bitcoin-core-pr-reviews 18:44 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #bitcoin-core-pr-reviews 19:03 -!- jesseposner [~jesse@user/jesseposner] has quit [Quit: Textual IRC Client: www.textualapp.com] 19:22 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Ping timeout: 250 seconds] 19:32 < david-bakin> I am getting a warning from the check "lint [bionic]": `A new Boost dependency in the form of "boost/test/execution_monitor.hpp" appears to have been introduced: `src/test/script_tapscript_tests.cpp:#include ` - is it not allowed to have new Boost dependencies? Is this warning ignorable? Is there a way to get `boost/test/execution_monitor.hpp` 19:32 < david-bakin> approved? 19:35 < sipa> @[david-bakin] The point of the linter is mostly not introducing dependencies on new boost *libraries*. We're already depending on boost test, and afaik there are no plans to get rid of it. 19:35 < sipa> So you can just add a new exception to the linter. 19:36 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 19:38 < david-bakin> ty, and ... how do I do that please? some file to edit? 19:40 < sipa> It's probably the file in which the error occurs. Does CI not mention it? 19:41 < david-bakin> oh wait ... 19:42 < david-bakin> yes, i was looking in the wrong place, ci/lint, it's in test/lint. thanks! 19:43 < sipa> You could also do `git grep "A new Boost dependency"` to see what script could be doing that check. 19:45 < david-bakin> found it, it's test/lint/lint-includes.py - even has a variable to set `EXPECTED_BOOST_INCLUDES` - now that I know where it is couldn't be easier, thanks! 20:33 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:31ca:a77e:83ce:86f9] has quit [Ping timeout: 240 seconds] 20:34 -!- jesseposner [~jesse@user/jesseposner] has joined #bitcoin-core-pr-reviews 20:43 < david-bakin> Is there any instability in the functional tests? My PR **only** has an additional unit test. No changes at all to bitcoin source. Yet on the [win64-native] CI run the functional test `feature_index_prune.py` failed. (The only func test failure.) Looks like it has something to do with confirming peer connections - so possibly networking related - so possibly flaky? Is 20:43 < david-bakin> there someplace I can see the history of this test to see how often it fails, if it does? 20:44 < sipa> I don't think there are any statistics, but unfortunately, yes, it's certainly possible it is flaky. 20:45 < sipa> There may be open issues or PRs about it if it's common. 20:45 < david-bakin> ok, i'll search 20:45 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Remote host closed the connection] 20:45 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 20:46 < david-bakin> sure enough, #25031 just opened 11 days ago 20:46 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Remote host closed the connection] 20:46 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:31ca:a77e:83ce:86f9] has joined #bitcoin-core-pr-reviews 20:46 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:604c:8e4e:3e45:1ecf] has joined #bitcoin-core-pr-reviews 20:51 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:604c:8e4e:3e45:1ecf] has quit [Ping timeout: 240 seconds] 21:07 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 21:29 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Remote host closed the connection] 21:31 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #bitcoin-core-pr-reviews 21:50 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:31ca:a77e:83ce:86f9] has quit [Ping timeout: 252 seconds] 22:05 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:31ca:a77e:83ce:86f9] has joined #bitcoin-core-pr-reviews 22:06 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 22:08 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Ping timeout: 250 seconds] 22:22 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 22:26 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Ping timeout: 260 seconds] 22:43 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #bitcoin-core-pr-reviews 22:54 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has joined #bitcoin-core-pr-reviews 23:54 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 23:59 -!- Kaizen_Kintsugi_ [~Kaizen_Ki@2600:8802:3806:c200:fc71:ae59:7019:5580] has quit [Ping timeout: 240 seconds] --- Log closed Tue May 10 00:00:19 2022