fatal error for invalid configuration

[jgrosseo]

No description provided.

[jgrosseo]

@victor-gonzalez What do you think?
In addition the centrality table has both process functions (run2 and run3) off by default. The disadvantage is one cannot run it at all to get a dpl-config.json to then edit it. I would suggest to enable one of them by default, as we do for the multiplicity task. What do you think?

[victor-gonzalez]

@jgrosseo I was just running a training session at the PAG about it (you probably got the input from Maja)
I was a bit surprised because the dpt-config.json file was actually written although the workflow was hung
Anyway, I agree, one of the processes should be enabled by default (Run 2)
Regarding the solution, as these are core service tasks, probably it is needed for orienting the local user

[jgrosseo]

in my case the file is written but has an empty config entry for centrality-table. It is not the case for you?

Is this PR ok for you?

[victor-gonzalez]

In the case of Malgorzata, which was the one which reported it, surprisingly, she got a complete centrality-table entry in the json file. Actually we used it for creating a configuration file which fixed the issue

The PR is OK for me

[alibuild]

Auto-approving on behalf of @jgrosseo.