Change Details

Prior to this, my test plan in D12386 would repopulate some data, but not all data. The issue is that we were treating it as an `INCREMENTAL` rather than `FULL`, but `INCREMENTAL` was not possible from time 0 because some of the updates since that point had been deleted. In additional to that, I did some work to verify the safety of this change: 1. I tested registration via the new registration flow, and confirmed that nothing weird happened (this is the other case where `serverTime` is set to 0) 2. I looked through the login/registration code on keyserver and on the client to confirm that there were only two cases where `serverTime` was set to 0

In my test plan in D12386, the socket crash loop would never really get healed, as I had hardcoded the keyserver to timeout. (I was just confirming that `fetch_pending_updates` was coming in.) Before I had D12389 in place, each `fetch_pending_updates` was returning an incremental update. I noticed that the incremental update was always the same (with the same updates being repeated). This was happening because the new session was not setting on the client. After this diff, that problem went away.

Prior to thisIn my test plan in D12386, my test plan in D12386the socket crash loop would repopulate some datanever really get healed, but not all dataas I had hardcoded the keyserver to timeout. The issue is that we were treating it as an `INCREMENTAL` rather than `FULL`, but `INCREMENTAL` was not possible from time 0 because some of the updates since that point had been deleted.(I was just confirming that `fetch_pending_updates` was coming in.) In additional to that,Before I had D12389 in place, each `fetch_pending_updates` was returning an incremental update. I noticed that the incremental update was always the same (with the same updates being repeated). I did some work to verify the safety of this change:This was happening because the new session was not setting on the client. 1. I tested registration via the new registration flow, and confirmed that nothing weird happened (this is the other case where `serverTime` is set to 0) 2.After this diff, I looked through the login/registration code on keyserver and on the client to confirm that there were only two cases where `serverTime` was set to 0that problem went away.