-
Notifications
You must be signed in to change notification settings - Fork 934
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AssertionError: AbstractLinkable._notifier is None in _notify_links method #1895
Comments
I am also running into this issue |
Digging into this a bit more, I've found that when I start my application with
gevent version: "~21.12.0" pypi I see these errors emitted at the beginning
but the server actually does startup and handles http requests in an asynchronous way. I tried load testing this by sending ~1000 requests to an endpoint that |
I don't know why it does this, but I found a workaround for gunicorn which is:
It does not make much sense to me, but it seems that yielding back the control to the hub prevents this issue from happening. |
I am also running into this issue. |
Hey there! I'm also running into the same issue. Any update on the issue? |
Maybe this help! I had same problem when I tried to to use monkey patch in |
Thanks for the workaround. But after using that, the original http RESTful server function is not working. |
I'm seeing this from |
|
I have started to receive this error when I upgrade the package gevent from 23.9.1 to 24.2.1 (Python image 3.11.8)
|
Description:
Running django 3.2 using gunicorn 20.1. I keep seeing this traceback in my logs from
gevent/_abstract_linkable.py
assert self._notifier is notifier, (self._notifier, notifier)
.No other logs surrounding these in the given context.
Is this something to be concerned about or anything I can fix?
What I've run:
ddtrace-run gunicorn --workers 5 --worker-class gevent project_name.wsgi:application
The text was updated successfully, but these errors were encountered: