Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translation of library expression failed with the following message: Syntax error at meno #686

Open
wizard982 opened this issue Jan 10, 2023 · 1 comment

Comments

@wizard982
Copy link

Hello

After I prepared the server with all the necessary data (that you can find enclosed to this issue):

  • Library_jsontxt
  • PlanDefinition_json.txt
  • Patient_json.txt
  • Practitioner_json.txt

I tried to execute the loaded service. Nevertheless, I received a 500 Internal Server Error with this message in the server console (you can find the rest of the exception in the "Exception.txt" file):
Translation of library expression failed with the following message: Syntax error at meno org.opencds.cqf.cql.engine.exception.CqlException: Translation of library expression failed with the following message: Syntax error at meno at...
These are the details about the request that I sent to the service:
Called URL: http://localhost:8088/cds-services/2
JSON BODY: you can find it in the "Call Specifications.txt" enclosed file
RECEIVED STATUS: 500 Internal Server Error

I also enclosed the CQL file (CQL_LIB_cql.txt) that I attached to the FHIR Library. It seems that the raised problem is related to some returned strings of the "Recommendation" define, but I don't understand why!
system arrived at the Cql2ElmVisitor's function "visitLibrary" it starts a series of recursions and it becomes too hard and too nested to follow.
I used the last version of the CQF-Ruler (but I have got the same error also with the previous versions).

Note: I changed the extension of the CQL and JSON files because the issue tracker tool doesn't recognize them well and didn't permit me to upload all the necessary files.

Call Specifications.txt
Exception.txt
Library_json.txt
Patient_json.txt
PlanDefinition_json.txt
Practitioner_json.txt
CQL_LIB_cql.txt

@pylgrim73
Copy link

Hi,

just to say I executed as for your indications and I confirm I got the same error. Maybe someone from the development team could provide a feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants