Repository navigation
Conversation
|
I'm not completely sure the verification was expected to be in |
3261199 to
7cd1dd8
Compare
|
I think your understanding is correct, the check should be at modification time. I would not create a new module, you can add your new function inside Modificator.py or inside src/DIRAC/FrameworkSystem/Utilities/diracx.py |
|
Thanks @fstagni for the clarification. |
|
One possible issue I see in what I've done is that, if my understanding is correct, in Modificatior, Is that ok like this? or should I verify only the current changes? |
|
It's probably OK. I am also wondering if instead of simply displaying a warning, the commit should simply be refused. |
In the issue it is precised that:
|
Here me and @chaen disagree but I also think it should be refused. Maybe it would be good to gate it behind an option in the CS service. |
014be21 to
90c38d1
Compare
1b3a58e to
8036c6e
Compare
|
Hi @fstagni , do I need to do or change something more here? |
|
No, I just opened/closed to get the tests running again. I will now hotfix this one and probably merge. |
|
I hotfixed this one, and tried it out. It works OK. |
Verify the CS config using diracx model validation before committing. If validation fails a warning is diplayed.
closes #8302