"False alarm" after hibernation wake-up: Doxument could not be loaded, lost connection
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
Describe the bug
Although the latest version is loaded, the editor claims that the document could not be loaded and the connection is lost.
To Reproduce
- Open a text document with some content in the browser and hibernate the computer
- Use a different device to add some text to the document
- Start the hibernated computer again and watch the browser window
- At first nothing happens, no notification of a lost connection or alike
- Then the document is automatically updated, i.e. the text added on the second device appears
- But at the same time the notification at the bottom of the screen appears. that the connection was lost and the document could not be loaded.
Expected behavior
If the document can be loaded/updated, do not show that error message or "remove" it, cancel it as soon as the connection is re-established.
Screenshots
Server details:
- Nextcloud version: 33.0.7
- PHP Version: 8.3.32
- Database: PostgreSQL 18.4
Client details:
- OS: Windows
- Browser: Firefox
- Browser version: 153.0.1
- Device: notebook
Logs
Nextcloud log (data/nextcloud.log)
Insert your Nextcloud log here
Browser log
[WARN] viewer: Some mimes were ignored because they are not enabled in the server previews config
Object { app: "viewer", uid: "username", level: 2, ignoredMimes: (1) […] }
previewUtils-Dqoyaeqv.chunk.mjs:5:313
Notifications permissions granted NotificationsApp-nYK0QT1r.chunk.mjs:86:58933
Has notify_push enabled, slowing polling to 15 minutes NotificationsApp-nYK0QT1r.chunk.mjs:86:54457
Polling interval updated to 900000 NotificationsApp-nYK0QT1r.chunk.mjs:86:58364
Started background fetcher as session_keepalive is enabled NotificationsApp-nYK0QT1r.chunk.mjs:86:55524
Got notification data, restoring default polling interval. NotificationsApp-nYK0QT1r.chunk.mjs:86:57319
[ERROR] files: Error while fetching content
Object { app: "files", uid: "username", level: 2, error: DOMException }
core-common.js:1:2984825
[ERROR] files: Error while fetching content
Object { app: "files", uid: "username", level: 2, error: DOMException }
core-common.js:1:2984825
[WARN] viewer: No files provided, skipping update
Object { app: "viewer", uid: "username", level: 2 }
previewUtils-Dqoyaeqv.chunk.mjs:5:313
File info for /Dokumente/E/Waldsee.md fetched
Object { filename: Getter & Setter, basename: Getter & Setter, lastmod: Getter & Setter, size: Getter & Setter, type: Getter & Setter, etag: Getter & Setter, mime: Getter & Setter, tags: Getter & Setter, getcontentlength: Getter & Setter, getcontenttype: Getter & Setter, … }
viewer-main.mjs:8:15411
[ERROR] text: [PollingBackend:fetchSteps] Network error when fetching steps, retry 1
Object { app: "text", uid: "username", level: 2 }
index-zDAq7SQt.chunk.mjs:4:374
Die Verbindung zu wss://doma.in/push/ws wurde unterbrochen, während die Seite geladen wurde. NotificationsApp-nYK0QT1r.chunk.mjs:10:10931
Network is offline, slowing down pollingInterval to 9000000 NotificationsApp-nYK0QT1r.chunk.mjs:86:55176
Polling interval updated to 9000000 NotificationsApp-nYK0QT1r.chunk.mjs:86:58364
Started background fetcher as session_keepalive is enabled NotificationsApp-nYK0QT1r.chunk.mjs:86:55524
Request to https://doma.in/ocs/v2.php/apps/user_status/api/v1/heartbeat?format=json failed because of a CSRF mismatch. Fetching a new token. index-CIlSxMEd.chunk.mjs:9:5994
Network is online, reseting pollingInterval to 900000 NotificationsApp-nYK0QT1r.chunk.mjs:86:55359
Polling interval updated to 900000 NotificationsApp-nYK0QT1r.chunk.mjs:86:58364
Started background fetcher as session_keepalive is enabled NotificationsApp-nYK0QT1r.chunk.mjs:86:55524
Slowing down notifications: Status 500 NotificationsApp-nYK0QT1r.chunk.mjs:86:57966
Polling interval updated to 9000000 NotificationsApp-nYK0QT1r.chunk.mjs:86:58364
Started background fetcher as session_keepalive is enabled NotificationsApp-nYK0QT1r.chunk.mjs:86:55524
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the hibernation and wake-up sequence with a text document, then start from the browser log entries for files content fetching and text's PollingBackend:fetchSteps network error. Trace how the connection recovery and document update affect the notification. Done means a successfully reloaded or updated document does not retain the connection-lost or could-not-be-loaded message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100