|
Welcome the channel on the development of Cro, a set of libraries for building reactive distributed systems, lovingly crafted to take advantage of all the Raku Programming Language has to offer (cro.services). This channel is being logged for historical purposes. Set by lizmat on 24 May 2021. |
|||
|
01:02
Pe_Elle left
01:09
Pe_Elle joined
06:56
leont left
06:57
leont joined
07:43
sena_kun joined
09:19
sena_kun left
17:31
timo joined
|
|||
| timo | a fresh stubbed cro http service with http 1.1 and 2 and websocket is unable to load the fake certs that cro built for it: error:068000A8:asn1 encoding routines::wrong tag | 17:32 | |
| oh i see it does not generate the certs, those fake-tls certs are just shipped with the cro cli tool | 17:37 | ||
| Geth | cro: timo++ created pull request #162: fix links in readme |
17:42 | |
| timo | github.com/croservices/cro/issues/119 i believe this can just be closed since the pull-request that addresses it was merged long ago | 17:45 | |
| also, maybe more worrying than the parse failure with the certs is that the cro application still seems to run, but is then not listening on the socket it is configured to use, instead of stopping by itself, or erroring out more aggressive | 17:47 | ||
| -ly | |||
| Geth | cro: timo++ created pull request #163: Try a newer "oldest" raku version in CI |
17:54 | |
| timo | i hope the github action runs with my changes like that without some extra permissions or extra thumbs-up from an actual project owner | ||
| does the cro project have some kind of official stance on supporting specific older rakudo versions in a Long-Term Support kind of way? | 17:57 | ||
| then an option could be to use an older package that doesn't asplode | |||
| lizmat | the cro team is in a bit of a flux atm... perhaps make an issue for that | ||
| timo | sure, no hurries, just doing some drive-by contributions that are hopefully helpful? not meaning to heap work on the good folx | 17:58 | |
| well, it took me a while but i just saw the announcements from the beginning of the year | 18:06 | ||
| cool, the 2022.02 version of raku has no trouble installing the dependencies for croservices/cro. maybe i'll make PRs for the same change in the other croservices repos | 18:17 | ||
| would surely be a better look to have the CI badges not show "failing" :) | 18:18 | ||
| [Coke] | yes please! | 18:20 | |
|
18:39
sena_kun joined
|
|||
| timo | i'm not coming up with a good way to flow-control jump out of a get -> { ... } block with my error checks, i.e. i'd enjoy it if i could just `not-found unless $target.e` but that only sets a content and status, and execution just goes on. so i'll have to structure my code with more ifs, or if-else, or i need to build exceptions and an exception handler that does the not-found further outside which | 19:42 | |
| feels kinda redundant | |||
| but a try { ... } around everything and then "die not-found" (even though not-found doesn't return anything) *kinda* does it? :D it also eats other kinds of exceptions though which is not ideal | 19:58 | ||
| CATCH { when $! === Nil { note "my control flow!" } } is not the absolute worst ... | 20:01 | ||
| well, the documentation does warn against putting business logic into handlers | 20:24 | ||