1. 01 Aug, 2023 2 commits
  2. 28 Jul, 2023 7 commits
  3. 27 Jul, 2023 9 commits
  4. 18 Jul, 2023 2 commits
  5. 13 Jul, 2023 5 commits
  6. 07 Jul, 2023 1 commit
  7. 04 Jul, 2023 2 commits
  8. 03 Jul, 2023 2 commits
  9. 28 Jun, 2023 2 commits
  10. 26 Jun, 2023 1 commit
  11. 22 Jun, 2023 1 commit
  12. 21 Jun, 2023 1 commit
  13. 20 Jun, 2023 5 commits
    • Jérome Perrin's avatar
      openid_connect,google_login: increase cache duration to 10 days · 3304ea33
      Jérome Perrin authored
      Because these two plugins implement the refresh of the authentication
      token (unlike the facebook plugin), we can use a longer cache here.
      With the previous value of 1 day, when not using the site for more than
      1 day, token would expire from cache and user have to authenticate again.
      Because the scenario of "access is revoked from authorization server"
      is handled by refreshing the access token, we can use a longer duration
      here, so that user do not have to login again after not using for two
      days.
      3304ea33
    • Jérome Perrin's avatar
      ERP5Security: fix some typos · 36d7f81e
      Jérome Perrin authored
      36d7f81e
    • Jérome Perrin's avatar
      ZMySQLDA: reconnect on mariadb's Connection was killed · 831627bf
      Jérome Perrin authored
      After server restarts, mariadb uses an error 1927 which is mariadb
      specific, with no corresponding constant in CR module when server
      restart. This is the case at least with mariadb 10.3.38.
      
      This fix the following problem:
       - start zope and use mariadb connection
       - restart mariadb
       - use mariadb connection again, see an error:
          Error Type: OperationalError
          Error Value: (1927, 'Connection was killed')
      
      This change to treat 1927 as an error for which we can reconnect and
      retry the query. Some other connectors do it, for example sqlalchemy in
      https://github.com/sqlalchemy/sqlalchemy/issues/5493
      831627bf
    • Jérome Perrin's avatar
      288063e6
    • Jérome Perrin's avatar
      test: try to explicitly stop HTTP server at the end of tests · 3fb0670d
      Jérome Perrin authored
      This prevents tracebacks during shutdown:
      
        Unhandled exception in thread started by <bound method Thread.__bootstrap of <Thread(Thread-1, stopped daemon 139820471113472)>>
        Traceback (most recent call last):
          File "soft/lib/python2.7/threading.py", line 774, in __bootstrap
            self.__bootstrap_inner()
          File "soft/lib/python2.7/threading.py", line 814, in __bootstrap_inner
            (self.name, _format_exc()))
          File "soft/lib/python2.7/traceback.py", line 242, in format_exc
            return ''.join(format_exception(etype, value, tb, limit))
          File "soft/lib/python2.7/traceback.py", line 141, in format_exception
            list = list + format_tb(tb, limit)
          File "soft/lib/python2.7/traceback.py", line 76, in format_tb
            return format_list(extract_tb(tb, limit))
          File "soft/lib/python2.7/traceback.py", line 100, in extract_tb
            linecache.checkcache(filename)
        TypeError: 'NoneType' object is not callable
      
      Also rename the method because this is not longer *Z*server.
      
      This waitress close() API is not public part of API, so we still ignore
      the case where the server thread does not stop after 5 seconds. This
      happens if some HTTP connections are still open at the end of test.
      3fb0670d