[Django] #35351: Getting event loop closed error when using aiomysql with Django async views

[Django]

#35351: Getting event loop closed error when using aiomysql with Django async views
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
owais142002 |
Type: Bug | Status: new
Component: Database | Version: 5.0
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I am getting same issue as this guy in StackOverflow
https://stackoverflow.com/questions/78165096/flask-with-aiomysql-runtime-
error-event-loop-closed
only difference is that he is using flask and I am using Django. First
request works fine and data is stored to db but then for all the requests
I am getting event loop closed error.
Can anyone help me here please.
--
Ticket URL: <https://code.djangoproject.com/ticket/35351>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#35351: Getting event loop closed error when using aiomysql with Django async views
-------------------------------------+-------------------------------------

Reporter: Owais Ahmed | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
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 Natalia Bidart):

* resolution: => invalid
* status: new => closed

Comment:

Hello,

This ticket seems better suited to be a support request. The best place to
get answers to your issue is using any of the user support channels from
[https://docs.djangoproject.com/en/dev/faq/help/#how-do-i-do-x-why-
doesn-t-y-work-where-can-i-go-to-get-help this link].

Since the goal of this issue tracker is to track issues about Django
itself, and your issue seems, at first, to be located in your custom code,
I'll be closing this ticket as invalid following the
[https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/#closing-tickets ticket triaging process]. If, after debugging,
you find out that this is indeed a bug in Django, please re-open with the
specific details and please be sure to include a small Django project to
reproduce or a failing test case.

Thank you!
--
Ticket URL: <https://code.djangoproject.com/ticket/35351#comment:1>