It is happening quite often lately. I don’t know how to help debug this. I had an article where it happened three times in a row after refreshing the page and requesting a summary again. Every time it broke off mid-sentence near the end of the summary (different summary each time of course). But then I tried 10 more times and all were ok. It has happened in other articles too, though. Asking Leo why it stopped mid-sentence will cause it to finish the summary properly. I’ve noticed the problem while using Claude-instant, at least.
I doubt it is the issue but would you mind disabling Translate just for a moment and test to see if the issue with Leo persists? Just so we cover our bases.
No problem. Disabled the extension and did a round of my tabs trying to summarize them and see if any are cutting off suddenly. I found a few that still do it. Here’s one a example which happens to maybe show a second bug too:
This tab strangely produced a proper summary when I first tried. Then I refreshed the tab with F5 and retried the summary and it not only cut off abruptly in its response, but it actually refuses to produce a summary. I tried a few times more, every time it refused to produce a summary and some more times it cut off abruptly. The page URL is: https://drive.google.com/file/d/1i9UphZ8S4yQJKPqZo-o3vmJHWAqd4yrk/view
Thanks for checking — I’ve informed the team about this. Looks like one of our team members is also seeing this behavior so we’ll get someone to take a look at it soon.
The bug report has been closed but I’ve encountered the issue again in a browser version that should contain the fix. I left a screenshot of it in the github issue. I wonder if it’s the same issue or something different. Truth be told I don’t encounter this often, it may have even been just that one time that I posted as a screenshot for days now.
I will leave this thread open and if you see this happen again, grab another screenshot and share it here and we’ll take another look. Most users (our team included) who were seeing this issue are reporting that it is now resolved.