Open fmunim opened 2 years ago
Did you get it just once or you get it on every app start? Do you run a single mail account in the app or many (with "local store" option enabled)?
This check was added by design to catch the case when the initial/bootstrap mails sync is about to be triggered more than once for the same account which would be a problem (syncing for the same mail account is not supposed to be run in parallel but for the different accounts). This should not normally happen (a similar error has never been posted here). This is basically an indication that the syncing triggering/processing logic still has room for improvement.
@vladimiry I get it sometimes but not always. I run 3 mail accounts with all local store option enabled. I think they all sync at the same time? Not sure could be the reason. But its just a thing I wanted to bring it to your attention.
I think they all sync at the same time?
It should not. If it does then it's an implementation error that I was not able to detect yet. The posted error is not about "sync" but about "initial/bootstrap sync". The app first does initial/bootstrap sync, which means downloading all the mails. After that, it does incremental/patch sync only (downloads only changed the mails, reactively).
I think they all sync at the same time?
It should not. If it does then it's an implementation error that I was not able to detect yet. The posted error is not about "sync" but about "initial/bootstrap sync". The app first does initial/bootstrap sync, which means downloading all the mails. After that, it does incremental/patch sync only (downloads only changed the mails, reactively).
Oops, I meant it only synced when I clicked on the tab, they sync but either way, I am guessing I should not be worrying about this error as the mail still works normally.
Vladmir, thank you for maintaining this app.
I am using the current version 5.0.0 with Electron: 15.5.7 Chromium: 94.0.4606.81 Node: 16.5.0 V8: 9.4.146.22-electron.0
using 3 proton mail accounts with offline storage each. I am getting this "Database bootstrap fetch has already been called once for the account, 0" as well at various times but could not figure out cause effect. Any help would be appreciated.
This error prevents the second bootstrap fetch to be called for the same account, which would be a logic issue. So this is a half-measure as it prevents the logic error to happen, but the root issue cause is still somewhere there. I think it's clear that I didn't catch the issue cause yet. Normally, an app restart should help if you in a way got blocked by this error. Also try to add the account one by one, waiting for the bootstrap fetch completion of each (that green sync process indication icon located on the account handle button stops blinking).
OK, will try your suggestions. Thank you very much for your reply.
Getting this error when opening up ElectronMail, any ideas what this could be?
On: