-
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
Cog 382 refactor demo notebook #145
Conversation
Combine all Jupyter Notebooks into one Refactor #COG-382
Added link to google colab that uses the latest notebook Refactor #COG-382
WalkthroughThe changes in this pull request involve updates to the Changes
Possibly related PRs
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🧰 Additional context used🪛 LanguageTool
🔇 Additional comments (1)
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 (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove: Some common questions
This tool is not a replacement for vector databases or Langchain, it's an extension
We want to help map the old data world to the new one
Local models and evals are on the roadmap
The relationships in the graph are customizable, so is the graph model. It is something we will continue exploring
Refactor the initial text you added, I think it is fine but it is a bit dated, and it could look better, and have a more consistent look. Some pics are grainy, text of different sizes, some pics have bad visibility. I did a lot of this in 2 hours for some meetup, so would be good to give it a fresh go |
Do we want to have successful code output already as part of the notebook? Or as part of the google colab? |
Should we handle installation of dependencies and setting up of virtual environment as part of the Jupyter Notebook? Or just for the google colab? |
What should we use regarding default databases for the Notebook? Would the following work: |
os.environ["LLM_API_KEY"] = "YOUR OPENAI_API_KEY" no longer works from python code for setting LLM key, it's only read from the .env file currently. Should we support this again? If not we need to update README and notebook |
Environment variables need to be setup properly before pruning Fix #COG-382
Hm, did you test this in collab? It should work |
Yes, that is the default embedded option |
Why? It should be done with pip install cognee as a lib |
Search is included, would need to be refactored to the latest search tasks Boris deployed yesterday. Chat with him on it. fyi @borisarzentar |
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
9573981 | Triggered | Generic Password | f2dfa64 | notebooks/cognee_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.
It's working for me now both in colab and in a local notebook, not sure why I had those issues yesterday |
…actor-demo-notebook
Removed segment regarding common questions from notebook Refactor #COG-382
Changed text size to be more readable and uniform across the notebook Refactor #COG-382
Added new diagram of the problems RAGs have I made with drawio Refactor #COG-382
Refactored most common problems with LLMs to notebook Refactor #COG-382
Refactored explanation about issues with RAGs. Added information on how results are scored. Refactor #COG-382
Added hyperlinks to article mention Refactor #COG-382
Combining all demo notebooks into one single notebook
Summary by CodeRabbit