Code

Opened 22 months ago

Last modified 22 months ago

#18542 new Bug

Intermittent unhandled exception when killing runserver

Reported by: RoySmith Owned by: nobody
Component: Core (Management commands) Version: 1.4
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Starting from a brand new django 1.4 project with no user code, I started up runserver and got the usual "Congratulations on your first Django-powered page.". Then I killed runserver with a Control-C and got the following. I haven't been able to reproduce this, so I'm guessing it's some race condition. Doesn't seem to be a critical issue, so just opening this ticket to document what happened.

I'm running:

OSX 10.6.8
Python 2.7
Django 1.4

$ ./manage.py runserver
Validating models...

0 errors found
Django version 1.4, using settings 'scoregatta.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
[29/Jun/2012 12:10:19] "GET / HTTP/1.1" 200 1961
^CUnhandled exception in thread started by <bound method Command.inner_run of <django.contrib.staticfiles.management.commands.runserver.Command object at 0x1019cc6d0>>
Traceback (most recent call last):
  File "/Users/roy/scoregatta/env/lib/python2.7/site-packages/django/core/management/commands/runserver.py", line 111, in inner_run
     ipv6=self.use_ipv6, threading=threading)
  File "/Users/roy/scoregatta/env/lib/python2.7/site-packages/django/core/servers/basehttp.py", line 253, in run

Attachments (0)

Change History (2)

comment:1 Changed 22 months ago by aaugustin

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

comment:2 Changed 22 months ago by claudep

Note the similarities with #14273 and #17581, even if the tracebacks are not identical.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as new
The owner will be changed from nobody to anonymous. Next status will be 'assigned'
as The resolution will be set. Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.