OAGi / Score

Score
MIT License
9 stars 6 forks source link

Validation 500 error when running module set release validation #1551

Closed michaelfigura closed 1 year ago

michaelfigura commented 1 year ago

image

kbserm commented 1 year ago

@hakjuoh Is my understanding right that the user got 500 error b/c the XML schemas were failed to be generated? Not sure if that is the only possible cause, but if so we should convey that specific message.

kbserm commented 1 year ago

@michaelfigura Keep in mind that the cause of error is usually because you assign components to the module that cause circular XML schema import/include. Please consider whether the module assignment could cause this situation, If you haven't already done so.

@hakjuoh Is there away to report this problem from your XML Schema generation algorithm as I think it is quite difficult for a human to sort through this.

hakjuoh commented 1 year ago

@kbserm @michaelfigura Duration. Open Duration Measure_ Duration BCCP revised in Working release, but left it in WIP state. Although the BCCP should point to the previous DT, it pointed to the revised DT in Working branch. That's a bug. I fixed the DB record manually now.

kbserm commented 1 year ago

@hakjuoh You also fixed the root cause?

hakjuoh commented 1 year ago

@hakjuoh You also fixed the root cause?

This is a temporary fix. I would like to revise all functions in DT management and introduce XBT management to fix the root cause of the problem. The main issue to address is the separation of BDTs from CDTs along with primitive types.