|
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. |
|||
|
02:13
lizmat_ joined
02:15
Geth left
02:16
lizmat left
06:27
Xliff_ joined
08:50
lizmat_ left
08:51
lizmat joined,
Geth joined
09:21
sena_kun joined
|
|||
| lizmat | Is there a particular reason why Cro::HTTP cannot be installed without forcing tests ? | 10:06 | |
| github.com/croservices/cro-http/issues/158 | 10:12 | ||
|
10:35
AlexDaniel left
|
|||
| jnthn | Yes, TLS tests depend on having a cert, but certs can only have a validity date so far into the future, which means after a while they expire, and the tests start failing | 10:35 | |
| The certs have already been regenerated, but given this has happened multiple times, I'm going to also move these tests under xt/ rather than t/ so they won't be run as the standard set of install-time tests. | 10:36 | ||
| (So we don't have a repeat of this in the future) | |||
| Otherwise we just repeat this in another year. | |||
|
10:38
AlexDaniel joined
|
|||
| lizmat | yeah, moving them to xt feels like the correct choice | 10:39 | |
| jnthn wonders how many langs aside from Perl and Raku default to running module tests as part of their installation | 10:44 | ||
| lizmat | maybe they generate a new certificate during testing somehow ? | 10:48 | |
| jnthn | No, I mean, Raku is a relative outlier in running tests *at all* as part of installing a module. | 10:51 | |
| lizmat | ah, ok, yes... I guess | 10:53 | |
| I'm so used to that never thought it would be different anywhere else :-) | |||
| jnthn | This year aside from Raku I've worked in Node.js, .Net, Python, and Java, and none of them do it, thus my curiosity of who else does. :-) | 10:57 | |
| I guess the upside is "faster module installation" and the downside is "but who knows if it works on my machine". | 10:58 | ||
| lizmat | well, this was a case of a false negative :-( | ||
|
15:44
rypervenche left
16:12
rypervenche joined
16:24
melezhik joined
16:39
melezhik left
16:58
melezhik joined
17:19
melezhik left
17:22
melezhik joined
17:53
xinming left
18:00
xinming joined
18:01
melezhik left
18:15
sena_kun left
18:18
sena_kun joined
19:48
sena_kun left
19:50
sena_kun joined
|
|||
| Geth | cro-tls: 6a42be31ad | (Jonathan Worthington)++ | 13 files Move certificate-dependent tests to xt/ This means they are not run as part of module installation. It seems we can only generate a certificate with a validity of a year, but there's no reason to block installation of the module because a test certificate became too old. |
21:24 | |
|
22:10
xinming left
22:11
xinming joined
|
|||
| Geth | cro-tls: d41b995880 | (Jonathan Worthington)++ | .github/workflows/ci.yml Try getting CI to run t/ and xt/ And remove MacOS, since it breaks over the OpenSSL dependency. |
22:13 | |
| cro-http: f88e9b12d4 | (Jonathan Worthington)++ | 23 files Move certificate-dependent tests into xt/ So that expiration of the certificates doesn't cause test failures. The certificate can only be valid for a year, which is not all that long. |
22:28 | ||
|
22:48
sena_kun left
22:55
Xliff left
|
|||