Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

gh-143952: Fix asyncio tools to work with the new remote debugging API#143954

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

@johnslavik
Copy link
Member

@johnslavikjohnslavik commentedJan 17, 2026
edited by bedevere-appbot
Loading

cocolato reacted with thumbs up emoji
@aisk
Copy link
Contributor

Hi, I'm wondering if we can add some tests to ensure we don't break this again in the future?

@johnslavikjohnslavik marked this pull request as draftJanuary 17, 2026 07:00
@johnslavik
Copy link
MemberAuthor

Something's very wrong here. On it.

@johnslavik
Copy link
MemberAuthor

johnslavik commentedJan 17, 2026
edited
Loading

Oh, okay. We have tests for tools but we don't import structures from_remote_debugging. Instead we have our own:

FrameInfo=namedtuple('FrameInfo', ['funcname','filename','lineno'])
CoroInfo=namedtuple('CoroInfo', ['call_stack','task_name'])
TaskInfo=namedtuple('TaskInfo', ['task_id','task_name','coroutine_stack','awaited_by'])
AwaitedInfo=namedtuple('AwaitedInfo', ['thread_id','awaited_by'])

CC@kumaraditya303

@johnslavik
Copy link
MemberAuthor

OK I guess that's it for the fix itself!

@johnslavikjohnslavik marked this pull request as ready for reviewJanuary 17, 2026 07:16
@johnslavik
Copy link
MemberAuthor

johnslavik commentedJan 17, 2026
edited
Loading

We'd want to keep these structures in sync later (we also don't have.opcode inFrameInfo in tests for instance).
I'll check the remote debugging tests in regard to how they manage these structures.

@johnslavik
Copy link
MemberAuthor

OK, it's not a problem. We would just have to pass sequences and we could use original structures.

>>>from _remote_debuggingimport FrameInfo>>> FrameInfo(range(4))_remote_debugging.FrameInfo(filename=0, location=1, funcname=2, opcode=3)

@johnslavik
Copy link
MemberAuthor

We'd want to keep these structures in sync later (we also don't have.opcode inFrameInfo in tests for instance). I'll check the remote debugging tests in regard to how they manage these structures.

SeeGH-143955.

pablogsal reacted with thumbs up emoji

Copy link
Member

@pablogsalpablogsal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Great catch! In retrospective this indeed was doomed to happen so I am glad that we are looking at this

johnslavik reacted with heart emoji
@pablogsalpablogsal merged commit63cc125 intopython:mainJan 18, 2026
51 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@pablogsalpablogsalpablogsal approved these changes

@1st11st1Awaiting requested review from 1st11st1 is a code owner

@asvetlovasvetlovAwaiting requested review from asvetlovasvetlov is a code owner

@kumaraditya303kumaraditya303Awaiting requested review from kumaraditya303kumaraditya303 is a code owner

@willingcwillingcAwaiting requested review from willingcwillingc is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@johnslavik@aisk@pablogsal

[8]ページ先頭

©2009-2026 Movatter.jp