1. 15 Mar, 2006 1 commit
    • 's avatar
      reverted r65902: · 363c6010
      authored
      - I still believe this was the Right Thing to do, but not everybody agrees
      363c6010
  2. 11 Mar, 2006 1 commit
  3. 10 Mar, 2006 1 commit
  4. 07 Mar, 2006 3 commits
  5. 06 Mar, 2006 1 commit
  6. 28 Feb, 2006 1 commit
    • Sidnei da Silva's avatar
      · bd5f1829
      Sidnei da Silva authored
      - Missing import of NotFound in webdav.Resource.
      bd5f1829
  7. 24 Feb, 2006 1 commit
  8. 21 Feb, 2006 1 commit
  9. 19 Feb, 2006 3 commits
  10. 08 Feb, 2006 2 commits
  11. 27 Jan, 2006 1 commit
  12. 21 Jan, 2006 1 commit
    • Sidnei da Silva's avatar
      · a4f81637
      Sidnei da Silva authored
            - Collector #2002: fixed broken 'ls -R' functionality (didn't
              recurse properly subclasses of OFS.Folder)
      a4f81637
  13. 16 Jan, 2006 1 commit
  14. 15 Jan, 2006 1 commit
  15. 12 Jan, 2006 1 commit
  16. 10 Jan, 2006 1 commit
  17. 28 Dec, 2005 1 commit
    • Sidnei da Silva's avatar
      · af8e4e38
      Sidnei da Silva authored
      - Report number of failures/errors
      af8e4e38
  18. 21 Dec, 2005 3 commits
    • Stefan H. Holek's avatar
      8e8ecbde
    • Sidnei da Silva's avatar
      · 118e4017
      Sidnei da Silva authored
      - Update with Mark's comments:
      
              Problem is that a service/pythonw.exe process *always* has an
              invalid sys.stdout.  But due to the magic of buffering, small
              print statements would not fail - but once the file actually
              got written to, the error happened.  Never a problem when
              debugging, as the process has a console, and hence a valid
              stdout.
      118e4017
    • Sidnei da Silva's avatar
      · fbd73284
      Sidnei da Silva authored
            - Collector #1939: When running as a service, Zope could
              potentially collect too much log output filling the NT Event
              Log. When that happened, a 'print' during exception handling
              would cause an IOError because the service had no 'redirection
              pipe' anymore (because it's shutting down) to write to,
              causing the service to not restart automatically.
      fbd73284
  19. 19 Dec, 2005 2 commits
  20. 16 Dec, 2005 2 commits
  21. 13 Dec, 2005 1 commit
  22. 06 Dec, 2005 1 commit
  23. 05 Dec, 2005 2 commits
  24. 03 Dec, 2005 1 commit
  25. 02 Dec, 2005 6 commits
    • Tres Seaver's avatar
      Made 'zopectl test' work for software homes which do not have an "inplace" build. · 7a46ecdd
      Tres Seaver authored
      It used to require that test.py be in $ZOPE_HOME/bin/;  now it will use
      $ZOPE_HOME as a fallback.
      7a46ecdd
    • Chris Withers's avatar
      4c139617
    • Chris Withers's avatar
      Note ConflictError logging changes. · dadbbc7e
      Chris Withers authored
      dadbbc7e
    • Chris Withers's avatar
      Merge error reporting changes from trunk: · f24d8f73
      Chris Withers authored
      - remove unused import.
      - change SimpleItem.py to use python logging module
      - log at error when standard_error_message can't be rendered
      - give more useful info about errors rendering standard_error_message to the browser.
      - all conflict errors are counted and logged at info
      - logging makes it clear where the conflict has been resolved and where it hasn't
      - errors seen by the user are rendered with standard_error_message and are sent to the error_log which will likely copy them to the event log, depending on the users setup.
      - also checking in a functional test for generating write conflict errors.
        
      (I'll be committing to CHANGES.TXT shortly, I just wanted to keep the merges simpler)
      f24d8f73
    • Chris Withers's avatar
      further changes to ConflictError logging: · b2ea75a2
      Chris Withers authored
      - all conflict errors are counted and logged at info, as they were before Florent's change
      - logging makes it clear where the conflict has been resolved and where it hasn't
      - errors seen by the user are rendered with standard_error_message and are sent to the error_log which will likely copy them to the event log, depending on the users setup.
      - also checking in a functional test for generating write conflict errors.
      
      (I'll be committing to CHANGES.TXT shortly, I just wanted to keep the merges simpler)
      b2ea75a2
    • Chris Withers's avatar
      - change to use python logging module · 1eae46f4
      Chris Withers authored
      - log at error when standard_error_message can't be rendered
      - give more useful info about errors rendering standard_error_message to the browser.
      1eae46f4