1 2018-02-12 09:06:47	0|razor948|┬┬─┐┌─┐ ┌─┐┬ ┬┌─┐┌─┐┬─┐┌┐┌┌─┐┌┬┐┌─┐ ┌─┐┬─┐┌─┐
  2 2018-02-12 09:06:48	0|razor948|┬┬─┐┌─┐ ┌─┐┬ ┬┌─┐┌─┐┬─┐┌┐┌┌─┐┌┬┐┌─┐ ┌─┐┬─┐┌─┐
  3 2018-02-12 09:06:49	0|razor948|┬┬─┐┌─┐ ┌─┐┬ ┬┌─┐┌─┐┬─┐┌┐┌┌─┐┌┬┐┌─┐ ┌─┐┬─┐┌─┐
  4 2018-02-12 09:06:49	0|razor948|┬┬─┐┌─┐ ┌─┐┬ ┬┌─┐┌─┐┬─┐┌┐┌┌─┐┌┬┐┌─┐ ┌─┐┬─┐┌─┐
  5 2018-02-12 09:06:51	0|razor948|│├┬┘│   └─┐│ │├─┘├┤ ├┬┘│││├┤  │ └─┐ │ │├┬┘│ ┬
  6 2018-02-12 09:06:51	0|razor948|│├┬┘│   └─┐│ │├─┘├┤ ├┬┘│││├┤  │ └─┐ │ │├┬┘│ ┬
  7 2018-02-12 09:06:51	0|razor948|│├┬┘│   └─┐│ │├─┘├┤ ├┬┘│││├┤  │ └─┐ │ │├┬┘│ ┬
  8 2018-02-12 09:06:52	0|razor948|│├┬┘│   └─┐│ │├─┘├┤ ├┬┘│││├┤  │ └─┐ │ │├┬┘│ ┬
  9 2018-02-12 09:06:55	0|razor948|┴┴└─└─┘o└─┘└─┘┴  └─┘┴└─┘└┘└─┘ ┴ └─┘o└─┘┴└─└─┘
 10 2018-02-12 09:06:56	0|razor948|┴┴└─└─┘o└─┘└─┘┴  └─┘┴└─┘└┘└─┘ ┴ └─┘o└─┘┴└─└─┘
 11 2018-02-12 09:06:56	0|razor948|┴┴└─└─┘o└─┘└─┘┴  └─┘┴└─┘└┘└─┘ ┴ └─┘o└─┘┴└─└─┘
 12 2018-02-12 09:06:56	0|razor948|┴┴└─└─┘o└─┘└─┘┴  └─┘┴└─┘└┘└─┘ ┴ └─┘o└─┘┴└─└─┘
 13 2018-02-12 09:06:59	0|razor948|rex_4539 eklitzke mmgen dlb76 ohnx Victorsueca intcat goatpig Sinclair6 arubi grafcaps DarylSharp dgy_ tryphe Randolf shesek Emcy meshcollider dcousens Arise2 mirese Evel-Knievel ghost43 Cory mandric DrFeelGood justanotheruser gmaxwell droark spinza unholymachine lnostdal boblee ludens[m] Masaomi[m] ajtowns[m] kewde[m] herzmeister[m] cncr04s Scrat Apocalyptic NielsvG bordeaux_facile_ Varunram Muis dagurval mariorz jnewbery mlz punch rockhouse Bas
 14 2018-02-12 09:07:33	0|meshcollider|not this again -_-
 15 2018-02-12 09:07:46	0|wumpus|yeah...
 16 2018-02-12 09:07:57	0|aj|at least it's not in colour?
 17 2018-02-12 09:08:56	0|wumpus|can anyone, that uses bitcoin-tx, comment on https://github.com/bitcoin/bitcoin/pull/10694?
 18 2018-02-12 09:12:11	0|bitcoin-git|13bitcoin/06master 14a8b5d20 15Sjors Provoost: Reset pblocktree before deleting LevelDB file
 19 2018-02-12 09:12:11	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/fe53d5f3636a...79313d2e2040
 20 2018-02-12 09:12:12	0|bitcoin-git|13bitcoin/06master 1479313d2 15Wladimir J. van der Laan: Merge #12401: Reset pblocktree before deleting LevelDB file...
 21 2018-02-12 09:12:59	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #12401: Reset pblocktree before deleting LevelDB file (06master...062018/02/reset-pblocktree) 02https://github.com/bitcoin/bitcoin/pull/12401
 22 2018-02-12 09:14:29	0|bitcoin-git|13bitcoin/06master 14c4af738 15Matt Corallo: Fix ignoring tx data requests when fPauseSend is set on a peer...
 23 2018-02-12 09:14:29	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/79313d2e2040...a8cbbdb07a59
 24 2018-02-12 09:14:30	0|bitcoin-git|13bitcoin/06master 14a8cbbdb 15Wladimir J. van der Laan: Merge #12392: Fix ignoring tx data requests when fPauseSend is set on a peer...
 25 2018-02-12 09:15:19	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #12392: Fix ignoring tx data requests when fPauseSend is set on a peer (06master...062018-02-fix-fpausesend-getdata-resp) 02https://github.com/bitcoin/bitcoin/pull/12392
 26 2018-02-12 09:25:56	0|jonasschnelli|rc4?
 27 2018-02-12 09:26:27	0|wumpus|maybe...
 28 2018-02-12 09:26:47	0|wumpus|might be too soon
 29 2018-02-12 09:27:06	0|jonasschnelli|maybe wait for other report, right.
 30 2018-02-12 09:27:12	0|jonasschnelli|*reports
 31 2018-02-12 09:27:44	0|wumpus|if you release too many rcs in short succession the number of testers will likely drop; I've already seen the first "I'll test next weekend when rc n+1 is out"
 32 2018-02-12 09:29:00	0|wumpus|so let's keep it to 1 per week
 33 2018-02-12 09:29:46	0|wumpus|going to do the backports already so people on the 0.16 branch can test
 34 2018-02-12 09:30:16	0|jonasschnelli|Makes sense.
 35 2018-02-12 09:31:05	0|gmaxwell|wumpus: though perhaps the things that would be in rc3 should ... nevermind you got it. :P
 36 2018-02-12 09:34:15	0|bitcoin-git|13bitcoin/060.16 14d44cd7e 15Sjors Provoost: Reset pblocktree before deleting LevelDB file...
 37 2018-02-12 09:34:15	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 060.16: 02https://github.com/bitcoin/bitcoin/compare/a5e3d44cc8f6...0f616517e1f2
 38 2018-02-12 09:34:16	0|bitcoin-git|13bitcoin/060.16 140f61651 15Matt Corallo: Fix ignoring tx data requests when fPauseSend is set on a peer...
 39 2018-02-12 09:34:22	0|wumpus|gmaxwell: ^^
 40 2018-02-12 09:35:23	0|gmaxwell|oh lol I was already running with those two patches.
 41 2018-02-12 09:35:30	0|bitcoin-git|[13bitcoin] 15laanwj pushed 5 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/a8cbbdb07a59...0dfc25f82a01
 42 2018-02-12 09:35:31	0|bitcoin-git|13bitcoin/06master 14ba91724 15Cory Fields: boost: remove useless threadGroup parameter from Discover
 43 2018-02-12 09:35:31	0|bitcoin-git|13bitcoin/06master 14f26866b 15Cory Fields: boost: drop boost threads for upnp
 44 2018-02-12 09:35:32	0|bitcoin-git|13bitcoin/06master 140827267 15Cory Fields: boost: drop boost threads from torcontrol
 45 2018-02-12 09:35:37	0|wumpus|heh
 46 2018-02-12 09:36:15	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #12381: Remove more boost threads (06master...06boost-threads-again) 02https://github.com/bitcoin/bitcoin/pull/12381
 47 2018-02-12 09:38:59	0|Randolf|Maybe #12393 is an easy one to close?
 48 2018-02-12 09:39:01	0|gribble|https://github.com/bitcoin/bitcoin/issues/12393 | Fix a-vs-an typos by practicalswift · Pull Request #12393 · bitcoin/bitcoin · GitHub
 49 2018-02-12 09:39:03	0|Randolf|Merge?
 50 2018-02-12 09:39:15	0|Randolf|Simple documentation fixes.
 51 2018-02-12 09:39:32	0|Randolf|Not a high priority.
 52 2018-02-12 09:40:07	0|gmaxwell|Randolf: it has pending requested changes by reviewers.
 53 2018-02-12 09:40:29	0|wumpus|documentation is high priority unless. yeah, this is only typos
 54 2018-02-12 09:40:58	0|Randolf|gmaxwell:  Okay.  Is there a place where one can see what's in the "pending requested changes by reviewers" list?  Or is the fact that they're open already implying that?
 55 2018-02-12 09:41:12	0|gmaxwell|Randolf: look at the last comments on it.
 56 2018-02-12 09:41:25	0|gmaxwell|oh I misread, sorry!
 57 2018-02-12 09:41:41	0|Randolf|I see "utACK" from luke-jr.
 58 2018-02-12 09:41:43	0|gmaxwell|(I thought the last comment was asking to remove that change, and I saw no commits after it)
 59 2018-02-12 09:42:14	0|Randolf|My curiosity on this is motivated by my desire to gain a better understanding of how this all works.
 60 2018-02-12 09:43:09	0|Randolf|(So far, the process overall seems to be well organized and efficient.)
 61 2018-02-12 09:50:31	0|bitcoin-git|13bitcoin/06master 1411376b5 15practicalswift: Fix a-vs-an typos
 62 2018-02-12 09:50:31	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/0dfc25f82a01...108af52ef75a
 63 2018-02-12 09:50:32	0|bitcoin-git|13bitcoin/06master 14108af52 15Wladimir J. van der Laan: Merge #12393: Fix a-vs-an typos...
 64 2018-02-12 09:51:19	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #12393: Fix a-vs-an typos (06master...06a-vs-an-typos) 02https://github.com/bitcoin/bitcoin/pull/12393
 65 2018-02-12 09:53:06	0|Randolf|wumpus:  I agree.
 66 2018-02-12 10:03:19	0|wumpus|Randolf: cool, someone finally agrees with me for once, mind if I save the quote? :)
 67 2018-02-12 10:06:00	0|Sentineo|:D
 68 2018-02-12 10:16:58	0|Randolf|wumpus:  Yes, I have no objections to being quoted.  (My full name is Randolf Richardson.)
 69 2018-02-12 10:17:19	0|wumpus|Randolf: woohoo!
 70 2018-02-12 10:17:52	0|Randolf|wumpus:  I'm a big fan of writing documentation before coding.  I do this with all the software that I write.
 71 2018-02-12 10:18:07	0|Randolf|wumpus:  It sure makes maintenance easier later on.
 72 2018-02-12 10:19:19	0|wumpus|Randolf: yup; it's good to have a background idea why something was done; and the most important thing is correct documentation, comments that are deceiving and don't match the code are worse than having no comments at all
 73 2018-02-12 10:20:36	0|Randolf|I like comments in code too.  Sometimes they are overdone though, so I prefer to have a mixture of per-line comments (for specific things that need it) and an introductory set prior to a number of instructions / lines of code.
 74 2018-02-12 10:21:31	0|wumpus|I think what is important about code comments is that they explain reasoning, not directly what the code does which is obvious to everyone with knowledge of the programming language
 75 2018-02-12 10:31:46	0|bitcoin-git|13bitcoin/06master 14faefd29 15MarcoFalke: qa: Prepare functional tests for Windows...
 76 2018-02-12 10:31:46	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/108af52ef75a...b4d85490f09e
 77 2018-02-12 10:31:47	0|bitcoin-git|13bitcoin/06master 14b4d8549 15Wladimir J. van der Laan: Merge #11858: qa: Prepare tests for Windows...
 78 2018-02-12 10:32:16	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #11858: qa: Prepare tests for Windows (06master...06Mf1712-qaWinForRealNow) 02https://github.com/bitcoin/bitcoin/pull/11858
 79 2018-02-12 10:41:37	0|bitcoin-git|13bitcoin/06master 14a25cb0f 15murrayn: Use ptrdiff_t type to more precisely indicate usage and avoid compiler warnings.
 80 2018-02-12 10:41:37	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/b4d85490f09e...c8b54b2044db
 81 2018-02-12 10:41:38	0|bitcoin-git|13bitcoin/06master 14c8b54b2 15Wladimir J. van der Laan: Merge #12351: Libraries: Use correct type ; avoid compiler warnings....
 82 2018-02-12 10:42:22	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #12351: Libraries: Use correct type ; avoid compiler warnings. (06master...06ptrdiff_t) 02https://github.com/bitcoin/bitcoin/pull/12351
 83 2018-02-12 10:44:33	0|bitcoin-git|[13bitcoin] 15jonasschnelli pushed 3 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/c8b54b2044db...8e6f9f4ebc74
 84 2018-02-12 10:44:34	0|bitcoin-git|13bitcoin/06master 14718f05c 15Gregory Sanders: move more bumpfee prechecks to feebumper::PreconditionChecks
 85 2018-02-12 10:44:34	0|bitcoin-git|13bitcoin/06master 14faca18d 15MarcoFalke: feebumper: Use PreconditionChecks to determine bump eligibility
 86 2018-02-12 10:44:35	0|bitcoin-git|13bitcoin/06master 148e6f9f4 15Jonas Schnelli: Merge #12296: wallet: Only fee-bump non-conflicted/non-confirmed txes...
 87 2018-02-12 10:45:40	0|bitcoin-git|[13bitcoin] 15jonasschnelli closed pull request #12296: wallet: Only fee-bump non-conflicted/non-confirmed txes (06master...06Mf1801-walletFeeBumpNoConf) 02https://github.com/bitcoin/bitcoin/pull/12296
 88 2018-02-12 10:47:26	0|provoostenator|In at least some cases the reference code is more clear than the BIP it implements, thanks to an abundance of comments.
 89 2018-02-12 10:48:44	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #12023: update the OpenBSD build guide (06master...06openbsd) 02https://github.com/bitcoin/bitcoin/pull/12023
 90 2018-02-12 10:48:48	0|promag|is it valid or not to have the on scriptpubkey duplicated?
 91 2018-02-12 10:48:56	0|wumpus|provoostenator: that's a good thing, yes :)
 92 2018-02-12 10:48:57	0|promag|*the same
 93 2018-02-12 10:50:05	0|gmaxwell|the same scriptpubkey duplicated where?
 94 2018-02-12 10:50:59	0|gmaxwell|promag: are you asking if a transaction can have multiple outputs using the same scriptpubkey?
 95 2018-02-12 10:51:18	0|promag|yes, sorry if it was't clear
 96 2018-02-12 10:51:30	0|gmaxwell|If so, thats valid in the consensus rules, though bitcoin core's wallet (and I assume most other wallets) won't produce it.
 97 2018-02-12 10:52:00	0|gmaxwell|(e.g. if you do a sendmany with repeated outputs it just merges them)
 98 2018-02-12 10:52:04	0|murrayn|sipa, I get that. But where's the bottleneck? I could see if one cpu was pegged. Or disk IO. But nothing seems to be happening. It's just slow.
 99 2018-02-12 10:52:28	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #11790: Add pixmaps for testnet and regtest (06master...06pixmaps) 02https://github.com/bitcoin/bitcoin/pull/11790
100 2018-02-12 10:52:29	0|promag|gmaxwell: well fundrawtransaction allows a change address to be one of the outputs
101 2018-02-12 10:52:46	0|promag|gmaxwell: should probably check that?
102 2018-02-12 10:53:55	0|wumpus|sounds like an edge case that might be checked, yes. Not because it would be invalid, but because it 100% sure means someone made amistake.
103 2018-02-12 10:54:13	0|promag|maybe 99%
104 2018-02-12 10:54:15	0|promag|:P
105 2018-02-12 10:54:27	0|wumpus|I can't think of any reason why it wouldn't be
106 2018-02-12 10:55:02	0|promag|like a stupid coin split to same address
107 2018-02-12 10:55:29	0|wumpus|I see no point to doing that
108 2018-02-12 10:55:30	0|promag|anyway, should we bother to check that on these raw rpc?
109 2018-02-12 10:58:05	0|wumpus|esp. after #12257, when the coin selection is changed so that all coins sent to a certain destination will always be spent at once
110 2018-02-12 10:58:07	0|gribble|https://github.com/bitcoin/bitcoin/issues/12257 | [wallet] Use destination groups instead of coins in coin select by kallewoof · Pull Request #12257 · bitcoin/bitcoin · GitHub
111 2018-02-12 11:00:38	0|promag|wumpus: should the check be in fundrawtransaction or CWallet::CreateTransaction?
112 2018-02-12 11:01:53	0|wumpus|probably in CreateTransaction if you want to catch all cases where this is a possibility
113 2018-02-12 11:02:33	0|wumpus|e.g. otherwise you could still do the same trick from the GUI with coincontrol?
114 2018-02-12 11:02:44	0|sipa|murrayn: usually it's RAM and disk access that's the bottleneck
115 2018-02-12 11:04:03	0|murrayn|sipa I can confirm that it's neither for me. I am running dbcache 2048 and disk IO is not a factor.
116 2018-02-12 11:04:16	0|sipa|what are you observing?
117 2018-02-12 11:04:27	0|murrayn|what do you mean?
118 2018-02-12 11:04:42	0|sipa|what do you see, what do you expect to see
119 2018-02-12 11:05:15	0|murrayn|like i said i could understand if one cpu was pegged. i have a quad core processor
120 2018-02-12 11:05:30	0|murrayn|there is no heavy disk i/o
121 2018-02-12 11:05:34	0|sipa|well is it making progress?
122 2018-02-12 11:05:47	0|murrayn|it moves forward, like time itself
123 2018-02-12 11:06:05	0|sipa|is it validating blocks?
124 2018-02-12 11:06:11	0|murrayn|yes!
125 2018-02-12 11:06:26	0|sipa|what's in debug.log?
126 2018-02-12 11:06:43	0|murrayn|but if i have the hardware, why not do it quicker? i'm waiting dammit!
127 2018-02-12 11:07:21	0|gmaxwell|murrayn: bitcoin it takes hours to sync even on the fastest hardware available, its doing a tremendous amount of work.
128 2018-02-12 11:07:48	0|gmaxwell|when you say 'disk IO is not a factor' -- this isn't particularly convincing. IOwait often doesn't look like high usage.
129 2018-02-12 11:08:18	0|phantomcircuit|gmaxwell, i do experience stang performance things doing IBD over the network where there isn't any obvious bottleneck
130 2018-02-12 11:08:28	0|phantomcircuit|(vm with fsync off)
131 2018-02-12 11:08:28	0|sipa|with dbcache 2048 i would expect 100% cpu usage on one core though
132 2018-02-12 11:08:39	0|sipa|for extended periods of time between flushes
133 2018-02-12 11:08:52	0|echeveria|it comes across to me as sort of bursty for no real reason.
134 2018-02-12 11:08:53	0|wumpus|I'm missing the context, but if it doesn't max out your CPUs, don't you happen to have bad peers so it's waiting for blocks?
135 2018-02-12 11:09:16	0|murrayn|https://pastebin.com/nAipD6J3
136 2018-02-12 11:09:17	0|phantomcircuit|wumpus, yes
137 2018-02-12 11:09:19	0|echeveria|wumpus: even when directly connected to a single peer on a 200Mbit line, I've seen that.
138 2018-02-12 11:09:19	0|wumpus|in the latter stages of synchronization it will generally use all cores at 100% where it can, in my experience
139 2018-02-12 11:09:23	0|murrayn|that's the tail of debug.log
140 2018-02-12 11:09:30	0|phantomcircuit|iirc there is supposed to be logic to handle that but it doesn't seem to work great
141 2018-02-12 11:09:40	0|phantomcircuit|but it works well enough that i haven't looked carefully
142 2018-02-12 11:09:59	0|sipa|murrayn: can you show a bit more?
143 2018-02-12 11:10:09	0|murrayn|sure, how much?
144 2018-02-12 11:10:13	0|sipa|a page
145 2018-02-12 11:10:14	0|gmaxwell|stalling peers is certantly a thing, the functionality to deal with that is "simplest thing necessary to avoid totally failing" grade.
146 2018-02-12 11:10:33	0|gmaxwell|murrayn: are you doing this sync on a computer you physically have or AWS or what?
147 2018-02-12 11:10:37	0|wumpus|gmaxwell: indeed
148 2018-02-12 11:10:59	0|murrayn|https://pastebin.com/jXXLpmxE
149 2018-02-12 11:11:11	0|murrayn|gmaxwell, my desktop
150 2018-02-12 11:11:33	0|echeveria|2018-02-12 11:06:21 version handshake timeout from 476
151 2018-02-12 11:11:35	0|echeveria|2018-02-12 11:06:24 version handshake timeout from 477
152 2018-02-12 11:11:36	0|echeveria|that's fun.
153 2018-02-12 11:12:52	0|echeveria|it's in my log a bunch too but I've never been able to work out a pattern in it.
154 2018-02-12 11:13:10	0|sipa|murrayn: you may want to run with -debug=bench of you want to figure out what it's spending time on
155 2018-02-12 11:13:18	0|sipa|but it may just be shitty peers
156 2018-02-12 11:13:34	0|sipa|that don't give you blocks fast enough for you to process
157 2018-02-12 11:13:38	0|murrayn|well i'm afraid to start over!
158 2018-02-12 11:13:45	0|sipa|it won't
159 2018-02-12 11:13:57	0|murrayn|"only" 1 year 16 weeks behind
160 2018-02-12 11:14:05	0|sipa|if you shutdown cleanly it will continue where it left off
161 2018-02-12 11:14:50	0|murrayn|ok sipa i will try
162 2018-02-12 11:15:06	0|gmaxwell|These logs look pretty normal.
163 2018-02-12 11:15:26	0|gmaxwell|other than it being a bit slow.
164 2018-02-12 11:15:29	0|murrayn|just to add some background this is running with -reindex-chainstate because i already had all the blocks downloaded
165 2018-02-12 11:15:45	0|sipa|oh
166 2018-02-12 11:15:58	0|gmaxwell|see now all these peer theories go out the window.
167 2018-02-12 11:15:58	0|sipa|well, then it's not due to slow peers
168 2018-02-12 11:16:02	0|murrayn|no
169 2018-02-12 11:16:22	0|sipa|but in any case, don't run with -reindex-chainstate the second time or it will start over again
170 2018-02-12 11:16:24	0|murrayn|my initial sync took 10 days which i thought was crazy
171 2018-02-12 11:16:40	0|sipa|but you can shutdown and it will continue the reindex
172 2018-02-12 11:17:02	0|gmaxwell|murrayn: what OS and what version of the software is this?
173 2018-02-12 11:17:15	0|murrayn|win7, 0.15.1
174 2018-02-12 11:17:30	0|gmaxwell|some anti-virus can absurdly slow down sync.
175 2018-02-12 11:17:37	0|murrayn|n/a
176 2018-02-12 11:18:31	0|gmaxwell|wumpus: why are you running -reindex-chainstate?
177 2018-02-12 11:19:04	0|murrayn|gmaxwell, do you mean me?
178 2018-02-12 11:19:07	0|gmaxwell|lol yes
179 2018-02-12 11:19:10	0|murrayn|ok
180 2018-02-12 11:19:22	0|murrayn|i moved the datadir to a new disk
181 2018-02-12 11:19:39	0|gmaxwell|would it happen to be a USB hard drive?
182 2018-02-12 11:19:43	0|murrayn|and when i restarted bitcoin-qt it did it's thing
183 2018-02-12 11:19:46	0|murrayn|gmaxwell, no
184 2018-02-12 11:19:52	0|phantomcircuit|murrayn, that looks like io issues
185 2018-02-12 11:19:58	0|phantomcircuit|there's 2-3 seconds between blocks
186 2018-02-12 11:20:00	0|phantomcircuit|it's not bursty
187 2018-02-12 11:20:15	0|murrayn|i would be glad to see 2-3s/block
188 2018-02-12 11:21:02	0|murrayn|phantomcircuit, it's just not IO. these aren't slow drives
189 2018-02-12 11:21:07	0|murrayn|i would hear them!
190 2018-02-12 11:21:51	0|bitcoin-git|[13bitcoin] 15promag opened pull request #12415: Interrupt loading thread after shutdown request (06master...062018-02-shutdown) 02https://github.com/bitcoin/bitcoin/pull/12415
191 2018-02-12 11:22:15	0|gmaxwell|hear them?
192 2018-02-12 11:22:18	0|murrayn|i do see memory use climb up to 2G+, but then it drops down and starts the cycle again
193 2018-02-12 11:22:51	0|murrayn|it's under 1G now
194 2018-02-12 11:23:13	0|gmaxwell|murrayn: yes when the cache fills it flushes.
195 2018-02-12 11:23:29	0|murrayn|yeah, makes sense
196 2018-02-12 11:23:41	0|gmaxwell|The name cache is largely a misnomer, the main useful thing the cache does during sync is act as a buffer to prevent spent outputs from ever hitting the database.
197 2018-02-12 11:24:02	0|gmaxwell|it caches too, but that function doesn't do much for performance.
198 2018-02-12 11:24:11	0|gmaxwell|(during sync)
199 2018-02-12 11:24:16	0|murrayn|ok, well i'm using -dbcache=2048
200 2018-02-12 11:25:42	0|murrayn|just out of curiosity, when is the last time any of you guys in this conversation started a new datadir
201 2018-02-12 11:26:23	0|murrayn|i'm willing to believe it's some issue with the windows build, and willing to try to track it down.
202 2018-02-12 11:27:01	0|gmaxwell|murrayn: several times a month.
203 2018-02-12 11:27:10	0|murrayn|ok, thought so
204 2018-02-12 11:27:24	0|gmaxwell|murrayn: it's not an issue with the 'windows build' people have reported couple hour syncs in windows with 0.15.x
205 2018-02-12 11:27:28	0|murrayn|gmaxwell, from the network?
206 2018-02-12 11:27:53	0|gmaxwell|murrayn: yes, and reindexes.
207 2018-02-12 11:28:38	0|murrayn|well in any case i would like to help track it down. from what I read I'm not alone.
208 2018-02-12 11:29:18	0|gmaxwell|in your case either you finished syncing from blocks on disk and started pulling from the network and your slower due to peers/network.. or your IO is just super high latency on your system.
209 2018-02-12 11:29:39	0|gmaxwell|murrayn: sipa asked you earlier to turn up bench debugging.
210 2018-02-12 11:30:03	0|gmaxwell|murrayn: you can turn them on without restarting dunno why he didn't suggest that.
211 2018-02-12 11:30:11	0|murrayn|gmaxwell, yeah but i don't want to restart and lose over two days of "progress"
212 2018-02-12 11:30:17	0|murrayn|oh ok
213 2018-02-12 11:30:18	0|gmaxwell|you won't lose progress.
214 2018-02-12 11:30:27	0|gmaxwell|regardless, it'll continue from where it is.
215 2018-02-12 11:30:45	0|gmaxwell|use the logging rpc/cli command to enable bench and net
216 2018-02-12 11:31:03	0|murrayn|can you give me a tldr?
217 2018-02-12 11:31:13	0|murrayn|the command
218 2018-02-12 11:31:18	0|wumpus|I think it's time to move this to #bitcoin
219 2018-02-12 11:31:55	0|gmaxwell|murrayn: you're using the gui interface? bring up the debug console and run logging '["bench","net"]'
220 2018-02-12 11:32:12	0|murrayn|or console. ok will try
221 2018-02-12 11:32:48	0|murrayn|done will report back in a few
222 2018-02-12 12:11:31	0|dcousens|wumpus - hope https://github.com/bitcoin/bitcoin/pull/12169#issuecomment-364903510 didn't de-rail,  I was genuinely curious and figured it might be useful to others to see a code example
223 2018-02-12 14:18:29	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 4 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/8e6f9f4ebc74...5dc00f68c49c
224 2018-02-12 14:18:30	0|bitcoin-git|13bitcoin/06master 14a570098 15MarcoFalke: Squashed 'src/univalue/' changes from 07947ff2da..51d3ab34ba...
225 2018-02-12 14:18:30	0|bitcoin-git|13bitcoin/06master 14fa1388e 15MarcoFalke: univalue: Bump subtree
226 2018-02-12 14:18:31	0|bitcoin-git|13bitcoin/06master 1491986ed 15Karel Bilek: scripted-diff: Use UniValue.pushKV instead of push_back(Pair())...
227 2018-02-12 14:19:14	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #12193: RPC: Consistently use UniValue.pushKV instead of push_back(Pair()) (karel-3d) (06master...06Mf1801-univalueDeprecatedPair) 02https://github.com/bitcoin/bitcoin/pull/12193
228 2018-02-12 14:51:46	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #12416: Fix Windows build errors introduced in #10498 (06master...06fix-windows-build) 02https://github.com/bitcoin/bitcoin/pull/12416
229 2018-02-12 16:22:09	0|instagibbs|is someone generating hashes of issues/prs somewhere?
230 2018-02-12 16:22:37	0|instagibbs|wumpus, oh i see you linked, nevermind
231 2018-02-12 16:24:06	0|wumpus|yes not so much hashes as a full mirror of information available through the API, though of course you can use it to compute hashes: https://github.com/zw/bitcoin-gh-meta
232 2018-02-12 18:10:34	0|qttmyth88|Hello, Is there a precaution to sending a request through bitcoin core. What happens if a malware classified me as a fraud because my name doesn't show as the name on the internet provider. Is there away to remove me off that alert?
233 2018-02-12 18:45:45	0|provoostenator|How is change_type in coincontrol used? There's no UI for it afaik, but maybe an RPC command?
234 2018-02-12 18:48:05	0|provoostenator|Or is coincontrol.h alwasys used even if the user turns off "Enable coin control features"?
235 2018-02-12 18:49:46	0|sipa|yes, it's just the interface to pass information to the coin selection algorithm
236 2018-02-12 18:59:16	0|polpol|i heard that after 0.16.0 segwit will be used "by default" is that correct?
237 2018-02-12 19:00:07	0|sipa|yes
238 2018-02-12 19:02:04	0|polpol|that means that segwit usage will be 100% or not necessarily?
239 2018-02-12 19:02:31	0|sipa|no, people may be using wallet software other than bitcoin core
240 2018-02-12 19:02:55	0|sipa|or may choose to turn it off
241 2018-02-12 19:03:10	0|sipa|or may continue to use addresses they created before
242 2018-02-12 19:03:25	0|polpol|got it, thank you sipa
243 2018-02-12 19:03:27	0|sipa|or may keep spending coins sent to earlier addresses
244 2018-02-12 19:04:21	0|michagogo|Does anyone here have any experience in working with Ubuntu packages (backports etc.)?
245 2018-02-12 19:17:31	0|instagibbs|provoostenator, yeah coin control is an overloaded term imo. consumers see it as that qt window, Core contributors see it as what sipa said
246 2018-02-12 19:18:55	0|provoostenator|Is there a good reason not to just remove that checbox and turn it on by default?
247 2018-02-12 19:20:05	0|sipa|which checkbox?
248 2018-02-12 19:20:37	0|provoostenator|There's a "Enable Coin Control Features" checkbox in the QT settings.Maybe move Coin Control Features to the bottom of the Send screen, below fees. As long as the basic stuff is at the top, it shouldn't be too intimiating.
249 2018-02-12 19:21:31	0|provoostenator|And some sort of Show / Hide toggle in the send screen itself make more sense to me in general.
250 2018-02-12 19:21:54	0|sipa|define basic stuff
251 2018-02-12 19:22:09	0|provoostenator|Basic stuff: how much, to which address
252 2018-02-12 19:22:33	0|sipa|the idea is that most users don't know and shouldn't care about things like coins, inputs, outputs, groupings, ...
253 2018-02-12 19:22:36	0|provoostenator|(and label / note)
254 2018-02-12 19:24:13	0|provoostenator|The Coin Control Feature at the moment are only Input selection and a custom change address. They can be hidden by default, but I don't need you need a setting to reveal them.
255 2018-02-12 19:26:00	0|provoostenator|E.g. there could be Coin Control button next to Add Recipient at the bottom of the screen to toggle that section.
256 2018-02-12 19:44:12	0|provoostenator|ryanofsky or someone else: re #11625, I have no idea how to use gdb other than "gdb src/qt/test/test_bitcoin-qt"
257 2018-02-12 19:44:14	0|gribble|https://github.com/bitcoin/bitcoin/issues/11625 | Add BitcoinApplication & RPCConsole tests by ryanofsky · Pull Request #11625 · bitcoin/bitcoin · GitHub
258 2018-02-12 19:44:54	0|provoostenator|And do I need to use any special configure flags?
259 2018-02-12 20:10:03	0|michagogo|Hm
260 2018-02-12 20:10:20	0|michagogo|I tried to see if mingw-w64 was easily backportable
261 2018-02-12 20:10:38	0|michagogo|And it's not really working, something about dependencies
262 2018-02-12 20:12:14	0|michagogo|For all I know it's easy to fix, but I don't actually know ~anything about Ubuntu packaging, so I have no idea how to do more than run the `backportpackage` command :-/
263 2018-02-12 20:19:39	0|cfields|sipa: 1day-ago pong.
264 2018-02-12 20:25:45	0|instagibbs|fAllowOtherInputs comment seems to be off. "//! If false, allows unselected inputs, but requires all selected inputs be used". But AvailableCoins immediately filters things not on the selected list when list is non-zero
265 2018-02-12 20:25:51	0|instagibbs|am I understanding it right
266 2018-02-12 20:27:02	0|instagibbs|SelectCoins allows you to use other inputs, but those inputs will never be fed in the normal Available->Select flow
267 2018-02-12 20:32:41	0|provoostenator|Gotta love Stack Overflow... "Here's one million ways to fix gdb on OSX...." "Oh by the way, you can use lldb"
268 2018-02-12 20:37:03	0|bitcoin-git|[13bitcoin] 15droark opened pull request #12417: [WIP] Delete mac_alias patch (06master...06master_del_mac_alias) 02https://github.com/bitcoin/bitcoin/pull/12417
269 2018-02-12 22:22:21	0|n1bor|@murrayn how much RAM do you have? I have seen this sort of performance with 4Gig or less of RAM. Put in 8-12 Gig and same machine was 10x faster.
270 2018-02-12 22:23:17	0|n1bor|ibd hate to be short of RAM. I think the filesystem cache needs it for leveldb reads?
271 2018-02-12 22:25:17	0|bitcoin-git|13bitcoin/06master 14f40df29 15practicalswift: Fix Windows build errors introduced in #10498...
272 2018-02-12 22:25:17	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/5dc00f68c49c...c997f8808256
273 2018-02-12 22:25:18	0|bitcoin-git|13bitcoin/06master 14c997f88 15MarcoFalke: Merge #12416: Fix Windows build errors introduced in #10498...
274 2018-02-12 22:26:19	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #12416: Fix Windows build errors introduced in #10498 (06master...06fix-windows-build) 02https://github.com/bitcoin/bitcoin/pull/12416
275 2018-02-12 23:32:53	0|BlueMatt|ugh, duh
276 2018-02-12 23:33:01	0|BlueMatt|cfields: see https://github.com/bitcoin/bitcoin/pull/12349#issuecomment-365095741
277 2018-02-12 23:33:56	0|BlueMatt|#12367 only fixed the issue for non-reindex cases (ie where LoadChainTip gets called)...any other cases will simply happily initialize pcoinsTip on top of an empty chainstate and then expect to have genesis loaded in the ThreadImport
278 2018-02-12 23:33:58	0|gribble|https://github.com/bitcoin/bitcoin/issues/12367 | Fix two fast-shutdown bugs by TheBlueMatt · Pull Request #12367 · bitcoin/bitcoin · GitHub
279 2018-02-12 23:34:58	0|cfields|grr
280 2018-02-12 23:36:06	0|BlueMatt|we could revert to the initial suggestion of #12349 and just short-circuit flushing, but I really hate that
281 2018-02-12 23:36:07	0|gribble|https://github.com/bitcoin/bitcoin/issues/12349 | shutdown: fix crash on shutdown with reindex-chainstate by theuni · Pull Request #12349 · bitcoin/bitcoin · GitHub
282 2018-02-12 23:36:15	0|BlueMatt|would rather be smarter and not call FlushStateToDisk somehow
283 2018-02-12 23:37:12	0|cfields|BlueMatt: yes, I don't like that either. It was really only intended to jump of discussion about where to fix it for real.
284 2018-02-12 23:37:26	0|cfields|*jump off
285 2018-02-12 23:37:34	0|BlueMatt|I mean looking at the issue I dont really see a way to fix it that I like to begin with :(
286 2018-02-12 23:37:47	0|BlueMatt|but should slip it into the next rc :(
287 2018-02-12 23:37:47	0|cfields|same, hence the punt :p
288 2018-02-12 23:38:00	0|BlueMatt|well I liked my earlier fix...that didnt actually fix it :/
289 2018-02-12 23:39:01	0|BlueMatt|I mean the other obvious option is to make it explicit - have some static in validation.cpp/CChainState that just means "ive gotten as far as loading the genesis block, I can flush now"
290 2018-02-12 23:39:39	0|cfields|right
291 2018-02-12 23:39:47	0|cfields|and don't we already have that, in some form?
292 2018-02-12 23:40:21	0|BlueMatt|not afaik.....I mean we just explicitly refuse to finish loading until we've gotten that far
293 2018-02-12 23:41:24	0|BlueMatt|Ive gotta run, but I'd say just do something in CChainState that gets set to true the first time we do a DisconnectBlock or ConnectBlock, and refuse to flush until then?
294 2018-02-12 23:41:37	0|BlueMatt|should fix the bug without hiding a hack in utxo flushing
295 2018-02-12 23:41:41	0|cfields|fHaveGenesis... ?
296 2018-02-12 23:42:00	0|BlueMatt|fHaveLoadedGenesis
297 2018-02-12 23:42:01	0|BlueMatt|sure
298 2018-02-12 23:42:12	0|BlueMatt|set either in LoadChainTip
299 2018-02-12 23:42:16	0|BlueMatt|or ConnectBlock
300 2018-02-12 23:42:17	0|BlueMatt|I think
301 2018-02-12 23:42:25	0|cfields|no i mean, look in init.cpp
302 2018-02-12 23:42:46	0|BlueMatt|yea, I know
303 2018-02-12 23:42:58	0|BlueMatt|it feels cleaner to duplicate it inside CChainState
304 2018-02-12 23:43:04	0|BlueMatt|so that its clearly a validation thing
305 2018-02-12 23:43:10	0|BlueMatt|instead of yet more global pollution
306 2018-02-12 23:43:26	0|BlueMatt|fHaveGenesis can continue to sit in init as a block-on-me-before-continuing
307 2018-02-12 23:43:58	0|BlueMatt|@eklitzke gets the credit for discovery, btw
308 2018-02-12 23:44:35	0|cfields|looking, cya