tolik518 / tolik518/factorion-bot
Add more logging
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 51
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
- What we're getting (if check_posts/check_mentions is true), like
Getting comments, posts, inbox - How many comments total were returned by the api (
comments.len()) - How long we sleep for (reply and polling)
- What the current ratelimit values are, like
504s till reset, 783 requests remaining - the current
last_idsvalues, likeLast ids were t1_msu372s (comments) t3_msu42sa (posts) t1_ue14n2s (inbox)
In general, I would use debug for data useful while developing/debugging (duh), logged once a loop or reply at most. And trace could be used for stuff that happens every gotten comment, though I have no ideas, what could be useful there.
Originally posted by @Aras14HD in https://github.com/tolik518/factorion-bot/issues/167#issuecomment-2781401621
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 locating the code paths for check_posts/check_mentions, comment retrieval, reply and polling sleeps, rate-limit handling, and last_ids updates. Add debug or trace coverage for the listed values, then verify that each loop or reply exposes the requested state without excessive per-comment logging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100