-
Notifications
You must be signed in to change notification settings - Fork 0
Add Issue Tracking Framework and Initial Monitoring Issues #90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Add systematic issue tracking framework in docs/issues/ with: - Standardized naming convention: <priority>-<type>-<description>.md - Priority levels 0-3 (critical to low) - Issue types: bug, feature, docs, chore - Comprehensive documentation and workflow guidelines Initial issues documented: - Startup duplicate notifications bug (priority 1) - Seen submission race condition (priority 1) - Timezone handling inconsistencies (priority 2) - Enhanced monitoring loop debug logging (priority 2) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Codecov ReportAttention: Patch coverage is
📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR introduces a structured issue tracking framework under docs/issues/ and documents four initial monitoring-related issues. Additionally, it tweaks runtime debug logging in the bot startup sequence and updates the Litestream replica path.
- Wraps initial debug logging in
before_monitor_task_loopwith error handling - Updates the Litestream replica path from
dbtodb-v2 - Adds framework documentation and four issue files for tracking bugs and features
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| src/cogs/runner.py | Wrap debug info logs in a try/except during startup |
| litestream.yml | Change replica path from db to db-v2 |
| docs/issues/CLAUDE.md | Add issue tracking framework guidelines |
| docs/issues/2-feature-monitoring-loop-debug-logging.md | Document feature for enhanced monitoring debug logs |
| docs/issues/2-bug-timezone-handling-inconsistency.md | Document timezone handling inconsistency bug |
| docs/issues/1-bug-startup-duplicate-notifications.md | Document startup duplicate notifications bug |
| docs/issues/1-bug-seen-submission-race-condition.md | Document seen submission race condition bug |
Comments suppressed due to low confidence (2)
src/cogs/runner.py:437
- Add a test case to simulate a failure during startup logging and verify that the error handling branch in this loop works as expected.
async def before_monitor_task_loop(self):
docs/issues/CLAUDE.md:1
- The filename
CLAUDE.mdmay be confusing and doesn’t follow the<priority>-<type>-<description>.mdpattern—consider renaming it to something likeissue-tracking-framework.mdorframework.md.
# Issue Tracking Framework
Fix prettier formatting issues in issue tracking framework: - Reformat all markdown files in docs/issues/ directory - Ensure consistent markdown formatting across the project - Resolve CI lint failures for prettier check 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Summary
docs/issues/Framework Features
<priority>-<type>-<description>.mdformatInitial Issues Documented
Benefits
🤖 Generated with Claude Code