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
Describe the bug
When attempting to publish a particular cube on INT it results in a SHACL validation error, but does not specify the source of the error. The SHACL UI link which could be used for debugging is dead (ERR_EMPTY_RESPONSE).
Since there is not apparent Affected functionalities (all that apply)
Expected behavior
Information should be displayed about the source of the validation error and the link should open the SHACL UI to be able to determine which part of the shacl shape failed to validate.
The text was updated successfully, but these errors were encountered:
I think the problem is that many dimensions lack the scaleType.
The strange thing is that violations are not reported in the UI and the validation report is not shown in the playground.
I could see the report in the playground only after reformatting the shapes graph using the converter.
I suspect there's something fishy going on with the serialization of shapes (which comes from cube.link). I keep investigating but, in the meantime, I hope you can publish the cube adding the missing scateType to the dimensions
Hi Giacomo
Thanks a lot for investigating the issue. I will be sure to look out for that in the future but having the reports would definitely be helpful!
Describe the bug
When attempting to publish a particular cube on INT it results in a SHACL validation error, but does not specify the source of the error. The SHACL UI link which could be used for debugging is dead (ERR_EMPTY_RESPONSE).
Since there is not apparent
Affected functionalities (all that apply)
Relevant links
https://int.cube-creator.lindas.admin.ch/app/cube-projects/cube-project!!programmanalyse-srg-radio-exnla52gad9/publication/jobs/cube-project!!programmanalyse-srg-radio-exnla52gad9!!jobs!!hxGX43bd6SUQ7GgJKzEOV
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Information should be displayed about the source of the validation error and the link should open the SHACL UI to be able to determine which part of the shacl shape failed to validate.
The text was updated successfully, but these errors were encountered: