From e2d657a04af2cb2422ce9d8e142a89d6d09e85ab Mon Sep 17 00:00:00 2001
From: Piotr Konopka <piotr.jan.konopka@cern.ch>
Date: Mon, 27 Nov 2023 16:19:25 +0100
Subject: [PATCH] Bring back accidentally removed validity check in
 postprocessing (#2048)

* Bring back accidentally removed validity check in postprocessing

* log why

* typo
---
 Framework/src/PostProcessingRunner.cxx | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/Framework/src/PostProcessingRunner.cxx b/Framework/src/PostProcessingRunner.cxx
index 6c6e6eb767..4a5b4e2850 100644
--- a/Framework/src/PostProcessingRunner.cxx
+++ b/Framework/src/PostProcessingRunner.cxx
@@ -230,6 +230,16 @@ void PostProcessingRunner::reset()
 
 void PostProcessingRunner::updateValidity(const Trigger& trigger)
 {
+  if (!trigger.activity.mValidity.isValid()) {
+    ILOG(Warning, Devel) << "Not updating objects validity, because the provided trigger validity is invalid ("
+                         << trigger.activity.mValidity.getMin() << ", " << trigger.activity.mValidity.getMax() << ")" << ENDM;
+    return;
+  }
+  if (trigger.activity.mValidity == gFullValidityInterval) {
+    ILOG(Warning, Devel) << "Not updating objects validity, because the provided trigger validity covers the"
+                         << " maximum possible validity, which is unexpected" << ENDM;
+    return;
+  }
   if (!core::activity_helpers::onNumericLimit(trigger.activity.mValidity.getMin())) {
     mActivity.mValidity.update(trigger.activity.mValidity.getMin());
   }