#36910: When using daphne, if some process is already listening on our preferred
port, `runserver` does not exit with a failure code.
-------------------------------+--------------------------------------
Reporter: Eric Hanchrow | Owner: (none)
Type: Bug | Status: closed
Component: Uncategorized | Version: 6.0
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Jacob Walls):
* resolution: => invalid
* status: new => closed
* type: Uncategorized => Bug
Comment:
Thanks for the report, but I think this needs to be handled in daphne's
`runserver` command. Can you open an issue on `django/daphne`, assuming
one does not exist already?
--
Ticket URL: <https://code.djangoproject.com/ticket/36910#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019c431c1844-47094835-f974-4f72-8cba-073d43e0c0fb-000000%40eu-central-1.amazonses.com.