Support nested tasks with reset_hwm
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 314
- Forks
- 77
- Avg merge
- 4d 6m
- Merged PRs (30d)
- 10
Description
Right now, reset_hwm is not meaningful when measuring nested tasks. We can handle this by tracking peak observed usage around resets ourselves.
Should do tha!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the reset_hwm handling and the code that measures nested tasks. Trace how peak observed usage is currently recorded around resets, then define completion as nested-task measurements retaining the correct peak usage after reset_hwm is used; add focused coverage for that behavior if the existing measurement tests are found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100