| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I'm not sure about news entry too. |
Sorry, something went wrong.
|
@pablogsal Could you please take a look? |
Sorry, something went wrong.
|
Thanks a lot for the great work on this @sergey-miryanov! I pushed a set of follow-up commits on top because we are getting close to beta freeze and I wanted to make sure this lands in a solid shape. The follow-ups validate the remote GC stats offset and reject incompatible remote layoutsinstead of accepting short reads, reject a NULL remote GC stats pointer, record timestamps in the free-threaded GC path, and document why ts_stop is published last. I also moved the non-trivial GC stats implementation out of the header into gc_stats.c and updated the POSIX and Windows build files for that split. The API now returns _remote_debugging.GCStatsInfo structseq objects instead of dictionaries, matching the rest of _remote_debugging, and the docs/Clinic text now describes the fields and errors properly. I dropped heap_size from the exposed docs since it is not actually exposed by the current stats layout. On the test side, I renamed the test file to test_gc_stats.py, added timestamp and field coverage, updated the assertions for GCStatsInfo, and changed the workload to allocate tracked self-referential containers so the candidate counts advance deterministically. |
Sorry, something went wrong.
Documentation build overview4 files changed ± contents.html ± c-api/perfmaps.html ± whatsnew/3.15.html ± whatsnew/changelog.html |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Thanks for this @sergey-miryanov this was such a cool idea!
Sorry, something went wrong.
|
Thanks so much, @pablogsal! You did excellent work shaping this into its final form! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR implements second part of the issue. Instead of adding a new module or extending the gc module we add new function to the _remote_debugging module as it is a best place for this.