1 2018-03-13 00:54:40 0|bitcoin-git|13bitcoin/06master 140eb84f3 15Ben Woosley: test: Use wait_until to ensure ping goes out...
2 2018-03-13 00:54:40 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/d8d9162f5bad...66e91420ab23
3 2018-03-13 00:54:41 0|bitcoin-git|13bitcoin/06master 1466e9142 15MarcoFalke: Merge #12545: test: Use wait_until to ensure ping goes out...
4 2018-03-13 00:55:27 0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #12545: test: Use wait_until to ensure ping goes out (06master...06ping-timing) 02https://github.com/bitcoin/bitcoin/pull/12545
5 2018-03-13 03:14:18 0|jojeyh|is there a way to easily specify the fee by sat/kb using bitcoin-cli ?
6 2018-03-13 03:32:52 0|bitcoin-git|[13bitcoin] 15Maivaza opened pull request #12679: 0.15 (06master...060.15) 02https://github.com/bitcoin/bitcoin/pull/12679
7 2018-03-13 03:33:25 0|kallewoof|jojeyh: for sendtoaddress? there's a PR but it's not been merged yet unfortunately: #11413
8 2018-03-13 03:33:27 0|gribble|https://github.com/bitcoin/bitcoin/issues/11413 | [wallet] [rpc] sendtoaddress/sendmany: Add explicit feerate option by kallewoof ÷ Pull Request #11413 ÷ bitcoin/bitcoin ÷ GitHub
9 2018-03-13 03:33:44 0|bitcoin-git|[13bitcoin] 15fanquake closed pull request #12679: 0.15 (06master...060.15) 02https://github.com/bitcoin/bitcoin/pull/12679
10 2018-03-13 03:33:57 0|kallewoof|jojeyh: I think your question is more suited for #bitcoin though, btw.
11 2018-03-13 03:33:59 0|jojeyh|kallewoof, thx i was wondering if someone had already done it
12 2018-03-13 03:35:47 0|jojeyh|aye
13 2018-03-13 06:57:27 0|pierre_rochard|Does anyone know of software / a script that can say ââ¬Åif you merge this pull request, then pull requests X, Y, and Z will have to be rebasedââ¬Â? Google didnââ¬â¢t turn anything up so Iââ¬â¢m interested in writing one
14 2018-03-13 07:20:43 0|Randolf|pierre_rochard: The folks on the #github channel have been helpful to me in the past. I suspect there's a good chance someone there might know of something like you describe if it exists.
15 2018-03-13 07:21:26 0|pierre_rochard|Iââ¬â¢ll ask them, thanks Randolf!
16 2018-03-13 07:24:33 0|Randolf|You're welcome.
17 2018-03-13 08:36:36 0|Alohaaaa|Hello
18 2018-03-13 09:44:04 0|wumpus|pierre_rochard: ajtowns[m] did some work in that direction (a script to figure out which PRs collide with which others) from what I remember
19 2018-03-13 09:52:04 0|pierre_rochard|wumpus: thanks, maybe https://github.com/ajtowns/bitcoin-prs is it and he hasnââ¬â¢t pushed the code up yet. ajtowns[m] Iââ¬â¢m happy to help out
20 2018-03-13 10:14:03 0|murrayn|argh. had an open PR, and made a mistake push. easy way to undo that?
21 2018-03-13 10:14:09 0|murrayn|https://github.com/bitcoin/bitcoin/pull/12630
22 2018-03-13 10:42:55 0|wumpus|murrayn: yes, go to git reflog, find the old commit id
23 2018-03-13 10:43:12 0|wumpus|murrayn: force-push that to the branch
24 2018-03-13 10:47:01 0|murrayn|wumpus, will that undo the push? or create a new push that undoes the bad push?
25 2018-03-13 10:47:11 0|murrayn|just curious
26 2018-03-13 10:47:15 0|wumpus|isn't that the same?
27 2018-03-13 10:47:24 0|murrayn|well
28 2018-03-13 10:47:47 0|murrayn|i'd rather just go back in time obviously.
29 2018-03-13 10:47:57 0|murrayn|than to document fixing a fuckup
30 2018-03-13 10:48:05 0|wumpus|well by finding the old commit id you're going back in time
31 2018-03-13 10:49:02 0|murrayn|ok, we'll see
32 2018-03-13 10:49:45 0|wumpus|to me it seems entirely philosophical wehther you consider that a new push of an old state, or re-doing an old push, or restoring the previous push
33 2018-03-13 10:50:20 0|murrayn|hmm
34 2018-03-13 10:52:43 0|wumpus|also you can do git reset --hard <commit> (on the branch) first to do it locally, then force-push the branch to the remote branch, if that's easier to understand
35 2018-03-13 10:56:37 0|murrayn|wumpus, just trying to understand: so after the reset, is the --force necessary?
36 2018-03-13 10:56:44 0|murrayn|wumpus, or just git push
37 2018-03-13 10:56:54 0|wumpus|yes, the force is necessary as you're pushing a commit that is not a child of the current branch
38 2018-03-13 10:57:00 0|murrayn|ah
39 2018-03-13 10:57:09 0|wumpus|it doesn't change, from regard of github, what you do locally
40 2018-03-13 10:58:16 0|murrayn|wumpus, thank you sir.
41 2018-03-13 10:58:26 0|murrayn|seems to have worked.
42 2018-03-13 10:58:54 0|wumpus|cool
43 2018-03-13 11:34:00 0|wumpus|I've invited eklitzke (as frequent contributor) to the bitcoin and bitcoin-core orgs
44 2018-03-13 12:25:43 0|kallewoof|if you literally want to go back to say '5 mins ago' you can also do: git reset --hard mynicebranch@{"5 minutes ago"}
45 2018-03-13 12:29:59 0|wumpus|kallewoof: ah yes, git understands time referencs, I forgot about that :)
46 2018-03-13 12:35:53 0|kallewoof|wumpus: I only learned about it a few weeks ago. I actually used it already, once. :) Very cool feature.
47 2018-03-13 14:21:36 0|contrapumpkin|esotericnonsense: hah, after a day of running -reindex, it popped up the exact same error message at the same place :P
48 2018-03-13 15:04:09 0|Randolf|contrapumpkin: Might there be a bad sector on your hard disk?
49 2018-03-13 15:09:49 0|Guest99|hey, looking through this reddit thread (https://www.reddit.com/r/CoinBase/comments/83syb6/warning_coinbase_merchant_segwit_implementation/) claiming the current Coinbase segwit implementation for merchants is broken,
50 2018-03-13 15:10:01 0|Guest99|can someone break down exactly what's wrong for me?
51 2018-03-13 15:10:21 0|Guest99|the poster said he confirmed it with bitcoin dev, but i cant find the chat logs
52 2018-03-13 15:18:46 0|bitcoin-git|13bitcoin/060.16 14faf316a 15Wladimir J. van der Laan: test: Update trust git root...
53 2018-03-13 15:18:46 0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 060.16: 02https://github.com/bitcoin/bitcoin/compare/60086ddc34ee...46ca8f383e53
54 2018-03-13 15:18:47 0|bitcoin-git|13bitcoin/060.16 1446ca8f3 15Wladimir J. van der Laan: Merge #12648: [0.16] test: Update trusted git root...
55 2018-03-13 15:26:31 0|provoostenator|Gues99: that's a topic for #bitcoin, unless it's a bug in Bitcoin Core
56 2018-03-13 15:26:47 0|provoostenator|Guest99 ^
57 2018-03-13 15:28:28 0|provoostenator|(there are Core devs on many IRC channels)
58 2018-03-13 15:38:23 0|Guest99|provoostenator thanks!
59 2018-03-13 16:00:14 0|bitcoin-git|13bitcoin/06master 14b1149ee 15practicalswift: Remove redundant code in MutateTxSign(CMutableTransaction&, const std::string&)
60 2018-03-13 16:00:14 0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/66e91420ab23...ae5bcc7abb14
61 2018-03-13 16:00:15 0|bitcoin-git|13bitcoin/06master 14ae5bcc7 15Wladimir J. van der Laan: Merge #10694: Remove redundant code in MutateTxSign(CMutableTransaction&, const std::string&)...
62 2018-03-13 16:00:30 0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10694: Remove redundant code in MutateTxSign(CMutableTransaction&, const std::string&) (06master...06remove-redundant-code-in-MutateTxSign) 02https://github.com/bitcoin/bitcoin/pull/10694
63 2018-03-13 16:18:36 0|bitcoin-git|13bitcoin/06master 14f4b68b3 15Evan Klitzke: Log fatal LevelDB errors more verbosely
64 2018-03-13 16:18:36 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/ae5bcc7abb14...3d16f581538b
65 2018-03-13 16:18:37 0|bitcoin-git|13bitcoin/06master 143d16f58 15MarcoFalke: Merge #12659: Improve Fatal LevelDB Log Messages...
66 2018-03-13 16:19:24 0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #12659: Improve Fatal LevelDB Log Messages (06master...06leveldb_errmsg) 02https://github.com/bitcoin/bitcoin/pull/12659
67 2018-03-13 16:39:51 0|bitcoin-git|13bitcoin/06master 14fa44af5 15MarcoFalke: travis: Full clone for git subtree check
68 2018-03-13 16:39:51 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/3d16f581538b...0f58d7f3d62f
69 2018-03-13 16:39:52 0|bitcoin-git|13bitcoin/06master 140f58d7f 15MarcoFalke: Merge #12405: travis: Full clone for git subtree check...
70 2018-03-13 16:40:34 0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #12405: travis: Full clone for git subtree check (06master...06Mf1802-travisSubtree) 02https://github.com/bitcoin/bitcoin/pull/12405
71 2018-03-13 16:46:14 0|bitcoin-git|13bitcoin/06master 14fa1436c 15MarcoFalke: [qa] util: Remove unused sync_chain
72 2018-03-13 16:46:14 0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/0f58d7f3d62f...0f0229d0c363
73 2018-03-13 16:46:15 0|bitcoin-git|13bitcoin/06master 140f0229d 15Wladimir J. van der Laan: Merge #12643: [qa] util: Remove unused sync_chain...
74 2018-03-13 16:47:00 0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #12643: [qa] util: Remove unused sync_chain (06master...06Mf1803-qaUtilSyncChain) 02https://github.com/bitcoin/bitcoin/pull/12643
75 2018-03-13 17:00:37 0|bitcoin-git|[13bitcoin] 15laanwj pushed 4 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/0f0229d0c363...702e8b70bd87
76 2018-03-13 17:00:38 0|bitcoin-git|13bitcoin/06master 148acd25d 15MarcoFalke: rpc: Allow typeAny in RPCTypeCheck
77 2018-03-13 17:00:38 0|bitcoin-git|13bitcoin/06master 14fa06dfc 15MarcoFalke: [rpc] createrawtransaction: Accept sorted outputs
78 2018-03-13 17:00:39 0|bitcoin-git|13bitcoin/06master 14fac7013 15MarcoFalke: rpc: Update createrawtransaction examples
79 2018-03-13 17:01:07 0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #11872: [rpc] createrawtransaction: Accept sorted outputs (06master...06Mf1712-rpcCreateRawSortedOuts) 02https://github.com/bitcoin/bitcoin/pull/11872
80 2018-03-13 17:16:24 0|aj|pierre_rochard: that repo was just where i was playing around with a bot that autotags pull requests. https://gist.github.com/ajtowns/d0cf97678dc83efdf3f6cbf7083a35a0 was where i was playing around with autodetecting conflicts
81 2018-03-13 17:40:16 0|bitcoin-git|[13bitcoin] 15laanwj pushed 3 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/702e8b70bd87...af88094e4f71
82 2018-03-13 17:40:17 0|bitcoin-git|13bitcoin/06master 14029ecac 15Pieter Wuille: Split up and sanitize CWalletTx serialization
83 2018-03-13 17:40:17 0|bitcoin-git|13bitcoin/06master 1442343c7 15Pieter Wuille: Split up and sanitize CAccountingEntry serialization
84 2018-03-13 17:40:18 0|bitcoin-git|13bitcoin/06master 14af88094 15Wladimir J. van der Laan: Merge #12658: Sanitize some wallet serialization...
85 2018-03-13 17:41:11 0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #12658: Sanitize some wallet serialization (06master...06201803_crazywalletser) 02https://github.com/bitcoin/bitcoin/pull/12658
86 2018-03-13 17:44:20 0|mrannanay|wumpus : Could you review #12288 when you're free?
87 2018-03-13 17:44:22 0|gribble|https://github.com/bitcoin/bitcoin/issues/12288 | [WIP][NET] Add NATPMP support. by annanay25 ÷ Pull Request #12288 ÷ bitcoin/bitcoin ÷ GitHub
88 2018-03-13 17:51:41 0|promag|candidate for merge #11041
89 2018-03-13 17:51:45 0|gribble|https://github.com/bitcoin/bitcoin/issues/11041 | Add LookupBlockIndex by promag ÷ Pull Request #11041 ÷ bitcoin/bitcoin ÷ GitHub
90 2018-03-13 18:05:19 0|provoostenator|#12666 made me curious: when do we use packages like UniValue from the OS, vs. compiling it from the src dir? And why even bother with the former?
91 2018-03-13 18:05:21 0|gribble|https://github.com/bitcoin/bitcoin/issues/12666 | configure: UniValue 1.0.4 is required for pushKV(, bool) by luke-jr ÷ Pull Request #12666 ÷ bitcoin/bitcoin ÷ GitHub
92 2018-03-13 18:06:31 0|sipa|provoostenator: becaause some people insist on being able to use OS packages
93 2018-03-13 18:06:48 0|provoostenator|Bonus question: how is this different from the Depends system?
94 2018-03-13 18:07:07 0|luke-jr|provoostenator: it is a bad practice to bundle libraries at all
95 2018-03-13 18:07:16 0|sipa|luke-jr: why?
96 2018-03-13 18:07:42 0|sipa|i buy that argument for large libraries that are outside of bitcoin core's development
97 2018-03-13 18:07:58 0|wumpus|mrannanay: will take a look at it again tomorrow
98 2018-03-13 18:08:29 0|luke-jr|sipa: https://wiki.gentoo.org/wiki/Why_not_bundle_dependencies https://fedoraproject.org/wiki/Bundled_Libraries?rd=Packaging:Bundled_Libraries
99 2018-03-13 18:08:49 0|wumpus|for libraries that are part of consensus (secp256k1,leveldb) there's a good reason to bundle it, for leveldb especially as we have some custom patches to it
100 2018-03-13 18:08:56 0|mrannanay|wumpus : Thanks!
101 2018-03-13 18:09:05 0|wumpus|for univalue the case is somewhat weaker, but based on it being a rarely-packaged library
102 2018-03-13 18:09:13 0|wumpus|not bundling it would give people a lot of pain
103 2018-03-13 18:09:40 0|sipa|luke-jr: none of that applies; univalue is effectively developed by us
104 2018-03-13 18:09:42 0|wumpus|finding it, building it, manually installing it. We save that for berkeleydb 4.8 :-)
105 2018-03-13 18:09:45 0|luke-jr|well, if we didn't depend on 1.0.4 specifically now, 1.0.2 is pretty widespreadly packaged
106 2018-03-13 18:09:52 0|wumpus|unilvalue is virtually only used by us
107 2018-03-13 18:10:13 0|wumpus|yes, bundling makes it possible to develop it in parallel
108 2018-03-13 18:10:22 0|wumpus|without having to support tons of combinations
109 2018-03-13 18:10:42 0|sipa|i think the arguments in those documents very much apply to not bundling bdb, boost, glibc, ...
110 2018-03-13 18:12:59 0|bitcoin-git|[13bitcoin] 15laanwj pushed 6 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/af88094e4f71...d42a4fe5aaae
111 2018-03-13 18:13:00 0|bitcoin-git|13bitcoin/06master 1402de6a6 15João Barbosa: Assert cs_main is held when accessing mapBlockIndex
112 2018-03-13 18:13:00 0|bitcoin-git|13bitcoin/06master 14c651df8 15João Barbosa: Lock cs_main while loading block index in AppInitMain
113 2018-03-13 18:13:01 0|bitcoin-git|13bitcoin/06master 14f814a3e 15João Barbosa: Fix cs_main lock in LoadExternalBlockFile...
114 2018-03-13 18:13:09 0|luke-jr|we're also not the upstream for univalue. jgarzik is.
115 2018-03-13 18:13:11 0|provoostenator|But why aren't univalue, secp256k1, etc part of the Depends system? Maybe there should be a way to build /depends skipping installed packages?
116 2018-03-13 18:13:13 0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #11041: Add LookupBlockIndex (06master...062017-08-lookup-block-index) 02https://github.com/bitcoin/bitcoin/pull/11041
117 2018-03-13 18:13:22 0|luke-jr|provoostenator: good idea
118 2018-03-13 18:13:40 0|luke-jr|(although even if leveldb is installed, we may still prefer to build our own)
119 2018-03-13 18:14:00 0|sipa|provoostenator: because they're subtrees
120 2018-03-13 18:14:05 0|provoostenator|Skipping installed packages if the version is acceptable.
121 2018-03-13 18:14:32 0|provoostenator|sipa: but they could be seperate repos under the bitcoin org?
122 2018-03-13 18:14:36 0|sipa|provoostenator: they are
123 2018-03-13 18:14:55 0|sipa|https://github.com/bitcoin-core/secp256k1
124 2018-03-13 18:14:59 0|wumpus|I'd really prefer not to change this - it works, people are used to it
125 2018-03-13 18:15:22 0|luke-jr|it's probably good enough as is; bumping the required version here and there is no big deal
126 2018-03-13 18:15:33 0|sipa|provoostenator: look up how subtrees work
127 2018-03-13 18:15:45 0|luke-jr|sipa: his point is that using depends would be superior to subtrees
128 2018-03-13 18:15:52 0|sipa|yes, and i disagree with that
129 2018-03-13 18:16:04 0|provoostenator|Subtrees as opposed to submodules?
130 2018-03-13 18:16:06 0|sipa|we want exact control over the source code used for some things
131 2018-03-13 18:16:26 0|luke-jr|sipa: we could have exact control over it with depends too
132 2018-03-13 18:16:35 0|sipa|yes, but we'd lose it for non-depends builds
133 2018-03-13 18:16:39 0|provoostenator|(I've had nothing but headaches dealing with git submodules, so not blaming anyone for not using them)
134 2018-03-13 18:16:40 0|luke-jr|not necessarily
135 2018-03-13 18:16:40 0|sipa|subtrees give us this property always
136 2018-03-13 18:16:52 0|luke-jr|anyhow, unless someone is going to put the work into migrating it over, no point wasting time discussing in depth IMO
137 2018-03-13 18:16:54 0|wumpus|also there is no special incantation needed to check things out
138 2018-03-13 18:17:00 0|wumpus|it's simply in one tree
139 2018-03-13 18:17:02 0|provoostenator|wumpus: I'm fine with not changing it even if it was better :-)
140 2018-03-13 18:17:10 0|wumpus|it's perfect like this IMO
141 2018-03-13 18:20:17 0|provoostenator|I didn't realize "git subtree" was a command, that's nice. Is there a way to check if it matches the original repo (other than git diff)?
142 2018-03-13 18:23:05 0|sipa|provoostenator: yes, we have a script that does that :)
143 2018-03-13 18:23:11 0|sipa|you need access to the original repo, of course
144 2018-03-13 18:23:14 0|wumpus|./contrib/devtools/git-subtree-check.sh
145 2018-03-13 18:28:30 0|provoostenator|"git-subtree-check.sh src/univalue" doesn't seem happy, I guess I need to add some hints to check the right fork?
146 2018-03-13 18:30:31 0|sipa|$ git remote add upstream-univalue https://github.com/bitcoin-core/univalue
147 2018-03-13 18:30:34 0|sipa|$ git fetch upstream-univalue
148 2018-03-13 18:30:40 0|sipa|$ contrib/devtools/git-subtree-check.sh src/univalue
149 2018-03-13 18:30:46 0|sipa|GOOD
150 2018-03-13 18:31:35 0|provoostenator|I missed the fetch bit, now it's happy.
151 2018-03-13 19:33:23 0|bitcoin-git|[13bitcoin] 15vasild opened pull request #12680: Trivial: Add missing virtual destructor in PeerLogicValidation (06master...06master-add-missing-vdtor-in-PeerLogicValidation) 02https://github.com/bitcoin/bitcoin/pull/12680
152 2018-03-13 20:49:44 0|provoostenator|Re #12665 by practicalswift: are these thread safety checks done automatically when I run make, or do I need to configure something?
153 2018-03-13 20:49:47 0|gribble|https://github.com/bitcoin/bitcoin/issues/12665 | Add compile time checking for run time locking assertions by practicalswift ÷ Pull Request #12665 ÷ bitcoin/bitcoin ÷ GitHub
154 2018-03-13 20:55:08 0|provoostenator|Looks like it's checked by default (I did some trial and error sabotage on my local machine).
155 2018-03-13 20:57:46 0|arubi|bip173 lists tc1qw508d6qejxtdg4y5r3zarvary0c5xw7kg3g4ty as being invalid due to "invalid human-readable part", is it just that "tc" is not one of "bc", "tb", or "bcrt" or is there anything else to it? seems that apart from that it does encode a valid p2wpkh
156 2018-03-13 20:58:13 0|sipa|arubi: yup
157 2018-03-13 20:58:18 0|arubi|cool, cheers
158 2018-03-13 20:58:20 0|sipa|invalid hrp
159 2018-03-13 20:58:41 0|arubi|right, in my mind hrp could be anything, but I see why it's not a "segwit address"
160 2018-03-13 20:58:58 0|sipa|BIP173 only specifies bc and tb, so anything else is invalid
161 2018-03-13 20:59:08 0|Chris_Stewart_5|arubi: I believe the lightning people repurpose it. Don't know how the author feels about that usage though :-)
162 2018-03-13 20:59:14 0|sipa|but it's certainly valid bech32... just not a valid segwit address
163 2018-03-13 20:59:36 0|sipa|Chris_Stewart_5: bech32 is designed to be generally useful :)
164 2018-03-13 20:59:48 0|arubi|right, so as long as some implementation keeps to its own hrp, we should all be fine
165 2018-03-13 20:59:52 0|sipa|(though they violate the spec by exceeding 90 characters)
166 2018-03-13 21:08:12 0|aj|sipa: did you get a chance to read the mail i sent about soft-fork compatible sig aggregation? see any obvious problems, or worth sending to bitcoin-dev do you think?
167 2018-03-13 21:08:31 0|sipa|aj: i haven't yet
168 2018-03-13 21:13:17 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 4 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/d42a4fe5aaae...0630974647da
169 2018-03-13 21:13:18 0|bitcoin-git|13bitcoin/06master 142b7064e 15John Newbery: [tests] Fix flake8 warnings in invalidblockrequest
170 2018-03-13 21:13:18 0|bitcoin-git|13bitcoin/06master 1454b8c58 15Conor Scott: [test] Fix nits leftover from 11771...
171 2018-03-13 21:13:19 0|bitcoin-git|13bitcoin/06master 14e97b113 15John Newbery: [tests] Change invalidblockrequest to use BitcoinTestFramework...
172 2018-03-13 21:13:41 0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #11772: [tests] Change invalidblockrequest to use BitcoinTestFramework (06master...06refactor_invalidblockrequest) 02https://github.com/bitcoin/bitcoin/pull/11772
173 2018-03-13 22:44:14 0|kobrabyte|hello all
174 2018-03-13 22:44:17 0|bitcoin-git|[13bitcoin] 15ryanofsky opened pull request #12681: Fix ComputeTimeSmart test failure with -DDEBUG_LOCKORDER (06master...06pr/locksmart) 02https://github.com/bitcoin/bitcoin/pull/12681
175 2018-03-13 22:45:59 0|bitcoin-git|[13bitcoin] 15MarcoFalke opened pull request #12682: travis: Clone depth 1 unless $CHECK_DOC (06master...06Mf1803-travisDepth1) 02https://github.com/bitcoin/bitcoin/pull/12682