12017-01-02T00:52:26  *** PaulCape_ has joined #bitcoin-core-dev
  22017-01-02T00:52:57  *** PaulCapestany has quit IRC
  32017-01-02T00:58:55  *** droark has joined #bitcoin-core-dev
  42017-01-02T01:37:26  *** Ylbam has quit IRC
  52017-01-02T02:14:28  *** windsok has quit IRC
  62017-01-02T02:51:32  *** windsok has joined #bitcoin-core-dev
  72017-01-02T02:55:39  <da2ce7> Happy new year! :)
  82017-01-02T03:03:48  *** harrymm has quit IRC
  92017-01-02T03:22:42  *** harrymm has joined #bitcoin-core-dev
 102017-01-02T04:12:53  *** paveljanik has quit IRC
 112017-01-02T04:15:01  *** shockoo has quit IRC
 122017-01-02T04:29:59  *** paveljanik has joined #bitcoin-core-dev
 132017-01-02T05:17:01  *** d9b4bef9 has quit IRC
 142017-01-02T05:18:08  *** d9b4bef9 has joined #bitcoin-core-dev
 152017-01-02T05:34:38  *** cannon-c has joined #bitcoin-core-dev
 162017-01-02T05:43:26  *** harrymm has quit IRC
 172017-01-02T05:44:38  *** Squidicc is now known as squidicuz
 182017-01-02T06:04:04  *** harrymm has joined #bitcoin-core-dev
 192017-01-02T06:48:03  <btcdrak> wumpus: can we tag 0.13.2? :-)
 202017-01-02T07:32:13  *** Ylbam has joined #bitcoin-core-dev
 212017-01-02T07:32:48  *** paveljanik has quit IRC
 222017-01-02T07:48:16  *** Saucery has joined #bitcoin-core-dev
 232017-01-02T08:09:07  *** BashCo has quit IRC
 242017-01-02T08:09:46  *** BashCo has joined #bitcoin-core-dev
 252017-01-02T08:13:47  *** BashCo has quit IRC
 262017-01-02T08:30:06  *** blur3d has joined #bitcoin-core-dev
 272017-01-02T08:30:46  *** BashCo has joined #bitcoin-core-dev
 282017-01-02T08:31:09  *** Saucery has quit IRC
 292017-01-02T08:35:37  *** Saucery has joined #bitcoin-core-dev
 302017-01-02T08:36:09  *** BashCo_ has joined #bitcoin-core-dev
 312017-01-02T08:37:30  <wumpus> btcdrak: yes
 322017-01-02T08:37:44  <bitcoin-git> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/1d2d67692c74a5539f3736754d84f0aa6a702c56
 332017-01-02T08:37:44  <bitcoin-git> bitcoin/master 1d2d676 Wladimir J. van der Laan: qt: Set transifex slug to 0.14...
 342017-01-02T08:38:58  *** BashCo has quit IRC
 352017-01-02T08:43:44  <bitcoin-git> [bitcoin] jonasschnelli pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/1d2d67692c74...53442af0aac3
 362017-01-02T08:43:45  <bitcoin-git> bitcoin/master 09aefb5 Cory Fields: build: Fix 'make deploy' for OSX...
 372017-01-02T08:43:45  <bitcoin-git> bitcoin/master b01667c Jonas Schnelli: Mention RSVG dependency when creating the disk image on OSX
 382017-01-02T08:43:46  <bitcoin-git> bitcoin/master 2fb98f6 Don Patterson: Fix bug in dmg builder so that it actually reads in the configuration file
 392017-01-02T08:44:02  <bitcoin-git> [bitcoin] jonasschnelli closed pull request #9412: build: Fix 'make deploy' for OSX (master...2016/12/fix_mac_deploy) https://github.com/bitcoin/bitcoin/pull/9412
 402017-01-02T08:52:03  *** udiWertheimer has joined #bitcoin-core-dev
 412017-01-02T08:55:11  <bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.13: https://github.com/bitcoin/bitcoin/commit/0d719145b018e28d48d35c2646a5962b87c60436
 422017-01-02T08:55:12  <bitcoin-git> bitcoin/0.13 0d71914 Wladimir J. van der Laan: doc: Remove ... from release notes
 432017-01-02T08:57:35  <wumpus>  * [new tag]         v0.13.2 -> v0.13.2
 442017-01-02T09:09:37  *** droark has quit IRC
 452017-01-02T09:09:46  <jonasschnelli> \o/
 462017-01-02T09:11:09  *** blur3d has quit IRC
 472017-01-02T09:11:17  <wumpus> *almost* new year tag :p
 482017-01-02T09:13:46  *** jannes has joined #bitcoin-core-dev
 492017-01-02T09:24:28  <jouke_> I updated a .10 node to .13.1. It connects to an other .13.1 node, but it doesn't seem to sync the blockchain. But when I look at the blockheight, it might already got "stuck" when it was a .10 node. I updated it, because some rpc calls were a bit slow.
 502017-01-02T09:27:49  <jouke_> In debug log I see that it is receiving "invs".
 512017-01-02T09:35:36  <gmaxwell> jouke_: if you were stuck it is presumably because corruption made you reject a block. you can try running 'reconsiderblock <block hash after your current height>'
 522017-01-02T09:40:09  <jouke_> I retreived the blockhash from an other node, but that doesn't seem to do anything.
 532017-01-02T09:42:22  <gmaxwell> jouke_: I assume you don't have historic logs from the point where it got stuck?
 542017-01-02T09:42:40  <jouke_> no, I don't unfortunately
 552017-01-02T09:46:14  <jouke_> It just received information about the latest block and I see it is retreiving and receiving the headers of that block, but that's it.
 562017-01-02T09:48:55  *** MarcoFalke has joined #bitcoin-core-dev
 572017-01-02T09:52:20  <jouke_> Hmm, we use that node to gather information about mempool size, and it stopped accepting blocks at around the 29th, but it did receive transactions which it added to it's mempool.
 582017-01-02T09:53:08  <gmaxwell> jouke_: do you have logs that cover the 29th?
 592017-01-02T09:54:22  <jouke_> no
 602017-01-02T09:59:07  <gmaxwell> the reconsiderblock did nothing? can you try invalidateblock <thatblock> then reconsider?
 612017-01-02T09:59:44  <gmaxwell> can you also run getchaintips and pastebin the results?
 622017-01-02T09:59:56  <jouke_> And thatblock = currentheight+1 right?
 632017-01-02T10:00:11  <gmaxwell> right what is your current height?
 642017-01-02T10:00:32  <jouke_> It's stuck at 445623
 652017-01-02T10:01:15  <gmaxwell> can you getblockhash for 445623 ?
 662017-01-02T10:02:12  <jouke_> 000000000000000002c45ed9057608b268a447499fcd8bea8e7930bfed11eaaf
 672017-01-02T10:03:27  <gmaxwell> jouke_: okay run reconsiderblock 000000000000000000fc97c4cd1f956f46a420536ca4851c31ad9d32f4e8ec0c
 682017-01-02T10:03:57  <jouke_> already did that
 692017-01-02T10:04:01  <jouke_> Didn't do anything
 702017-01-02T10:04:34  <gmaxwell> jouke_: can you try doing a getblock 000000000000000000fc97c4cd1f956f46a420536ca4851c31ad9d32f4e8ec0c and see if it says anything?  grep your logs for that hash and see if there is any mention?
 712017-01-02T10:05:06  <gmaxwell> unfortunately I think there are types of rejection that reconsider will not reconsider, it's really just intended to be the compliment to invalidateblock
 722017-01-02T10:05:41  <jouke_> error code: -32603
 732017-01-02T10:05:41  <jouke_> error message:
 742017-01-02T10:05:42  <jouke_> Can't read block from disk
 752017-01-02T10:06:24  <jouke_> chaintips: https://www.zerobin.net/?70af58e5db340709#1i/w7FQhQE0ubu1+9QO5ANJPRSJ+V24C0LgiYVl15gU=
 762017-01-02T10:06:26  <gribble> https://github.com/bitcoin/bitcoin/issues/1 | JSON-RPC support for mobile devices ("ultra-lightweight" clients) · Issue #1 · bitcoin/bitcoin · GitHub
 772017-01-02T10:07:29  <gmaxwell> jouke_: okay your blockchain data is corrupted. the block isn't on your disk (or is corrupted on disk) but is in the blockindex.
 782017-01-02T10:08:41  <jouke_> Hmm. nothing strange in syslog about file corruption or anything.
 792017-01-02T10:09:52  <gmaxwell> any chance you had a unclean power loss? the block isn't added into the block index until its written to disk and fsynced, but if your system is ignoring fsyncs or there is some other misbehavior in your storage it could be lost during a power failure.
 802017-01-02T10:10:30  <jouke_> no, system has been up for a whie
 812017-01-02T10:10:31  <jouke_> while
 822017-01-02T10:10:53  <gmaxwell> oh this was 0.10 before?
 832017-01-02T10:10:57  <jouke_> yes
 842017-01-02T10:11:02  <gmaxwell> ah ha.
 852017-01-02T10:11:24  <gmaxwell> I believe we actually had a bug that could cause that before.
 862017-01-02T10:12:09  <jouke_> I was already looking through the issues, but I did not come across it yet.
 872017-01-02T10:13:28  <gmaxwell> jouke_: in any case, I believe there is no other resolution right now to your condition but to reindex.  setting a higher dbcache than default, if you have the ram will make it run much faster.
 882017-01-02T10:14:33  <jouke_> Shame I don't have the logs. I am making a note to push all bitcoin node logs to a log server.
 892017-01-02T10:14:47  <jouke_> gmaxwell: thanks for the help!
 902017-01-02T10:22:40  *** BashCo has joined #bitcoin-core-dev
 912017-01-02T10:22:48  *** BashCo_ has quit IRC
 922017-01-02T10:23:22  *** BashCo_ has joined #bitcoin-core-dev
 932017-01-02T10:27:01  *** BashCo has quit IRC
 942017-01-02T10:27:57  *** AaronvanW has quit IRC
 952017-01-02T10:28:36  *** JackH has joined #bitcoin-core-dev
 962017-01-02T10:33:36  *** AaronvanW has joined #bitcoin-core-dev
 972017-01-02T11:36:11  <bitcoin-git> [bitcoin] MarcoFalke opened pull request #9457: WIP: [qt] translate bitcoin.cpp and libbitcoin_common_a_SOURCES (master...Mf1701-qtTrans) https://github.com/bitcoin/bitcoin/pull/9457
 982017-01-02T12:04:30  *** paveljanik has joined #bitcoin-core-dev
 992017-01-02T12:44:47  *** JackH has quit IRC
