Tgv 53 alter cognee prompts to be project relevant #886
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
Update dockerfile
…aset Add dataset parameter for search
Update to cognee main
Please make sure all the checkboxes are checked:
|
Contributor
|
Caution Review failedThe pull request is closed. WalkthroughThis update introduces a new setup guide, enhances file and URL handling for add and delete endpoints, adds a health check API, includes a graph metrics calculation task, and updates the Dockerfile to install the PostgreSQL client library. The entrypoint script gains improved logging and process management. A notebook subproject reference is removed. Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant API as FastAPI App
participant AddRouter
participant DeleteRouter
participant GitHub
participant HTTPServer
Client->>API: POST /api/v1/add (file or url)
API->>AddRouter: handle add()
alt file upload
AddRouter->>AddRouter: Read/decode file
else url provided
AddRouter->>AddRouter: Validate URL
alt github url
AddRouter->>GitHub: git clone
else http url
AddRouter->>HTTPServer: GET content
end
end
AddRouter-->>API: Response
API-->>Client: HTTP Response
Client->>API: POST /api/v1/delete (file or url)
API->>DeleteRouter: handle delete()
alt file upload
DeleteRouter->>DeleteRouter: Read/decode file
else url provided
DeleteRouter->>DeleteRouter: Validate URL
alt github url
DeleteRouter->>GitHub: git clone
else http url
DeleteRouter->>HTTPServer: GET content
end
end
DeleteRouter-->>API: Response
API-->>Client: HTTP Response
Client->>API: GET /health
API->>API: health_check()
API-->>Client: {"status": "healthy"}
sequenceDiagram
participant CognifyAPI
participant TaskPipeline
participant GraphEngine
participant DB as Database
CognifyAPI->>TaskPipeline: get_default_tasks()
TaskPipeline->>GraphEngine: get_graph_metrics()
GraphEngine-->>TaskPipeline: Metrics data
TaskPipeline->>DB: Store GraphMetrics
DB-->>TaskPipeline: Commit
TaskPipeline-->>CognifyAPI: Continue pipeline
Possibly related PRs
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (12)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 9573981 | Triggered | Generic Password | 085b201 | .github/workflows/relational_db_migration_tests.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
almondbuttertoast
deleted the
TGV-53-alter-cognee-prompts-to-be-project-relevant
branch
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.
Description
DCO Affirmation
I affirm that all code in every commit of this pull request conforms to the terms of the Topoteretes Developer Certificate of Origin.