Closed ggonzr closed 8 months ago
Hi @lmoureaux, this is deployed in the development instance as requested. Please check it and let me know if this solves the issue. Thanks
Seems to be working in -dev
(but I don't have a broken setup to compare to)
I suggest asking the colleague who reported this for the details of the request tried to create so that we can replicate it first in dev before merging this. Please could you ask for the details and replicate this in dev first? Thanks
I reproduced in production McM with HIG-RunIISummer20UL18wmLHEGEN-13372. This request isn't in the dev database but I couldn't reproduce the same message when validating similar requests.
I synced the data for both environments and now the request is available in dev HIG-RunIISummer20UL18wmLHEGEN-13372. Please can you reproduce the issue and check if it is solved.
I can confirm that the issue doesn't appear in dev
Checking again the request, I don't the issue is on our side. The last update related to the cross-section
(#1126) doesn't affect any validation performed by the web server (in the backend). I am going to ask the colleague about how the generator_parameters
attribute was set for its request. This seems more like an input data issue.
Hi Geovanny, I confirmed that the API was used to change the cross_section
in the generator parameters so it passed the check. I still think this fix is needed
Related topic: https://cms-talk.web.cern.ch/t/problem-with-adding-cross-section-to-mcm-requests/36272/3