Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: daf_butler
-
Labels:
-
Story Points:0.5
-
Epic Link:
-
Sprint:Arch 2019-07-29
-
Team:Architecture
Description
While debugging some changes I made related to the new astrometry code, I tripped over the except Exception as e: at posixDatastore.py::309, which swallows the initial exception. This, and any other such broad exception catching in daf_butler should use raise from exception chaining, so that the original exception information does not get lost.
Added some that are missing. I do wonder if the ones from getStoredFileInfo shouldn't be using from None instead of from e since the original exception really is irrelevant.