Amy

Hmm. I think my particular case was kind of a one-off. (Most people won't manage to trigger weird errors so soon after deploying and want to just start over :)....

I also saw this error when the cluster had been sitting idle for a few days. This seems like a very common error. Would it make sense to have the...

Update: for now, the team has dropped v2 compatible mode support. Instead, a v2 engine mode is in the works, ETA early next year for an alpha version.

Yes, will do (there may be a few days’ delay due to the holidays). I wonder if something has changed about the Cloud Run auth config. @raerevvo , did you...

@raerevvo -- To keep you posted: the `gcr.io/cloud-automl-tables-public/model_server` image has changed since I wrote that tutorial, and the issues are related in some way to how the new image works....

Btw -- in the process I noticed that there is a typo in the "Build a container to use for Cloud Run" section -- for the Dockerfile, `ADD model-export/tbl/[YOUR_RENAMED_DIRECTORY]/models/default/0000001` should...

Thanks for the additional repro. Interesting, you are right -- after about 10 mins the loop does seem to stabilize, though not persistently, as another prediction request a few mins...

Interestingly, when I deployed a cloud run version set to always have 1 instance running, then let this deployment sit for 30 mins, then tried it, prediction seems to work...

> Please note that, while some of the extensions are installed via pip, they aren't detected in JupyterLab, only the manually installed ones via the deprecated labextension install commands. I'm...

> You are using JupyterLab 3.x. This issue is about JupyterLab 4.0. There are completely different extension managers between the two. I am afraid the extension manager in JupyterLab 3...