1. 27 Nov, 2023 2 commits
    • Rafael Monnerat's avatar
      erp5_web: Introduce no-store policy · fb869e0a
      Rafael Monnerat authored
        We must ensure that some Web Section (under a website with must-revalidate caching policy) can have a session that isn't stored.
      
        Different from no-cache (that is similar to must-revalidate + max-age=0), no-store tells the client (and frontends) that it must not cache the content ever.
      fb869e0a
    • Rafael Monnerat's avatar
      erp5_web: authenticate cache should send Last-Modified · 1ae11adc
      Rafael Monnerat authored
        Since we issue an no-store and no 304s, the Last-Modified could confuse the frontend if If-Modified-Since header is present on the request.
      
        If-Modified-Since is sent, the ERP5 wont return with 304, so we don't expect that the frontend does it (but it does), so since we don't expect that user stores the last request it makes no sense to return with Last-Modified.
      1ae11adc
  2. 20 Nov, 2023 2 commits
  3. 16 Nov, 2023 3 commits
  4. 15 Nov, 2023 1 commit
  5. 13 Nov, 2023 2 commits
  6. 10 Nov, 2023 2 commits
  7. 08 Nov, 2023 8 commits
  8. 07 Nov, 2023 3 commits
  9. 02 Nov, 2023 2 commits
  10. 27 Oct, 2023 4 commits
    • Jérome Perrin's avatar
      corporate_identity_test: fix coding style test · 07496d63
      Jérome Perrin authored
      This code seems to have been pushed accidentally as part of 6e5e8e8c
      (fixup! test: follow recent ImageMagick spec., 2023-10-11)
      07496d63
    • Jérome Perrin's avatar
      Revert "erp5_pdm: show first newest movement in movement history dialog" · e8d20966
      Jérome Perrin authored
      This reverts commit 14831fae.
      
      As discussed in nexedi/erp5@14831fae (comment 188678)
      this change breaks test and it seems more natural to implement this with
      listbox's sort parameter.
      
      This change will be pushed again, probably as part of
      nexedi/erp5!1305
      e8d20966
    • Jérome Perrin's avatar
      ui_test_core: trigger a change event after setFile · dd353a28
      Jérome Perrin authored
      This is what browsers do when user selects a file.
      dd353a28
    • Jérome Perrin's avatar
      testnode: make killall support processes with changed title · 21147419
      Jérome Perrin authored
      testnode uses ProcessManager.killall to terminate all processes from a
      path. To determine if a process is from a path, it looks at the command
      line. This does not work for processes using setproctitle to change
      their command line.
      
      We can see in ps:
      
          $ ps -edf | grep nginx
          slapuse+ 115059  45574  0 16:14 ?        00:00:00 nginx: master process /srv/slapgrid/slappart46/t/cvt/i/0/tmp/shared/nginx/6d79cb0e7d81dce1be97eec8a5712f08/sbin/nginx -c /srv/slapgrid/slappart46/t/cvt/i/0/tmp/inst/T-0/etc/nginx-master-introspection.conf
          slapuse+ 115090 115059  0 16:14 ?        00:00:00 nginx: worker process
      
      or by looking at cmdline, which is what psutil.Process.cmdline is using:
      
          $ cat /proc/115090/cmdline
          nginx: worker process
      
      and that's why sometimes when cancelling a software release test while
      it is running tests from a software using nginx, some processes are
      leaked, they keep using the port and next test running on this testnode
      fail.
      
      In that case, killall is called with /srv/slapgrid/slappart46/t/cvt , we
      can not find such process with cmdline, but we can extend this heuristic
      to use the current working directory:
      
          $ ls -al /proc/115090/cwd
          lrwxrwxrwx 1 slapuser46 slapuser46 0 Oct 19 16:16 /proc/115090/cwd -> /srv/slapgrid/slappart46/t/cvt/i/0/tmp/inst/T-0
      
      This also applies an optimization of only considering processes of the
      current unix user.
      21147419
  11. 20 Oct, 2023 3 commits
  12. 19 Oct, 2023 2 commits
  13. 18 Oct, 2023 3 commits
  14. 17 Oct, 2023 3 commits