Changes between Initial Version and Version 1 of Ticket #26886, comment 7


Ignore:
Timestamp:
Aug 7, 2017, 2:55:19 PM (7 years ago)
Author:
Tim Graham

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #26886, comment 7

    initial v1  
    11Hi,
    22
    3     I another developer who has encountered the same issue. I perused the comments on the mailing list also to see how this would be handled. I agree with the sentiment that errors need to be raised as they are good indicators of underlying issues that need to be fixed. That is true even if, overall, the system works. On the other hand it would be great if the error can be identified for what it is - An known error raised by django internals and handled accordingly. Like the contributer Antony King suggested, a single line capturing the essence of the error would suffice
     3I am another developer who has encountered the same issue. I perused the comments on the mailing list also to see how this would be handled. I agree with the sentiment that errors need to be raised as they are good indicators of underlying issues that need to be fixed. That is true even if, overall, the system works. On the other hand it would be great if the error can be identified for what it is - An known error raised by django internals and handled accordingly. Like the contributer Antony King suggested, a single line capturing the essence of the error would suffice
    44
    5 ``
    6 some_app/home.html:32:24: Undefined variable: missing_variable
    7 ``
     5`some_app/home.html:32:24: Undefined variable: missing_variable`
    86
    97The reason I am suggesting this is, I am using Django 1.11 and the Template_404's error messages are drowning out all other errors. The error is basically caused by favicon.ico resulting in a 404. In the process of development, favicons are the last priority.  So, the developers might have to endure the error messages for a long time. Adding a temporary favicon is a possibility, but I would rather prefer a `"GET /favicon.ico HTTP/1.1" 404 4296` message on the console to remind that favicon is not set :)
    … …  
    119I am providing an example of an exception trace from a single favicon 404 error. May be I am doing something wrong too. If so please suggest an appropriate correction.
    1210
    13 
     11{{{
    1412Exception while resolving variable 'name' in template 'unknown'.
    1513Traceback (most recent call last):
    … …  
    105103Not Found: /favicon.ico
    106104"GET /favicon.ico HTTP/1.1" 404 4296
     105}}}
Back to Top