DPL: do not calculate context quantities if the GUI is disabled

[ktf]

Correct solution would be to do that on demand, quick fix for now.

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

[ktf]

@davidrohr this should improve the situation with the dummy sink (and probably affecting FLPs as well). What is still not clear to me is why the dummy sink is processing data at kHz rate, in particular in async. I am investigating.

[ehellbar]

Isn't it the same check which is done in the function itself https://github.com/ehellbar/AliceO2/blob/dev/Framework/Core/src/DataRelayer.cxx#L1037 ?

You introduced it there a few weeks ago to try to mitigate the issues spotted on FLPs

[ktf]

Nevermind this is already there, so it must be something else which triggers it.

[ktf]

In the Async reco tag it was not backported.