-
Notifications
You must be signed in to change notification settings - Fork 716
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Showed popup "Failed to assign a backend" but it did assign one #4865
Comments
Hi Corrie :) Impressed you caught this, we had a few minutes of assignment outage, everything back in order for the last hour ish, should be good to go. |
The spike in assignment failures was known and fixed, but this seems a bit different. It was a successful assignment, but the FE reported failure. @katlyn-edwards Thoughts? |
Also, hi Corrie! 👋 |
Thanks for flagging the polish bug, Ben! I miss you all on Colab! Hope you're doing well. :) |
We miss you too! I'm sure folks would love to see you at lunch sometime... :D |
Tracking internally as b/369841183 |
Describe the current behavior
There was a long delay in connecting to a CPU and I got the "Failed to assign a backend
Sorry, no backends available. Please try again later.
More info" popup, however it did actually also connect.
Describe the expected behavior
Expected a connection without the long delay and no popup.
What web browser you are using
Chrome
Additional context
New notebook, nothing in the repro steps is notebook-dependent. The runtime was a normal CPU runtime.
The text was updated successfully, but these errors were encountered: