Hi Alex
It could. What we did was wrap the entire handler in a try: block, then in
the except section set a instance/module level variable to signal a failed
startup (error in the handler)
Then if there was time we would try and allocate enough memory to kill the
process. After DEE you might
Thanks Tim. That was the problem.
I have warmup requests on, but the first request was a non-warmup loading
request which got a DeadlineExceededError. Your fix probably wouldn't work
since its not a warmup request.
I found this bug report, marked as Won't Fix. It provides some background
in ca
Go back through the logs for the instance, and see if it had a
DeadlineExceeded Error during startup.
My guess is you are not using warmup requests, and the instance hasn't
started properly leaving imports in a bad state.
This used to happen a lot in the early days when startup times in pytho
