Add logging support
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- backend, observability
Research direction
Start by locating the code that currently writes messages to stdout and the code that updates hot comments. Determine where elapsed time for those updates can be observed, then define what logging output is needed to assess whether the bot should use a different resume-scraping rubric. No files or tests are named in the issue.
Written by the indexing model from the issue text.
Description
Right now it just pushes messages to stdout. We should have some real logging going on of some kind. In particular, I'd like to log the amount of time it takes to update hot comments to determine if perhaps the bot shouldn't have a different rubric for when to resume normal scraping.
- Dominant language
- Python
- Stars
- 26
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from dmarx/VideoLinkBot
-
"by request" botOpendream
Difficulty 5/5 Over a week Newbie friendliness 25/100
dmarx/VideoLinkBot#37 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
dmarx/VideoLinkBot#36 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
dmarx/VideoLinkBot#34 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
dmarx/VideoLinkBot#33 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
dmarx/VideoLinkBot#31 ·
All issues in dmarx/VideoLinkBot
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openvinotoolkit/openvino_notebooks#3665 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
docs
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
benchmark-gap
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day