1 2017-05-03 00:48:01	0|Chris_Stewart_5|Has anyone had to deal with using bitcoind as a dependency with travis ci? Is there a way to get them to whitelist it's use in -regtest mode?
  2 2017-05-03 00:50:32	0|sipa|?
  3 2017-05-03 00:50:52	0|sipa|why would it need a whitelist?
  4 2017-05-03 00:52:21	0|Chris_Stewart_5|It looks like travis-ci bans people that use bitcoin as a dependency in .travis.yml
  5 2017-05-03 00:52:29	0|Chris_Stewart_5|https://travis-ci.org/bitcoin-s/bitcoin-s-rpc-client/requests
  6 2017-05-03 00:52:40	0|Chris_Stewart_5|claiming I am mining
  7 2017-05-03 00:52:57	0|sipa|ah, i see
  8 2017-05-03 00:53:10	0|sipa|perhaps if you built bitcoind inside the VM?
  9 2017-05-03 00:53:13	0|Chris_Stewart_5|and now I am a repeat offender :o. I emailed the travis ci people to hopefully get off of the list
 10 2017-05-03 00:53:23	0|sipa|rather than using it as a dependency
 11 2017-05-03 00:53:27	0|sipa|yeah, contact them to explain first
 12 2017-05-03 00:53:29	0|Chris_Stewart_5|I asked if they could whitelist 'bitcoind -regtest'
 13 2017-05-03 00:53:43	0|Chris_Stewart_5|We will see what the response is :/
 14 2017-05-03 00:55:01	0|sipa|bitcoind doesn't even contain a miner anymore
 15 2017-05-03 00:55:12	0|luke-jr|sipa: they banned us too
 16 2017-05-03 00:55:31	0|luke-jr|had to get whitelisted :/
 17 2017-05-03 00:55:41	0|Chris_Stewart_5|luke-jr: How long ago was that?
 18 2017-05-03 00:55:53	0|luke-jr|not sure, a Looooooong time ago
 19 2017-05-03 00:57:19	0|gmaxwell|great so even we're using a service that bans people for running our software. :(
 20 2017-05-03 00:58:52	0|Chris_Stewart_5|yeah, I didn't even just get banned on that repo, it looks like I am banned on all repos :S
 21 2017-05-03 01:22:15	0|bitcoin-git|[13bitcoin] 15sipa opened pull request #10322: Use hardware timestamps in RNG seeding (06master...06rdtsc) 02https://github.com/bitcoin/bitcoin/pull/10322
 22 2017-05-03 01:43:58	0|sipa|gmaxwell: std::random_device in libstdc++ from modern G++ uses rdrand when available, so we could just include that into the seeding
 23 2017-05-03 01:44:28	0|sipa|and /dev/urandom otherwise
 24 2017-05-03 01:44:57	0|sipa|... however, the mingw-64 version just uses a mersenne twister with a constant(!) seed
 25 2017-05-03 02:27:03	0|bitcoin-git|[13bitcoin] 15sipa opened pull request #10323: Update to latest libsecp256k1 master (06master...06secp_up) 02https://github.com/bitcoin/bitcoin/pull/10323
 26 2017-05-03 03:29:55	0|sipa|TIL: C++ template parameters can be (uninstantiated) templates themselves
 27 2017-05-03 03:42:43	0|bitcoin-git|13bitcoin/06master 14db994b2 15Pieter Wuille: Simplify DisconnectBlock arguments/return value...
 28 2017-05-03 03:42:43	0|bitcoin-git|[13bitcoin] 15sipa pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/75171f099e82...431a548faaf5
 29 2017-05-03 03:42:44	0|bitcoin-git|13bitcoin/06master 14431a548 15Pieter Wuille: Merge #10297: Simplify DisconnectBlock arguments/return value...
 30 2017-05-03 03:43:02	0|bitcoin-git|[13bitcoin] 15sipa closed pull request #10297: Simplify DisconnectBlock arguments/return value (06master...06disconnect_enum) 02https://github.com/bitcoin/bitcoin/pull/10297
 31 2017-05-03 06:15:54	0|bitcoin-git|13bitcoin/06master 14bd1f138 15Pieter Wuille: Add getchaintxstats RPC
 32 2017-05-03 06:15:54	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/431a548faaf5...d4732f3232c3
 33 2017-05-03 06:15:55	0|bitcoin-git|13bitcoin/06master 14d4732f3 15Wladimir J. van der Laan: Merge #9733: Add getchaintxstats RPC...
 34 2017-05-03 06:17:42	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #9733: Add getchaintxstats RPC (06master...06chaintxstats) 02https://github.com/bitcoin/bitcoin/pull/9733
 35 2017-05-03 06:47:59	0|bitcoin-git|13bitcoin/06master 14b8251f6 15John Newbery: [tests] allow zmq test to be run in out-of-tree builds
 36 2017-05-03 06:47:59	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/d4732f3232c3...83073de4bdd8
 37 2017-05-03 06:48:00	0|bitcoin-git|13bitcoin/06master 1483073de 15Wladimir J. van der Laan: Merge #10307: [tests] allow zmq test to be run in out-of-tree builds...
 38 2017-05-03 06:48:25	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10307: [tests] allow zmq test to be run in out-of-tree builds (06master...06fix_zmq_test_out_of_tree) 02https://github.com/bitcoin/bitcoin/pull/10307
 39 2017-05-03 07:12:05	0|bitcoin-git|13bitcoin/06master 14185c7f0 15Matt Corallo: Avoid reading the old hd master key during wallet encryption...
 40 2017-05-03 07:12:05	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/83073de4bdd8...d3dce0eb67e8
 41 2017-05-03 07:12:06	0|bitcoin-git|13bitcoin/06master 14d3dce0e 15Wladimir J. van der Laan: Merge #10115: Avoid reading the old hd master key during wallet encryption...
 42 2017-05-03 07:12:25	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10115: Avoid reading the old hd master key during wallet encryption (06master...062017-03-cleanup-sethdmasterkey) 02https://github.com/bitcoin/bitcoin/pull/10115
 43 2017-05-03 08:04:59	0|bitcoin-git|[13bitcoin] 15spencerlievens opened pull request #10324: Add OSX keystroke to clear RPCConsole (06master...06patch-3) 02https://github.com/bitcoin/bitcoin/pull/10324
 44 2017-05-03 09:04:14	0|bitcoin-git|[13bitcoin] 15laanwj pushed 3 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/d3dce0eb67e8...2a183de0ecb5
 45 2017-05-03 09:04:15	0|bitcoin-git|13bitcoin/06master 1491c91e1 15John Newbery: Control mempool persistence using a command line parameter....
 46 2017-05-03 09:04:15	0|bitcoin-git|13bitcoin/06master 14a750d77 15John Newbery: Add tests for mempool persistence...
 47 2017-05-03 09:04:16	0|bitcoin-git|13bitcoin/06master 142a183de 15Wladimir J. van der Laan: Merge #9966: Control mempool persistence using a command line parameter...
 48 2017-05-03 09:04:35	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #9966: Control mempool persistence using a command line parameter (06master...06mempoolpersistenceoption) 02https://github.com/bitcoin/bitcoin/pull/9966
 49 2017-05-03 09:40:55	0|bitcoin-git|13bitcoin/06master 1456f09df 15Spencer Lievens: [Makefile] Alphabetically Reorder addrdb.cpp...
 50 2017-05-03 09:40:55	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/2a183de0ecb5...0912620888e8
 51 2017-05-03 09:40:56	0|bitcoin-git|13bitcoin/06master 140912620 15Wladimir J. van der Laan: Merge #10302: [Makefile] Alphabetically Reorder addrdb.cpp...
 52 2017-05-03 09:41:20	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10302: [Makefile] Alphabetically Reorder addrdb.cpp (06master...06patch-2) 02https://github.com/bitcoin/bitcoin/pull/10302
 53 2017-05-03 09:48:05	0|bitcoin-git|13bitcoin/06master 141ff2bb4 15BtcDrak: Remove unused args from GetFetchhFlags()
 54 2017-05-03 09:48:05	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/0912620888e8...22d870016eb6
 55 2017-05-03 09:48:06	0|bitcoin-git|13bitcoin/06master 1422d8700 15Wladimir J. van der Laan: Merge #10311: Remove unused args from GetFetchFlags()...
 56 2017-05-03 09:48:30	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10311: Remove unused args from GetFetchFlags() (06master...06getflags) 02https://github.com/bitcoin/bitcoin/pull/10311
 57 2017-05-03 10:40:43	0|bitcoin-git|[13bitcoin] 15fanquake opened pull request #10325: 0.15.0 Depends Updates (06master...06depends-0-15-0) 02https://github.com/bitcoin/bitcoin/pull/10325
 58 2017-05-03 13:03:08	0|jtimon|more begging for review on https://github.com/bitcoin/bitcoin/pull/9494
 59 2017-05-03 13:06:25	0|jnewbery|wumpus did you see my comment on #10225? It's causing test runs to fail intermittently for me. Can we revert it until it's had some review?
 60 2017-05-03 13:06:27	0|gribble|https://github.com/bitcoin/bitcoin/issues/10225 | [test] Add aborttrescan tests by kallewoof · Pull Request #10225 · bitcoin/bitcoin · GitHub
 61 2017-05-03 13:07:10	0|wumpus|jnewbery: sure
 62 2017-05-03 13:08:10	0|wumpus|just commenting out the test so it doesn't run automatically would be enough I guess
 63 2017-05-03 13:10:16	0|jnewbery|yes, that would solve the immediate problem, but I'd also like to make sure that the test gets some review. I had a bunch of review comments for the PR which I didn't add because it wasn't even running reliably for me
 64 2017-05-03 13:11:03	0|wumpus|no matter waht, comments must be addressed in a new PR
 65 2017-05-03 13:11:09	0|wumpus|it's not possible to unmerge and reopen a PR
 66 2017-05-03 13:12:13	0|jnewbery|can we do something like: new PR or commit to remove the test entirely, and then PR it again
 67 2017-05-03 13:12:22	0|wumpus|I guess if no one fixes it, we can remove the test again at some point
 68 2017-05-03 13:13:18	0|wumpus|I don't really see how that is better than just disabling the test (so it can still be run manually) then fixing its problems while it's not blocking travis, but okay...
 69 2017-05-03 13:14:11	0|jnewbery|because the test is unreviewed and untested. I think we *should* have the test, I'd just like it to go through a review process before it gets merged :)
 70 2017-05-03 13:18:28	0|bitcoin-git|[13bitcoin] 15jnewbery opened pull request #10327: [tests] remove import-abort-rescan.py (06master...06remove_abort_rescan) 02https://github.com/bitcoin/bitcoin/pull/10327
 71 2017-05-03 13:44:52	0|bitcoin-git|13bitcoin/06master 14981e586 15John Newbery: [tests] remove import-abort-rescan.py...
 72 2017-05-03 13:44:52	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/22d870016eb6...35da2aeed7d4
 73 2017-05-03 13:44:53	0|bitcoin-git|13bitcoin/06master 1435da2ae 15Wladimir J. van der Laan: Merge #10327: [tests] remove import-abort-rescan.py...
 74 2017-05-03 13:45:19	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10327: [tests] remove import-abort-rescan.py (06master...06remove_abort_rescan) 02https://github.com/bitcoin/bitcoin/pull/10327
 75 2017-05-03 14:01:55	0|bitcoin-git|[13bitcoin] 15TheBlueMatt opened pull request #10328: Update contrib/debian to latest Ubuntu PPA upload. (06master...062017-05-update-debian) 02https://github.com/bitcoin/bitcoin/pull/10328
 76 2017-05-03 14:14:41	0|BlueMatt|jonasschnelli: re: qt4: I think we need to just remove our tray icon anyway, at this point?
 77 2017-05-03 14:14:53	0|BlueMatt|then the issues with qt4 should be resolved, I believe?
 78 2017-05-03 14:14:54	0|jonasschnelli|BlueMatt: I think there is an option
 79 2017-05-03 14:15:05	0|jonasschnelli|let me check
 80 2017-05-03 14:15:34	0|jonasschnelli|setTrayIconVisible(optionsModel->getHideTrayIcon());
 81 2017-05-03 14:16:12	0|BlueMatt|can someone close #10326 as "follow up with antpool, we are not antpool support there is nothing we can do"
 82 2017-05-03 14:16:16	0|gribble|https://github.com/bitcoin/bitcoin/issues/10326 | block accepted in solo mining in Antpool and never rewards in the dashboard · Issue #10326 · bitcoin/bitcoin · GitHub
 83 2017-05-03 14:17:05	0|BlueMatt|jonasschnelli: i believe there was previously discussion of just always not having tray icons
 84 2017-05-03 14:17:50	0|jonasschnelli|Yes. Removing the tray makes sense... though, to prevent distraction, we shouldn't hurry. The option was a good start IMO
 85 2017-05-03 14:19:18	0|jonasschnelli|I mean "removing the tray icon".
 86 2017-05-03 14:19:55	0|jonasschnelli|OSX has already deprecated those "global menu icons" since years. Because it looks like that every new application wants to place a icon there and mostly the space is limited to just a handfull.
 87 2017-05-03 14:20:02	0|jonasschnelli|I guess it's similar on Ubuntu/Windows.
 88 2017-05-03 14:20:17	0|jonasschnelli|But all new application ignore these deprecations. :)
 89 2017-05-03 14:20:27	0|jonasschnelli|Dropbox / Adobe / VMWare, etc.
 90 2017-05-03 14:20:42	0|wumpus|ubuntu is going to drop unity anyhow
 91 2017-05-03 14:20:46	0|wumpus|so the problem will go way
 92 2017-05-03 14:21:26	0|jonasschnelli|wumpus: There are no such thing like Tray icons in GNOME?
 93 2017-05-03 14:21:26	0|wumpus|but yes completely removing tray icon functionality would be a possible future thing too
 94 2017-05-03 14:21:36	0|wumpus|jonasschnelli: there are, but that problem shouldn't exist there
 95 2017-05-03 14:21:55	0|wumpus|it's a problem specific to how unity intercepts the tray menu
 96 2017-05-03 14:22:01	0|wumpus|as I understand, at least
 97 2017-05-03 14:22:10	0|jonasschnelli|Okay. Yes. I think as long as users like apps that inject tray icons, we should not hurry with removing the option.
 98 2017-05-03 14:22:17	0|jonasschnelli|We could first set the option to false by default
 99 2017-05-03 14:22:31	0|wumpus|right
