databrickslabs / databrickslabs/pytester
Watchdog documentation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
I'm interested in the watchdog functionality, but I'm a bit lost as to how it works.
Looking at the code I can see it's setting timestamps for a watchdog to go and clean up resources later, but I can't find any code that goes to do that cleanup.
Could someone point me to some docs or code that would explain how the watchdog works?
Contributor guide
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 tracing the watchdog functionality from the code that sets cleanup timestamps and locate the code that performs the later resource cleanup. Document the relevant entry points and lifecycle so a reader can follow how the watchdog works; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100