On Mon, 13 May 2019 at 18:42, Bill Igoe <billi...@gmail.com> wrote: > > In a prop shop long ago , I also emailed all exception messages. It is a > great way to correct logic errors and capture potentially sloppy code. > Graphing the errors resulted in an exponential decline in errors. > > I also developed a handy performance tracker for critical algorithms and > saved those results to a log file. > > Helps a ton.
A 'ton' is the appropriate word - there have been over 100 emails to the dev@commons list complaining about the same problem. (They have not been moderated through as it would not help) It's only appropriate to email errors if they are sent to the people who can do something about the problem. In this case, that is the website developers who are using Collections incorrectly. Furthermore, they have exposed the Exception message to end users, which means we get the emails direct from end users. > Cheers to all > > > > > On Sun, May 12, 2019 at 3:22 PM Emmanuel Bourg <ebo...@apache.org> wrote: > > > Le 12/05/2019 à 14:25, Gary Gregory a écrit : > > > +1 to removing email addresses from exception messages. We should do a > > pass > > > over all of Commons. > > > > +1, makes sense. > > > > Emmanuel Bourg > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
