🛠️ fix: fix telegram sender

[sudoskys]

Summary by CodeRabbit

• New Features
  • Introduced a new configuration file for contributor management, allowing customization of issue tracking and reporting.
• Improvements
  • Enhanced message handling by considering both text and caption attributes in message objects.
  • Improved retry mechanism with a dynamic exponential backoff strategy for better performance during transient errors.

[coderabbitai]

Walkthrough

The recent updates enhance the contributor management system by introducing a new configuration file, .nerve.toml, which allows for customizable contributor settings and improved issue handling. In addition, the transcribe function in the Telegram sender module now robustly retrieves message text or captions, and the retry mechanism in the OpenAI request handling has been refined with an exponential backoff strategy. These changes improve the overall functionality and error handling across the system.

Changes

Files	Change Summary
.nerve.toml	Introduced configuration settings for contributors, including unique identifiers, language preference, and issue handling options.
app/sender/telegram/__init__.py	Updated transcribe function to robustly retrieve message text or caption, enhancing message handling.
llmkira/openai/request.py	Modified extract method with an improved @retry decorator that incorporates an exponential backoff strategy for retries.

Poem

🐇 In the meadow where the code does play,
New settings sprout, brightening the day!
With messages clear and retries so grand,
Our system hops forward, just like we planned!
So let's cheer for changes, a dance in the light,
For coding together makes everything right! 🌼✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between eb39140 and 72ae92d.

Files selected for processing (3)

• .nerve.toml (1 hunks)
• app/sender/telegram/init.py (1 hunks)
• llmkira/openai/request.py (1 hunks)

Files skipped from review due to trivial changes (1)

• .nerve.toml

Additional comments not posted (2)

llmkira/openai/request.py (1)

232-236: LGTM! But verify the method usage in the codebase.

The code changes are approved.

However, ensure that all calls to the extract method are correctly handled with the new retry mechanism.

Verification successful

---

Verified: The extract method is correctly handled across the codebase.

The method extract is used in several files, and there are no issues with the new retry mechanism.

• llmkira/openai/cell.py
• llmkira/logic/__init__.py
• llmkira/extra/voice/__init__.py
• llmkira/openai/request.py

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify all method calls to `extract` are correctly handled.

# Test: Search for the method usage. Expect: Only occurances of the new method signature.
rg --type python -A 5 $'extract'

Length of output: 62

---

Script:

#!/bin/bash
# Description: Verify all method calls to `extract` are correctly handled.

# Test: Search for the method usage. Expect: Only occurrences of the new method signature.
rg --type py -A 5 $'extract'

Length of output: 3428

app/sender/telegram/__init__.py (1)

73-81: LGTM!

The updated logic for assigning the message_text variable enhances the robustness of the code by considering both text and caption attributes.