Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/
Set by moderator on 9 December 2017.
jnthn Welcome :) 00:06
Bed time here; 'night o/ 00:17
bazzaar jnthn: here's the gist (not urgent :-), (gist.github.com/anonymous/5d3f85c4...87ee9c1fb) 01:09
03:01 ilbot3 joined
moderator Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/
10:19 sena_kun joined 10:24 bazzaar joined
bazzaar jnthn: that gist file must have expired, created another (still not urgent :) (gist.github.com/bazzaar/168b94d4eb...dce2313ff) 10:27
jnth: also I bit the bullet and tried to do the upgrade to 0.72, unfortunately no success (gist.github.com/bazzaar/9c794fa9ef...4da078d04) 11:01
jnthn Odd, it's ending up picking HTTP/2 even when there's no negotiation 13:44
14:10 Geth joined 15:33 scimon joined
japhb jnthn: github.com/croservices/sample-app-...ckage.json has a lot of specific versions in it. IIUC according togithub.com/npm/node-semver#caret-r...23-025-004 this means versions starting at the listed value and all other releases with the same major version (since all listed versions are at least 1.0.0). 17:36
This *seems* like it would be slow-moving enough to just use those versions in a default template of package.json, knowing that every few months, someone might want to test with latest values and upgrade the template. Do you agree with this assessment? 17:37
Being out of the frontend world for a while, I don't know how rapid node dependencies tend to be about major version upgrades.
jnthn The JavaScript world often feels like it operates in "move fast and break stuff" mode 17:38
japhb (Node itself being "disturbingly rapid for something that claims LTS releases")
Still? WTH, frontenders
jnthn :) 17:39
I'd expect major things like React, Redux, and Babel to be relatively stable
japhb remembers fondly how slow jQuery was to break compatibility back in the day
jnthn Given their wide usage
japhb Fair enough
Gah, not even 10 AM and my eyes are already tired ... 17:42
jnthn aww
jnthn wasn't even awake at 10 AM here...
japhb Lucky you!
:-)
jnthn Indeed :-) 17:43
Resting up before travel :)
20:05 bazzaar joined 21:51 Pat__ joined
Pat__ Hello... I am trying to install Cro on windows10 but I get an error and the installation hangs when installing Cro::TLS ... " # Failed test 'Listening for connections once the Supply is tapped' # at t\\tls.t line 39 # Cannot locate symbol 'SSL_CTX_set_default_verify_paths' in native library 'C:\\Users\\Patrick\\AppData\\Local\\Temp\\CC3194C8F3C5FE010D435C81DA195F6B1B4EF65E\\libeay32.dll' " 21:52
sena_kun Pat__, hi! I am on linux, but it seems like openssl library is no good to me. Could you please check if you're using an actual version of openssl? 22:23
*but it seems to me like 22:24
timotimo i believe cro downloaded(?) that dll file during installation
or maybe it's bundled 22:25
sena_kun is it? 22:26
don't see anything related to bundling, to be honest.
timotimo OK
just thought the path with its hashy dir name looked suspicious 22:27
sena_kun indeed
timotimo bbl
sena_kun Pat__, I will be happy if you could file an issue at github.com/croservices/cro-tls/issues with the error trace so we had some report to look at. 22:29
Pat__ Yes Cro is redownloading the file every time I try to install it 22:37
sena_kun: I am not using openssl 22:38
jnthn IO::Socket::Async::SSL depends on IO::Socket::SSL, which in turn bundles an openssl DLL on Windows 22:39
sena_kun oh, it explain things then.
jnthn But...perhaps not one that has that function 22:40
I might be able to have a poke at that on the train tomorrow, if there's wifi :)
(Laptop has Windows on it) 22:41
Windows/OSX porting work for Cro is still on the roadmap, I suspect there'll be least one other issue we have to take some care of 22:44
Pat__: In the meantime you can zef install --/test cro and that'll not run the tests
Pat__ so maybe if i manually find and replace the dll that comes with IO::Socket::SSL ?
jnthn If you need the SSL support, yeah
Pat__ I can live without it for now 22:45
jnthn OK, then install without running the tests
Pat__ I'll do that. Thanks jnthn. 22:47
btw I initially tried running with --force-test to install even if the tests fail... so it installed the dependencies... but Cro's test hangs so it could not install... 22:52