1002017-01-02T12:52:07  <jonasschnelli> Hmm... full block SPV with random peers is horrible slow. 10-12 blocks per minute around height 445100
1012017-01-02T12:52:20  <jonasschnelli> (on a 100MBit link)
1022017-01-02T12:52:46  <jonasschnelli> Maybe I just had bad luck with remote peers
1032017-01-02T12:52:50  <gmaxwell> increase your socket recieve buffer maximum size.
1042017-01-02T12:53:09  <gmaxwell> by like a factor of 10, you'll likely see it much faster.
1052017-01-02T12:53:36  <gmaxwell> Does your fetching code fetch in parallel?
1062017-01-02T12:54:18  <jonasschnelli> Yes. Same code.
1072017-01-02T12:54:26  <jonasschnelli> Maybe I need to unset NODE_NETWORK?
1082017-01-02T12:54:37  <jonasschnelli> debug=net shows plenty of tx invs
1092017-01-02T12:55:48  <gmaxwell> increase your socket recieve buffer maximum size.
1102017-01-02T12:56:50  <gmaxwell> One problem (no doubt there is more) is that it cannot achieve high throughput for transfers because the recieve buffers are so small that almost any processing delay and they fill.
1112017-01-02T12:57:13  <jonasschnelli> gmaxwell: Thanks. I'll try that.
1122017-01-02T13:10:19  *** JackH has joined #bitcoin-core-dev
1132017-01-02T13:13:22  *** JackH has quit IRC
1142017-01-02T13:23:24  <jonasschnelli> gmaxwell: -maxreceivebuffer=50000 = 1block per second. Better,... need to profile.. but I guess SyncTransaction with IsMine, etc. is the bottleneck
1152017-01-02T13:26:04  <gmaxwell> thanks for checking and, it sounds like, validating my theory.  Not just how long sync takes, but the block deseralization isn't fast, ans I assume your sync runs in order, which means that when blocks arrive out of order and eventually the missing one shows up, it is probably processing many blocks at once, which creates a long delay in the message handling loop which will stall the recieve buf
1162017-01-02T13:26:10  <gmaxwell> fers.
1172017-01-02T13:27:24  <jonasschnelli> The blockdownload im using (#9171) does download in parallel, then store them on the disk and, process them in order (unserialize again probably).
1182017-01-02T13:27:26  <gribble> https://github.com/bitcoin/bitcoin/issues/9171 | Introduce auxiliary block requests by jonasschnelli · Pull Request #9171 · bitcoin/bitcoin · GitHub
1192017-01-02T13:29:27  <gmaxwell> right, and say that you recieve blocks 0 2 3 4 5 6 7 8 9 1 will it end up processing 9 of them at the moment it recieves block 1 in the message handler? if so... it is not emptying the recieve buffers during that time.
1202017-01-02T13:30:45  <jonasschnelli> gmaxwell: I think it does empty the receive buffer,... ProcessNewBlock gets called for all blocks where only the header gets verified, the stored to the disk. I guess this drains the buffer...
1212017-01-02T13:30:54  <jonasschnelli> *then
1222017-01-02T13:32:13  <gmaxwell> the recieve buffer is drained as the blocks are saved to disk. it saves 1 to disk but then processes it and then will connect 1 2 3 4 5 6 7 8 9  all within that function call.
1232017-01-02T13:32:25  <gmaxwell> and during that time the message handler is not handling any messages. :)
1242017-01-02T13:32:36  <gmaxwell> so the recieve buffers fill.
1252017-01-02T13:33:40  <jonasschnelli> hmmm...
1262017-01-02T13:33:56  <jonasschnelli> https://github.com/bitcoin/bitcoin/pull/9171/files#diff-6905024871a5ac748c4465bb25973c39R37
1272017-01-02T13:36:49  <jonasschnelli> Ah. Right... all the processing (LoadBlock, SyncTransaction, etc.) is done in thread "bitcoin-msghandler".
1282017-01-02T13:39:00  <gmaxwell> which fine, but not if it's processing a bunch of blocks at once.
1292017-01-02T13:39:34  <gmaxwell> e.g. it should just process two and then return control to the message handler loop.
1302017-01-02T13:39:57  <jonasschnelli> Okay.. I'll try that. Is 16 atm.
1312017-01-02T13:40:01  <jonasschnelli> *It's
1322017-01-02T13:41:03  <gmaxwell> where is it limited to 16?  like.. if you get 0 2 3 4 5 ... 999 1 doesn't end up processing 1000 at once?
1332017-01-02T13:41:15  <jonasschnelli> I guess an explicit thread "process spv" (or similar) doesn't make that much sense. SyncTransaction does hold cs_main anyways.
1342017-01-02T13:41:47  <jonasschnelli> 16 is the limit for the max amount of blocks per auxiliary request
1352017-01-02T13:42:01  <jonasschnelli> If block 1 comes in last, it processes 15 blocks in a row.
1362017-01-02T13:42:20  <jonasschnelli> Once the 16 are processed, it continues with the next batch of 16
1372017-01-02T13:42:30  <jonasschnelli> (through findNextBlocksToDownload())
1382017-01-02T13:42:49  <jonasschnelli> Ah. no, MAX_BLOCK_TO_PROCESS_PER_ITERATION == 5
1392017-01-02T13:44:47  <gmaxwell> oh that isn't many blocks to have in flight at once.
1402017-01-02T13:45:01  <gmaxwell> it should be possible to have many in flight but only process a few at a time.
1412017-01-02T13:45:26  <gmaxwell> if you cut the number in flight your throughput will decrease due to round trip delays.
1422017-01-02T13:46:47  <jonasschnelli> I just got in 16 blocks nice in order. It took more then 5s per block. I think its a slow peer.
1432017-01-02T13:47:32  <gmaxwell> thats one of the reasons you want to have lots of blocks in flight at once. :)
1442017-01-02T13:48:21  <jonasschnelli> Okay. Let me try that.
1452017-01-02T13:48:37  <jonasschnelli> 16 is max per peer. Maybe the request should contain 16*16 or similar.
1462017-01-02T13:49:18  <gmaxwell> yes 16 max per peer is probably fine.
1472017-01-02T13:50:45  *** cannon-c has quit IRC
1482017-01-02T13:51:37  *** Giszmo has joined #bitcoin-core-dev
1492017-01-02T13:56:35  <jonasschnelli> gmaxwell: Oh yes. That was the bottleneck, not enough blocks in flight, parallelism was not ideal
1502017-01-02T13:56:51  <jonasschnelli> now 450 blocks in 1min.
1512017-01-02T13:57:23  <jonasschnelli> (at height 445761)
1522017-01-02T13:58:12  *** laurentmt has joined #bitcoin-core-dev
1532017-01-02T13:59:45  *** laurentmt has quit IRC
1542017-01-02T14:02:29  <MarcoFalke> wumpus: No, the translations were never added back
1552017-01-02T14:02:52  <MarcoFalke> As of today we are missing the ones that were moved to warnings.cpp
1562017-01-02T14:03:02  <MarcoFalke> (additionally)
1572017-01-02T14:03:47  <MarcoFalke> I don't understand the translation process code enough to fix this, but something like #9457 should do it
1582017-01-02T14:03:49  <gribble> https://github.com/bitcoin/bitcoin/issues/9457 | WIP: [qt] translate bitcoin.cpp and libbitcoin_common_a_SOURCES by MarcoFalke · Pull Request #9457 · bitcoin/bitcoin · GitHub
1592017-01-02T14:16:44  <gmaxwell> oh interesting, I didn't really realize translations were file specific, I thought they were string to string conversions?
1602017-01-02T14:17:47  <MarcoFalke> It is an issue with some files are not picked up by the translation process code
1612017-01-02T14:20:26  <gmaxwell> oh I see.
1622017-01-02T14:36:47  *** BashCo has joined #bitcoin-core-dev
1632017-01-02T14:39:38  *** BashCo_ has quit IRC
1642017-01-02T14:41:25  *** jouke_ is now known as Jouke
1652017-01-02T14:46:26  *** Guyver2 has joined #bitcoin-core-dev
1662017-01-02T14:55:47  *** wasi has quit IRC
1672017-01-02T14:56:20  *** wasi has joined #bitcoin-core-dev
1682017-01-02T15:06:01  * BlueMatt is willing to review in exchange for review on #9289, #9419 or #9375 :)
1692017-01-02T15:06:03  <gribble> https://github.com/bitcoin/bitcoin/issues/9289 | net: drop boost::thread_group by theuni · Pull Request #9289 · bitcoin/bitcoin · GitHub
1702017-01-02T15:06:05  <gribble> https://github.com/bitcoin/bitcoin/issues/9419 | Stop Using cs_main for CNodeState/State() by TheBlueMatt · Pull Request #9419 · bitcoin/bitcoin · GitHub
1712017-01-02T15:06:07  <gribble> https://github.com/bitcoin/bitcoin/issues/9375 | Relay compact block messages prior to full block connection by TheBlueMatt · Pull Request #9375 · bitcoin/bitcoin · GitHub
1722017-01-02T15:26:23  <gmaxwell> Is there a reason that make check doesn't run qa/pull-tester/rpc-tests.py  ?
1732017-01-02T15:26:38  <gmaxwell> the tests in that are far more meaningful than most of the unit tests, IMO.
1742017-01-02T15:27:56  <BlueMatt> someone was complaining the other day that there is no way (afaik) to run rpc-tests from make ...
1752017-01-02T15:54:19  *** JackH has joined #bitcoin-core-dev
1762017-01-02T15:54:20  *** JackH has quit IRC
1772017-01-02T15:54:45  *** JackH has joined #bitcoin-core-dev
1782017-01-02T15:56:48  *** BashCo has quit IRC
1792017-01-02T15:57:24  *** BashCo has joined #bitcoin-core-dev
1802017-01-02T16:01:42  *** BashCo has quit IRC
1812017-01-02T16:21:49  *** MarcoFalke has quit IRC
1822017-01-02T16:22:04  *** MarcoFalke has joined #bitcoin-core-dev
1832017-01-02T16:32:26  *** Giszmo has quit IRC
1842017-01-02T16:39:42  *** PaulCape_ has quit IRC
1852017-01-02T16:40:53  *** PaulCapestany has joined #bitcoin-core-dev
1862017-01-02T16:54:10  *** PaulCapestany has quit IRC
1872017-01-02T16:54:37  *** abpa has joined #bitcoin-core-dev
1882017-01-02T16:56:06  *** PaulCapestany has joined #bitcoin-core-dev
1892017-01-02T16:56:31  *** PaulCapestany has quit IRC
1902017-01-02T16:57:24  *** f0nky has joined #bitcoin-core-dev
1912017-01-02T16:58:05  <f0nky> hi all, can i ask u guys a question?
1922017-01-02T16:59:32  *** f0nky has left #bitcoin-core-dev
1932017-01-02T16:59:47  *** PaulCape_ has joined #bitcoin-core-dev
1942017-01-02T17:02:28  *** udiWertheimer has quit IRC
1952017-01-02T17:07:51  *** BashCo has joined #bitcoin-core-dev
1962017-01-02T17:51:52  *** NicolasDorier has quit IRC
1972017-01-02T17:52:14  *** nOgAnOo has quit IRC
1982017-01-02T17:52:20  *** btcdrak has quit IRC
1992017-01-02T17:52:50  *** eragmus has quit IRC
2002017-01-02T17:52:57  *** rubensayshi has quit IRC
2012017-01-02T17:52:57  *** pindarhk has quit IRC
2022017-01-02T17:53:11  *** ibrightly has quit IRC
2032017-01-02T17:54:08  *** limpkin has quit IRC
2042017-01-02T17:55:27  *** rubensayshi has joined #bitcoin-core-dev
2052017-01-02T17:56:40  *** limpkin has joined #bitcoin-core-dev
2062017-01-02T17:57:23  *** btcdrak has joined #bitcoin-core-dev
2072017-01-02T17:57:36  *** pindarhk has joined #bitcoin-core-dev
2082017-01-02T17:58:27  *** ibrightly has joined #bitcoin-core-dev
2092017-01-02T18:02:16  *** Saucery has quit IRC
2102017-01-02T18:07:26  *** NicolasDorier has joined #bitcoin-core-dev
2112017-01-02T18:12:01  *** eragmus has joined #bitcoin-core-dev
2122017-01-02T18:18:41  *** justanotheruser has quit IRC
2132017-01-02T18:23:50  *** justanotheruser has joined #bitcoin-core-dev
2142017-01-02T18:46:21  *** AaronvanW has quit IRC
2152017-01-02T18:48:53  *** bitcog has joined #bitcoin-core-dev
2162017-01-02T18:53:23  *** AaronvanW has joined #bitcoin-core-dev
2172017-01-02T19:18:11  *** laurentmt has joined #bitcoin-core-dev
2182017-01-02T19:18:22  *** laurentmt has quit IRC
2192017-01-02T20:02:43  *** lol_ has joined #bitcoin-core-dev
2202017-01-02T20:03:32  *** norotartagen has quit IRC
2212017-01-02T20:03:44  *** nOgAnOo has joined #bitcoin-core-dev
2222017-01-02T20:03:50  *** lol_ has quit IRC
2232017-01-02T20:04:06  *** lol_ has joined #bitcoin-core-dev
2242017-01-02T20:04:45  *** negatratoron has joined #bitcoin-core-dev
2252017-01-02T20:18:35  *** bitcog has quit IRC
2262017-01-02T20:19:44  *** bitcog has joined #bitcoin-core-dev
2272017-01-02T20:21:25  *** negatratoron has quit IRC
2282017-01-02T20:21:50  *** norotartagen has joined #bitcoin-core-dev
2292017-01-02T20:24:12  *** bitcog has quit IRC
2302017-01-02T20:26:35  *** bitcog has joined #bitcoin-core-dev
2312017-01-02T20:27:33  *** droark has joined #bitcoin-core-dev
2322017-01-02T20:29:24  <achow101> are the 0.13.2 detached sigs ready yet?
2332017-01-02T20:34:33  *** bitcog has quit IRC
2342017-01-02T20:36:11  *** bitcog has joined #bitcoin-core-dev
2352017-01-02T20:41:47  <cfields> achow101: running sanity tests. eta ~10 min.
2362017-01-02T20:50:25  <cfields> gitian builders: 0.13.2 detached sigs pushed
2372017-01-02T20:56:34  <luke-jr> crap, forgot to save a copy of the intermediate files
2382017-01-02T21:06:14  *** bitcog0 has joined #bitcoin-core-dev
2392017-01-02T21:08:22  *** bitcog0 has quit IRC
2402017-01-02T21:08:48  *** bitcog has quit IRC
2412017-01-02T21:46:08  *** Guyver2 has quit IRC
2422017-01-02T21:48:42  *** wvr has quit IRC
2432017-01-02T22:00:07  <bitcoin-git> [bitcoin] isle2983 opened pull request #9459: Improvements to copyright_header.py and some minor copyright header tweaks. (master...PR-copyright-script-improve) https://github.com/bitcoin/bitcoin/pull/9459
2442017-01-02T22:44:42  *** Saucery has joined #bitcoin-core-dev
2452017-01-02T22:46:13  *** jannes has quit IRC
2462017-01-02T23:01:42  <cfields> BlueMatt: right, so does making CNodeState::cs static not enforce the only-one-nodestate-at-once rule?
2472017-01-02T23:19:00  *** robert__ has quit IRC
2482017-01-02T23:31:27  *** robert__ has joined #bitcoin-core-dev
2492017-01-02T23:48:26  *** Giszmo has joined #bitcoin-core-dev