Difference between revisions of "Improve error handling/reporting"

From VistrailsWiki
Jump to navigation Jump to search
Line 1: Line 1:
* Can we have an error console on the splash screen?
* Splash screen now shows package initialization


* Classifying log levels
* Classifying log levels
Line 6: Line 6:
** warning 30
** warning 30
** critical 50
** critical 50
*the QT signal handling is currently unused but I assume it is being used when debugging signals. Don't know if it should be logged as critical though? I can remove the QT dependency by moving relevant parts to the gui directory.


*~800 print statements in VisTrails + 200 commented ones
*~800 print statements in VisTrails + 200 commented ones


* persistence package heavily uses own debug_print function
* Translating issues
 
** core/upgradeworkflow.py
*What to do with the classic startup sequence:
*** debug.critical('Package cannot handle upgrade request. VisTrails will attempt automatic upgrade.') - Should it be critical?
**Do we want to keep them visible?
**If we set them as info they wont be seen on the default verboseness level.
Initializing basic_modules
Initializing spreadsheet
Loading Spreadsheet widgets...
==> Successfully import <Basic Widgets>
==> Successfully import <SVG Widgets>
==> Successfully import <WebKit Viewer>
==> Successfully import <Image Viewer>
==> Successfully import <HTML Viewer>
Initializing controlflow
Initializing HTTP

Revision as of 09:48, 12 November 2010

  • Splash screen now shows package initialization
  • Classifying log levels
    • debug 10 (cannot be accessed by setting loglevel)
    • log(info) 20
    • warning 30
    • critical 50
  • ~800 print statements in VisTrails + 200 commented ones
  • Translating issues
    • core/upgradeworkflow.py
      • debug.critical('Package cannot handle upgrade request. VisTrails will attempt automatic upgrade.') - Should it be critical?
Retrieved from "https://www.vistrails.org//index.php?title=Improve_error_handling/reporting&oldid=3693"