(new docs): update branch and resolve conflicts around build #21271
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
…ndling (#20116) Co-authored-by: gaoyuan <[email protected]>
…/17690 Thank you for contributing to LangChain! - [x] **Fix Google Lens knowledge graph issue**: "langchain: community" - Fix for [No "knowledge_graph" property in Google Lens API call from SerpAPI](#17690) - [x] **PR message**: ***Delete this entire checklist*** and replace with - **Description:** handled the existence of keys in the json response of Google Lens - **Issue:** [No "knowledge_graph" property in Google Lens API call from SerpAPI](#17690) - [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/ If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, hwchase17. Co-authored-by: Bagatur <[email protected]>
- **Description:** Change Bedrock's Mistral stop sequence key mapping to "stop" rather than "stop_sequences" which is the correct key [Bedrock docs link](https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters-mistral.html) `{ "prompt": string, "max_tokens" : int, "stop" : [string], "temperature": float, "top_p": float, "top_k": int }` - **Issue:** #20053 - **Dependencies:** N/A - **Twitter handle:** N/a
…route with `HuggingFaceEndpoint` (#20100) - **Description:** allows to use the /generate route of `text-generation-inference` with the `HuggingFaceEndpoint`
- [x] **Add Near NFT loader**: "community: Load NFT near block chain
using mintbase graph API"
- [x] **PR message**:
- **Description:** a description of the change
- **Twitter handle:**Kurodenjiro
---------
Co-authored-by: Bagatur <[email protected]>
Co-authored-by: Bagatur <[email protected]>
Right now, `tool_calls` are not included in the `pretty_print()` output. Would be nice to show! 
Cassio 0.6+ is recommended for async vector store (not blocking on getting the embedding dimension) and for hybrid search support.
Chains should not be emitting deprecation warnings.
Technically a slight prompt breaking change, but I think positive EV in that it saves tokens and results in more sane / in-distribution prompts
## Summary I ran `ruff check --extend-select RUF100 -n` to identify `# noqa` comments that weren't having any effect in Ruff, and then `ruff check --extend-select RUF100 -n --fix` on select files to remove all of the unnecessary `# noqa: F401` violations. It's possible that these were needed at some point in the past, but they're not necessary in Ruff v0.1.15 (used by LangChain) or in the latest release. Co-authored-by: Erick Friis <[email protected]>
…s to core (#20750) * Move storage interface to core * Move in memory and file system implementation to core
…21042) ### Description: When attempting to download PDF files from arXiv, an unexpected 404 error frequently occurs. This error halts the operation, regardless of whether there are additional documents to process. As a solution, I suggest implementing a mechanism to ignore and communicate this error and continue processing the next document from the list. Proposed Solution: To address the issue of unexpected 404 errors during PDF downloads from arXiv, I propose implementing the following solution: - Error Handling: Implement error handling mechanisms to catch and handle 404 errors gracefully. - Communication: Inform the user or logging system about the occurrence of the 404 error. - Continued Processing: After encountering a 404 error, continue processing the remaining documents from the list without interruption. This solution ensures that the application can handle unexpected errors without terminating the entire operation. It promotes resilience and robustness in the face of intermittent issues encountered during PDF downloads from arXiv. ### Issue: #20909 ### Dependencies: none --------- Co-authored-by: Bagatur <[email protected]>
…ecursiveUrlLoader (#20632) As shown in #13749 , `RecursiveUrlLoader` has encoding issue. This PR is to solve this. --------- Co-authored-by: Bagatur <[email protected]> Co-authored-by: Bagatur <[email protected]>
…trusted_input parameter (#19985) **Description:** update version of LayerupSecurity package for the Layerup Security integration. Add untrusted_input parameter.
## Summary No new diagnostics (given that the set of enabled rules hasn't changed), but gains access to our new parser (much faster) and reduced false positives all around.
Migrate document transformers
Upgrades prompts module to use optional imports. This code was generated with a migration script, but had to be adjusted manually a bit. Testing in preparation for applying this code modification across the rest of the modules in langchain package to reverse the dependency between langchain community and langchain.
…21100) Migrate graphs to use optional community imports.
…y imports (#21103) Migrate output parsers
#21117) Migrate tools to treat community imports as optional
* Introduce individual `fetch_` methods for easier typing. * Rework some docstrings to google style * Move some logic to the tool * Merge the 2 cassandra utility files
…using tool_calls or content) (#21201) This PR fixes #21196. The error was occurring when calling chat completion API with a chat history. Indeed, the Mistral API does not accept both `content` and `tool_calls` in the same body. This PR removes one of theses variables depending on the necessity. --------- Co-authored-by: Maxime Perrin <[email protected]> Co-authored-by: Chester Curme <[email protected]>
…gent (#21205) **PR message**: - **Description:** Corrected a syntax error in the code comments within the `create_tool_calling_agent` function in the langchain package. - **Issue:** N/A - **Dependencies:** No additional dependencies required. - **Twitter handle:** N/A
Co-authored-by: ccurme <[email protected]>
- this hasn't been used in a long time and requires some additional bookkeeping i'm going to streamline in the next pr
Updating Nvidia docs ahead for 5/15 competition. Thanks!
The current doc-string comment is referring to the wrong schema.
# Newline Characters breaking formatting **Description**: As you can see in the image below, the formatting in the documentation is broken. As far as I can see the two added `\n` characters are breaking the documentation. Therefore I would propose to remove those  **Dependencies**: None **Twitter Handle** - epu9byj --------- Co-authored-by: gere <[email protected]> Co-authored-by: Chester Curme <[email protected]>
dosubot
bot
added
the
size:XXL
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dosubot
bot
added
🔌: google
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.
No description provided.