This project is mirrored from https://github.com/sympa-community/sympa.git. Pull mirroring updated .
  1. 09 Jun, 2021 2 commits
  2. 10 Feb, 2021 1 commit
  3. 02 Feb, 2021 1 commit
  4. 30 Jan, 2021 1 commit
  5. 27 Jan, 2021 1 commit
  6. 08 Dec, 2020 1 commit
    • Samuel's avatar
      Update List.pm · 739af93e
      Samuel authored
      Upgrade process may fail inserting records in the `list_table` table, due to the `searchkey_list` value overflowing that column size (`varchar(255)`).
      Truncates that field, to ensure upgrade doesn't skip anything.
      
      Wild guess / maybe there's other places we could do this.
      Found out a mention of that issue over there: https://listes.renater.fr/sympa/arc/sympa-fr/2019-10/msg00017.html
      As of patching that file on my server, I can re-run the upgrade (from 5.4.7 to 6.2.40),  without any mention of such failures.
      739af93e
  7. 13 Oct, 2020 1 commit
  8. 10 Oct, 2020 1 commit
  9. 16 Sep, 2020 1 commit
  10. 15 Sep, 2020 1 commit
  11. 14 Sep, 2020 1 commit
  12. 25 Jul, 2020 1 commit
  13. 10 Jul, 2020 1 commit
    • IKEDA Soji's avatar
      Deprecate implicit sync_include in Sympa::List constructor (#955) · 6aa1a06d
      IKEDA Soji authored
      * review: Won't process sync_include in advance so that processing will be faster.
      
      * Refactoring. Sympa::List::on_the_fly_sync_include() was removed. Instead, "include" request handler had "delay" option.
      
      * Remove unused "last_sync" cache entries.  "last_change" entries remain.
      
      * sync_include will no longer be invoked during Sympa::List->new():
        - No owner defined in a list is no longer treated as error_config.
        - Instead, if no owner defined,
           - If possible, discard incoming message and send back DSN to original sender,
           - or, notifications to owners will be redirected to listmaster(s).
      
      * Refactoring: Remove unused functions
      
      * Small refactoring: mail_tt2/listeditor_notification.tt2 is no longer used.
      
      * Clarify log messages and DSN about undefined owner/editor/listmaster
      6aa1a06d
  14. 30 Apr, 2020 1 commit
    • root's avatar
      Fix: List::load() does call check_param_constraint(). This is not required;... · 871b3796
      root authored
      Fix: List::load() does call check_param_constraint(). This is not required; check_param_constraint() only make sense when a family list gets re/instantiated. These calls are very expensive for institutions heavily using families. Our production list service has 2.500 lists; most of them belonging to a family. In these circumstances wwsympa.fcgi startup takes 3 minutes. Applying this patch lowers wwsympa.fcgi to 35 seconds. Much better. I did some tests to ensure this patch does not prevent param_constraint checking while instantiating, modifying, adding lists to families. My tests (based on Test::BDD::Cucumber) are public on https://github.com/salaun-urennes1/sympa-functional-tests
      871b3796
  15. 29 Feb, 2020 1 commit
  16. 16 Feb, 2020 1 commit
  17. 12 Feb, 2020 1 commit
  18. 02 Feb, 2020 1 commit
  19. 29 Jan, 2020 1 commit
  20. 23 Nov, 2019 1 commit
  21. 11 Oct, 2019 1 commit
  22. 11 Sep, 2019 1 commit
  23. 02 Aug, 2019 1 commit
  24. 26 Jul, 2019 1 commit
  25. 02 Jul, 2019 1 commit
  26. 28 Jun, 2019 1 commit
  27. 26 Jun, 2019 1 commit
  28. 24 Jun, 2019 1 commit
  29. 24 May, 2019 1 commit
  30. 16 May, 2019 1 commit
    • seblgr's avatar
      Prevent unnecessary DB access in add_list_member · 5c3b724e
      seblgr authored
      In add_list_member the value $current_list_members_count is discarded if max_list_member == 0 (default setting).
      This prevents the "high db load" produced by the successive DB accesses.
      5c3b724e
  31. 26 Apr, 2019 1 commit
  32. 03 Apr, 2019 1 commit
    • VERDIN David's avatar
      When changing a list's admin two times in the same second, the list admins... · 3f39f564
      VERDIN David authored
      When changing a list's admin two times in the same second, the list admins cache is not updated. Consequently, when trying to add a third admin in the same second, the second one is not in the cache at the time.
      Obviously it does not sound like a recurrent scenario and I met this problem when running a test file only.
      However, it is possible that this happens more often when trying to make batch modifications in the shell. And also, it made my test fail which is an engineering problem: it could be misguiding about the cause of a test failure.
      So I changed the expiration test, replacing "<" by "<=" and it solves the problem.
      I don't see any side problem that could result from this change bu I commit it separately anyway because the cache is very sensitive.
      3f39f564
  33. 08 Mar, 2019 1 commit
  34. 03 Mar, 2019 2 commits
  35. 24 Feb, 2019 1 commit
  36. 08 Feb, 2019 1 commit
  37. 07 Feb, 2019 1 commit
  38. 04 Feb, 2019 1 commit