08:35 rakkable left, ab5tract left 08:37 ab5tract joined 10:41 librasteve_ left 13:12 coleman_ joined 13:13 coleman left, coleman_ is now known as coleman 13:45 notable6 left, notable6__ joined 13:47 greppable6__ joined 13:49 greppable6 left 13:55 nativecallable6_ joined 13:59 nativecallable6 left, refactus left 14:01 refactus joined, refactus left, refactus joined 14:12 librasteve_ joined 14:48 Pixi` joined 14:55 Pixi left, tbrowder left, tbrowder joined 15:04 Voldenet_ joined 15:07 coleman left, coleman_ joined, coleman_ is now known as coleman 15:08 Voldenet left, Voldenet_ is now known as Voldenet 15:47 timo1 joined 15:53 sivoais left, timo left 15:55 sivoais joined 16:41 librasteve_ left 16:48 samebchase7 joined 16:50 ntv joined 16:54 nativecallable6_ left, ab5tract left, apogee_ntv left, samebchase left, jdv left, samebchase7 is now known as samebchase 16:59 librasteve_ joined, jdv joined, nativecallable6 joined, ab5tract joined
[Coke] anyone have an issue with these conditions: partners.snyk.io/prm/English/c/dev...pplication 18:12
they do open source scanning (vulnerabilities, licenses, etc.), and you can get free setup for your open source project if you 1) don't have a corporate sponsor, 2) attribute snyk in your readme on the website, and grank snyk permission to use the logo "and related content" on their website. 18:14
Going to submit raku (but they will probably only be able to scan moarvm)
But that'll (probably) be a step towards them adding raku support in the future. (be nice if their project scanning recognized meta6.json files, etc.) 18:15
Submitted, but can back out if anyone sees an issue. 18:19
lizmat [Coke]++ 18:47
[Coke] we use it at dayjob, does a good job on JS & .NET 20:48
El_Che [Coke]: we use trivy in our CI: trivy.dev/ 20:49
(and sonarcube)
[Coke] we also use sonar/cube/cloud/ 20:55
22:21 rakkable joined
japhb I'd be happy with anything (with reasonable licensing terms for FOSS projects) that helps us nail more bugs in MoarVM. Because they always bubble up. 22:32
Oh that reminds me. lizmat, rak has a resource exhaustion bug in that it doesn't limit its concurrency settings to a combination that fits within the user's max open files limit. I discovered this running rak on a box with 20 hardware threads, where rak defaulted to 19 x 64 concurrency, but I only had 1024 max open files. Ooopsie. 22:35
22:41 librasteve_ left