GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||
GeezerVison is showing github.com — GH-100126: Skip incomplete frames in more places by brandtbucher · Pull Request #100613 · python/cpython Conversation
|
|
🤖 New build scheduled with the buildbot fleet by @brandtbucher for commit 53d066e 🤖 If you want to schedule another build, you need to add the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
The one failing buildbot (ARM64 Windows) has been failing on other PRs too. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
One quibble about naming.
Looks good. Hopefully this is the last of the frame stack traversal issues.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
| } | ||
|
|
||
| static inline _PyInterpreterFrame * | ||
| _PyFrame_GetComplete(_PyInterpreterFrame *frame) |
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This name gives no sense of traversing the stack until a complete frame is found.
Maybe _PyFrame_GetFirstComplete()?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.