From e832450e482ffd900196e50951a31adf6a2834ee Mon Sep 17 00:00:00 2001
From: Piotr Konopka <piotr.jan.konopka@cern.ch>
Date: Mon, 21 Aug 2023 13:24:23 +0200
Subject: [PATCH] [QC-429] Old validity in aggregators until we move everything

Contrary to my assumptions, we cannot use the new validity rules just in aggregators without applying them to check outputs, because they are used at the same time in some postprocessing tasks.
---
 Framework/src/AggregatorRunner.cxx | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Framework/src/AggregatorRunner.cxx b/Framework/src/AggregatorRunner.cxx
index c3f22f2d23..cf37d691cc 100644
--- a/Framework/src/AggregatorRunner.cxx
+++ b/Framework/src/AggregatorRunner.cxx
@@ -236,9 +236,13 @@ QualityObjectsType AggregatorRunner::aggregate()
 void AggregatorRunner::store(QualityObjectsType& qualityObjects)
 {
   ILOG(Info, Devel) << "Storing " << qualityObjects.size() << " QualityObjects" << ENDM;
+  auto validFrom = getCurrentTimestamp();
   try {
     for (auto& qo : qualityObjects) {
+      auto tmpValidity = qo->getValidity();
+      qo->setValidity(ValidityInterval{ static_cast<unsigned long>(validFrom), validFrom + 10ull * 365 * 24 * 60 * 60 * 1000 });
       mDatabase->storeQO(qo);
+      qo->setValidity(tmpValidity);
     }
     if (!qualityObjects.empty()) {
       auto& qo = qualityObjects.at(0);