You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few PostgreSQL queries have timed out from being too long (45s+).
When this happens, trying to access the debugtoolbar BEFORE the request is killed will break the toolbar and generate a generic 'Internal Server Error' from waitress.
This is "secondarily" caused by exceptions raised in templates or panels due to the lack of proper variables in the environment. For example:
panels/performance.py will not have set self.total_time
panels/templates/headers.dbtmako doesn't have request_headers or response_headers
I'm not sure that the primary cause of this code even being executed is though. I think it may be because the request is added to the toolbar before it completes, but I'm not familiar with that part of the package. If that is the case, it may make sense to annotate the request with a 'completed' flag, and only run the panels on completed requests. This is just a wild guess though.
Edit:
This error happens when accessing the root/splash '/_debug_toolbar/' or a page that no longer exists and there is a long-running query. It does not happen when accessing a valid/completed request in the toolbar during the same long-running query.
The text was updated successfully, but these errors were encountered:
A few PostgreSQL queries have timed out from being too long (45s+).
When this happens, trying to access the debugtoolbar BEFORE the request is killed will break the toolbar and generate a generic 'Internal Server Error' from waitress.
This is "secondarily" caused by exceptions raised in templates or panels due to the lack of proper variables in the environment. For example:
I'm not sure that the primary cause of this code even being executed is though. I think it may be because the request is added to the toolbar before it completes, but I'm not familiar with that part of the package. If that is the case, it may make sense to annotate the request with a 'completed' flag, and only run the panels on completed requests. This is just a wild guess though.
Edit:
This error happens when accessing the root/splash '/_debug_toolbar/' or a page that no longer exists and there is a long-running query. It does not happen when accessing a valid/completed request in the toolbar during the same long-running query.
The text was updated successfully, but these errors were encountered: