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
as a pixl pipeline user, I'd like to be able to set the timeout period in minutes for the rest request used in pixl export-patient-data. So that for large exports, it doesn't time out but I get notified of any failures. Default of half an hour might be reasonable.
Testing
No response
Documentation
Update documentation of CLI
Dependencies
No response
Details and Comments
No response
The text was updated successfully, but these errors were encountered:
Setting the timeout on the request side is already possible as of #370 , albeit with a lower default of 5 minutes.
I haven't tested this with particularly long-running exports, however. I'm not sure whether the server (or docker) would time us out after a while.
We would probably want to look into whether FastAPI can be configured to send periodic messages to show it's still processing, or better to make it fully asynchronous so we're not dependent on this long-running TCP connection staying up, and then it'd be the CLI's job to query for status every so often. (see also https://fastapi.tiangolo.com/tutorial/background-tasks/ )
Definition of Done / Acceptance Criteria
as a pixl pipeline user, I'd like to be able to set the timeout period in minutes for the rest request used in
pixl export-patient-data
. So that for large exports, it doesn't time out but I get notified of any failures. Default of half an hour might be reasonable.Testing
No response
Documentation
Update documentation of CLI
Dependencies
No response
Details and Comments
No response
The text was updated successfully, but these errors were encountered: