GNOME Bugzilla – Bug 781532
Be more strict about invalid code paths
Last modified: 2021-07-05 11:31:30 UTC
Certain errors are indicative of outright programming flaws, as opposed to something that can possibly fail at run-time. Let's be more strict about these by throwing an exception. (The C equivalents would be to log a CRITICAL or abort with an assertion.)
Created attachment 350123 [details] [review] selections: Be more strict about invalid code paths
Created attachment 350124 [details] [review] documents: Tie the catch blocks more tightly to the failure sites
Created attachment 350125 [details] [review] documents: Be more strict about invalid code paths
Review of attachment 350123 [details] [review]: ++
Review of attachment 350124 [details] [review]: Good idea
Review of attachment 350125 [details] [review]: ++
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-documents/-/issues/ Thank you for your understanding and your help.