On Saturday, January 18, 2020 6:31:11 PM MST John Reiser wrote: > On 2020-01-19 00:21 UTC, Ken Dreyer wrote: > > > On Sat, Jan 18, 2020 at 5:09 AM Richard W.M. Jones <rjones@xxxxxxxxxx> > > wrote: > [[snip]] > > >> Sorry, not a bug. I remembered that I had put some alternate > >> certificates into ~/.koji to access another Koji instance. > > > > > I think there is a usability RFE here. If we get an SSLError *and* the > > Koji client is configured to use one specific CA bundle file on disk, > > then we should log that path to the CA file we used. > > > +1. This is analogous to ENOENT, where the error message should include > the actual path that was attempted, and not just "File not found". > Even using a pronoun such as "configuration file not found" is not enough; > give the actual path. ENOENT is a much different scenario. In the case of ENOENT, what that actually means depends on what function you've just tried to call, and you know the path, if one is relevant. -- John M. Harris, Jr. Splentity _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
