Open boriskovar-m2ms opened 3 months ago
@boriskovar-m2ms has been investigating performance of snapshots, more investigation needed into synchronisation issues to see the work required to fix. Definitely a priority for green/v2.1
@boriskovar-m2ms has improved the reliability of reconstructing snapshots with large numbers of actions, especially with weaker connections / computers
As mentioned in issue #1373 this snapshot doesn't work.
Seems like false alarm because the reason is that I can't see given target
@boriskovar-m2ms I broke the snapshot by removing the compound set, is it possible for the snapshot to restore everything possible, and then stop at the compound set?
Problem is that we are restoring actions exactly in the same order as they are captured. I usually try to just skip actions for stuff that is missing but I guess I need to revisit this because these scenarios are usually not tested because it's usually very hard to do so.
But in this case why the snapshot is not working for me is because I don't have access to that target on staging.
Oh yes I see now that it requires authentication (which seems to be down due to the power cut). Is it possible to show a login screen for private targets and then resume snapshot restoration?
Hmmm I'm not sure because without backend changes FE can't distinguish between private targets and deleted targets (for example after data wipe). I need to also investigate how the login mechanism works because currently when you log in you're redirected back to the landing page. Just checked and FE is not in control where user will be redirected after successful login.
If a snapshot contains more actions (around 4 MB worth of actions) then restoring usually fails as they do not work more often then they actually do work.
It seems there is some serious synchronization issue.