You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
then the `ObjA` will be uploaded only to the default server (`http://alice-ccdb.cern.ch`), `ObjB` will be uploaded to both default and `local` server and
103
103
`ObjC` will be uploaded to the `local` server only.
104
104
105
-
But default the ccdb-populator-workflow will produce `fatal` on failed upload. To avoid this a switch `--no-fatal-on-failure` can be used.
105
+
By default the ccdb-populator-workflow will not produce `fatal` on failed upload. To require it an option `--fatal-on-failure` can be used.
if (runNoFromDH > 0 && md->find(o2::base::NameConf::CCDBRunTag.data()) == md->end()) { // if valid run number is provided and it is not filled in the metadata, add it to the clone
76
95
metadata = *md; // clone since the md from the message is const
@@ -93,6 +112,11 @@ class CCDBPopulator : public o2::framework::Task
93
112
}
94
113
}
95
114
115
+
voidendOfStream(o2::framework::EndOfStreamContext& ec) final
116
+
{
117
+
LOG(info) << "EndOfStream received";
118
+
}
119
+
96
120
private:
97
121
CcdbApi mAPI;
98
122
boolmFatalOnFailure = true; // produce fatal on failed upload
@@ -121,7 +145,7 @@ DataProcessorSpec getCCDBPopulatorDeviceSpec(const std::string& defCCDB, const s
121
145
{"ccdb-path", VariantType::String, defCCDB, {"Path to CCDB"}},
122
146
{"sspec-min", VariantType::Int64, -1L, {"min subspec to accept"}},
123
147
{"sspec-max", VariantType::Int64, -1L, {"max subspec to accept"}},
124
-
{"no-fatal-on-failure", VariantType::Bool, false, {"do not produce fatal on failed upload"}}}};
148
+
{"fatal-on-failure", VariantType::Bool, false, {"do not produce fatal on failed upload"}}}};
0 commit comments