1. 26 May, 2021 1 commit
  2. 05 May, 2021 1 commit
  3. 07 Jul, 2021 3 commits
  4. 29 Jun, 2021 1 commit
  5. 30 Jun, 2021 1 commit
  6. 24 Jun, 2021 1 commit
  7. 22 Jun, 2021 1 commit
  8. 09 Jun, 2021 2 commits
  9. 16 Jun, 2021 1 commit
  10. 04 May, 2021 1 commit
  11. 16 Apr, 2021 1 commit
    • Nicolas Chauvat's avatar
      fix previous merge · e9bcc40fe720
      Nicolas Chauvat authored
      - renaming raw_input to input
      - removing from __future__ import
      - web/views/management.py
      
      --HG--
      branch : 3.28
      e9bcc40fe720
  12. 03 Dec, 2020 1 commit
  13. 07 Oct, 2020 2 commits
  14. 04 Jun, 2020 1 commit
  15. 15 May, 2020 1 commit
  16. 12 May, 2020 1 commit
  17. 08 May, 2020 2 commits
    • Simon Chabot's avatar
      fix(tests): test_chmod checks whether the permissions are the same as the source file · 527d2989602e
      Simon Chabot authored
      test_chmod used to check that permission are 644, but this is not what is done
      in the `process_resource` method. This function sets the permissions to the same
      as the source file.
      
      As a consequence, depending on your configuration (default umask for instance),
      you may end up with the expected 644 permissions or… something else. (666 on our
      gitlab-runner for instance).
      
      To make the test consistent with what is done in the function, and consistent
      with the initial purpose of this test [0], let's simply check that the
      permissions of the source file and the compiled file are the same.
      
      If it appears that this is not enough, a solution could be to enforce 644
      permissions in the `process_resource` method, or give the expected permissions
      through parameters.
      
      [0]: https://www.cubicweb.org/ticket/17143773
      527d2989602e
    • Simon Chabot's avatar
      fix(tests): test_chmod checks whether the permissions are the same as the source file · 8b49be4828fc
      Simon Chabot authored
      test_chmod used to check that permission are 644, but this is not what is done
      in the `process_resource` method. This function sets the permissions to the same
      as the source file.
      
      As a consequence, depending on your configuration (default umask for instance),
      you may end up with the expected 644 permissions or… something else. (666 on our
      gitlab-runner for instance).
      
      To make the test consistent with what is done in the function, and consistent
      with the initial purpose of this test [0], let's simply check that the
      permissions of the source file and the compiled file are the same.
      
      If it appears that this is not enough, a solution could be to enforce 644
      permissions in the `process_resource` method, or give the expected permissions
      through parameters.
      
      [0]: https://www.cubicweb.org/ticket/17143773
      
      --HG--
      branch : 3.27
      8b49be4828fc
  18. 11 Apr, 2020 3 commits
  19. 28 Jan, 2021 1 commit
  20. 26 Jan, 2021 1 commit
  21. 18 Sep, 2020 1 commit
  22. 20 Mar, 2020 1 commit
    • Simon Chabot's avatar
      [plpython] Drop plpython support · dcf0ff54dec6
      Simon Chabot authored
      plpython has never been used in cubicweb. Moreover, it prevents
      the upgrade to postgresql 12. In consequence, as of now importing
      plpython is the responsability of each cube.
      
      closes #17277267
      
      co-authors:
          - Guillaume Vandevelde
          - Katia Saurfelt
          - Noé Gaumont
          - Simon Chabot
      dcf0ff54dec6
  23. 28 May, 2021 1 commit
  24. 12 Jun, 2021 1 commit
  25. 09 Jun, 2021 1 commit
  26. 20 May, 2021 1 commit
  27. 28 May, 2021 1 commit
  28. 08 Jun, 2021 1 commit
  29. 04 Jun, 2021 1 commit
  30. 20 May, 2021 1 commit
  31. 26 May, 2021 1 commit
  32. 20 May, 2021 1 commit
  33. 05 May, 2021 1 commit