Status Update
Comments
an...@google.com <an...@google.com> #2
Chrome Diagnostics Report of following results:
The DNS diagnostic test in Chrome Diagnostics Report is known to have some issues in some configuration. Internal bug id is
Here the diagnostic failure could indicate a real problem. Jason, Jie, what m126 bugs could this report be a duplicate of ?
dm...@gmail.com <dm...@gmail.com> #3 Restricted
sk...@google.com <sk...@google.com> #4
This might be a dup of the internal bug of
As Jie mentioned, if this is still reproducible, a feedback report would help debug the issue further. Thank you!
dm...@gmail.com <dm...@gmail.com> #5
sw...@gmail.com <sw...@gmail.com> #6
Bugjuggler: wait 8w -> hugobenichi
st...@duke.edu <st...@duke.edu> #7
ku...@gmail.com <ku...@gmail.com> #8
It is still happening, so I will report the next instance with the requested text. It doesn't happen on a specific network, but all networks I am connecting to. It's not repeatable on other non ChromeOS devices in at least two of those, but is repeatable on the exact same device of another owner. I can ask them to also report with the reference number if that is helpful. Let me know if I can provide any additional information or troubleshooting.
I am out of the office for a few days this weekend, but should be able to repeat issue by eod Monday.
ad...@google.com <ad...@google.com> #9
ar...@gmail.com <ar...@gmail.com> #10
I looked at 2 reports, in both case we see that the WiFi network service state is eventually changed to "failure".
Rerouting to WiFi component to take an initial look if this is a WiFi issue.
Description
I'm running Gemini Nano locally on Pixel 9 Pro, version
com.google.ai.edge.aicore:aicore:0.0.1-exp01
, and I'm getting this error more often than the actual response.The prompt details certainly affect this behavior, but I can't figure out what trips it exactly.
Model config:
Prompt:
I shoehorned the card part because it seems like the model consistently breaks on similar inputs.
The web version (not Nano though) works fine. Removing
You can use your card 1234 4567 1234 8907 to withdraw it from ATM.
fixes the issue.I've had this error on many other prompts as well.