Skip to content
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

AbstractLinkable._notify_links under VS Code debugger #1999

Open
dsuch opened this issue Sep 27, 2023 · 2 comments
Open

AbstractLinkable._notify_links under VS Code debugger #1999

dsuch opened this issue Sep 27, 2023 · 2 comments

Comments

@dsuch
Copy link

dsuch commented Sep 27, 2023

Hello,

this is more of a FYI ticket - I will not have time to work on it further but it may be of interest or importance to you, @jamadden.

I have an application that is currently using gevent v. 23.9.1, the behaviour that I am about to describe was observable under 22.10.2 and it started less than a year ago. Python versions are from 3.8 to 3.11.

The behaviour is this - whenever I start the application under debugger in VS Code, I am getting this exception in logs:

Traceback (most recent call last):
  File "src/gevent/_abstract_linkable.py", line 287, in gevent._gevent_c_abstract_linkable.AbstractLinkable._notify_links
  File "src/gevent/_abstract_linkable.py", line 333, in gevent._gevent_c_abstract_linkable.AbstractLinkable._notify_links
AssertionError: (None, <callback at 0x7f80422c3dc0 args=([],)>)
2023-09-27T18:53:43Z <callback at 0x7f80422c3dc0 args=([],)> failed with AssertionError

This never happens in a standalone process and, under VS Code, this does not prevent the application from anything, it continues to run correctly, which is why it is not any priority from my perspective.

Yet, perhaps this is a manifestation of something that you would like to know about, which is why I am opening this ticket.

Regards.

@digdeep44
Copy link

Observing the same after upgrading to 3.11, traced it back till 3.8 as per this post, it occurs till 3.9
Application does not break, and our greenlets also work fine, but getting this traceback on first yield/blocking operation.

@jamadden any update on this?

@Pajinek
Copy link

Pajinek commented Feb 15, 2024

I found similar old issue #1895 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants