I've refactored the application to support local execution with a SQL… #7
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
…ite database. I also removed the Telegram integration, replacing it with a database-based notification system, and switched the LLM provider to Moonshot. Here are the main changes: - **Database:** The database backend has been updated to support both PostgreSQL and SQLite. The default configuration is now set to use a local SQLite database. - **Configuration:** The configuration has been simplified and adapted for local execution. The `config.yml` file is now used to store local settings, including the LLM API key. - **LLM:** The LLM service has been updated to use the Moonshot API, with the model and API key configurable in `config.yml`. - **Telegram Removal:** The Telegram notification service has been completely removed and replaced with a `DatabaseNotificationService` that writes notifications to a new `notifications` table in the database. - **Manual Bounty Input:** The Immunefi indexer has been modified to read bounty information from a local `bounties.json` file, allowing for manual input. - **Error Handling:** The application has been made more resilient to missing block explorer API keys and other environment-specific issues. - **Dependencies:** The `requirements.txt` file has been updated to remove PostgreSQL and Telegram-specific dependencies and add `aiosqlite`.
|
|
Owner
|
Hey thanks for the PR! Those are some big changes packed into a single PR. Would you mind splitting those changes up into 7 separate PRs, one for each feature? Then I'll review them one-by-one. Also, please make sure to sign the Contributor License Agreement. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
…ite database. I also removed the Telegram integration, replacing it with a database-based notification system, and switched the LLM provider to Moonshot.
Here are the main changes:
config.ymlfile is now used to store local settings, including the LLM API key.config.yml.DatabaseNotificationServicethat writes notifications to a newnotificationstable in the database.bounties.jsonfile, allowing for manual input.requirements.txtfile has been updated to remove PostgreSQL and Telegram-specific dependencies and addaiosqlite.