BUG: fhircrack fhir_search function gets stuck

[polar-fhir]

BUG: fhircrack fhir_search function gets stuck

[palmjulia]

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 fhir_search() into either a webbrowser or Postman (if you're using that) and let me know if you get back a bundle there. Thanks!

[esalehi92]

Hi, thank you for the quick response!
Yes, you were right.
The same query cannot be run via curl.
But isn't there any timeout option or something similar to get a feedback if the query is not doing anything? Because there are different scenarios that it gets stuck! For example, for the same query that works, if I increase the number of counts and/or bundles, it also gets stuck in between!
look at the query and result in screenshots

It gets stuck in the middle! Can it be a performance issue? or maybe it is curling something that doesn't exist?
Thanks a lot!

[palmjulia]

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.
And then of course curl should have its default connect time out parameter which should at some point stop the request. You can try setting this manually just to be sure at the start of you R session with httr::set_config(httr::config(connecttimeout = 30)) (this should in theory cause a timeout after 30 seconds of no server response.

[esalehi92]

Thank you for the help. It was neither a problem of fhircrackr nor R. There were performance bottlenecks causing it.