#30799: Unknown call done to "GET /graphql HTTP/1.1" with brand new project
django
2.2.5
-------------------------------------+-------------------------------------
Reporter: Roberto Fernandez | Owner: nobody
Diaz |
Type: Bug | Status: closed
Component: Uncategorized | Version: 2.2
Severity: Release blocker | Resolution: invalid
Keywords: graphql, http | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Not sure if graphene is behind this `/graphql` endpoint but I encountered
a really similar issue a while ago that was caused by the fact
[https://github.com/syrusakbary/promise/issues/57#issuecomment-396716706
the promise library it uses is not thread safe] and Django's development
server uses threads by default. You can determine if that's the actual
issue by [https://docs.djangoproject.com/en/2.2/ref/django-admin
/#cmdoption-runserver-nothreading temporarily disabling multi-threading in
the development server].
As Claude said please seek advice from our support channels to confirm
this is an actual issue with Django itself before submitting a bug report
--
Ticket URL: <https://code.djangoproject.com/ticket/30799#comment:4>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/071.36aa1897856812c334a1d68ea32087be%40djangoproject.com.
