Opened 4 years ago
Closed 4 years ago
#32240 closed Cleanup/optimization (fixed)
ConnectionAbortedError should be treated as a broken pipe error in the development server
Reported by: | Petter Strandmark | Owned by: | Petter Strandmark |
---|---|---|---|
Component: | HTTP handling | Version: | 3.1 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
People using Windows have been complaining about very long stack traces in the development server for a long time:
These happen under normal interaction with the development server using Chrome.
I have fixed one issue in CPython in wsgiref, but I belive that we should also fix is_broken_pipe_error in django/core/servers/basehttp.py
Change History (6)
comment:1 by , 4 years ago
Has patch: | set |
---|
comment:2 by , 4 years ago
Triage Stage: | Unreviewed → Accepted |
---|---|
Type: | Uncategorized → Cleanup/optimization |
comment:3 by , 4 years ago
Needs tests: | set |
---|
comment:4 by , 4 years ago
Needs tests: | unset |
---|
comment:5 by , 4 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
Note:
See TracTickets
for help on using tickets.
Hi Petter. Thanks for the report. Happy to have a look at this yes!