Python app answers 500 because its code uses an API removed from an unpinned dependency
The application started but did not answer on any port it publishes. The deploy log has the per-port result; a worker or queue-only app can ignore this. | The site returned 500 instead of a page. The 500 came back in about 2ms -- too fast for the application to have answered. A proxy returned it -- the engine's, or one the image runs in front of the app -- because nothing answered behind it: the container never started or is crash-looping. Read the container's STARTUP output with docker logs -…
TypeWarningAn issue PanelAlpha Engine catches around a deploy that does not break it. It tells you, before or after, that you may need to do something.
Seen3 times
WherePython
StatusIn AnalysisOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The application starts, but the front page raises an error inside the app: the current FastAPI/Starlette release no longer accepts the old TemplateResponse call the code makes.