-
Notifications
You must be signed in to change notification settings - Fork 3
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
Regular outages when reloading data to local IDB after a save #287
Comments
What do you mean by “reloading data to local IDB after a save”? This is happening right after saving changes to a local database? |
Yes. Make changes to a period definition, click save; then instead of a
short spinning period and the reload of the browse page with the period one
just edited highlighted, that error message.
…On Sat, Jul 11, 2020 at 8:24 AM Ryan Shaw ***@***.***> wrote:
What do you mean by “reloading data to local IDB after a save”? This is
happening right after saving changes to a local database?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/periodo/periodo-server/issues/171#issuecomment-657061746>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABEFPA3FAX3HH2WJSRKZ4R3R3BRXJANCNFSM4OXEPTQQ>
.
|
I've been working on changing/updating for the last three hours, on and off (˜7pm to ˜10pm Central time, 7/11), and have not encountered this problem again until just now, shortly after 10pm Central. The original report was also for work being done after 10pm. |
@atomrab This is a client issue (I think) so I moved the issue. |
Oh, also: @atomrab are you using client.perio.do or client.staging.perio.do? |
This is a very strange. Just out of curiosity- how much free space do you have on your hard drive? |
Also, next time this happens to you, can you copy the error from another browser? I am wondering if it will have the same error ( |
I am not sure if this is actually a server issue, but since it happened to all of us at the same time during the last call we had, I am assuming it's not just my local browser (it also happens across all my browsers at once, regardless of the datasource).
As I have been going through the LCSH to clean up spatial coverage, I am getting the following error at fairly regular, roughly 20-minute intervals. It persists for about three to seven minutes and then the client loads as normal (the last save is ignored).
Client error
Error stack
OpenFailedError: UnknownError Internal error opening backing store for indexedDB.open.
at Transaction.create (https://client.perio.do/periodo-client-4.4.3.min.js:123:515822)
at https://client.perio.do/periodo-client-4.4.3.min.js:123:516784
at executePromiseTask (https://client.perio.do/periodo-client-4.4.3.min.js:123:473816)
at new Promise (https://client.perio.do/periodo-client-4.4.3.min.js:123:474362)
at https://client.perio.do/periodo-client-4.4.3.min.js:123:516620
at usePSD (https://client.perio.do/periodo-client-4.4.3.min.js:123:481992)
at newScope (https://client.perio.do/periodo-client-4.4.3.min.js:123:481839)
at Transaction._promise (https://client.perio.do/periodo-client-4.4.3.min.js:123:516581)
Component stack
in F
in Unknown
in Unknown
in ConnectFunction
in div
in Clean.div
in UI:Box
in Resource:backend-home
in div
in Clean.div
in UI:Box
in div
in Clean.div
in UI:Box
in MenuedResource
in div
in Clean.div
in UI:Box
in div
in Clean.div
in UI:Grid
in ThemeProvider
in PeriodoApplication
in F
in ThemeProvider
in Provider
in Unknown
The text was updated successfully, but these errors were encountered: