1. 29 Jul, 2020 5 commits
  2. 17 Jun, 2020 4 commits
  3. 15 Jun, 2020 6 commits
  4. 11 Jun, 2020 1 commit
  5. 10 Jun, 2020 1 commit
  6. 01 Jun, 2020 1 commit
  7. 22 Apr, 2020 4 commits
  8. 07 Apr, 2020 1 commit
  9. 30 Mar, 2020 2 commits
    • blam's avatar
      [buteo-sync-plugins-social] Use org.sailfishos.backup dbus service. Contributes to JB#49022 · 13e017fe
      blam authored
      The backup profile may now be triggered automatically via sync
      schedules. When the profile is triggered, use org.sailfish.backup
      to start system backup processes before uploading backup files to
      the cloud service.
      All backup configuration is now handled by org.sailfishos.backup,
      so it's no longer necessary to read/write this config via the
      sync profile.
      Restrict the upload/download implementation to only transfer one
      file from the local/remote directory as it's not necessary to
      transfer more than one during the sync process.
    • blam's avatar
      [buteo-sync-plugins-social] Split backup plugins. Contributes to JB#48784 · cfb74073
      blam authored
      Split Dropbox and OneDrive plugins into separate plugins for each of
      the backup, backup-query and backup-restore features.
  10. 13 Mar, 2020 6 commits
  11. 04 Mar, 2020 1 commit
  12. 29 Jan, 2020 8 commits
    • chriadam's avatar
      Bump version · eaf7901e
      chriadam authored
    • chriadam's avatar
      Merge branch 'jb47783' into 'master' · 1b0b1e27
      chriadam authored
      [buteo-sync-plugins-social] Fix Google calendar event duplication. Contributes to JB#47783
      See merge request !54
    • chriadam's avatar
      Handle 410 errors by early-exiting sync · fb592ddc
      chriadam authored
      This commit ensures that if the sync token or timeMin value for a
      notebook is invalid, we immediately abort sync, and then clear the
      sync token stored in the notebook's custom property as well as
      update the syncDate to an appropriate value.
    • chriadam's avatar
      [buteo-sync-plugins-social] Fix bugs in local delta calculation. Contributes to JB#47783 · 039257d4
      chriadam authored
      Store created/updated timestamps appropriate to ensure that filtering
      events for change or deletion since the last sync anchor works.
      Fix bugs in codepaths related to partial upsync artifacts, by ensuring
      that the event gcalId is calculated appropriately.
    • chriadam's avatar
      [buteo-sync-plugins-social] Discard spurious local addition due to downsync.... · 747fe3f4
      chriadam authored
      [buteo-sync-plugins-social] Discard spurious local addition due to downsync. Contributes to JB#47783
      Previously, we would determine that local additions caused by a
      downsync during the previous sync cycle should be treated as
      local modifications, and upsynced.
      This commit checks whether a local modification has indeed occurred
      by checking the lastModified date stamp, and if no modification has
      occurred, discarding the change to prevent spurious upsync.
      It also fixes a bug where the wrong "since" date time would be used
      when determining the local changeset, as it may be using one from
      a different notebook by mistake.  This commit updates the code so
      that the appropriate previous sync date for the specific notebook
      is used.
    • chriadam's avatar
      [buteo-sync-plugins-social] Discard spurious local modification due to remote... · 9426b482
      chriadam authored
      [buteo-sync-plugins-social] Discard spurious local modification due to remote organizer change. Contributes to JB#47783
      If a local modification is reported as a change since the last sync,
      but the data in the event is identical to the data reported by the
      server for that event except for the organizer email address,
      then it is probably a spurious change (since Google will add the
      organizer email automatically).
      This commit detects that case and doesn't attempt to upsync the
    • chriadam's avatar
      Ignore 403 ContentOperationNotPermitted errors due to shared calendars · 6940f22c
      chriadam authored
      Some changes (e.g. changing the organizer of an event in a shared
      calendar) are not allowed, even if the user has Owner access to the
      shared calendar (since the organizer field is managed specially
      by Google in the shared-calendar case, allowing only the organizer
      or the creator of the event to write changes there).
      If we hit such a failure, ignore it and allow sync to succeed.
    • chriadam's avatar
      [buteo-sync-plugins-social] Properly store the mapping between gcalId and... · b8563fb3
      chriadam authored
      [buteo-sync-plugins-social] Properly store the mapping between gcalId and local UID. Contributes to JB#47783
      Previously, we always stored an empty gcalId in the mapping.
      This could result in "known" partial upsync artifacts being
      ignored and re-upsynced, causing server-side event duplication.