On Wed, Mar 9, 2022 at 6:22 PM Matthew Miller <mattdm(a)fedoraproject.org> wrote:
On Wed, Mar 09, 2022 at 12:14:28PM +0100, Alexander Sosedkin wrote:
> I left my crystal ball at home today,
> but I don't need it to say it'd be ~0 bugs filed if we log to syslog
> and ~3 if we log to stderr/stdout, all named
> "$CRYPTOLIB has no business messing up my stderr/stdout",
> which we'll promptly close by reverting the changes.
Yeah, that's a little more cynically-phrased than I'd put it, but I had
similar thoughts.
But: maybe if we logged it _and_ had a tool people could run to
look specifically for those log entries, we could do something like a Test
Day where people could send in reports?
On one hand, this still is a risky territory
of libraries leaning heavily into things that libraries shouldn't do
because they can never guess the weird ways they're being used
when they have existing interfaces to deny operations with some algorithms.
On the other hand, this makes much more sense to me
than the stdout/stderr proposal.
Especially if it accompanies a drawn-out multicycle change,
it could be a noticeable impact dampener.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure