🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
Geth rakudo/lizmat-fail-io-socket-inet: 14baac4659 | (Elizabeth Mattijsen)++ | src/core.c/IO/Socket/INET.pm6
Make unsuccessful connect fail rather than die

Spotted in stackoverflow.com/questions/726398...socketinet
There is no documentation or tests covering the behaviour of a failed connect. It is actually the nqp::connect that throws (which turns out also to be not documented BTW).
Having it return a Failure feels more natural indeed.		 08:35
rakudo: lizmat++ created pull request #4957:
Make unsuccessful connect fail rather than die
patrickb o/ 11:52
Geth rakudo/rakuast: 24 commits pushed by (Stefan Seifert)++
review: github.com/rakudo/rakudo/compare/c...52d61ec594		 12:37
carlmasak greetings, #raku-dev 13:17
lizmat carlmasak o/ 13:20
carlmasak hi, lizmat. it must be mid-afternoon in your part of the world 13:22
lizmat yea, 15:23 or so
carlmasak here in .cn, we start every day a few hours earlier than Europe
must be the work ethic
lizmat I guess... :-) 13:23
carlmasak :P 13:23
I know I mentioned it before, but I was one of the sad saps who bought a Beat watch from Swatch, many years ago 13:24
a "beat" is one thousandth of a 24-hour day, and you write the time like this: @499
and it's time zone independent
needless to say, this PR stunt from Swatch didn't catch on like wildfire 13:25
m: say (60 #`[seconds/minute] * 60 #`[minutes/hour] * 24 #`[hours/day]) / 1000 #`[beats/day] 13:30
camelia 86.4
carlmasak ...which makes a beat one minute and 26.4 seconds long.
lizmat feels a bit like Tau::Station::DateTime? 13:37
[Coke] does anything in the ecosystem given an idea of # of downloads/users, etc.? 13:39
lizmat raku.land keeps some stats I think 13:40
patrickb is working on the RCB (Rakudo CI Bot). 13:47
Currently implementing the branch matching logic. So when a commit in a PR should be tested it'll search for a matching branch in the respective other repos. 13:48
Should a requirement for a branch to be picked be, that a repective PR exists?
Or should it just take any same named branch in either the same project/user that the PR was created (or the rakudo/rakudo, Raku/nqp, MoarVM/MoarVM repos)? 13:50
For now I'll go with just taking any matching branch name and not requiring a PR. Please comment if you object. 13:55
nine I think that's a sensible thing to do 13:56
[Coke] I think if we were all in on an automated workflow, a PR would be required, but this matching branch-if-exists seems reasonable to me 13:57
Geth rakudo: vlmarek++ created pull request #4959:
Todo failing test on Solaris		 22:05
roast: vlmarek++ created pull request #810:
Make spectest pass on Solaris		 22:44

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!