1 2017-11-07 00:26:17 0|bitcoin-git|[13bitcoin] 15vivganes opened pull request #11624: Docs: Change formatting for sequence of steps (06master...06patch-1) 02 https://github.com/bitcoin/bitcoin/pull/11624
2 2017-11-07 00:43:02 0|ossifrage|ProcessMessages(headers, 161031 bytes): Exception 'ReadCompactSize(): size too large: iostream error' caught
3 2017-11-07 00:44:17 0|ossifrage|I've been getting a fairly large number of this error with 0e707919f596c80056bca295abd71543ccae4956
4 2017-11-07 00:45:23 0|ossifrage|Ugg, that was from the wrong debug.log, not a recent version
5 2017-11-07 01:13:52 0|sipa|ossifrage: that means a peer is not following the protocol
6 2017-11-07 02:36:52 0|sipa|jnewbery: https://github.com/bitcoin/bitcoin/pull/10150 -> any reason why the logging RPC is hidden?
7 2017-11-07 04:43:33 0|achow101|there's a logging RPC?
8 2017-11-07 04:50:49 0|sipa|achow101: QED.
9 2017-11-07 06:48:29 0|wumpus|I think it started as experimental
10 2017-11-07 06:48:33 0|wumpus|could be un-hidden now
11 2017-11-07 06:48:46 0|wumpus|I think it's useful enough for general use now
12 2017-11-07 06:52:44 0|wumpus|#11626
13 2017-11-07 06:52:46 0|gribble|https://github.com/bitcoin/bitcoin/issues/11626 | rpc: Make `logging` RPC public by laanwj ÷ Pull Request #11626 ÷ bitcoin/bitcoin ÷ GitHub
14 2017-11-07 06:55:52 0|wumpus|sipa: ossifrage: we should probably hide such protocol errors unless net debugging is enabled
15 2017-11-07 06:56:21 0|wumpus|any peer can connect and violate the protocol grossly and spam your debug.log, it can be scary to esp. new users
16 2017-11-07 09:10:50 0|gmaxwell|I've updated my banlists, in addition to the spies and mass-connectors, they now also include about 30 hosts which are running B2X but using fake service flags: https://people.xiph.org/~greg/banlist.cli.txt https://people.xiph.org/~greg/banlist.gui.txt
17 2017-11-07 15:42:24 0|jnewbery|sipa: I implemented it that way because logging is a debug/troubleshooting feature which shouldn't be of interest to the general user
18 2017-11-07 15:42:55 0|jnewbery|I have no strong opionion about whether it should hidden or unhidden
19 2017-11-07 15:43:43 0|jnewbery|sipa: #11389 failed travis here: https://travis-ci.org/bitcoin/bitcoin/jobs/298345172 . Looks unrelated, I'm going to restart it
20 2017-11-07 15:43:45 0|gribble|https://github.com/bitcoin/bitcoin/issues/11389 | Support having SegWit always active in regtest by sipa ÷ Pull Request #11389 ÷ bitcoin/bitcoin ÷ GitHub
21 2017-11-07 15:54:36 0|wumpus|jnewbery: well the number of surprised people all around that are glad to see that call seems to indicate otherwise :)
22 2017-11-07 15:58:33 0|MarcoFalke|The gh irc bot seems dead
23 2017-11-07 16:03:10 0|wumpus|maybe it's lagging again
24 2017-11-07 16:25:17 0|bsm117532|I really liked Anthony Towns' talk at Scaling Bitcoin regarding adding some kind of replay protection to Bitcoin.
25 2017-11-07 16:25:36 0|bsm117532|Because you can't expect hostile forkers to Do The Right Thing or do it correctly.
26 2017-11-07 16:25:57 0|bsm117532|And his points about using market information (e.g. futures) to decide on forks.
27 2017-11-07 16:26:07 0|bsm117532|Are there any plans to implement something like this?
28 2017-11-07 16:26:31 0|bsm117532|I have the green light from my new employer to do some work on Bitcoin, and I might be interested in pursuing this.
29 2017-11-07 16:33:37 0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #11629: Fixed some typoes in norwegian translation. (06master...06patch-1) 02 https://github.com/bitcoin/bitcoin/pull/11629
30 2017-11-07 16:35:00 0|ghost43|https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki -- "Created: 2016-03-20" I think there is a typo and it should be 2017, as the date of the first commit here is 2017-03-20 https://github.com/sipa/bech32/commit/52b5a0fa6d3174c4150393fb7d6b58d34b4f5e0b -- I can't open an issue in the BIP repo, so I figured I would just note it here. sipa luke-jr
31 2017-11-07 16:36:51 0|MarcoFalke|ghost43: Pull request welcome :)
32 2017-11-07 16:51:07 0|ghost43|ok, done
33 2017-11-07 17:14:42 0|wumpus|bsm117532: no, I don't think anyone is working on replay protection on our side of the chain, the risk is also that they might also try to thwart it, like w/ the service bits
34 2017-11-07 17:15:34 0|bsm117532|wumpus: A proposal is far from complete, clearly.
35 2017-11-07 17:15:46 0|bitcoin-git|13bitcoin/06master 14d0b1fc8 15Vivek Ganesan: Docs: Change formatting for sequence of steps...
36 2017-11-07 17:15:46 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02 https://github.com/bitcoin/bitcoin/compare/998c3046fab2...f9b74ef3fc74
37 2017-11-07 17:15:47 0|bitcoin-git|13bitcoin/06master 14f9b74ef 15MarcoFalke: Merge #11624: Docs: Change formatting for sequence of steps...
38 2017-11-07 17:16:33 0|bsm117532|I think some mechanisms could not be thwarted, e.g. OP_CHECKBLOCKHASHATHEIGHT or committing to a chain's block hash with the signing algorithm.
39 2017-11-07 17:18:41 0|yurit|Hello everyone. I am interested in learning about bitcoin one of the doubts that I have is technically. What makes the difficulty of mining increase?
40 2017-11-07 17:23:32 0|bsm117532|yurit: try asking your question in #bitcoin
41 2017-11-07 17:24:26 0|bsm117532|I'll answer there
42 2017-11-07 18:00:43 0|yurit|bsm117532: ok
43 2017-11-07 19:19:30 0|cfields|\o/ #10866
44 2017-11-07 19:19:32 0|gribble|https://github.com/bitcoin/bitcoin/issues/10866 | Fix -Wthread-safety-analysis warnings. Compile with -Wthread-safety-analysis if available. by practicalswift ÷ Pull Request #10866 ÷ bitcoin/bitcoin ÷ GitHub
45 2017-11-07 20:16:43 0|bitcoin-git|13bitcoin/06master 14a02c5e4 15Karl-Johan Alm: [trivial] Fix error messages in CFeeBumper
46 2017-11-07 20:16:43 0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02 https://github.com/bitcoin/bitcoin/compare/ef8a63435884...6f01dcf63873
47 2017-11-07 20:16:44 0|bitcoin-git|13bitcoin/06master 146f01dcf 15MarcoFalke: Merge #11597: [trivial] Fix error messages in CFeeBumper...
48 2017-11-07 20:23:42 0|BlueMatt|cfields: #11363 needs rebase
49 2017-11-07 20:23:43 0|gribble|https://github.com/bitcoin/bitcoin/issues/11363 | net: Split socket create/connect by theuni ÷ Pull Request #11363 ÷ bitcoin/bitcoin ÷ GitHub
50 2017-11-07 20:39:57 0|cfields|BlueMatt: thanks, done
51 2017-11-07 20:40:49 0|BlueMatt|cfields: "Cannot post comment, commit is no longer a part of PR".......
52 2017-11-07 20:41:33 0|cfields|eh?
53 2017-11-07 20:42:39 0|BlueMatt|cfields: oh, ignore my comment
54 2017-11-07 20:42:58 0|cfields|heh, comment at exactly the same time i force-pushed ?
55 2017-11-07 20:43:02 0|BlueMatt|cfields: is SOCKET ever going to be a not-int?
56 2017-11-07 20:43:14 0|BlueMatt|can we just pass-by-copy instead of pass-by-const-ref for an int?
57 2017-11-07 20:44:35 0|cfields|BlueMatt: i think passing by const ref reinforces the idea that it's a handle. Otherwise I'm afraid someone may stash it somewhere and destroy it elsewhere
58 2017-11-07 20:44:52 0|BlueMatt|hmm, alright fair
59 2017-11-07 20:45:15 0|cfields|could wrap it up in a struct or something to force the semantics if you'd like?
60 2017-11-07 20:45:49 0|BlueMatt|nah, all good
61 2017-11-07 21:15:01 0|BlueMatt|can I get some comments on #11517? Specifically, it adds the ability for bench_bitcoin to generate html which has a <script ref="cdn.server"> - should we check in this plotly.js library (its apparently already mit) or would we prefer to keep the link in the generated output (its optional, you can still get the csv-style output on cli if you want)
62 2017-11-07 21:15:03 0|gribble|https://github.com/bitcoin/bitcoin/issues/11517 | Tests: Improve benchmark precision by martinus ÷ Pull Request #11517 ÷ bitcoin/bitcoin ÷ GitHub
63 2017-11-07 21:15:12 0|BlueMatt|probably a wumpus decision, I suppose
64 2017-11-07 21:29:23 0|gmaxwell|BlueMatt: is the plotting thing that you use with fibre that kills firefox?
65 2017-11-07 21:29:39 0|BlueMatt|gmaxwell: heh, no, thats some google charts library thing
66 2017-11-07 21:29:47 0|BlueMatt|gmaxwell: and, fwiw, I can now *only* plot it on firefox
67 2017-11-07 21:29:56 0|BlueMatt|it blows chromium up by exceeding some per-tab memory limit they have
68 2017-11-07 21:30:04 0|BlueMatt|but firefox does fine
69 2017-11-07 21:36:52 0|cfields|BlueMatt: how much of plotly would we need?
70 2017-11-07 21:38:03 0|BlueMatt|cfields: no idea, haven't looked, but the usage is rather trivial
71 2017-11-07 21:38:10 0|BlueMatt|its just like making box plots of runtimes of benchmark runs
72 2017-11-07 21:39:31 0|cfields|I'm confused as to why that wouldn't just be a server-side thing, though? Why not just parse a csv in realtime?
73 2017-11-07 21:40:56 0|BlueMatt|server-side?
74 2017-11-07 21:41:01 0|BlueMatt|there is no server?
75 2017-11-07 21:48:22 0|MarcoFalke|The plotly printout is optional, right?
76 2017-11-07 21:48:40 0|cfields|BlueMatt: I meant that outputting a reasonable csv seems like enough. If a nice plot/markup is desired, that seems beyond the scope of the bench tool
77 2017-11-07 21:49:14 0|BlueMatt|MarcoFalke: yes, default is to print the csv-style output
78 2017-11-07 21:49:32 0|MarcoFalke|I don't mind adding an option for common formats
79 2017-11-07 21:49:44 0|BlueMatt|cfields: its nice to have a tool to do it....anyway, I was asking for comments, would like to get comments ont he pr
80 2017-11-07 21:49:46 0|BlueMatt|on the
81 2017-11-07 21:50:35 0|cfields|ok, will do
82 2017-11-07 21:50:35 0|MarcoFalke|They would just sit around free for people to use and fix in case they break. Why not? Would at least encourage some to run the bench more often
83 2017-11-07 21:51:01 0|MarcoFalke|Or we could host a nightly bench on github pages
84 2017-11-07 21:52:11 0|cfields|if it can be setup so that you just supply your own plotly, that seems fine to me. But if it requires that we commit it, or fetch it, i'd be uneasy
85 2017-11-07 21:57:35 0|sipa|cfields: yes, it's just a url
86 2017-11-07 22:04:11 0|phantomcircuit|BlueMatt, 2.8 GB btw
87 2017-11-07 22:04:49 0|BlueMatt|phantomcircuit: E_NO_CONTEXT
88 2017-11-07 22:05:23 0|phantomcircuit|memory requirement under chromium for fibre stats page
89 2017-11-07 22:05:51 0|BlueMatt|yea, well also that stats page hasnt been updated in months cause I changed the network topology and haven't updated the stats-parsing script to actually understand the new topology
90 2017-11-07 22:26:21 0|bitcoin-git|[13bitcoin] 15sipa opened pull request #11630: Simplify Base32 and Base64 conversions (06master...06201711_simpleconvert) 02 https://github.com/bitcoin/bitcoin/pull/11630