| Age | Commit message (Collapse) | Author |
|---|
|
start(folder.first) ignored fetch request due to folder having version
|
|
|
|
inappropriate param
|
|
Same thing as commit cf692c40b0b9f8d0d04cd10a02a84e3f697a2e99
which was removed due to shutdown freezes.
Error thread is no longer there so doesn't cause any race sonditions,
was not able to repro any issues so will ask QA to test shutdown
|
|
|
|
|
|
|
|
|
|
Previously was bounced to login screen on error only,
now should be bounced back if failed too many times as well
|
|
|
|
|
|
|
|
|
|
|
|
- Don't Warn about unknown cof version, it's expected during fetch, Info is enough
- Fix 'unexpected attachments' due to unknown cof, also should fix viewer trying to create a link before cof is ready
- Fix 'accounting' warnings when getting item updates for unfetched folders (Note: viewer doesn't know folders version, if fetch is already in progress we might get an old version)
|
|
|
|
Is supposed to set version and descendant info in parseCategory
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Privileged
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
in release job to reference outputs from the build job.
Also mark the release as prerelease, and fail the release action if we still
can't find the files we're trying to post.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
simulator
|
|
There is still a chance user will try to move multiple landmarks one after another, but if it didn't update in the time user moves landmarks it's going to end up out of order either way
|
|
|
|
|
