Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/
Set by moderator on 8 December 2017.
jnthn Cro is on Perl 6 Advent today: perl6advent.wordpress.com/2017/12/...-with-cro/ 00:04
timotimo jnthn: what's asycnrhonous? :) 00:29
also, is there any need to explain why the requestparser is instantiated but the response serializer is just the type object?
jnthn Fixed typo 00:43
Should perhaps of stuck .new on both
timotimo nice post in any case :) 00:44
jnthn :) 00:57
Sleep time for me, 'night
timotimo night jnthn 01:12
03:00 ilbot3 joined
moderator Cro: libraries and tools for building reactive services in Perl 6 | cro.services/ | Logs: irclog.perlgeek.de/cro/
japhb jnthn++ # Nice advent post 03:35
05:08 bazzaar joined
bazzaar o/ cro 05:09
05:11 japhb joined 05:12 bazzaar joined
bazzaar excellent advent calendar post, thanks 05:12
05:14 Geth joined
bazzaar slight issue with formatting in the code sections, cutting and pasting into a text editor results in code lines separated by lots of blank lines. 05:14
05:15 jnthn joined
bazzaar minor inconvenience, that's all 05:15
also, maybe it's my setup, but I seem always to have difficulty upgrading cro with zef 05:17
zef install --/test cro ... just results in 'All candidates are currently installed' 05:20
I got into an almighty tangle upgrading to v.0.71, eventually resorting to a Rakudo Star re-install, before the cro install 05:23
not complaining though, far from it, very appreciative of all the effort and expertise by the team to build such a polished product 05:28
Definitely think that a book on web programming using cro and Perl 6 could be a best seller. ( especially if it had a chapter utilising DBIish :-) 05:37
09:10 cdc joined
cdc just a couple of words to say that Cro looks amazing! (reactive programming, HTTPS/2, WebSocket, NFA matching, ...) 09:14
..., signature matching, ...) 09:15
09:25 sena_kun joined
jnthn cdc: :) 12:12
Hm, wonder what the upgrade issue bazzaar is running into is. 12:13
Maybe it needs a `zef update` first; 0.7.0 was distributed with git, but 0.7.1 and later using proper releases on CPAN
timotimo it's that zef will refuse to upgrade a module if an older version is already installed 12:14
it still fails even after "zef update"
i.e. i grepped "zef list" and it had the newer ones, but "zef list --installed" still had only the older ones
jnthn I thought it only did that if the version in META6.json hadn't been bumped? 12:22
timotimo not sure what's going on 12:24
i could be on a too old zef?
jnthn Maybe that also 12:27
Curious.
20:56 lizmat joined 22:10 bazzaar joined
bazzaar o/ cro 22:16
jnthn o/ 22:18
bazzaar hi, I'm following the Cro advent calendar post, it's very clearly written, and will really help me to understand how to build reactive services with perl6 22:21
jnthn Glad it was helpful :) 22:22
I hoped it'd generate a bit of interest.
bazzaar I haven't really worked with multi component code over the years, so I am having to re-wire my brain a little :-) 22:24
I'm guessing I need to upgrade to Cro 0.72, because I get a 'Client's HTTP/2 preface value is incorrect' message when running the Cro::HTTP::Server (for https) 22:28
zef info cro .. reports .. Identity: cro:ver<0.7.1> 22:30
however 'zef install --/test cro' then just says 'All candidates are currently installed, no reason to proceed', and I'm a bit reluctant to try --force-install 22:32
On the cro 'Getting Started' page, there is just the instruction for a new (first time?) install. I'm wondering if it would be useful to have instructions on how to upgrade to a new cro version too? 22:36
Just trying to help with constructive feedback, with the aim being to help others following along 22:38
jnthn Yeah, it's a fair idea to have some upgrade note on there 22:40
I wonder if `zef update && zef upgrade cro` is enough to get it to update the various dependencies 22:41
'Client's HTTP/2 preface value is incorrect' suggests the client didn't send a HTTP/2 preface; what was the client? 22:42
bazzaar 'zef upgrade cro' was what got me into a tangle for 0.71 previously :) 22:43
jnthn Yeah, I'll have to take a look at what exactly happens
That the obvious thing doesn't just week is a pretty strong case for documenting this :) 22:44
bazzaar the client was just a curl request in a different shell, on the same machine.
jnthn OK, check that your curl supports HTTP/2
I was somewhat surprised to discover that on Ubuntu 16.04, which isn't all that old, I had to build a new curl to get that, as the one from the package manager didn't have that. 22:45
I don't know what the situation is on other distros, OSes, etc.
Also, fair warning: the HTTP/2 support is certainly one of the areas where Cro's current BETA status very much applies. So any problem you're seeing could certainly be something not quite right in Cro also 22:46
Gotta go for a bit; bbl 22:47
bazzaar I got it to run for the preceding Cro::TLS example using 'curl -k localhost:4242/' >>> Muskox Rocks!
jnthn Do curl -v -k ... 22:48
It will show you if it's actually negotiating/using HTTP/2
bazzaar thanks for that, will try :)
jnthn OK, will check back here in an hour or so :) 22:49
jnthn back 23:34
bazzaar been trying to figure it out, might be falling back to HTTP/1 23:38
my curl is v.7.37.0 (x86_64-suse-linux-gnu) libcurl/7.37.0 OpenSSL/1.0.2j zlib/1.2.8 libidn/1.28 libssh2/1.4.3
Opensuse Leap 42.3
might be down to my 'certs-and-keys' dir location? Built them for first time ever, yesterday :), moved the dir into the same directory as the perl6 script 23:41
so many places for me to have screwed up, don't want to take up your time jnthn, you have helped with the curl -v option, it's given me some options to research 23:43
thanks for that :)
jnthn bazzaar: If you can share the curl -v output, I might be able to read something more into it 23:45
Also, did you configure with :http<2> or :http<1.1 2> ?
(I'm actually quite interested in seeing failure modes, because if you've hit them, somebody else will) 23:46
bazzaar configured with :http<1.1 2>
how best to share the curl -v output? 23:47
jnthn OK, then it should fall back to 1.1 if curl can't support it, which suggests to me something very fishy is going on
gist.github.com/
Paste it there
Also, if you run your example with CRO_TRACE=1 set in the environment, then it'll dump a bunch of output on how the server saw things too 23:48
bazzaar will do, and will try to annotate the gist, showing the different runs so it's hopefully clearer, thanks for helping, jnthn. 23:50