1. 25 Feb, 2018 1 commit
    • Benjamin Neff's avatar
      Don't retry for PublicKeyNotFound · f0aca56c
      Benjamin Neff authored
      We only return `nil` when we know the person, but don't know the key or
      the key is invalid, so it doesn't make sense to retry in this case. When
      the person isn't known and can't be fetched we raise a DiscoveryError
      which will be retried.
      
      Also the errors were moved to the `Signable` module in the last release.
      
      closes #7717
      f0aca56c
  2. 21 Feb, 2018 1 commit
  3. 17 Feb, 2018 1 commit
  4. 01 Feb, 2018 6 commits
  5. 21 Jan, 2018 1 commit
  6. 12 Jan, 2018 1 commit
    • Benjamin Neff's avatar
      Fix notifications when people remove their birthday date · 5bc4473e
      Benjamin Neff authored
      Some people may remove their birthday date after the notification was
      sent, which then breaks the notification page for other users. Let's
      just display the date when the notification was created, and not display
      the users updated birthday date. When users update from date A to B it
      always looks weird anyway, when we display the same new date B twice on
      different days, or display two different dates for the same user.
      
      We could remove notifications when users change or remove their
      birthday, but that would be way more complex and also we usually don't
      remove notifications (not even for deleted posts).
      
      Fixes #7689
      
      closes #7691
      5bc4473e
  7. 08 Jan, 2018 4 commits
  8. 05 Jan, 2018 2 commits
    • Janakas's avatar
      Fix invite link on /contacts · d150a6b2
      Janakas authored
      closes #7690
      d150a6b2
    • Benjamin Neff's avatar
      Fix notifications when people remove their birthday date · c135ace4
      Benjamin Neff authored
      Some people may remove their birthday date after the notification was
      sent, which then breaks the notification page for other users. Let's
      just display the date when the notification was created, and not display
      the users updated birthday date. When users update from date A to B it
      always looks weird anyway, when we display the same new date B twice on
      different days, or display two different dates for the same user.
      
      We could remove notifications when users change or remove their
      birthday, but that would be way more complex and also we usually don't
      remove notifications (not even for deleted posts).
      
      Fixes #7689
      
      closes #7691
      c135ace4
  9. 25 Dec, 2017 2 commits
  10. 24 Dec, 2017 1 commit
  11. 18 Dec, 2017 2 commits
  12. 27 Oct, 2017 1 commit
  13. 20 Oct, 2017 1 commit
    • Benjamin Neff's avatar
      Group notifications by updated_at · 0f688b9d
      Benjamin Neff authored
      The notifications need to be grouped by the same date as they are
      sorted, otherwise the date used for the group doesn't match all
      timestamps in the group and also the groups are sorted by the wrong
      date.
      
      This fixes #7647, a regression of #7568.
      
      closes #7648
      0f688b9d
  14. 16 Oct, 2017 6 commits
  15. 28 Sep, 2017 9 commits
  16. 26 Sep, 2017 1 commit
    • Senya's avatar
      Memory usage optimization for archive export · c6ed850a
      Senya authored
      - Removed posts and non contacts from other's data
      - Collections are exported in batches to lower memory footprint
      - In base exporters create User object instead of keeping instance because it caches all associations
      
      closes #7627
      c6ed850a