-
Notifications
You must be signed in to change notification settings - Fork 4
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
BUG: fhircrack fhir_search function gets stuck #126
Comments
Hi, thanks for reporting. The error that's shown when you cancel is fine, I think that's just what happens when the curl request is canceld before there's a proper answer from the server. Have you tried your request outside of R? That would be the first check, copy the request you're giving to |
Okay, but you are still inside R here, at least in the screenshot. You did try it outside of R though via curl in a shell or something like that, correct? Because if the same problem occurs outside of R it's not really a fhircrackr bug, there's something wrong with your blaze server and I would advise making contact with Alexander Kiel to figure it out. You are right though that it is weird the program isn't interrupting at some point. For starters, I would expect the server to send a time out message after some time. At least ours does. |
Thank you for the help. It was neither a problem of fhircrackr nor R. There were performance bottlenecks causing it. |
Hi,
I am currently trying to run a R-script on our Blaze-fhir-server but the script gets stuck when running the fhir_search function from fhircrackr library.
I testet it with simple queries and it works when only one condition is applied (e.g. icd-code = E84.0) but with more complex queries, it gets stuck (see screenshot below).
![fhir-protected2](https://user-images.githubusercontent.com/114484055/192528350-1efb5220-d7b7-4ec3-b791-6727c7f740b0.png)
and if I cancel the run via Ctrl+C, the error below is shown:
![fhir-protected](https://user-images.githubusercontent.com/114484055/192528042-836f8671-ad14-4c71-8592-a56a67d28e00.png)
I'd appreciate any help! Thank you
The text was updated successfully, but these errors were encountered: