feat: implement Telegram API integration and fix TEE memory usage #71
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Replace mock implementation with actual Telegram Bot API calls - Use Node.js fetch to send messages via https://api.telegram.org/bot - Add proper error handling for API responses - Include detailed error messages in response - Fix linter issues with property shorthand
abbesBenayache
requested changes
Aug 8, 2025
- Update e2e tests to handle new response structure with result field - Fix test expectations for error status codes (404 instead of 500) - Update unit tests to use fetch mocks instead of node-telegram-bot-api - All 45 tests now passing with real Telegram API integration
abbesBenayache
force-pushed
the
fix/memory-range-error
branch
from
90d4ae5 to
9f37680
Compare
abbesBenayache
approved these changes
Aug 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Testing
Impact