From e4706232adfe7c6afbf85e25494732c1d66809c4 Mon Sep 17 00:00:00 2001 From: Mike Lang Date: Sun, 3 Nov 2019 07:30:15 -0800 Subject: [PATCH] cutter: Fix bug in handling cancellation before finalize it would always think it's finalized --- cutter/cutter/main.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cutter/cutter/main.py b/cutter/cutter/main.py index 83553c5..ec39944 100644 --- a/cutter/cutter/main.py +++ b/cutter/cutter/main.py @@ -341,7 +341,7 @@ class Cutter(object): if result.rowcount != 1: # If we hadn't yet set finalizing, then this means an operator cancelled the job # while we were cutting it. This isn't a problem. - if not finalize_begun: + if not finalize_begun[0]: raise JobCancelled() raise JobConsistencyError("No job with id {} and uploader {} when setting: {}".format( job.id, self.name, ", ".join("{} = {!r}".format(k, v) for k, v in kwargs.items())