Merge pull request #451 from lsst/tickets/DM-46948

DM-46948: Add NoWorkFound subclass that indicates an upstream failure
lsst · Oct 18, 2024 · fb5b7f0 · fb5b7f0
2 parents a403324 + f1a7c17
commit fb5b7f0
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 0 deletions.
diff --git a/doc/changes/DM-46948.feature.md b/doc/changes/DM-46948.feature.md
@@ -0,0 +1 @@
+Add `UpstreamFailureNoWorkFound`, an exception that is handled the same way as `NoWorkFound` that indicates that the root problem is probably in an upstream `PipelineTask`.
diff --git a/python/lsst/pipe/base/_status.py b/python/lsst/pipe/base/_status.py
@@ -39,6 +39,7 @@
     "UnprocessableDataError",
     "AnnotatedPartialOutputsError",
     "NoWorkFound",
+    "UpstreamFailureNoWorkFound",
     "RepeatableQuantumError",
     "AlgorithmError",
     "InvalidQuantumError",
@@ -67,6 +68,13 @@ class NoWorkFound(BaseException):
     """
 
 
+class UpstreamFailureNoWorkFound(NoWorkFound):
+    """A specialization of `NoWorkFound` that indicates that an upstream task
+    had a problem that was ignored (e.g. to prevent a single-detector failure
+    from bringing down an entire visit).
+    """
+
+
 class RepeatableQuantumError(RuntimeError):
     """Exception that may be raised by PipelineTasks (and code they delegate
     to) in order to indicate that a repeatable problem that will not be
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		Add `UpstreamFailureNoWorkFound`, an exception that is handled the same way as `NoWorkFound` that indicates that the root problem is probably in an upstream `PipelineTask`.