1. 22 Mar, 2018 3 commits
  2. 15 Feb, 2018 2 commits
  3. 05 Mar, 2018 1 commit
    • Denis Laxalde's avatar
      [pyramid] Recreate CWSession entity when eid no longer exists · 77a543e7878a
      Denis Laxalde authored
      As noted in comment, it might occur that we receive a "sessioneid" from
      a valid cookie while respective CWSession got dropped (typical case is
      db being recreated while users got preserved). In such case, we just
      recreate the CWSession entity as if it did not exist.
      branch : 3.26
  4. 22 Feb, 2018 2 commits
  5. 21 Feb, 2018 1 commit
  6. 15 Feb, 2018 11 commits
  7. 06 Feb, 2018 1 commit
  8. 07 Feb, 2018 1 commit
  9. 01 Feb, 2018 2 commits
  10. 25 Jan, 2018 1 commit
  11. 12 Jan, 2018 1 commit
    • Denis Laxalde's avatar
      [schema] Define a decorator to handle methods override · 46a8146f9703
      Denis Laxalde authored
      There is a number of external classes (from yams/rql) methods overridden
      "by hand" in cubicweb/schema.py. Define a single decorator to factor out
      the pattern. It handles specifying the method name (to avoid conflict
      with the local namespace) and passing the original method to the new
      definition when needed.
  12. 24 Jan, 2018 9 commits
  13. 12 Jan, 2018 3 commits
  14. 12 Dec, 2017 1 commit
    • Denis Laxalde's avatar
      [pyramid] Let logging be configured through .ini file · cd760c411242
      Denis Laxalde authored
      We do not initialize logging in CubicWebPyramidConfiguration thus
      preventing logging to be started with cubicweb's configuration. On the
      other hand, any logging configuration defined in ``development.ini``
      file will be loaded by whatever start the instance using this file (i.e.
      pserve, gunicorn, etc.). The benefit is that logging can now be
      configured per "qualified name" in this file (i.e. one can easily set
      the DEBUG level for the application cube while keeping all dependencies'
      level to WARNING). In the development.ini template, we add logger
      configurations for "logilab" and "cubicweb" qualified names (along with
      those of the application cube).
  15. 01 Dec, 2017 1 commit
    • Denis Laxalde's avatar
      Disable pytest's logs reporting · 6a71cb23f827
      Denis Laxalde authored
      CubicWeb already prints captured logs in stderr upon test failure, so we
      get them twice. Until we fix our logging management, disabling pytest
      capture and restore brings the output level back to sanity.