1 2017-04-25 01:32:39	0|bitcoin-git|[13bitcoin] 15fanquake opened pull request #10270: Remove Clang workaround for Boost 1.46 (06master...06remove-boost-clang-workaround) 02https://github.com/bitcoin/bitcoin/pull/10270
  2 2017-04-25 01:40:35	0|bitcoin-git|[13bitcoin] 15fanquake opened pull request #10271: Use std::thread::hardware_concurrency, instead of Boost, to determine available cores (06master...06replace-boost-getnumcores) 02https://github.com/bitcoin/bitcoin/pull/10271
  3 2017-04-25 06:49:45	0|bitcoin-git|[13bitcoin] 15paveljanik opened pull request #10272: [Tests] Prevent warning: variable 'x' is uninitialized (06master...0620170425_FastRandomContext_test_warnings) 02https://github.com/bitcoin/bitcoin/pull/10272
  4 2017-04-25 07:39:28	0|bitcoin-git|13bitcoin/06master 145ec8836 15Pavel Janík: Prevent warning: variable 'x' is uninitialized
  5 2017-04-25 07:39:28	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/c73af5416b66...54e2d87e792f
  6 2017-04-25 07:39:29	0|bitcoin-git|13bitcoin/06master 1454e2d87 15Wladimir J. van der Laan: Merge #10272: [Tests] Prevent warning: variable 'x' is uninitialized...
  7 2017-04-25 07:39:53	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10272: [Tests] Prevent warning: variable 'x' is uninitialized (06master...0620170425_FastRandomContext_test_warnings) 02https://github.com/bitcoin/bitcoin/pull/10272
  8 2017-04-25 07:45:35	0|bitcoin-git|[13bitcoin] 15practicalswift closed pull request #10212: Make sure parameter names in .cpp and .h files are in sync (06master...06make-doxygen-happy-by-using-consistent-parameter-names) 02https://github.com/bitcoin/bitcoin/pull/10212
  9 2017-04-25 07:50:26	0|jl2012|are all 127.0.0.1 peers (incoming and outgoing) whitelisted by default?
 10 2017-04-25 07:51:30	0|wumpus|no, absolutely not
 11 2017-04-25 07:51:48	0|wumpus|remember, that's where tor onion connections come from
 12 2017-04-25 07:52:32	0|gmaxwell|jl2012: localhost does not get banned however.
 13 2017-04-25 07:52:41	0|gmaxwell|but it will happily be kicked.
 14 2017-04-25 07:52:49	0|gmaxwell|(also whitelisting implies a bunch of other stuff)
 15 2017-04-25 07:53:26	0|gmaxwell|I wonder if we define a FORCETX message that is only accepted from WL peers if we could get rid of that forced relay behavior...
 16 2017-04-25 07:53:29	0|wumpus|unless someone implements https://github.com/bitcoin/bitcoin/issues/8973 to make onion connections come in on either an alternative port or a unix socket, it's unsafe to whitelist 127.0.0.1 [by default]
 17 2017-04-25 07:53:46	0|wumpus|of course if you're not using tor, yuu can do that
 18 2017-04-25 07:54:02	0|jl2012|i see. I start with  --whitelist=127.0.0.1 --addnode=127.0.0.1:9333 , but in getpeerinfo it says "whitelisted": false,
 19 2017-04-25 07:54:28	0|wumpus|outgoing connections are not whitelisted ever
 20 2017-04-25 07:54:45	0|wumpus|see https://github.com/bitcoin/bitcoin/issues/9923
 21 2017-04-25 07:55:01	0|wumpus|implemented in https://github.com/bitcoin/bitcoin/pull/10051
 22 2017-04-25 07:55:54	0|jl2012|good, thanks!
 23 2017-04-25 08:19:08	0|bitcoin-git|[13bitcoin] 15chrisgavin opened pull request #10273: [scripts] Minor improvements to `macdeployqtplus` script. (06master...06macdeployqtplus) 02https://github.com/bitcoin/bitcoin/pull/10273
 24 2017-04-25 08:51:44	0|bitcoin-git|[13bitcoin] 15ericchong opened pull request #10274: Replace by fee v0.11.2 (06master...06replace-by-fee-v0.11.2) 02https://github.com/bitcoin/bitcoin/pull/10274
 25 2017-04-25 08:53:52	0|bitcoin-git|[13bitcoin] 15kallewoof opened pull request #10275: [rpc] Allow fetching tx directly from specified block in getrawtransaction (06master...06gettx-with-blockhash) 02https://github.com/bitcoin/bitcoin/pull/10275
 26 2017-04-25 10:04:00	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10274: Replace by fee v0.11.2 (06master...06replace-by-fee-v0.11.2) 02https://github.com/bitcoin/bitcoin/pull/10274
 27 2017-04-25 10:05:29	0|bitcoin-git|13bitcoin/06master 1493dbb15 15fanquake: Remove Clang workaround for Boost 1.46
 28 2017-04-25 10:05:29	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/54e2d87e792f...95f5e4407502
 29 2017-04-25 10:05:30	0|bitcoin-git|13bitcoin/06master 1495f5e44 15Wladimir J. van der Laan: Merge #10270: Remove Clang workaround for Boost 1.46...
 30 2017-04-25 10:05:54	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10270: Remove Clang workaround for Boost 1.46 (06master...06remove-boost-clang-workaround) 02https://github.com/bitcoin/bitcoin/pull/10270
 31 2017-04-25 11:03:26	0|bitcoin-git|[13bitcoin] 15knocte opened pull request #10276: contrib/verifybinaries: allow filtering by platform (06master...06filterByPlatformInVerifySh) 02https://github.com/bitcoin/bitcoin/pull/10276
 32 2017-04-25 11:28:50	0|bitcoin-git|13bitcoin/06master 1494807be 15CryptAxe: Trivial: fix fee estimate write error log message
 33 2017-04-25 11:28:50	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/95f5e4407502...cb007e4346cf
 34 2017-04-25 11:28:51	0|bitcoin-git|13bitcoin/06master 14cb007e4 15Wladimir J. van der Laan: Merge #10263: Trivial: fix fee estimate write error log message...
 35 2017-04-25 11:29:09	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10263: Trivial: fix fee estimate write error log message (06master...06coinbase) 02https://github.com/bitcoin/bitcoin/pull/10263
 36 2017-04-25 12:47:24	0|wumpus|disconnect_ban.py              | ✓ Passed  | 908 s
 37 2017-04-25 12:47:24	0|wumpus|here this test is *much* slower than all of the others (runner-up is p2p-fullblocktest with 187s)
 38 2017-04-25 12:47:30	0|wumpus|anyone else experiencing that?
 39 2017-04-25 13:35:41	0|jnewbery|wumpus - I think I see the problem. https://github.com/bitcoin/bitcoin/blob/master/test/functional/disconnect_ban.py#L67
 40 2017-04-25 13:36:20	0|jnewbery|I shouldn't have added that line until #10234 was merged
 41 2017-04-25 13:36:21	0|gribble|https://github.com/bitcoin/bitcoin/issues/10234 | [net] listbanned RPC and QT should show correct banned subnets by jnewbery · Pull Request #10234 · bitcoin/bitcoin · GitHub
 42 2017-04-25 13:38:08	0|wumpus|jnewbery: ok in that case it makes sense to aim for #10234 to be merged instead of work on a workaround, thanks
 43 2017-04-25 13:38:10	0|gribble|https://github.com/bitcoin/bitcoin/issues/10234 | [net] listbanned RPC and QT should show correct banned subnets by jnewbery · Pull Request #10234 · bitcoin/bitcoin · GitHub
 44 2017-04-25 14:04:52	0|bitcoin-git|13bitcoin/06master 14c36ea69 15Karl-Johan Alm: [wallet] Make sure pindex is non-null before possibly referencing in LogPrintf call.
 45 2017-04-25 14:04:52	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/cb007e4346cf...c29a0d48129d
 46 2017-04-25 14:04:53	0|bitcoin-git|13bitcoin/06master 14c29a0d4 15Wladimir J. van der Laan: Merge #10265: [wallet] [moveonly] Check non-null pindex before potentially referencing...
 47 2017-04-25 14:05:20	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10265: [wallet] [moveonly] Check non-null pindex before potentially referencing (06master...06fix-check-pindex-scanforwallettx) 02https://github.com/bitcoin/bitcoin/pull/10265
 48 2017-04-25 14:14:00	0|bitcoin-git|13bitcoin/06master 14ed60970 15Karl-Johan Alm: [test] Test abortrescan command.
 49 2017-04-25 14:14:00	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/c29a0d48129d...e0a7e1994e6f
 50 2017-04-25 14:14:01	0|bitcoin-git|13bitcoin/06master 14e0a7e19 15Wladimir J. van der Laan: Merge #10225: [test] Add aborttrescan tests...
 51 2017-04-25 14:14:24	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10225: [test] Add aborttrescan tests (06master...06abort-rescan-tests) 02https://github.com/bitcoin/bitcoin/pull/10225
 52 2017-04-25 14:18:49	0|bitcoin-git|[13bitcoin] 15mm-s opened pull request #10277: Improved efficiency in constructors of COutPoint (06master...06master) 02https://github.com/bitcoin/bitcoin/pull/10277
 53 2017-04-25 14:24:27	0|cfields|jnewbery: too late to second the request having GetBanned call SweepBanned there? I think that's the right thing to do
 54 2017-04-25 14:28:40	0|bitcoin-git|[13bitcoin] 15jimmysong opened pull request #10278: [test] Add Unit Test for GetListenPort (06master...06test_listenport) 02https://github.com/bitcoin/bitcoin/pull/10278
 55 2017-04-25 14:29:18	0|wumpus|cfields: jnewbery had already agreed with that, just he still had some concern: https://github.com/bitcoin/bitcoin/pull/10234#issuecomment-295354958
 56 2017-04-25 14:31:08	0|cfields|wumpus: right, I just didn't want to set him back since I didn't follow-up then. Will respond there now.
 57 2017-04-25 14:31:27	0|jnewbery|ok, thanks cfields. Not too late to change this
 58 2017-04-25 14:57:48	0|wumpus|never too late
 59 2017-04-25 15:01:03	0|BlueMatt|for those who follow fibre, rebased on 0.14.1 with two small bug fixes and local device support: https://github.com/bitcoinfibre/bitcoinfibre/releases/tag/v0.14.1-fibre0.7
 60 2017-04-25 15:08:19	0|wumpus|nice
 61 2017-04-25 15:08:44	0|BlueMatt|(ie you can write to a named pipe)
 62 2017-04-25 15:08:47	0|BlueMatt|or read
 63 2017-04-25 15:11:53	0|sipa|BlueMatt: finally support for rfc 1149
 64 2017-04-25 15:12:36	0|BlueMatt|well you can already do that, but now we support FIBREoAC directly, no need for the pesky overhead of IP
 65 2017-04-25 15:14:27	0|sipa|well with P2P over IP over avian carrier you'd get ping timeouts
 66 2017-04-25 15:15:14	0|BlueMatt|ah, suppose you would via native FIBRE as well, indeed, i guess you need the local device support either way
 67 2017-04-25 16:41:22	0|cfields|sipa: probably more efficient for the avian carriers to tweet.
 68 2017-04-25 19:03:22	0|sipa|benchmarking libsecp256k1 signature validation, there is hardly any advantage for using hyperthreading cores
 69 2017-04-25 19:06:24	0|sipa|that doesn't mean there is no advantage for HT cores in bitcoin block validation, as ECDSA verification isn't the only thing involved
 70 2017-04-25 19:09:09	0|gmaxwell|sipa: what are you benchmarking on? because I saw non-trivial advantages before.
 71 2017-04-25 19:09:23	0|sipa|laptop, which is thermally throttled
 72 2017-04-25 19:09:41	0|sipa|though the effect is immediate
 73 2017-04-25 19:10:11	0|gmaxwell|wait you said hardly, how little is hardly. I would call 3% a lot.
 74 2017-04-25 19:10:46	0|sipa|oh, i would call 50% a lot
 75 2017-04-25 19:10:53	0|sipa|it's more like 5% benefit
 76 2017-04-25 19:13:31	0|gmaxwell|I'm doubtful 50% is really possible even with memory latency bound workloads, you'll bottleneck the instruction decoder.
 77 2017-04-25 19:27:00	0|BlueMatt|gmaxwell: lol, fucking x86 and its instruction decompressor
 78 2017-04-25 19:27:23	0|gmaxwell|BlueMatt: you mean icache expander. :P
 79 2017-04-25 19:27:34	0|gmaxwell|Cache doubler technology.
 80 2017-04-25 19:27:37	0|BlueMatt|lol
 81 2017-04-25 19:27:40	0|BlueMatt|yea
 82 2017-04-25 19:28:02	0|BlueMatt|I'm surprised their marketing material doesnt refer to x86 as "effecient instruction stream compression to double cache performance"
 83 2017-04-25 19:28:29	0|gmaxwell|IIRC one of the extensions for riscv is an explicit instruction stream compression.
 84 2017-04-25 19:28:34	0|BlueMatt|lol
 85 2017-04-25 19:49:00	0|ryan-c|I told bitcoind 0.14.0 to shutdown via bitcoin-cli over four hours ago, and it's still running. strace shows it waiting on a futex call. Is there anything I should do before sending it a kill -9? The system is not low on memory.
 86 2017-04-25 19:52:30	0|BlueMatt|ryan-c: a gdb "thread apply all bt" would be nice
 87 2017-04-25 19:52:45	0|ryan-c|BlueMatt: Can you walk me through that?
 88 2017-04-25 19:52:57	0|ryan-c|installing gdb one sec
 89 2017-04-25 19:53:14	0|BlueMatt|ryan-c: do you have a copy of the binary you are running (and does it have debug symbols)?
 90 2017-04-25 19:53:28	0|BlueMatt|if not, just kill -9, not much to be had
 91 2017-04-25 19:54:03	0|ryan-c|BlueMatt: It's the binary release from bitcoin.org, sha256sum 860a046514961aeead8b640f1a321da8eb575d727fd8c37de5a4cee5908bbd9d
 92 2017-04-25 19:54:27	0|ryan-c|`file` says the binary is stripped
 93 2017-04-25 19:56:30	0|ryan-c|waiting to for you to confirm there's nothing useful to dump before killing it
 94 2017-04-25 19:56:35	0|gmaxwell|ryan-c: 0.14.0? are you using addnode?
 95 2017-04-25 19:56:44	0|BlueMatt|ohoh, .1, duh
 96 2017-04-25 19:56:44	0|ryan-c|gmaxwell: yes, i am using addnode
 97 2017-04-25 19:56:47	0|BlueMatt|yea, kill -9
 98 2017-04-25 19:56:51	0|BlueMatt|known issue, fixed in .1
 99 2017-04-25 19:56:53	0|gmaxwell|ryan-c: known issue, run 0.14.1
