Pebblo retrieval qa/policy propagation #89
Draft
Conversation
This file contains 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
Raj725
force-pushed
the
PebbloRetrievalQA/policy_propagation
branch
from
3ffafb8
to
ce3b01d
Compare
Raj725
force-pushed
the
PebbloRetrievalQA/policy_propagation
branch
from
ce3b01d
to
0bc6d5a
Compare
Update the migration script message
Firecrawl integration is currently on v0 - which is supported until version 0.0.20. @rafaelsideguide is working on a pr for v1 but meanwhile we should fix the docs.
Update broken langgraph link in the README.md file Co-authored-by: Jess Ou <[email protected]>
Added changes for pip installation
takes redirects from 0.1 docs and factors them into suggested redirects in 0.3 docs
- Fix comments in Python - Fix repeated sentences
langchain-cli 0.0.31 release
`langchain-qdrant` imports pydantic but was importing pydantic proper before 0.3 release: https://github.com/langchain-ai/langchain/blob/042e84170bcf05a78ed5892e4c6a66565f2624f3/libs/partners/qdrant/langchain_qdrant/sparse_embeddings.py#L5-L8
Release to work with langchain 0.3
Release to work with langchain 0.3
Release to work with langchain 0.3
Update issue and discussion templates
Update v0.3 instructions a bit --------- Co-authored-by: Bagatur <[email protected]>
… `Cust… (langchain-ai#26312) …omSelfQueryRetriever` This commit corrects an issue in the `_get_docs_with_query` method of the `CustomSelfQueryRetriever` class. The method was incorrectly using `self.vectorstore.similarity_search_with_score(query, **search_kwargs)` without including the `self` argument, which is required for proper method invocation. The `self` argument is necessary for calling instance methods and accessing instance attributes. By including `self` in the method call, we ensure that the method is correctly executed in the context of the current instance, allowing it to function as intended. No other changes were made to the method's logic or functionality. Thank you for contributing to LangChain! - [ ] **PR title**: "package: description" - Where "package" is whichever of langchain, community, core, experimental, etc. is being modified. Use "docs: ..." for purely docs changes, "templates: ..." for template changes, "infra: ..." for CI changes. - Example: "community: add foobar LLM" - [ ] **PR message**: ***Delete this entire checklist*** and replace with - **Description:** a description of the change - **Issue:** the issue # it fixes, if applicable - **Dependencies:** any dependencies required for this change - **Twitter handle:** if your PR gets announced, and you'd like a mention, we'll gladly shout you out! - [ ] **Add tests and docs**: If you're adding a new integration, please include 1. a test for the integration, preferably unit tests that do not rely on network access, 2. an example notebook showing its use. It lives in `docs/docs/integrations` directory. - [ ] **Lint and test**: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/ Additional guidelines: - Make sure optional dependencies are imported within a function. - Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests. - Most PRs should not touch more than one package. - Changes should be backwards compatible. - If you are adding something to community, do not re-import it in langchain. If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17. Co-authored-by: Erick Friis <[email protected]>
Renamed `Layout Analysis` to `Document Parser` in the doc as we have recently renamed it! --------- Co-authored-by: Erick Friis <[email protected]>
**Description:** Add Notebook for NVIDIA prompt completion llm class. cc: @sumitkbh @mattf @dglogo --------- Co-authored-by: Erick Friis <[email protected]>
Co-authored-by: Erick Friis <[email protected]>
happens in Azure
…hain-ai#27110) Given the current erroring behavior, every time we've moved a kwarg from model_kwargs and made it its own field that was a breaking change. Updating this behavior to support the old instantiations / serializations. Assuming build_extra_kwargs was not something that itself is being used externally and needs to be kept backwards compatible
…en used with Box AI (langchain-ai#27012) Thank you for contributing to LangChain! **Description:** Box AI can return responses, but it can also be configured to return citations. This change allows the developer to decide if they want the answer, the citations, or both. Regardless of the combination, this is returned as a single List[Document] object. **Dependencies:** Updated to the latest Box Python SDK, v1.5.1 **Twitter handle:** BoxPlatform - [x] **Add tests and docs**: If you're adding a new integration, please include 1. a test for the integration, preferably unit tests that do not rely on network access, 2. an example notebook showing its use. It lives in `docs/docs/integrations` directory. - [x] **Lint and test**: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/ Additional guidelines: - Make sure optional dependencies are imported within a function. - Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests. - Most PRs should not touch more than one package. - Changes should be backwards compatible. - If you are adding something to community, do not re-import it in langchain. If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17. Co-authored-by: Erick Friis <[email protected]>
…27124) Thank you for contributing to LangChain! - [X] **PR title**: "package: description" - Where "package" is whichever of langchain, community, core, etc. is being modified. Use "docs: ..." for purely docs changes, "templates: ..." for template changes, "infra: ..." for CI changes. - Example: "community: add foobar LLM" - [x] **PR message**: ***Delete this entire checklist*** and replace with - **Description:** Update Spanner VS integration doc - **Issue:** None - **Dependencies:** None - **Twitter handle:** NA - [x] **Add tests and docs**: If you're adding a new integration, please include 1. a test for the integration, preferably unit tests that do not rely on network access, 2. an example notebook showing its use. It lives in `docs/docs/integrations` directory. - [x] **Lint and test**: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/ Additional guidelines: - Make sure optional dependencies are imported within a function. - Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests. - Most PRs should not touch more than one package. - Changes should be backwards compatible. - If you are adding something to community, do not re-import it in langchain. If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17. Co-authored-by: Erick Friis <[email protected]>
updated OpenAI cost definition according to the following: https://openai.com/api/pricing/
# Conflicts: # libs/community/langchain_community/chains/pebblo_retrieval/utilities.py
…725/langchain into PebbloRetrievalQA/policy_propagation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pebblo retrieval qa/policy propagation