100 2017-05-03 14:23:43	0|wumpus|but as I understand it this problem is specific to unity: it doesn't exist on GNOME, nor KDE
101 2017-05-03 14:24:03	0|wumpus|haven't tested, though.
102 2017-05-03 14:24:16	0|jonasschnelli|Yes. I think so.
103 2017-05-03 14:24:29	0|jonasschnelli|BlueMatt: the current PPA is built with Qt4? Right?
104 2017-05-03 14:24:36	0|BlueMatt|yes
105 2017-05-03 14:24:47	0|jonasschnelli|Hmm... what speaks against Qt5?
106 2017-05-03 14:25:11	0|BlueMatt|wumpus: luke-jr was also complaining about qt5 not working with kde4 folks (do people still use kde4...or kde?)
107 2017-05-03 14:26:04	0|jonasschnelli|Yes. But that orthogonal to the PPA.
108 2017-05-03 14:26:36	0|BlueMatt|true, but it is further reason why we need to support Qt4
109 2017-05-03 14:26:52	0|BlueMatt|(is there even a reason to migrate to qt5)
110 2017-05-03 14:26:56	0|BlueMatt|or, quickly migrate, that is
111 2017-05-03 14:28:11	0|wumpus|well, most software moved away from qt4 by now, so requiring qt4 for the ppa pulls that in, and makes the software look different from other things
112 2017-05-03 14:28:36	0|wumpus|this is a different decision than stopping qt4 support anyhow
113 2017-05-03 14:28:44	0|BlueMatt|how do other projects support qt5 on ubuntu? just no tray icons?
114 2017-05-03 14:29:19	0|wumpus|I think so, yes
115 2017-05-03 14:29:32	0|jonasschnelli|I expect much less maintenance on the qt4 branch. Things like HiDPI, etc. which nowadays is also common on Ubuntu is only possible with Qt5.
116 2017-05-03 14:29:38	0|wumpus|software on linux that adds tray icons is kind of rare
117 2017-05-03 14:29:44	0|BlueMatt|lol, why is all software terrible
118 2017-05-03 14:31:05	0|wumpus|the "correct way" to do tray functionality on ubuntu is to register beneath one of the existing (vendor-provided) tray icons in the tray menu. They have an API for this. Of course, given that it's going to disappear it's not worth spending time on that.
119 2017-05-03 14:31:08	0|wumpus|(if it ever was)
120 2017-05-03 14:31:34	0|wumpus|but e.g. some instant messenger and email clients etc do that
121 2017-05-03 14:31:46	0|BlueMatt|ah
122 2017-05-03 14:32:01	0|wumpus|(probably, ubuntu maintains their own patches for that)
123 2017-05-03 14:32:43	0|BlueMatt|<BlueMatt> lol, why is all software terrible
124 2017-05-03 14:33:47	0|wumpus|why is all terrible
125 2017-05-03 14:34:03	0|BlueMatt|fair point
126 2017-05-03 14:49:30	0|luke-jr|BlueMatt: Qt5 doesn't adapt to Qt4, *and vice versa*. KDE 4 is rapidly becoming Windows XP. I think we're okay to drop Qt4 entirely as soon as it becomes a burden, but changing builds to use Qt5 ASAP is a good idea.
127 2017-05-03 14:50:32	0|wumpus|the bitcoin.org builds have been using qt5 for considerable time, it's just the PPA using qt4
128 2017-05-03 14:52:01	0|luke-jr|Ubuntu is no longer Unity; I'm guessing we still support an older Unity-based version though?
129 2017-05-03 14:52:59	0|wumpus|there's no Ubuntu no-Unity release yet afaik? I just meant that starting from there we can switch it to qt5
130 2017-05-03 14:53:22	0|luke-jr|is there a way to make debs use a different version based on their target?
131 2017-05-03 14:53:41	0|luke-jr|(parazyd - the guy who opened that PR - 's target is Knots on Devuan FWIW)
132 2017-05-03 14:53:47	0|wumpus|"On 5 April 2017 Mark Shuttleworth announced that Canonical's work on Unity will end and that Ubuntu 18.04 LTS, a year away from release at the time, will abandon the Unity desktop and employ the GNOME 3 desktop instead"
133 2017-05-03 14:55:16	0|wumpus|yes he's using KDE5, which doesn't work with qt4 all too well, so I understand his concern
134 2017-05-03 15:04:33	0|BlueMatt|luke-jr: all debian builds have the release hardcoded
135 2017-05-03 15:04:45	0|BlueMatt|well, for uploads to ppa/debian builds/ubuntu builds
136 2017-05-03 15:04:51	0|BlueMatt|manual builds ignore that
137 2017-05-03 15:07:15	0|luke-jr|I thought for PPAs you upload once and it built for everything? :o
138 2017-05-03 15:07:43	0|BlueMatt|nope, it gets uploaded like 5 times
139 2017-05-03 15:08:15	0|luke-jr|ew
140 2017-05-03 15:08:42	0|luke-jr|BlueMatt: it would be nice if there was a gitian descriptor that produced the files to upload btw ;)
141 2017-05-03 15:10:39	0|BlueMatt|the files to upload is pretty much just the debian/ folder from contrib/debian and a copy of the git archive, all signed by my pgp key
142 2017-05-03 15:10:45	0|BlueMatt|not sure how useful it would be, then, unsigned :p
143 2017-05-03 15:12:51	0|luke-jr|there isn't something that requires a Debian-based OS to generate?
144 2017-05-03 15:13:14	0|BlueMatt|I dunno, I use the debian tools to upload, but used to use the debain tools on arch, even
145 2017-05-03 15:13:18	0|BlueMatt|now its in a vm
146 2017-05-03 15:14:06	0|sipa|i thought PPA was ubuntu-spdcific
147 2017-05-03 15:14:29	0|luke-jr|it is
148 2017-05-03 15:14:33	0|BlueMatt|PPAs are, but the tools to upload to them are debian-generic
149 2017-05-03 15:15:56	0|luke-jr|BlueMatt: well, it'd be nice to have that VM turned into a gitian descriptor simply for convenience IMO; gitian as an automating tool rather that determinism tool ;)O
150 2017-05-03 15:16:22	0|BlueMatt|luke-jr: yes, but there'd be no point in anyone but me using it?
151 2017-05-03 15:16:24	0|BlueMatt|so why bother?
152 2017-05-03 15:16:30	0|BlueMatt|its already dead-simple to do
153 2017-05-03 15:16:35	0|luke-jr|BlueMatt: well, you don't want to maintain a PPA for Knots I assume?
154 2017-05-03 15:16:39	0|BlueMatt|just copy contrib/debian into debian and run dpkg-buildpackage
155 2017-05-03 15:17:22	0|BlueMatt|iirc dpkg-buildpackage -S -sa -d && dput ppaname *.changes
156 2017-05-03 15:17:47	0|luke-jr|k, will try that
157 2017-05-03 15:18:07	0|BlueMatt|you need to add ppaname to some config file
158 2017-05-03 15:18:25	0|BlueMatt|but ofc thats the part that is me-specific
159 2017-05-03 15:18:30	0|BlueMatt|not gitian-able
160 2017-05-03 15:19:04	0|BlueMatt|also your pgp key name has to match the top entry in debian/changelog for dpkg-buildpackage to sign it right
161 2017-05-03 15:20:12	0|luke-jr|your daily and RC PPAs seem dead since 2011 btw
162 2017-05-03 15:20:18	0|BlueMatt|im aware
163 2017-05-03 15:20:30	0|BlueMatt|they need to be deleted, probably
164 2017-05-03 15:25:35	0|Lauda|Is 'walletpassphrase' supposed to return 'null' now on correct entry of pass?
165 2017-05-03 15:27:47	0|wumpus|it always did AFAIK
166 2017-05-03 15:28:42	0|wumpus|on failure it throws an error, on success it returns NullUniValue
167 2017-05-03 15:33:20	0|Lauda|It may just be me, but I haven't noticed 'null' up until today on 0.14.1
168 2017-05-03 15:33:27	0|Lauda|Thanks for clarifying though!
169 2017-05-03 15:33:33	0|BlueMatt|luke-jr: i cant add people to the "bitcoin" team on launchpad because adding people means they get instant upload rights....so adding people needs to be a public process of "this person is gonna get PPA upload rights"
170 2017-05-03 15:33:48	0|wumpus|Lauda: might be that the GUI now displays it differently?
171 2017-05-03 15:35:07	0|Lauda|wumpus IIRC the GUI never returned 'null', that's why it surprised me (it had an empty line or something). Again, might be me :l
172 2017-05-03 15:37:23	0|luke-jr|BlueMatt: hmm, no way to add me with just a second PPA for knots?
173 2017-05-03 15:37:35	0|BlueMatt|luke-jr: I dont believe so, but may be wrong
174 2017-05-03 15:38:12	0|luke-jr|weird
175 2017-05-03 15:40:23	0|wumpus|Lauda: ah I think I remember now, IIRC that was changed because an empty line was confusing people
176 2017-05-03 15:41:04	0|Lauda|maybe in 0.14.0 (just tested that one, as it also has null). Thanks :D
177 2017-05-03 15:44:41	0|luke-jr|BlueMatt: dpkg-source: error: can't build with source format '3.0 (quilt)': no upstream tarball found at ../bitcoin_0.11.0.orig.tar.{bz2,gz,lzma,xz}
178 2017-05-03 15:45:39	0|BlueMatt|luke-jr: you need to create a git archive with the listed name :p
179 2017-05-03 15:48:32	0|luke-jr|dpkg-source: info: local changes detected, the modified files are: bitcoin/source/clientversion.cpp
180 2017-05-03 15:49:03	0|BlueMatt|yes, and the source has to match the git archive exactly, so the git archive magic in clientversion.cpp needs to be updated accordingly
181 2017-05-03 15:49:22	0|BlueMatt|really you're supposed to just untar the release source (which for us is git archive)
182 2017-05-03 15:49:36	0|luke-jr|not the gitian-generated tarball?
183 2017-05-03 15:50:09	0|BlueMatt|i suppose it doesnt matter?
184 2017-05-03 15:50:27	0|BlueMatt|i mean you can upload any source you want, i use git archives
185 2017-05-03 15:50:30	0|luke-jr|the latter has clientversion correct and configure generated :D
186 2017-05-03 15:51:11	0|BlueMatt|ehh, I'll stick with autogen on launchpad, doesnt matter
187 2017-05-03 16:03:42	0|jtimon|mhmm, travis wasn't launched for #9494 on last rebase... wumpus can you or someone else make it happen or should I just push with a different commit id or something?
188 2017-05-03 16:03:45	0|gribble|https://github.com/bitcoin/bitcoin/issues/9494 | Introduce an ArgsManager class encapsulating cs_args, mapArgs and mapMultiArgs by jtimon · Pull Request #9494 · bitcoin/bitcoin · GitHub
189 2017-05-03 16:05:41	0|bitcoin-git|[13bitcoin] 15RHavar closed pull request #10100: Make ApproximateBestSubset optimize for amount of inputs (06master...06coinselection) 02https://github.com/bitcoin/bitcoin/pull/10100
190 2017-05-03 16:38:07	0|sipa|anyone know what could be happening here? https://travis-ci.org/bitcoin/bitcoin/jobs/228201960
191 2017-05-03 16:38:25	0|sipa|no output for 10 minutes while/after running bitcoin-util-test.py
192 2017-05-03 16:38:48	0|sipa|this is the second PR where I see this problem
193 2017-05-03 16:40:00	0|wumpus|no, no idea. This was after the revert of #10225?
194 2017-05-03 16:40:02	0|gribble|https://github.com/bitcoin/bitcoin/issues/10225 | [test] Add aborttrescan tests by kallewoof · Pull Request #10225 · bitcoin/bitcoin · GitHub
195 2017-05-03 16:43:37	0|sipa|let me rebase on top of that revert
196 2017-05-03 16:45:43	0|sipa|reindex-chainstate on my laptop with pertxoutcache: 1h27m to block 453354 (default assumevalid)
197 2017-05-03 16:46:17	0|sipa|(and infinite dbcache, which is larger now)
198 2017-05-03 16:46:56	0|sipa|i'll benchmark master as well
199 2017-05-03 17:01:46	0|luke-jr|BlueMatt: how to get db4.8 built? :p
200 2017-05-03 17:03:38	0|luke-jr|(maybe it should be a separate PPA that can just be used as a dep?)
201 2017-05-03 17:04:52	0|TD-Linux|which reminds me, a recent beautiful locking bug with latest glibc and libdb breaks rpm on Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1394862
202 2017-05-03 17:05:09	0|TD-Linux|I don't think this affects db4.8 or wallet btw
203 2017-05-03 17:13:10	0|BlueMatt|sipa: context? what is non-per-utxo?
204 2017-05-03 17:13:16	0|BlueMatt|wait, what is pertxoutcache?
205 2017-05-03 17:13:40	0|sipa|BlueMatt: pertxoutcache = #10195
206 2017-05-03 17:13:41	0|gribble|https://github.com/bitcoin/bitcoin/issues/10195 | Switch chainstate db and cache to per-txout model by sipa · Pull Request #10195 · bitcoin/bitcoin · GitHub
207 2017-05-03 17:13:56	0|sipa|sorry, i think in my own branch names rather than PRs
208 2017-05-03 17:14:11	0|BlueMatt|ah, k
209 2017-05-03 17:14:53	0|sipa|dbcache was 6.3G at that point though, and 2.7G on disk after flushing
210 2017-05-03 17:22:21	0|BlueMatt|sipa: still missing lots of context...how do those numbers compare to previously :p
211 2017-05-03 17:22:47	0|BlueMatt|(esp cache size)
212 2017-05-03 17:23:53	0|sipa|BlueMatt: yeah, i haven't done a rigorous benchmark on this system recently, so i can't tell
213 2017-05-03 17:24:01	0|sipa|i was just surprised by a reindex of 1.5h
214 2017-05-03 17:24:20	0|sipa|maybe that's due to improvements in master i'm not aware of, or maybe my memory is faulty :)
215 2017-05-03 17:29:21	0|BlueMatt|or assumevalid
216 2017-05-03 17:45:28	0|bitcoin-git|[13bitcoin] 15jnewbery opened pull request #10330: fix zapwallettxes interaction with persistent mempool (06master...06zapwallettxes) 02https://github.com/bitcoin/bitcoin/pull/10330
217 2017-05-03 17:55:59	0|jnewbery|indicates that bitcoin-util-test.py has returned and you're now running the unit tests
218 2017-05-03 17:55:59	0|jnewbery|make[4]: Entering directory `/home/travis/build/bitcoin/bitcoin/build/bitcoin-i686-w64-mingw32/src'
219 2017-05-03 17:55:59	0|jnewbery|sipa: I may be wrong, but I think that your travis issue is with the unit tests rather than bitcoin-util-test.py. Compare: https://travis-ci.org/bitcoin/bitcoin/jobs/228344728 . I think the final line in your output:
220 2017-05-03 17:58:56	0|sipa|jnewbery: sounds plausible
221 2017-05-03 18:00:12	0|sipa|any idea on how to find out which test is the cause?
222 2017-05-03 18:01:34	0|luke-jr|I'm not sure the UAWITNESS service bit in BIP 149 is sufficient. At the very least, relying on service bits is a bad idea.
223 2017-05-03 18:03:22	0|luke-jr|what happens if a malicious node sends 0.14.1 a segwit block when BIP9 didn't activate? will it permanently flag it as invalid and never reconsider a stripped version?
224 2017-05-03 18:04:54	0|abpa|Don't you have the same issue if SegWit 2 is proposed with BIP9 over again?
225 2017-05-03 18:05:12	0|luke-jr|abpa: possibly. changing the dummy byte may workaround this.
226 2017-05-03 18:06:39	0|jnewbery|how reproducible is this on travis? Perhaps you could update the travis/make config to run the unit tests with verbose output?
227 2017-05-03 18:16:45	0|sipa|jnewbery: i have 2 PRs which reproducibly failed in 1 or 2 builds, both windows builds
228 2017-05-03 18:16:55	0|sipa|how do i run the tests verbose?
229 2017-05-03 18:26:02	0|jnewbery|sipa: test_bitcoin --log_level=all if you're running them manually, but that produces a lot of output. I haven't looked at how you'd update makefiles/travis config to do this
230 2017-05-03 18:43:16	0|sipa|jnewbery: i cannot reproduce it locally
231 2017-05-03 18:43:19	0|sipa|ok
232 2017-05-03 18:52:36	0|bitcoin-git|[13bitcoin] 15jnewbery opened pull request #10331: Share config between util and functional tests (06master...06shared_util_function_test_config) 02https://github.com/bitcoin/bitcoin/pull/10331
233 2017-05-03 18:59:01	0|luke-jr|woo success https://launchpad.net/~luke-jr/+archive/ubuntu/db48
234 2017-05-03 19:29:56	0|luke-jr|FYI: release tarballs are missing contrib/debian entirely
235 2017-05-03 20:05:28	0|bitcoin-git|[13bitcoin] 15parazyd closed pull request #10316: fix contrib/debian builds; prefer qt5 (06master...06debian-packaging) 02https://github.com/bitcoin/bitcoin/pull/10316
236 2017-05-03 21:14:04	0|bitcoin-git|[13bitcoin] 15instagibbs opened pull request #10333: CreateTransction fee fixes: always create change, adjust value, and p… (06master...06fixfeefinal) 02https://github.com/bitcoin/bitcoin/pull/10333
237 2017-05-03 21:24:54	0|sipa|cfields: how do i go about having a #define available for the presence of clock_gettime?
238 2017-05-03 21:25:12	0|sipa|cfields: it seems configure.ac already tests for it, but there is no macro
239 2017-05-03 21:27:27	0|cfields|sipa: looks like we assume it's always there?
240 2017-05-03 21:28:40	0|sipa|cfields: the interwebs tell me that OSX doesn't have it
241 2017-05-03 21:28:55	0|cfields|sipa: ergh, I remember something about it changing in 10.12
242 2017-05-03 21:29:47	0|cfields|sipa: ah right, maybe it was added and we'll have to deal with it like getentropy
243 2017-05-03 21:29:48	0|cfields|checking
244 2017-05-03 21:30:10	0|cfields|sipa: wait. What do you need it for?
245 2017-05-03 21:30:46	0|sipa|cfields: #10322
246 2017-05-03 21:30:47	0|gribble|https://github.com/bitcoin/bitcoin/issues/10322 | Use hardware timestamps in RNG seeding by sipa · Pull Request #10322 · bitcoin/bitcoin · GitHub
247 2017-05-03 21:31:15	0|sipa|ARM does not have an rdtsc instruction, and clock_gettime has much higher precision than gettimeofday
248 2017-05-03 21:32:05	0|sipa|i guess it does not matter that much... because on OSX we'll always be on a platform that does have rdtsc
249 2017-05-03 21:32:19	0|cfields|sipa: opposed to using std::chrono::high_resolution_clock ?
250 2017-05-03 21:33:04	0|sipa|ah!
251 2017-05-03 21:33:44	0|cfields|(i assume it's just an abstraction around clock_gettime for *nix)
252 2017-05-03 21:34:35	0|sipa|checking how it is implemented; thanks for the suggestion
253 2017-05-03 21:34:49	0|cfields|np
254 2017-05-03 21:37:43	0|cfields|to answer your question, in case this doesn't work out, in the "AC_SEARCH_LIBS([clock_gettime]", just add a third argument. Do the AC_DEFINE there.
255 2017-05-03 21:44:17	0|cfields|libc++ uses:  clock_gettime(CLOCK_REALTIME, &tp)
256 2017-05-03 21:45:38	0|cfields|but seems to round it to msecs :(
257 2017-05-03 21:45:58	0|sipa|"uses" ?
258 2017-05-03 21:46:00	0|sipa|for what?
259 2017-05-03 21:46:24	0|sipa|oh, for high_resolution_clock?
260 2017-05-03 21:46:27	0|sipa|rly?
261 2017-05-03 21:47:27	0|cfields|ah wait, that's only if there's no monotick source
262 2017-05-03 21:47:47	0|cfields|https://github.com/llvm-mirror/libcxx/blob/master/src/chrono.cpp#L137
263 2017-05-03 21:48:54	0|cfields|and https://github.com/llvm-mirror/libcxx/blob/master/src/chrono.cpp#L224
264 2017-05-03 21:50:10	0|sipa|cfields: can you try compiling and running https://zerobin.net/?f8af7a8040549857#9JGDEBZvv+MQzzGCfLGyvIC5C8plMb7L/Jxg34DuCYM= ?
265 2017-05-03 21:50:11	0|gribble|https://github.com/bitcoin/bitcoin/issues/9 | Fix for GUI on Macs and latest wxWidgets by gavinandresen · Pull Request #9 · bitcoin/bitcoin · GitHub
266 2017-05-03 21:50:35	0|sipa|on linux it gives me nanosecond precision, in mingw-w64 + wine microsecond
267 2017-05-03 21:50:39	0|cfields|mmm, i'm about ready to take back that suggestion. probably not worth the risk.
268 2017-05-03 21:50:52	0|cfields|sec
269 2017-05-03 21:52:20	0|cfields|yea, I get nano
270 2017-05-03 21:52:44	0|sipa|cool
271 2017-05-03 21:54:26	0|sipa|i like c++:
272 2017-05-03 21:54:27	0|sipa|return std::chrono::duration_cast<std::chrono::nanoseconds>(std::chrono::high_resolution_clock::now().time_since_epoch()).count();
273 2017-05-03 21:54:30	0|sipa|...
274 2017-05-03 21:57:34	0|cfields|heh
275 2017-05-03 21:57:41	0|sipa|translates to a single instruction
276 2017-05-03 21:57:59	0|sipa|(a library call, to be clear... but no conversion anywhere)
277 2017-05-03 21:58:01	0|cfields|oh, nice :)
278 2017-05-03 21:58:08	0|cfields|sipa: static_assert(std::ratio_greater_equal<std::chrono::high_resolution_clock::period, std::nano>::value == true, "no nanosecond precision");
279 2017-05-03 21:58:13	0|cfields|zero instructions for that one :)
280 2017-05-03 21:59:17	0|sipa|cfields: that compiles fine on mingw, even though the result only has microsecond precision
281 2017-05-03 22:00:08	0|sipa|(it always returns numbers that are multiples of 1000)
282 2017-05-03 22:00:14	0|cfields|hmm
283 2017-05-03 22:00:54	0|sipa|what output do you get on osx from my snippet?
284 2017-05-03 22:03:03	0|cfields|nano
285 2017-05-03 22:03:15	0|cfields|1033378907044228
286 2017-05-03 22:03:15	0|cfields|1033378907124163
287 2017-05-03 22:03:19	0|cfields|...
288 2017-05-03 22:07:07	0|cfields|oh sorry, got that static_assert backwards. That should be ratio_less_equal
289 2017-05-03 22:07:16	0|cfields|with that change, mingw fails to compile for me.
290 2017-05-03 22:07:55	0|sipa|still compiles fine here
291 2017-05-03 22:19:04	0|cfields|sipa: to avoid multiples of 1000 with microsecond precision, you can use: "auto value = std::chrono::duration_cast<std::chrono::high_resolution_clock::duration>(epoch);"
292 2017-05-03 22:19:52	0|cfields|(though it sounds like your mingw is lying to you about precision at compile-time, so that may not help)
293 2017-05-03 22:19:58	0|cfields|works here