web client: non-hatch white screen issues
Bug #1768947 reported by
Kathy Lussier
This bug report is a duplicate of:
Bug #1775719: Multiple IndexedDB connections (via tabs) can result in data inconsistency.
Edit
Remove
This bug affects 13 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Medium
|
Unassigned |
Bug Description
I'm starting this bug to see if we can begin to identify the source of web client white screen issues that are unrelated to hatch. In my experience, these problems are hard to reproduce and are usually resolved after clearing cookies from the browser.
In the latest instance of this issues, we saw the following message in the browser console:
Constraint error: (201) Duplicate keys are not allowed, index: Setting.pkSetting, key: "circ.staff_
I know I've seen other errors when this issue occurs. Maybe if we can begin documenting them, we might find out what's causing the white screens.
tags: | added: webstaffblocker |
To post a comment you must log in.
We're seeing white screens in the web client. (not completely white. the menu bar loads, but the rest is white). It happens when we try to load any page - records, reports, acquisitions, etc. The console says:
10:36:46.063 opensrf_ws.js:46 pending count 1 /eg/staff/ reporter/ legacy/ main" resulted in a network error response: an object that was not a Response was passed to respondWith().
10:36:46.094 opensrf_ws.js:72 pending count 1
10:37:07.686 The FetchEvent for "https://[server]
The console error always mentions the URL that was tried to access - it's not fixed.
I can usually resolve it by reloading the page 1-5 times.