-
Notifications
You must be signed in to change notification settings - Fork 21
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
No response to updates after prolonged wait time #289
Comments
Another possibly related issue is that, when I force and update by running Where using This is in the end quite annoying, as I need to restart typst-preview frequently. EDIT: In fact, it seems even weirder, once I encountered this issue at least once I can reproduce it instantly, even though they are completely separate instances. It seems, that it works for a while after freshly starting my PC or window manager and after a while it just doesn't anymore. Logs:
|
This might be the root cause. The browser tab seems close the websocket. Can you provide browser logs? I will also try reproduce this when i leave work |
I'm not sure, in the second log I sent you can't see that at all. The browser logs are structured, so I opened them to the depth I deemed important. Here too I noticed that regular updates work, then a non-update using Bowser Logs
PS.: I didn't find a way to easily export the logs in firefox, sanitizing this myself was painful, surely there's a better way in case you need more logs. |
The second log may indicates something might be wrong with file watcher. |
So this may be a problem upstream at typst.ts? It seems the file watching is done using their |
Describe the bug
After a prolonged period where I did not edit any files, subsequent edits do not update the logs or preview at all.
To Reproduce
typst-preview file.typ
Expected behavior
Edits continue to update the preview after I come back.
Package/Software version:
typst-preview extension version:
none
(using cli)Logs:
Simplified for brevity
Additional context
OS:
Endeavor OS
The text was updated successfully, but these errors were encountered: