fix: don't report SIGTERM & friends to Sentry

lib/zinnia.js

@@ -169,7 +169,7 @@ const catchChildProcessExit = async ({
         const exitReason = p.exitCode
           ? `with exit code ${p.exitCode}`
           : p.signalCode ? `via signal ${p.signalCode}` : undefined
-        throw Object.assign(err, { moduleName: p.moduleName, exitReason })
+        throw Object.assign(err, { moduleName: p.moduleName, exitReason, signalCode: p.signalCode })
       }
     })())
 
@@ -187,14 +187,20 @@ const catchChildProcessExit = async ({
       // Store the full error message including stdout & stder in the top-level `details` property
       Object.assign(moduleErr, { details: err.message })
 
-      // Apply a custom rule to force Sentry to group all issues with the same module & exit code
-      // See https://docs.sentry.io/platforms/node/usage/sdk-fingerprinting/#basic-example
-      Sentry.withScope(scope => {
-        scope.setFingerprint([message])
-        maybeReportErrorToSentry(moduleErr)
-      })
+      if (err.signalCode && ['SIGTERM', 'SIGKILL', 'SIGINT'].includes(err.signalCode)) {
+        // These signal codes are triggered when somebody terminates the process from outside.
+        // It's not a problem in Zinnia, there is nothing we can do about this.
+        // Don't report this error to Sentry.
+        Object.assign(err, { reportToSentry: false })
+      } else {
+        // Apply a custom rule to force Sentry to group all issues with the same module & exit code
+        // See https://docs.sentry.io/platforms/node/usage/sdk-fingerprinting/#basic-example
+        Sentry.withScope(scope => {
+          scope.setFingerprint([message])
+          maybeReportErrorToSentry(moduleErr)
+        })
+      }
     }
-    throw err
   } finally {
     controller.abort()
   }