[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #19259 [Metrics/Onionoo]: uncaught NFE



#19259: uncaught NFE
-----------------------------+---------------------
 Reporter:  iwakeh           |          Owner:
     Type:  defect           |         Status:  new
 Priority:  High             |      Milestone:
Component:  Metrics/Onionoo  |        Version:
 Severity:  Major            |     Resolution:
 Keywords:                   |  Actual Points:
Parent ID:                   |         Points:
 Reviewer:                   |        Sponsor:
-----------------------------+---------------------

Comment (by iwakeh):

 And, also scan for `try`s w/o a `catch`. The try-with-resources closes the
 resource, but if an exception was the reason for that it should be logged.
 (the above code excerpt is surrounded by a try-with-resources statement).

 I see two tasks here:
 * checking for parsing statements that are not safeguarded against
 erroneous or unexpected input
 * check for `try`s w/o `catch`

 maybe, have a general try-catch inside `Main.run` to log unexpected
 exceptions?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19259#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs