data inconsistencies across peers about ouronote HOT 2 OPEN

We ran into this while testing. But was unable to reproduce.

It seemed to occur when a peer was offline and edits were being made. The online peer's changes didn't automatically sync up to the offline peer, and the offline peer's changes never seemed to be communicated to the rest of the peers when returning online, even after a lot of other sync'd changes and time passing.

This fit the pattern we had before the peer connection system was implemented.

Current suspicion is that there is a size issue somehow impacting the indexedDB > radata storage area as the toy version of the test (after clearing things out of the browser) did not have the issue, and was the only major thing changed between tests.

A different problem entirely was that having more than one tab open seemed to cause massive delays in syncing that were resolved when the older tab closed. This was creating a similar effect with partial changes being sent to the incompletely loaded tab. That might be worth a separate issue entry.

from ouronote.

There were two variables tested within the gun configuration, using the IndexedDB vs. LocalStorage storage adapters, and WebRTC enabled vs. disabled. The storage adapter appeared to have an effect on the primary issue (data consistency after a network connection reset), while WebRTC may have only caused multi-tab issues. Needs more rigorous testing against each permutation of these options, with well-defined sequences of events, along with the state of the client's local graph after each test, to prepare an issue for the gun team, assuming we can confirm the issue is occurring within gun.

from ouronote.