Andrew just modified the Testament service to eliminate unsightly errors and immediately e-mail the service developers when an unexpected error occurs.<\/p>\n
At some point, most Testament users will probably have encountered an uncaught exception (in non-programmer-speak, that’s an error that we haven’t anticipated and don’t handle gracefully) with a confusing looking error and traceback (a way for programmers to tell which sequence of events in the program caused the problem) that looks something like this:<\/p>\n
Request Method: GET
\nRequest URL: http:\/\/btptestament.com\/log-package\/2\/<\/a>
\nDjango Version: 0.97-pre-SVN-7554
\nPython Version: 2.5.2
\nInstalled Applications:
\n[‘django.contrib.auth’,
\n‘django.contrib.contenttypes’,
\n‘django.contrib.sessions’,
\n‘django.contrib.sites’,
\n‘django.contrib.admin’,
\n‘btp.core’]
\nInstalled Middleware:
\n(‘django.middleware.common.CommonMiddleware’,
\n‘django.contrib.sessions.middleware.SessionMiddleware’,
\n‘django.contrib.auth.middleware.AuthenticationMiddleware’,
\n‘django.middleware.doc.XViewMiddleware’,
\n‘btp.core.middleware.RequireLoginMiddleware’)<\/p>\nTraceback:
\nFile “\/usr\/lib\/python2.5\/site-packages\/django\/core\/handlers\/base.py” in get_response
\n82. response = callback(request, *callback_args, **callback_kwargs)
\nFile “\/var\/www\/testament\/testament_trunk\/btp\/core\/views.py” in package_address
\n205. add_infobox_context(request, context)
\nFile “\/var\/www\/testament\/testament_trunk\/btp\/core\/helpers.py” in add_infobox_context
\n66. if i.number == NULL_INMATE_NUMBER:<\/p>\nException Type: UnboundLocalError at \/log-package\/2\/
\nException Value: local variable ‘i’ referenced before assignment<\/p><\/blockquote>\nNow you won’t see this mess and we’ll get e-mailed when it happens so we can get the problem identified and fixed ASAP.<\/p>\n
As always, if you want to report a bug, submit a feature request, or ask a question, please use the Testament Get Satisfaction Page<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Andrew just modified the Testament service to eliminate unsightly errors and immediately e-mail the service developers when an unexpected error occurs. At some point, most Testament users will probably have encountered an uncaught exception (in non-programmer-speak, that’s an error that … Continue reading