-
-
Notifications
You must be signed in to change notification settings - Fork 997
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
Error: Uncaught (in promise): AbortError: The transaction was aborted, so the request cannot be fulfilled. #401
Comments
Thank you very much. Could you maybe provide a little bit more inside on what happened before the error? Common reasons for database issues like this are:
|
Unfortunately I can't add much. I was not running multiple instances and I
have a lot of disk space. I think it happened when I was trying to manually
edit the time for a task.
…On Fri, Jun 12, 2020 at 11:21 AM Johannes Millan ***@***.***> wrote:
Thank you very much. Could you maybe provide a little bit more inside on
what happened before the error?
Common reasons for database issues like this are:
1. Running multiple instances of the app
2. Not enough disk space
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#401 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMSESTF3BIN7KVATQKQP2LRWHXRNANCNFSM4N4E52RQ>
.
|
Have you been idle for while before doing this? |
I don't think so. It's happened a few times. I'll keep using it and let you
know if it happens again.
…On Fri 12 Jun 2020, 15:06 Johannes Millan, ***@***.***> wrote:
Have you been idle for while before doing this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#401 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMSESXLS7BO42ESX4UZWX3RWIR37ANCNFSM4N4E52RQ>
.
|
That would be great! Thank you. I really can use all the info I can get regarding this issue. |
May I ask if you encountered this or a similar issue again? I am asking because I had the feeling that this might have gotten better with the most recent electron version (introduced with Super Productivity 5.6.5) as nobody has reported a similar issue after that. |
I think i got the same error. Details in #542 -- should have checked for duplicate issues, my bad. |
I added some advanced data repair/restore functionality, as a compromise as there is no way to fix this completely without replacing the database adapter, which is not trivial and likely to cause new issues on other fronts. I think this is acceptable, as the issue only occurs rarely. I am closing this, but please open up new issues, if you encounter this again. Thank you! |
META: SP5.3.4 Electron – en-GB – Linux x86_64 – Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) superProductivity/5.3.4 Chrome/80.0.3987.165 Electron/8.3.0 Safari/537.36
Steps to Reproduce
Console Output
Error Log (Desktop only)
Stacktrace
The text was updated successfully, but these errors were encountered: