00:23 rmv left 01:53 kylese left, kylese joined 01:54 simcop2387 left, simcop2387 joined 01:56 MasterDuke joined 02:15 kylese left, kylese joined 02:37 guifa_ left 02:45 MasterDuke left 02:50 coverable6 left, unicodable6__ left, sourceable6 left, quotable6 left, shareable6 left, greppable6 left, tellable6 left, evalable6 left, committable6 left, linkable6 left, nativecallable6 left, huggable6 left, notable6 left, releasable6 left, bisectable6 left, bloatable6 left, benchable6 left 02:53 committable6 joined, coverable6 joined, greppable6 joined 02:54 unicodable6 joined, bloatable6 joined, nativecallable6 joined, benchable6 joined, bisectable6 joined 02:55 notable6 joined, quotable6 joined, linkable6 joined, releasable6 joined, shareable6 joined 02:56 evalable6 joined, sourceable6 joined, huggable6 joined, tellable6 joined
simon_sibl Voldenet: I did try the interval supply, which stops, but not sure if that’s cpu speed issue because the other supply even in the same thread continues to work.. but indeed I didn’t take into account ipv6 but worst case it should “simply” make the connection not work since the ip:port is wrong but not block the rest of the program to work 03:05
When the freeze happen, the tracker thread continues but get stuck at the http request step, the main thread continues to disconnect clients with timeout but that’s about it, even tho I added interval in the main file to show progress every 5s, it doesn’t do it, but that’s in the same thread so if one work, the others should work too.. ? 03:07
03:23 vasko4535586 left
Voldenet Cro::HTTP::Client has no timeout by default 03:42
or rather, it has timeout on connection and headers, but not body 03:44
by default
cro.raku.org/docs/reference/cro-ht...t#Timeouts
so perhaps tracker gets connected but fails for some reason 03:45
> use Cro::HTTP::Client; react whenever Cro::HTTP::Client.get($!uri, :timeout(10)) { whenever .body-blob { .say } } # consider this 03:54
04:11 tejr left 04:17 belluzj joined 04:34 [dpk] joined, inspork_ joined 04:35 releasable6 left, linkable6 left, coverable6 left, unicodable6 left, committable6 left, tellable6 left, evalable6 left, nativecallable6 left, benchable6 left, quotable6 left, notable6 left, dpk left, inspork left, coverable6 joined, releasable6 joined, linkable6 joined, inspork_ is now known as inspork
patrickb simon_sibl: Are you using Cro::HTTP::Client? If so, can you create an unencrypted TCP dump of the lock up? 04:40
04:40 tejr joined
Voldenet `start` is extremely good at covering up errors, so maybe it just dies 04:44
used to be, at least
what I'd do is something similar to this pastebin.com/GpBAG0vk 04:47
patrickb see github.com/croservices/cro-http/pull/162 04:48
for how to do that
i.e. a normal TCP dump dump + the ssl session key log 05:01
That then allows looking at the http procol. 05:02
Voldenet it's this piece of code, I think it connects to trackers from the file in that repo github.com/4zv4l/rbt/blob/main/lib...er.rakumod 05:05
still, wouldn't timeout catch tls hangs? 05:09
05:27 Sgeo left, Sgeo joined 06:18 rmv joined, rmv left, rmv joined 06:23 rmv left 07:18 rmv joined, rmv left, rmv joined 07:24 eseyman left 07:31 manu_ joined 07:32 manu_ is now known as eseyman 07:36 [dpk] is now known as dpk 07:59 kylese left 08:00 kylese joined
patrickb Not necessarily. If there is a bug in Cro's HTTP (2) stack (and there have been quite a few in the past) then a timeout most probably doesn't help. 10:12
10:42 guifa_ joined 10:50 belluzj left 10:51 Sgeo left 12:49 guifa_ left 12:59 guifa_ joined
guifa_ only one typo in my talk this year 13:30
lol
13:50 belluzj joined 13:52 belluzj left 13:55 guifa_ left 14:35 guifa_ joined 14:46 shareable6 left, huggable6 left, sourceable6 left, bloatable6 left, linkable6 left, bisectable6 left, coverable6 left, releasable6 left, greppable6 left 14:48 shareable6 joined 14:49 greppable6 joined, bloatable6 joined, nativecallable6 joined, quotable6 joined, linkable6 joined 14:50 unicodable6 joined, sourceable6 joined, huggable6 joined, tellable6 joined, releasable6 joined 14:51 bisectable6 joined, benchable6 joined, notable6 joined, committable6 joined, coverable6 joined 14:52 evalable6 joined 15:12 abraxxa joined 15:14 abraxxa left 15:15 abraxxa joined 15:28 guifa_ left 16:26 guifa_ joined
ugexe m: role N[::TValue] { has TValue @!x; }; N[Int].new; say 42 16:47
camelia 42
ugexe Voldenet ^ (from github.com/rakudo/rakudo/issues/6056)
17:56 wayland76 joined, wayland left 18:20 guifa_ left 18:29 guifa_ joined 18:32 MasterDuke joined 18:34 guifa_ left 19:15 Sgeo joined 19:34 MasterDuke left
Voldenet m: role N[::TValue] { has TValue @!x[$n]; }; N[Int].new 20:27
camelia ===SORRY!=== Error while compiling <tmp>
Variable '$n' is not declared. Perhaps you forgot a 'sub' if this was
intended to be part of a signature?
at <tmp>:1
------> role N[::TValue] { has TValue @!x[<HERE>$n]; }; N[Int].new
Voldenet m: my $n = 42; role N[::TValue] { has TValue @!x[$n]; }; N[Int].new
camelia ( no output )
Voldenet yeah, it sounds like it's all fixed 20:28
20:37 vrurg joined 20:39 rmv left, vrurg_ left 20:40 rmv joined, rmv left, rmv joined 21:07 MasterDuke joined 21:29 MasterDuke left 22:08 abraxxa left 22:39 AlexDaniel joined 22:42 bisectable6 left, bloatable6 left, unicodable6 left, notable6 left, tellable6 left, releasable6 left, huggable6 left, linkable6 left, sourceable6 left, quotable6 left, evalable6 left, benchable6 left, shareable6 left, coverable6 left, nativecallable6 left, committable6 left 22:46 greppable6 left 22:48 unicodable6 joined, linkable6 joined 22:49 evalable6 joined, shareable6 joined, bloatable6 joined, greppable6 joined 22:50 coverable6 joined, tellable6 joined, sourceable6 joined, benchable6 joined 22:51 nativecallable6 joined, releasable6 joined, committable6 joined, quotable6 joined, bisectable6 joined, notable6 joined, huggable6 joined
wayland76 patrickb: I misunderstood your problem. When I carefully read timo's followup, I understood it better, and think that the solutions that others have offered are the better ones for your situation. 23:58

Powered by Cro and the Raku® Programming Language.

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

Thank you!