-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 0.1.21 #431
Version 0.1.21 #431
Conversation
… permission already given to group Added error handling in case permission is already given to group and user is already part of group Feature COG-656
chore: Create pr_lint
Verify user has access to data before returning it Feature COG-656
Add compute search to cognee which makes searches human readable Feature COG-656
Add simple instruction for system prompt Feature COG-656
Raise unauth access error when trying to read data without access Feature COG-656
Rename searching type from compute to completion Refactor COG-656
Update typo in string in code Chore COG-656
Cog 656 deployment state
…cognify pass pydantic model to cognify
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Add mcp to cognee
… pruning data When running cognee a second time after pruning data some metadata doesn't get pruned. This makes cognee believe some tables exist that have been deleted Fix
Added fix when reflecting metadata to sqlite as well Fix
This reverts commit 394a0b2.
fix: Resolve reflection issue when running cognee a second time after…
* feat: parse repo to call graph * Update/repo_processor/top_down_repo_parse.py task * fix: minor improvements * feat: file parsing jedi script optimisation ---------
* Add type to DataPoint metadata * Add missing index_fields * Use DataPoint UUID type in pgvector create_data_points * Make _metadata mandatory everywhere
Added ability to search by datasets for cognee users Feature COG-912
feat: Add ability to change graph database configuration through cognee
…hub.com/topoteretes/cognee into feature/cog-971-preparing-swe-bench-run
Match Ruff version in config to the one in github actions
Code graph pipeline improvements and fixes
…e-bench-run Feature/cog 971 preparing swe bench run
Format with Ruff 0.9.0
…e-bench-run Fix: deleting incorrect repo path
…ting cognee in different packages
…allation fix: resolve issue with langfuse dependency installation
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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 | 7232b04 | notebooks/hr_demo.ipynb | 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.
No description provided.