1 2016-06-01 05:20:37 0|iniana|phantomcircuit, gmaxwell: Tried synching from scratch in a clean dir, but it is just as slow. I am wondering if it has something to do with the fact that I am running it in a Qubes AppVM. Funny thing is I was synching another (pruned) node from scratch in a whonix (tor-only) VM, and it went unexpectedly fast. Though that VM had the blockchain stored on an SSD.
2 2016-06-01 05:22:00 0|gmaxwell|iniana: syncing from scratch with your dbcache increased?
3 2016-06-01 05:22:51 0|iniana|gmaxwell: yes, lowered it from 4k to 2k when I realized I only had 4G of memory assigned to the VM
4 2016-06-01 05:23:17 0|iniana|the tor VM had default dbcache
5 2016-06-01 05:24:38 0|gmaxwell|with a dbcache of 2000 its unlikely that your slowness is related to disk io... but perhaps the vm is just doing something awful.
6 2016-06-01 05:25:57 0|iniana|gmaxwell: yeah, will try the fedora-based VM instead of Debian and see if that makes a difference
7 2016-06-01 12:03:27 0|tbear|If a bitcoin transaction is stuck from low payout fee like .0000012 how long should I wait before doing something plz? been 3 days thx
8 2016-06-01 12:04:35 0|tbear|hi lowest payouts should be where transaction doesn't get stuck
9 2016-06-01 12:04:39 0|tbear|If a bitcoin transaction is stuck from low payout fee like .0000012 how long should I wait before doing something plz? been 3 days thx
10 2016-06-01 12:07:00 0|instagibbs|tbear, #bitcoin is a better venue for this question
11 2016-06-01 12:07:24 0|tbear|thx nobody replied
12 2016-06-01 12:07:39 0|instagibbs|well it's off-topic here sorry
13 2016-06-01 12:07:47 0|tbear|lowest payouts should be where transaction doesn't get stuck
14 2016-06-01 12:08:13 0|tbear|ok thx bye geese
15 2016-06-01 12:24:49 0|instagibbs|I am not a gaggle of geese
16 2016-06-01 13:38:57 0|GitHub92|13bitcoin/06master 14e4f73c7 15fanquake: [Doc] Update implemented BIPs list
17 2016-06-01 13:38:57 0|GitHub92|[13bitcoin] 15sipa pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/862fd24b40b4...58f0c929a3d7
18 2016-06-01 13:38:58 0|GitHub92|13bitcoin/06master 1458f0c92 15Pieter Wuille: Merge #8121: [Doc] Update implemented BIPs list...
19 2016-06-01 13:39:07 0|GitHub78|[13bitcoin] 15sipa closed pull request #8121: [Doc] Update implemented BIPs list (06master...06missing_bips) 02https://github.com/bitcoin/bitcoin/pull/8121
20 2016-06-01 14:05:42 0|GitHub3|13bitcoin/06master 144d8993b 15Gregory Maxwell: Defer inserting into maprelay until just before relaying....
21 2016-06-01 14:05:42 0|GitHub3|[13bitcoin] 15sipa pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/58f0c929a3d7...01d8359983e2
22 2016-06-01 14:05:43 0|GitHub3|13bitcoin/06master 1401d8359 15Pieter Wuille: Merge #8082: Defer inserting into maprelay until just before relaying....
23 2016-06-01 14:05:52 0|GitHub19|[13bitcoin] 15sipa closed pull request #8082: Defer inserting into maprelay until just before relaying. (06master...06just_in_time_maprelay) 02https://github.com/bitcoin/bitcoin/pull/8082
24 2016-06-01 16:23:05 0|GitHub68|[13bitcoin] 15sipa pushed 13 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/01d8359983e2...b89ef131147f
25 2016-06-01 16:23:06 0|GitHub68|13bitcoin/06master 14a545127 15Pieter Wuille: Squashed 'src/crypto/ctaes/' content from commit cd3c3ac...
26 2016-06-01 16:23:06 0|GitHub68|13bitcoin/06master 14cd2be44 15Pieter Wuille: Merge commit 'a545127fbccef4ee674d18d43732ce00ba97f782' as 'src/crypto/ctaes'
27 2016-06-01 16:23:07 0|GitHub164|[13bitcoin] 15sipa closed pull request #7689: Replace OpenSSL AES with ctaes-based version (06master...06const_aes) 02https://github.com/bitcoin/bitcoin/pull/7689
28 2016-06-01 16:23:07 0|GitHub68|13bitcoin/06master 146bec172 15Pieter Wuille: Add ctaes-based constant time AES implementation
29 2016-06-01 16:36:35 0|GitHub44|13bitcoin/06master 14383fc10 15Suhas Daftuar: Only use AddInventoryKnown for transactions...
30 2016-06-01 16:36:35 0|GitHub44|[13bitcoin] 15sipa pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/b89ef131147f...6a22373771ed
31 2016-06-01 16:36:36 0|GitHub44|13bitcoin/06master 146a22373 15Pieter Wuille: Merge #7960: Only use AddInventoryKnown for transactions...
32 2016-06-01 16:36:40 0|GitHub91|[13bitcoin] 15sipa closed pull request #7960: Only use AddInventoryKnown for transactions (06master...06block-inv-filter) 02https://github.com/bitcoin/bitcoin/pull/7960
33 2016-06-01 16:38:18 0|gmaxwell|sipa: now that ctaes is in, are we only left the RNG stopping the removal of openssl in bitcoind?
34 2016-06-01 16:38:45 0|sipa|yes
35 2016-06-01 16:39:57 0|gmaxwell|next step in that would be getting in a seeder, I guess.
36 2016-06-01 16:48:05 0|GitHub178|13bitcoin/06master 1488f14b9 15Pieter Wuille: Include signal.h for sig_atomic_t in WIN32
37 2016-06-01 16:48:05 0|GitHub178|[13bitcoin] 15sipa pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/6a22373771ed...7fa8d7585984
38 2016-06-01 16:48:06 0|GitHub178|13bitcoin/06master 147fa8d75 15Pieter Wuille: Merge #8112: Include signal.h for sig_atomic_t in WIN32...
39 2016-06-01 17:41:02 0|GitHub5|[13bitcoin] 15kazcw closed pull request #8052: rpc tests: increase http timeout (06master...06rpcwallet-test-timeout) 02https://github.com/bitcoin/bitcoin/pull/8052
40 2016-06-01 17:46:01 0|luke-jr|cfields_: https://github.com/bitcoin/bips/pull/365#issuecomment-219181320
41 2016-06-01 17:46:50 0|cfields_|luke-jr: thanks, will take a look. Pretty sure I'm happy now though.
42 2016-06-01 17:57:48 0|sipa|luke-jr: why are you excess flood'ing all the time? :)
43 2016-06-01 18:00:38 0|luke-jr|sipa: TCP packet gets lost, waits for re-xmit, freenode reassembles that packet + the packets following it and decides it's too much "at once"
44 2016-06-01 18:00:40 0|luke-jr|makes me wonder if I should just hack my router to send all TCP packets twice
45 2016-06-01 18:00:51 0|luke-jr|looks like i have ~20% packet loss over IPv6 only at the moment :/
46 2016-06-01 18:04:53 0|sipa|ouch
47 2016-06-01 18:08:53 0|midnightmagic|You finally solved that problem?
48 2016-06-01 18:10:14 0|luke-jr|midnightmagic: solved what?
49 2016-06-01 18:12:32 0|jonasschnelli|sipa: can you explain: https://github.com/bitcoin/bitcoin/pull/8035/commits/f19025106de47a92396f9fb98e6d3bbc568c40b5#r65400352?
50 2016-06-01 18:13:38 0|sipa|jonasschnelli: ask instagibbs
51 2016-06-01 18:14:15 0|jonasschnelli|sipa: you mean why AddKeyPubKey instead of AddKey?
52 2016-06-01 18:14:23 0|sipa|jonasschnelli: yes
53 2016-06-01 18:15:00 0|jonasschnelli|sipa: Yes. Should also be possible. :)
54 2016-06-01 18:15:42 0|jonasschnelli|AddKeyPubKey is virtual so,... yes. Let me change this
55 2016-06-01 18:15:55 0|sipa|AddKey is also virtual
56 2016-06-01 18:16:48 0|jonasschnelli|sipa: wait. There is a reason for AddKeyPubKey
57 2016-06-01 18:16:55 0|jonasschnelli|https://github.com/bitcoin/bitcoin/pull/8035/commits/f19025106de47a92396f9fb98e6d3bbc568c40b5#diff-b2bb174788c7409b671c46ccc86034bdR1106
58 2016-06-01 18:17:19 0|jonasschnelli|CKey.GetPubKey() does not cache
59 2016-06-01 18:17:42 0|sipa|updated my comment, thanks :)
60 2016-06-01 18:19:05 0|jonasschnelli|sipa: "Agree about adding a named constant." -> do you mean using a constant for 0x80000000?
61 2016-06-01 18:19:11 0|sipa|yes
62 2016-06-01 18:19:57 0|jonasschnelli|sipa: Or i could use the same style you used in key.cpp (if ((nChild >> 31) == 0) {)
63 2016-06-01 18:20:28 0|jonasschnelli|though, I'm in favor of | 0x80000000
64 2016-06-01 18:20:36 0|sipa|a named constant is most readable :)
65 2016-06-01 18:20:41 0|instagibbs|oh that comment was quite a while ago, but i was wrong, I distinctly remember :)
66 2016-06-01 18:21:11 0|jonasschnelli|instagibbs: you where right... but you where wrong saying you where wrong. :)
67 2016-06-01 18:22:35 0|instagibbs|oh yeah, I think sipa had it right
68 2016-06-01 18:25:48 0|midnightmagic|luke-jr: or at least analyzed it. the constant excess flooding
69 2016-06-01 18:27:00 0|luke-jr|midnightmagic: it's mostly an educated guess right now
70 2016-06-01 18:29:24 0|midnightmagic|the retransmit period should be fast enough to handle one or two missing packets occasionally
71 2016-06-01 18:39:03 0|GitHub165|[13bitcoin] 15sipa pushed 3 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/7fa8d7585984...2e0a99037dcc
72 2016-06-01 18:39:04 0|GitHub165|13bitcoin/06master 1416cf85f 15Pieter Wuille: Revert "Include signal.h for sig_atomic_t in WIN32"...
73 2016-06-01 18:39:04 0|GitHub165|13bitcoin/06master 14a886dbf 15Pieter Wuille: Use std::atomic for fRequestShutdown and fReopenDebugLog
74 2016-06-01 18:39:05 0|GitHub165|13bitcoin/06master 142e0a990 15Pieter Wuille: Merge #8123: Use std::atomic for fRequestShutdown and fReopenDebugLog...
75 2016-06-01 18:39:18 0|GitHub26|[13bitcoin] 15sipa closed pull request #8123: Use std::atomic for fRequestShutdown and fReopenDebugLog (06master...06notsigbutatomic) 02https://github.com/bitcoin/bitcoin/pull/8123
76 2016-06-01 18:52:47 0|GitHub116|13bitcoin/06master 14ee9f4a5 15Jorge Timón: Consensus: Decouple from chainparams.o and timedata.o...
77 2016-06-01 18:52:47 0|GitHub116|[13bitcoin] 15sipa pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/2e0a99037dcc...715e9fd7454f
78 2016-06-01 18:52:48 0|GitHub116|13bitcoin/06master 14715e9fd 15Pieter Wuille: Merge #8077: Consensus: Decouple from chainparams.o and timedata.o...
79 2016-06-01 18:52:57 0|GitHub45|[13bitcoin] 15sipa closed pull request #8077: Consensus: Decouple from chainparams.o and timedata.o (06master...060.12-consensus-chainparams) 02https://github.com/bitcoin/bitcoin/pull/8077
80 2016-06-01 19:29:15 0|GitHub127|[13bitcoin] 15MarcoFalke closed pull request #7947: Global params cleanup (06master...06global-params-cleanup) 02https://github.com/bitcoin/bitcoin/pull/7947
81 2016-06-01 19:32:41 0|GitHub109|[13bitcoin] 15luke-jr opened pull request #8132: wallet: Add key generation type (06master...06keygentype) 02https://github.com/bitcoin/bitcoin/pull/8132
82 2016-06-01 19:33:06 0|GitHub27|[13bitcoin] 15MarcoFalke closed pull request #7985: [Consensus] Add nAdjustedTime parameter to CheckBlock and CheckBlockHeader. (06master...062016-05-01-checkblock-header) 02https://github.com/bitcoin/bitcoin/pull/7985
83 2016-06-01 21:27:41 0|gmaxwell|Whats the minimum ubuntu release to build master with now (with the C++11 requirement)
84 2016-06-01 21:30:09 0|sipa|14.04 lts works
85 2016-06-01 21:31:05 0|gmaxwell|Does 13 not work?
86 2016-06-01 21:31:20 0|sipa|it may, but i don't see a way to search its repository
87 2016-06-01 21:33:32 0|sipa|precise (12.04) has gcc 4.7
88 2016-06-01 21:33:49 0|sipa|i think we use features from 4.8 though
89 2016-06-01 21:35:20 0|gmaxwell|it looks like our test doesn't work with 4.7. So 12.x is no, 14.x is yes. And 13 is dunno.
90 2016-06-01 21:35:20 0|sipa|maybe not
91 2016-06-01 21:35:38 0|sipa|well 13 is not supported anymore
92 2016-06-01 21:35:54 0|sipa|12.04 and 14.04 are
93 2016-06-01 21:35:59 0|btcdrak|petrov is having dependency issues, not sure which version of Ubuntu
94 2016-06-01 21:36:19 0|btcdrak|https://www.irccloud.com/pastebin/eDUdpJen/
95 2016-06-01 21:37:02 0|sipa|maybe the configure test is too strong
96 2016-06-01 21:37:18 0|sipa|because it tests for full c++11 language support
97 2016-06-01 21:37:38 0|sipa|but the only thing we may be using in 4.8 is inheriting constructors
98 2016-06-01 21:38:16 0|sipa|i don't think we use thread local storage yet
99 2016-06-01 21:39:35 0|sipa|so i think 4.7 may work, if we'd disable the test
100 2016-06-01 21:40:17 0|btcdrak|cfields_: ping ^
101 2016-06-01 21:40:59 0|cfields_|i believe 4.7 was missing a few pretty major things. atomics, maybe?
102 2016-06-01 21:41:15 0|btcdrak|ok so he needs gcc 4.8 in that case.
103 2016-06-01 21:41:31 0|cfields_|don't quote me on that. checking.
104 2016-06-01 21:42:00 0|sipa|some tweaks to the memory model were made in 4.8 still
105 2016-06-01 21:42:26 0|sipa|but atomics exist since 4.4
106 2016-06-01 21:42:58 0|cfields_|ah right, thread_local in 4.8
107 2016-06-01 21:45:59 0|cfields_|btcdrak: fwiw, i'm able to compile w/ my ancient raring install. I'm unsure if I grabbed the toolchain from a ppa, or if it exists in-repo
108 2016-06-01 21:46:31 0|cfields_|btcdrak: either way, if gcc-4.8/g++-4.8 are installed, you can just use: ./configure CXX=g++-4.8 CC=gcc-4.8
109 2016-06-01 21:47:13 0|gmaxwell|we may want to write some instructions for users on somewhat older systems.
110 2016-06-01 21:48:36 0|sipa|cfields_: raring is 13.04
111 2016-06-01 21:48:38 0|sipa|right?
112 2016-06-01 21:48:41 0|cfields_|it'd likely be easier to get someone building with clang, since those get backported more often. iirc clang 3.3 is enough.
113 2016-06-01 21:49:33 0|cfields_|sipa: yep. like i said though, i'm unsure if the gcc-4.8 here came from the ubuntu repos. checking.
114 2016-06-01 21:51:07 0|sipa|clang 3.1 is likely even enough, as long as we don't use tls
115 2016-06-01 21:51:37 0|cfields_|haven't we merged some of the tls PRs already?
116 2016-06-01 21:51:43 0|sipa|not afaik
117 2016-06-01 21:52:43 0|cfields_|ah
118 2016-06-01 21:53:28 0|sipa|nope
119 2016-06-01 21:54:51 0|sipa|8007 did, but got changed to using atomics instead
120 2016-06-01 21:55:26 0|cfields_|ah damn, looks like my 4.8 came from a ppa
121 2016-06-01 21:56:42 0|cfields_|I think i'd be uneasy recommending 4.7 though. That'd mean we're walking on eggshells.
122 2016-06-01 21:59:41 0|gmaxwell|I'm much happier with GCC 4.8 in general.
123 2016-06-01 22:42:32 0|gmaxwell|does setban not disconnect newly banned peers?
124 2016-06-01 22:43:47 0|sipa|seems not
125 2016-06-01 22:43:51 0|sipa|but there is disconnectnode
126 2016-06-01 22:44:35 0|gmaxwell|help on disconnect node is not very helpful. the argument is "the node"
127 2016-06-01 22:44:49 0|gmaxwell|like, do I digitize the whole peer and provide it in hex on the commandline? :)
128 2016-06-01 22:46:47 0|gmaxwell|apparently it wants the fully qualified inbound address and port.
129 2016-06-01 23:46:58 0|GitHub51|[13bitcoin] 15theuni opened pull request #8133: build: Finish up out-of-tree changes (06master...06out-of-tree-clean) 02https://github.com/bitcoin/bitcoin/pull/8133