jihoson/The-Ouroboros
1
0
Fork 0
Code Issues Pull Requests Actions 10 Packages Projects Releases Wiki Activity

Implement TelegramClient core module #31

New Issue
Closed
opened 2026-02-04 21:26:03 +09:00 by agentson · 0 comments
agentson commented 2026-02-04 21:26:03 +09:00
Collaborator
Copy Link

Goal

Create the core TelegramClient module for sending notifications to Telegram.

Scope

  • Create src/notifications/ package
  • Implement TelegramClient class in telegram_client.py
    • NotificationPriority enum (LOW/MEDIUM/HIGH/CRITICAL)
    • LeakyBucket rate limiter (1 msg/sec)
    • Async notification methods (trade, circuit breaker, fat finger, market open/close, system start/shutdown, errors)
    • Graceful degradation (optional API, never crashes)
  • Create src/notifications/__init__.py
  • Create src/notifications/README.md (setup guide, troubleshooting)

Implementation Notes

  • Follow NewsAPI pattern for optional APIs (src/data/news_api.py)
  • Use aiohttp for async HTTP (no new dependencies)
  • Session management pattern from KISBroker

Success Criteria

  • TelegramClient sends notifications successfully
  • Rate limiter prevents spam
  • Works with and without credentials (graceful degradation)

Related

Part 1 of Telegram notification system implementation

## Goal Create the core TelegramClient module for sending notifications to Telegram. ## Scope - Create `src/notifications/` package - Implement `TelegramClient` class in `telegram_client.py` - NotificationPriority enum (LOW/MEDIUM/HIGH/CRITICAL) - LeakyBucket rate limiter (1 msg/sec) - Async notification methods (trade, circuit breaker, fat finger, market open/close, system start/shutdown, errors) - Graceful degradation (optional API, never crashes) - Create `src/notifications/__init__.py` - Create `src/notifications/README.md` (setup guide, troubleshooting) ## Implementation Notes - Follow NewsAPI pattern for optional APIs (src/data/news_api.py) - Use aiohttp for async HTTP (no new dependencies) - Session management pattern from KISBroker ## Success Criteria - TelegramClient sends notifications successfully - Rate limiter prevents spam - Works with and without credentials (graceful degradation) ## Related Part 1 of Telegram notification system implementation
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agentson jihoson
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jihoson/The-Ouroboros#31
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?