Did anyone face the problem of UI bug? #209
Replies: 2 comments 1 reply
-
|
If you're able to get a consistent repro of this, please consider filing an issue, or writing back here with it! We aren't doing anything special w.r.t. rendering or the cell UI (native to VS Code) so I suspect this may be something in vscode/jupyter but we can start here and go from there? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
OK!Thank you!
Kevin Eger ***@***.***> 于 2025年12月24日周三 06:49写道:
… Closed #209 <#209>
as resolved.
—
Reply to this email directly, view it on GitHub
<#209>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBZDI5HXQLVBDQD56YDZJML4DHBGHAVCNFSM6AAAAACMCB6W2WVHI2DSMVQWIX3LMV45UABFIRUXGY3VONZWS33OIV3GK3TUHI5E433UNFTGSY3BORUW63R3GIZTENBUHEZQ>
.
You are receiving this because you authored the thread.Message ID:
<googlecolab/colab-vscode/repo-discussions/209/discussion_event/2324493@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The code itself runs successfully — it compiles without syntax errors, executes all designed logical workflows smoothly, and completes its core operational steps without crashing.
However, due to persistent UI lag, the rendering process for data visualization images is disrupted. The lag causes delays or interruptions in the UI thread, which is responsible for generating and displaying the visual output.
As a result, despite the code functioning correctly in terms of logic and execution, the data visualization images fail to generate entirely.
Beta Was this translation helpful? Give feedback.
All reactions