--- Log opened Fri Jul 27 00:00:22 2018 00:21 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 00:40 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 00:42 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 00:52 -!- murrayn [~dafuq@unaffiliated/murrayn] has quit [Quit: Adios mofos] 00:54 -!- ken2812221 [~User@1.200.198.248] has quit [Quit: Leaving] 00:54 -!- timothy [tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:01 -!- csknk [~csknk@unaffiliated/csknk] has joined #bitcoin-core-dev 01:02 -!- csknk [~csknk@unaffiliated/csknk] has quit [Client Quit] 01:08 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 01:13 -!- polydin [~delphi@2602:306:b8b6:b970:18b3:4dc2:268f:c5cc] has quit [Ping timeout: 256 seconds] 01:15 < jonasschnelli> sipa: would adding 'h' as equivalent to ' in the descriptor xpub/xpriv range definition makes sense? >'< in conjunction with JSON and the GUI/bitcoin-cli/shell seems to be a hassle 01:18 -!- csknk [~csknk@unaffiliated/csknk] has joined #bitcoin-core-dev 01:18 -!- csknk [~csknk@unaffiliated/csknk] has quit [Client Quit] 01:21 -!- csknk [~csknk@unaffiliated/csknk] has joined #bitcoin-core-dev 01:22 -!- csknk [~csknk@unaffiliated/csknk] has quit [Client Quit] 01:22 -!- csknk [~csknk@unaffiliated/csknk] has joined #bitcoin-core-dev 01:30 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:37 -!- vicenteH [~user@195.235.96.150] has joined #bitcoin-core-dev 02:37 -!- go1111111 [go1111111@gateway/vpn/privateinternetaccess/go1111111] has quit [Ping timeout: 240 seconds] 02:54 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:08 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 03:14 -!- csknk [~csknk@unaffiliated/csknk] has quit [Ping timeout: 260 seconds] 04:45 -!- exit70 [sid231392@gateway/web/irccloud.com/x-qbqfqojfbpqftske] has quit [Ping timeout: 256 seconds] 04:45 < sipa> jonasschnelli: yes perhaps; but for compatibility with existing RPCs i stayed with ' 04:46 -!- exit70 [sid231392@gateway/web/irccloud.com/x-vwoabewaeovhokka] has joined #bitcoin-core-dev 04:53 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 04:54 < jonasschnelli> sipa: is think it should not be OR, it should be AND 04:54 < jonasschnelli> support ' AND h 04:56 -!- vicenteH [~user@195.235.96.150] has quit [Read error: Connection reset by peer] 04:57 -!- vicenteH [~user@195.235.96.150] has joined #bitcoin-core-dev 05:00 -!- jtimon [~quassel@213.28.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 05:37 -!- csknk [~csknk@unaffiliated/csknk] has joined #bitcoin-core-dev 06:03 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 06:06 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [] 06:17 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 06:20 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 06:23 -!- jpe_ [~jpe@200116b84209f800147509125f2bc37d.dip.versatel-1u1.de] has quit [Quit: Leaving] 06:23 -!- jpe [~jpe@200116b84209f800147509125f2bc37d.dip.versatel-1u1.de] has joined #bitcoin-core-dev 06:27 -!- setpill [~setpill@unaffiliated/setpill] has quit [Ping timeout: 260 seconds] 06:29 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 06:30 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 06:52 -!- profmac [~ProfMac@2001:470:1f0f:226:8040:bd1d:20fc:fc4f] has quit [Ping timeout: 276 seconds] 07:20 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 07:26 < brighton36> so, I'm looking to find out a few things about the bitcoincore.org site. Chiefly, content changes are delegated. Who can I speak to about that? 07:26 < brighton36> *how 07:26 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 07:27 < brighton36> Is there a policy somewhere perhaps? 07:29 -!- csknk [~csknk@unaffiliated/csknk] has quit [Quit: leaving] 07:31 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 07:35 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 07:40 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 07:48 < harding> brighton36: I help maintain the site. I don't relaly understand your question. There's a basic contributing policy at https://github.com/bitcoin-core/bitcoincore.org/blob/master/CONTRIBUTING.md but the basic process is the same for any open source project: people open PRs proposing changes, other people provide feedback, once the feedback is generally positive, the PR is merged. If the PR never gets to that stage, it's 07:48 < harding> eventually closed. If there's something wonky going on (like lots of comments from unknown accounts), that's factored into the merge/no-merge decision. 08:08 < brighton36> thank-you harding :) 08:08 < brighton36> I get that this is a heavily politicized issue. But, I'd like to know what the process is 08:08 < brighton36> I think a mission statement would help greatly 08:09 < brighton36> less would obviously be more, but, just being able to point at a mission would help us out greatly 08:09 < brighton36> Borrowing one from any other prominent open source project, and redacting specifics would seem productive. Less is more. 08:10 -!- harrymm [~harrymm@69.161.195.103] has quit [Ping timeout: 248 seconds] 08:10 < brighton36> Is there a process by which the stakeholders could decide that, or is a PR the process? 08:10 < harding> brighton36: I'm not sure what you're talking about, but it feels a bit off topic for this channel. Would you mind joining #bitcoin-core-website to discuss further? (Or you can PM me if you're a registered user.) 08:10 < brighton36> yep 08:10 < brighton36> thank-you sir 08:12 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Quit: Konversation terminated!] 08:20 -!- marcinja_ [~marcin@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Remote host closed the connection] 08:20 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 08:25 -!- savil [~savil@c-71-202-1-72.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 08:34 -!- vicenteH [~user@195.235.96.150] has quit [Ping timeout: 256 seconds] 08:44 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 08:45 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 08:48 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 08:49 -!- |EHG| [|EHG|@gateway/vpn/privateinternetaccess/ehg/x-82069683] has quit [Quit: |EHG|] 08:50 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 08:55 -!- |EHG| [|EHG|@gateway/vpn/privateinternetaccess/ehg/x-82069683] has joined #bitcoin-core-dev 08:55 -!- |EHG| [|EHG|@gateway/vpn/privateinternetaccess/ehg/x-82069683] has left #bitcoin-core-dev [] 09:00 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 09:01 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 09:02 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:658f:7cd8:c293:965c] has joined #bitcoin-core-dev 09:06 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 265 seconds] 09:06 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 09:12 -!- dqx__ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 09:12 -!- dqx__ [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 09:15 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Ping timeout: 265 seconds] 09:31 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/] 09:34 -!- jarthur [~jarthur@pool-108-4-183-133.ronkva.east.verizon.net] has joined #bitcoin-core-dev 09:40 -!- leishman [~leishman@50.237.113.98] has joined #bitcoin-core-dev 09:52 -!- leishman___ [32ed1d16@gateway/web/freenode/ip.50.237.29.22] has joined #bitcoin-core-dev 09:53 -!- leishman___ [32ed1d16@gateway/web/freenode/ip.50.237.29.22] has left #bitcoin-core-dev [] 10:26 -!- rex4539 [~rex4539@2a02:587:3516:600:755d:6904:8b22:298] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 10:26 -!- jarthur [~jarthur@pool-108-4-183-133.ronkva.east.verizon.net] has quit [] 10:32 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 10:36 -!- timothy [tredaelli@redhat/timothy] has quit [Ping timeout: 260 seconds] 10:40 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:658f:7cd8:c293:965c] has quit [Ping timeout: 260 seconds] 10:45 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:658f:7cd8:c293:965c] has joined #bitcoin-core-dev 10:55 -!- rex4539 [~rex4539@2a02:587:3516:600:9dd7:eaf3:ccba:938a] has joined #bitcoin-core-dev 11:23 < sipa> MarcoFalke: AssertionError: not(0.00700000 == 0.007) 11:23 < sipa> any idea how to deal with that in tests? 11:24 < luke-jr> sipa: maybe assert_approx? 11:25 < sipa> i don't see that anywhere in our source code 11:25 < sipa> this can't be the only place where this is an issue 11:25 < sipa> so i must be doing something wrong 11:25 < sipa> (it's ValueFromAmount output in RPC 11:26 < sipa> i'll just try to stick to integer amounts 11:26 < luke-jr> sipa: test/functional/wallet_groups.py 11:30 < sdaftuar> sipa: are both values coming from rpc calls, or is one hardcoded in? i think we use Decimal() in the test framework a bunch, presumably to solve that problem 11:31 < sipa> sdaftuar: ah! 11:31 < sipa> one is hardcoded 11:33 < jonasschnelli> sipa: re xpub range in descriptors... 11:33 < gmaxwell> :( even we can't get it right. 11:34 < jonasschnelli> sipa: if you disagree with the index <= vs <, then I guess you need to +1 when populating the range from the JSON or change the doc 11:34 < jonasschnelli> Because the doc states: "\"range\": n, (numeric, optional) Up to what child index HD chains should be explored (default: 1000)\n"" 11:34 < jonasschnelli> if you pass in 1000, it will only derive up to 999 11:35 < jonasschnelli> I think the doc is correct and would recommend to +1 somewhere else 11:37 < sipa> jonasschnelli: good point 11:38 < jonasschnelli> IMO if one puts a range of 1500, then one probably expect that key at index 1500 will be included... 11:39 < jonasschnelli> sipa: why not a real range X-Y? instead of pure Y? 11:39 < sipa> ok, will fix 11:39 < sipa> jonasschnelli: sounds like something for a later extension? 11:39 < jonasschnelli> (although could be changed later) 11:39 < jonasschnelli> agree 11:42 < sipa> GAH 11:42 < sipa> AssertionError: not(0.00200000 == 0.00200000000000000004163336342344337026588618755340576171875) 11:44 < sdaftuar> sipa: i think you need to do `Decimal("0.002")`? 11:45 < sdaftuar> at least, that's what i see all over our python test code 11:46 < sipa> sdaftuar: thanks! that works 11:47 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 11:50 -!- jtimon [~quassel@213.28.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 11:54 -!- rex4539 [~rex4539@2a02:587:3516:600:9dd7:eaf3:ccba:938a] has quit [Quit: Textual IRC Client: www.textualapp.com] 11:56 < sipa> jonasschnelli: regarding support for "h" instead of "'", should it roundtrip? 11:56 < jonasschnelli> no... I think only input 11:56 < sipa> ok, that's easy enough then 11:56 < jonasschnelli> Yes. 11:57 < jonasschnelli> I guess no-one will complain about the missing roundtripness... 11:57 < jonasschnelli> IMO it's mainly useful to bypass shellish input sources 11:57 < jonasschnelli> *shellish input source restrictions 11:58 -!- satwo [~textual@2602:306:378a:6fb0:a8dd:332e:b9f1:5be8] has joined #bitcoin-core-dev 12:04 < satwo> Has the bitcoind config param -rpcclienttimeout been removed? I'm getting errors trying to set it in both the command line and in bitcoin.conf. 12:04 -!- rex4539 [~rex4539@2a02:587:3516:600:9dd7:eaf3:ccba:938a] has joined #bitcoin-core-dev 12:05 < sipa> satwo: no, but it's a bitcoin-cli command line option; not a bitcoind one 12:06 < satwo> Thanks sipa. This doc may need updating then: https://github.com/bitcoin/bitcoin/blob/master/contrib/debian/examples/bitcoin.conf 12:09 < satwo> Would it be appropriate to remove the section for rpcclienttimeout there? Or am I missing something? 12:09 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 12:10 < sipa> in bitcoin.conf it should work fine; that file should be read by both bitcoind and bitcoin-cli 12:10 -!- go1111111 [~go1111111@199.231.240.191] has joined #bitcoin-core-dev 12:11 < satwo> That's what I thought, but I got the following error when starting bitcoind: Error reading configuration file: Invalid configuration value rpcclienttimeout 12:12 < sipa> oh, of course 12:13 < sipa> right; you can't put it in bitcoin.conf anymore, because it's not a bitcoind option 12:13 < sipa> and since 0.17 bitcoind will give an error if an invalid option is passed 12:13 < sipa> we could add an exception to ignore it 12:16 < satwo> For just that one param? 12:16 < sipa> no, this is true for every parameter 12:16 < sipa> in earlier versions bitcoind would just ignore unknown options; now it will give an error 12:20 < satwo> Got it. What do you mean exactly by adding an exception to ignore it? Show the error/warning but allow bitcoind to start anyway? 12:20 < sipa> but we should probably make it ignore bitcoin-cli only options like this one, when present in bitcoin.conf 12:20 < wumpus> it's good that it now gives errors on unkonwn options, this was a long-running issue 12:20 < wumpus> but yes, that's firly annoying too... 12:21 < wumpus> sipa: though that means that all executables need to have knowledge of all other executables' flags 12:21 < wumpus> which is exactly what we were trying to avoid by modularizing the options system 12:21 < sipa> wumpus: or we need a way to specify bitcoin.conf options that only apply to a particular binary 12:21 < wumpus> it's kind of annoying, maybe cli-specific options could have their own sections? 12:21 < sipa> like the network sections 12:21 < wumpus> right 12:22 < wumpus> for 0.17 I agree we could just make it a warning 12:22 < wumpus> if an unknown option is specified 12:22 < wumpus> then for 0.18 think about for to sensibly enforce this 12:23 < sipa> that's one possibility 12:23 < sipa> or we could use the deprecation mechanism 12:23 < sipa> (by default it's enforced, unless you pass -ignoreunknownconfigoptions or so; and then it still only applies to bitcoin.conf and not to command line options) 12:24 < wumpus> yes 12:27 < luke-jr> wumpus: actually, it might be annoying if users get errors for Knots configs in bitcoin.conf 12:28 < luke-jr> perhaps there should be a way to explicitly say "don't error if you don't understand this" 12:28 < wumpus> sipa has a good point 12:28 < luke-jr> per-option seems safer IMO 12:28 < wumpus> make it an error if an unknown option on the command line 12:28 < luke-jr> though we could do both 12:28 < wumpus> but a warning if in bitcoin.conf 12:28 < luke-jr> sure 12:39 < satwo> Happy to attempt an implementation of this, if no one else wants to knock it out. 12:42 < sipa> i vaguely remember we already have an exception for some option, but i can't check right now 12:43 -!- grubles [~grubles@unaffiliated/grubles] has joined #bitcoin-core-dev 12:49 -!- polydin [~delphi@2602:306:b8b6:b970:ddb8:954:b1bd:ceea] has joined #bitcoin-core-dev 12:53 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 256 seconds] 12:59 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 13:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 13:01 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 13:04 -!- savil [~savil@c-71-202-1-72.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 13:16 < wumpus> satwo: would be awesome 13:17 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Quit: Leaving] 13:27 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 13:46 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 13:47 < satwo> wumpus: Will work on it this weekend. Still learning C++ but I'll do the best I can 13:57 -!- booyah is now known as booyah_ 14:00 < cfields> jonasschnelli: 0.16.2 macOS signature ping :) 14:05 -!- michaelsdunn1 [~mdunn@38.126.31.226] has joined #bitcoin-core-dev 14:15 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 14:18 < jonasschnelli> cfields: Oh. Yes. Just started the build,... will PR the detatched sig tomorrow (in 10-12h). 14:23 < cfields> jonasschnelli: np, thanks 14:27 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:658f:7cd8:c293:965c] has quit [Ping timeout: 276 seconds] 14:38 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:658f:7cd8:c293:965c] has joined #bitcoin-core-dev 14:39 -!- savil [~savil@c-71-202-1-72.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 14:42 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 14:44 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 14:45 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 248 seconds] 15:07 -!- LKbTkXFn [~kanotix@80.178.110.155.adsl.012.net.il] has joined #bitcoin-core-dev 15:14 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Quit: https://www.Quanto.ga/] 15:37 -!- jhfrontz [~Adium@cpe-184-57-118-36.columbus.res.rr.com] has joined #bitcoin-core-dev 15:39 -!- spinza [~spin@155.93.246.187] has quit [Ping timeout: 255 seconds] 15:55 < jhfrontz> Is there anything that needs to be done to enable use of the 0.16.2 version of contrib/gitian-descriptors/gitian-linux.yml (when using a docker-based gitian build)? 15:56 < jhfrontz> I'm getting errors about missing symbols (like described here: https://github.com/bitcoin/bitcoin/issues/12511#issuecomment-386740137 ). 16:01 -!- michaelsdunn1 [~mdunn@38.126.31.226] has quit [Remote host closed the connection] 16:03 < jhfrontz> It looks like all the signers of 0.16.2 for linux so far have used "trusty" (instead of the 0.16.2-gitian-linux.yml-spec'd "bionic"). So maybe I shouldn't be using the new version? 16:03 < wumpus> yes 0.16.2 is built with trusty 16:03 < wumpus> no releases yet have been built with bionic, though this is the plan for 0.17 16:05 < sipa> jhfrontz: if you build on bionic (even if it works), you won't get the same binaries as others 16:06 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 16:06 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 260 seconds] 16:06 < jhfrontz> OK, tnx. I must've pulled down the wrong version? 16:07 < wumpus> I guess so? I'm not sure how you end up in that situation at all, the descriptors on the 0.16 branch shouldn't point to bionic 16:07 < jhfrontz> of gitian-linux.yml, I mean 16:07 < jhfrontz> doh, wrong branch… 16:07 < sipa> https://github.com/bitcoin/bitcoin/blob/v0.16.2/contrib/gitian-descriptors/gitian-linux.yml <- specifies trusty 16:08 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 16:29 -!- leishman [~leishman@50.237.113.98] has quit [Remote host closed the connection] 16:44 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 264 seconds] 16:49 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 17:01 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 17:02 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 17:09 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 17:29 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 17:30 -!- IGHOR [~quassel@93.178.216.72] has quit [Remote host closed the connection] 17:31 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 17:35 -!- IGHOR [~quassel@93.178.216.72] has joined #bitcoin-core-dev 18:04 -!- jpe_ [~jpe@200116b84285530079eef810c99a8f5e.dip.versatel-1u1.de] has joined #bitcoin-core-dev 18:07 -!- jpe [~jpe@200116b84209f800147509125f2bc37d.dip.versatel-1u1.de] has quit [Ping timeout: 260 seconds] 18:20 -!- savil [~savil@c-71-202-1-72.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 18:21 -!- savil [~savil@c-71-202-1-72.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 18:21 -!- savil [~savil@c-71-202-1-72.hsd1.ca.comcast.net] has quit [Client Quit] 18:47 -!- savil [~savil@c-71-202-1-72.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 18:48 -!- savil [~savil@c-71-202-1-72.hsd1.ca.comcast.net] has quit [Client Quit] 18:51 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:658f:7cd8:c293:965c] has quit [Ping timeout: 265 seconds] 18:51 -!- savil [~savil@c-71-202-1-72.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 18:53 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has quit [Ping timeout: 248 seconds] 18:55 -!- murrayn [~dafuq@unaffiliated/murrayn] has joined #bitcoin-core-dev 18:57 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:bc7a:6d20:9548:affd] has joined #bitcoin-core-dev 19:08 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 19:10 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 19:10 -!- jtimon [~quassel@213.28.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 19:20 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 19:24 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 19:32 -!- murrayn [~dafuq@unaffiliated/murrayn] has quit [Quit: Adios mofos] 19:41 -!- savil [~savil@c-71-202-1-72.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 20:16 < windsok> +1 to making invalid options in bitcoin.conf a warning. I'm having trouble figuring out which option is causing the error 20:17 < warren> windsok: +1 20:21 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 20:23 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 20:24 -!- d9b4bef9 [~d9b4bef9@207.38.86.239] has joined #bitcoin-core-dev 20:25 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds] 20:44 -!- LKbTkXFn [~kanotix@80.178.110.155.adsl.012.net.il] has quit [Quit: Leaving] 20:53 -!- murrayn [~dafuq@unaffiliated/murrayn] has joined #bitcoin-core-dev 20:57 -!- satwo [~textual@2602:306:378a:6fb0:a8dd:332e:b9f1:5be8] has quit [Quit: Textual IRC Client: www.textualapp.com] 21:00 -!- Orion3k [~Orion3k@24-176-200-142.static.mtpk.ca.charter.com] has quit [Ping timeout: 268 seconds] 21:33 -!- Orion3k [~Orion3k@24-176-200-142.static.mtpk.ca.charter.com] has joined #bitcoin-core-dev 21:50 -!- ken2812221 [~androirc@36-226-69-128.dynamic-ip.hinet.net] has joined #bitcoin-core-dev 21:51 < ken2812221> Seems like mingw does not support wchar_t in filename, but msvc do. 21:52 < ken2812221> what I am talking about is fstream. 21:54 < ken2812221> mingw do provide _wfopen that support wchar_t filename, but they don't have the same support on C++ fstream. 21:56 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 22:11 -!- ken2812221 [~androirc@36-226-69-128.dynamic-ip.hinet.net] has quit [Read error: Connection reset by peer] 22:22 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 22:24 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 22:27 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 22:35 -!- vicenteH [~user@54.104.135.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 22:45 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:bc7a:6d20:9548:affd] has quit [Remote host closed the connection] 22:45 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:bc7a:6d20:9548:affd] has joined #bitcoin-core-dev 22:50 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:bc7a:6d20:9548:affd] has quit [Ping timeout: 256 seconds] 22:57 < luke-jr> hm, this looks useful https://gcc.gnu.org/onlinedocs/gcc/x86-Built-in-Functions.html#index-_005f_005fbuiltin_005fcpu_005fsupports-1 22:58 < luke-jr> sipa: ^ 23:06 -!- no_input_found [no_input_f@gateway/vpn/privateinternetaccess/noinputfound/x-24977668] has quit [Remote host closed the connection] 23:06 -!- no_input_found [no_input_f@gateway/vpn/privateinternetaccess/noinputfound/x-24977668] has joined #bitcoin-core-dev 23:22 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:a466:8115:e1ad:7bb7] has joined #bitcoin-core-dev 23:23 -!- masonicb_ [~masonicbo@2600:8802:5501:17c0:cc41:3f7a:f860:23e1] has joined #bitcoin-core-dev 23:24 -!- masonic__ [~masonicbo@2600:8802:5501:17c0:4018:fb8c:1998:574a] has joined #bitcoin-core-dev 23:25 < sipa> luke-jr: hmm, how portable? 23:25 -!- masoni___ [~masonicbo@2600:8802:5501:17c0:14ba:6e28:8ef7:4f47] has joined #bitcoin-core-dev 23:27 < luke-jr> x86 only I think 23:27 -!- masonicboom [~masonicbo@2600:8802:5501:17c0:a466:8115:e1ad:7bb7] has quit [Ping timeout: 265 seconds] 23:27 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has quit [Quit: ZNC - http://znc.in] 23:28 < luke-jr> apparently introduced in GCC 4.8 23:28 -!- masonicb_ [~masonicbo@2600:8802:5501:17c0:cc41:3f7a:f860:23e1] has quit [Ping timeout: 265 seconds] 23:29 -!- masonic__ [~masonicbo@2600:8802:5501:17c0:4018:fb8c:1998:574a] has quit [Ping timeout: 265 seconds] 23:29 < luke-jr> Clang 3.8 23:30 -!- masoni___ [~masonicbo@2600:8802:5501:17c0:14ba:6e28:8ef7:4f47] has quit [Ping timeout: 260 seconds] 23:43 < sipa> luke-jr: i mean clang etc --- Log closed Sat Jul 28 00:00:23 2018