Robert
07/01/2024, 6:24 PMephemeral-prefect/api
?Marvin
07/01/2024, 6:24 PM500 Internal Server Error
when running certain tests.
- The error logs indicate issues with the API endpoint for logging (`http://ephemeral-prefect/api/logs/`).
- Source: GitHub Issue #14297
2. Functionality degradation in Prefect 3.0.0rc1:
- Users reported that submissions of flows in a Flask app (served via gunicorn + gevent) worked only on the first attempt in Prefect 3.0.0rc1; subsequent attempts failed.
- This error might be by-passed when using the Flask dev server (python app.py
).
- Source: GitHub Issue #13744
3. on_cancellation
Hook Not Triggered in Prefect 2.16.4:
- The on_cancellation
hook was not triggered for canceled flows, despite the workflow appearing as canceled in the UI and client.
- Logs indicated an issue with the hook execution.
- Source: GitHub Issue #13834
Based on these issues, the ephemeral-prefect/api
endpoint is associated with server-side errors and logging issues in certain testing and operational scenarios. The term is likely related to ephemeral instances of the Prefect API server used in these contexts. It would be best to monitor or address the specific implementation details around this endpoint in your setup.
For further details and potential solutions, you can explore the linked issues directly. If you need more help, please let me know how I can assist further!Nate
07/01/2024, 6:27 PMpip install prefect
and do nothing else and then run some flows, we'll spin up an ephemeral instance of the API so all that run data gets persisted to the db and stuff
its meant for an easy on ramp before engaging with the conceptual bulk of our OSS server or cloudRobert
07/01/2024, 6:28 PMPREFECT_API_URL
env varNate
07/01/2024, 6:28 PM