100 2017-04-25 19:57:09	0|gmaxwell|If you have more than 8 addnode peers it can get stuck in shutdowin in 0.14.0
101 2017-04-25 19:57:11	0|ryan-c|gmaxwell: okay, cool thanks - I was shutting it down to replace with 0.14.1
102 2017-04-25 19:57:14	0|gmaxwell|it's harmless to kill it.
103 2017-04-25 19:57:24	0|gmaxwell|Sorry about that.
104 2017-04-25 19:57:31	0|BlueMatt|can we close #10209 now that we fixed the "regenerate bitcoin-config.h" issue and #10210 now that #10215 is merged?
105 2017-04-25 19:57:32	0|gribble|https://github.com/bitcoin/bitcoin/issues/10209 | Stalled shutdown · Issue #10209 · bitcoin/bitcoin · GitHub
106 2017-04-25 19:57:33	0|gribble|https://github.com/bitcoin/bitcoin/issues/10210 | Frozen (for 15 minutes) on shutdown · Issue #10210 · bitcoin/bitcoin · GitHub
107 2017-04-25 19:57:34	0|gribble|https://github.com/bitcoin/bitcoin/issues/10215 | Check interruptNet during dnsseed lookups by TheBlueMatt · Pull Request #10215 · bitcoin/bitcoin · GitHub
108 2017-04-25 19:59:03	0|ryan-c|I'm not getting peers automatically from my testnet node
109 2017-04-25 19:59:15	0|ryan-c|last time i ended up manually running
110 2017-04-25 19:59:39	0|ryan-c|host testnet-seed.bitcoin.jonasschnelli.ch | grep ' has address ' | awk '{print$4}' | xargs -n1 -I IP bitcoin-cli -testnet addnode IP add
111 2017-04-25 19:59:43	0|ryan-c|to get it online
112 2017-04-25 19:59:52	0|ryan-c|is there something else I should do instead?
113 2017-04-25 20:00:36	0|jonasschnelli|testnet-seed.bitcoin.jonasschnelli.ch should be up and running... do you use tor?
114 2017-04-25 20:00:57	0|ryan-c|I do not use tor.
115 2017-04-25 20:01:08	0|jonasschnelli|Hmm.. maybe pastebin your debug.log
116 2017-04-25 20:01:27	0|jonasschnelli|You should see what seeders where asked to retrieve addrs.
117 2017-04-25 20:01:43	0|ryan-c|jonasschnelli: it's like 10MB, wanna give me something to grep for?
118 2017-04-25 20:01:54	0|jonasschnelli|let me look...
119 2017-04-25 20:02:42	0|jonasschnelli|Maybe check for "DNS seeds"
120 2017-04-25 20:03:00	0|ryan-c|I have a message that DNS seeding is disabled
121 2017-04-25 20:03:19	0|ryan-c|oh
122 2017-04-25 20:03:51	0|ryan-c|Okay, well that's probably because for not-testnet I've got peers explicitly configred via connect=
123 2017-04-25 20:05:21	0|ryan-c|starting with -forcednsseed should resolve?
124 2017-04-25 20:05:49	0|jonasschnelli|Ah.. yes. connect= will bypass seeders.
125 2017-04-25 20:05:58	0|BlueMatt|just addnode a few public seeds
126 2017-04-25 20:06:03	0|BlueMatt|testnet is usually otherwise broken
127 2017-04-25 20:06:51	0|ryan-c|-forcednsseed does not fix it
128 2017-04-25 20:07:50	0|ryan-c|-forcednsseed -dnsseed gives me the message '130 addresses found from DNS seeds', but i'm not seeing it actually connect
129 2017-04-25 20:08:53	0|gmaxwell|ryan-c: I'm confused by your comments, if you use connect you won't automatically connect to anyone else.
130 2017-04-25 20:09:19	0|ryan-c|gmaxwell: It won't automatically connect to anyone else even if I manually enable dnsseed?
131 2017-04-25 20:09:40	0|gmaxwell|ryan-c: -connect's purpose is to disable automatic connection generation completely.
132 2017-04-25 20:10:53	0|ryan-c|ah
133 2017-04-25 23:09:32	0|sipa|gmaxwell: better benchmark with fixed CPU frequency now, it's more like 14% faster with 8 threads in parallel than 4
134 2017-04-25 23:09:55	0|sipa|(secp256k1 only, so no memory effects)