11213 Commits (da113f63630f4c37ba9271e8580da5b77cbecc83)

 

All Branches   

Search

Author	SHA1	Message	Date
Bagatur	da113f6363	docs: ChatOpenAI.with_structured_output nits (#25952)	2 weeks ago
Bagatur	5b99bb2437	docs: fix bullet list spacing (#25950) ... Fix #25935	2 weeks ago
Yuki Watanabe	ef329f6819	docs: Fix databricks doc (#25941) ... https://github.com/langchain-ai/langchain/pull/25929 broke the layout because of missing `:::` for the caution clause. Signed-off-by: B-Step62 <yuki.watanabe@databricks.com>	2 weeks ago
Bagatur	f872c50b3f	docs: installation nits (#24484)	2 weeks ago
Isaac Francisco	4833375200	community[patch]: added option to change how duckduckgosearchresults tool converts api outputs into string (#22580) ... Co-authored-by: Bagatur <baskaryan@gmail.com>	3 weeks ago
JonZeolla	78ff51ce83	community[patch]: update the default hf bge embeddings (#22627) ... **Description:** This updates the langchain_community > huggingface > default bge embeddings ([the current default recommends this change](https://huggingface.co/BAAI/bge-large-en)) **Issue:** None **Dependencies:** None **Twitter handle:** @jonzeolla --------- Co-authored-by: Bagatur <baskaryan@gmail.com>	3 weeks ago
Leonid Ganeline	150251fd49	docs: `integrations` reference updates 13 (#25711) ... Added missed provider pages and links. Fixed inconsistent formatting. Added arxiv references to docstirngs. --------- Co-authored-by: Harrison Chase <hw.chase.17@gmail.com> Co-authored-by: Bagatur <22008038+baskaryan@users.noreply.github.com>	3 weeks ago
Yuki Watanabe	64dfdaa924	docs: Add Databricks integration (#25929) ... Updating the gateway pages in the documentation to name the `langchain-databricks` integration. --------- Signed-off-by: B-Step62 <yuki.watanabe@databricks.com> Co-authored-by: Bagatur <baskaryan@gmail.com>	3 weeks ago
Bagatur	933bc0d6ff	core[patch]: support additional kwargs on StructuredPrompt (#25645)	3 weeks ago
Yash Parmar	51dae57357	community[minor]: jina search tools integrating (jina reader) (#23339) ... - **PR title**: "community: add Jina Search tool" - **Description:** Added the Jina Search tool for querying the Jina search API. This includes the implementation of the JinaSearchAPIWrapper and the JinaSearch tool, along with a Jupyter notebook example demonstrating its usage. - **Issue:** N/A - **Dependencies:** N/A - **Twitter handle:** [Twitter handle](https://x.com/yashp3020?t=7wM0gQ7XjGciFoh9xaBtqA&s=09) - [x] **Add tests and docs**: If you're adding a new integration, please include 1. 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/ --------- Co-authored-by: Bagatur <baskaryan@gmail.com> Co-authored-by: Chester Curme <chester.curme@gmail.com>	3 weeks ago
Matthew DeGenaro	66828f4ecc	text-splitters[patch]: Modified SpacyTextSplitter to fully keep whitespace when strip_whitespace is false (#23272) ... Previously, regardless of whether or not strip_whitespace was set to true or false, the strip text method in the SpacyTextSplitter class used `sent.text` to get the sentence. I modified this to include a ternary such that if strip_whitespace is false, it uses `sent.text_with_ws` I also modified the project.toml to include the spacy pipeline package and to lock the numpy version, as higher versions break spacy. - **Issue:** N/a - **Dependencies:** None	3 weeks ago
Qingchuan Hao	3145995ed9	community[patch]: BingSearchResults returns raw snippets as artifact(#23304) ... Returns an array of results which is more specific and easier for later use. Tested locally: ``` resp = tool.invoke("what's the weather like in Shanghai?") for item in resp: print(item) ``` returns ``` {'snippet': '<b>Shanghai</b>, <b>Shanghai</b>, China <b>Weather</b> Forecast, with current conditions, wind, air quality, and what to expect for the next 3 days.', 'title': 'Shanghai, Shanghai, China Weather Forecast | AccuWeather', 'link': 'https://www.accuweather.com/en/cn/shanghai/106577/weather-forecast/106577'} {'snippet': '5. 99 / 87 °F. 6. 99 / 86 °F. 7. Detailed forecast for 14 days. Need some help? Current <b>weather</b> <b>in Shanghai</b> and forecast for today, tomorrow, and next 14 days.', 'title': 'Weather for Shanghai, Shanghai Municipality, China - timeanddate.com', 'link': 'https://www.timeanddate.com/weather/china/shanghai'} {'snippet': '<b>Shanghai</b> - <b>Weather</b> warnings issued 14-day forecast. <b>Weather</b> warnings issued. Forecast - <b>Shanghai</b>. Day by day forecast. Last updated Friday at 01:05. Tonight, ... Temperature feels <b>like</b> 34 ...', 'title': 'Shanghai - BBC Weather', 'link': 'https://www.bbc.com/weather/1796236'} {'snippet': 'Current <b>weather</b> <b>in Shanghai</b>, <b>Shanghai</b>, China. Check current conditions <b>in Shanghai</b>, <b>Shanghai</b>, China with radar, hourly, and more.', 'title': 'Shanghai, Shanghai, China Current Weather | AccuWeather', 'link': 'https://www.accuweather.com/en/cn/shanghai/106577/current-weather/106577'} 13-Day Beijing, Xi&#39;an, Chengdu, <b>Shanghai</b> Chinese Language and Culture Immersion Tour. <b>Shanghai</b> in September. Average daily temperature range: 23–29°C (73–84°F) Average rainy days: 10. Average sunny days: 20. September ushers in pleasant autumn <b>weather</b>, making it one of the best months to visit <b>Shanghai</b>. <b>Weather</b> in <b>Shanghai</b>: Climate, Seasons, and Average Monthly Temperature. <b>Shanghai</b> has a subtropical maritime monsoon climate, meaning high humidity and lots of rain. Hot muggy summers, cool falls, cold winters with little snow, and warm springs are the norm. Midsummer through early fall is the best time to visit <b>Shanghai</b>. <b>Shanghai</b>, <b>Shanghai</b>, China <b>Weather</b> Forecast, with current conditions, wind, air quality, and what to expect for the next 3 days. 1165. 45.9. 121. Winter, from December to February, is quite cold: the average January temperature is 5 °C (41 °F). There may be cold periods, with highs around 5 °C (41 °F) or below, and occasionally, even snow can fall. The temperature dropped to -10 °C (14 °F) in January 1977 and to -7 °C (19.5 °F) in January 2016. 5. 99 / 87 °F. 6. 99 / 86 °F. 7. Detailed forecast for 14 days. Need some help? Current <b>weather</b> in <b>Shanghai</b> and forecast for today, tomorrow, and next 14 days. Everything you need to know about today&#39;s <b>weather</b> in <b>Shanghai</b>, <b>Shanghai</b>, China. High/Low, Precipitation Chances, Sunrise/Sunset, and today&#39;s Temperature History. <b>Shanghai</b> - <b>Weather</b> warnings issued 14-day forecast. <b>Weather</b> warnings issued. Forecast - <b>Shanghai</b>. Day by day forecast. Last updated Friday at 01:05. Tonight, ... Temperature feels <b>like</b> 34 ... <b>Shanghai</b> 14 Day Extended Forecast. <b>Weather</b> Today <b>Weather</b> Hourly 14 Day Forecast Yesterday/Past <b>Weather</b> Climate (Averages) Currently: 84 °F. Passing clouds. (<b>Weather</b> station: <b>Shanghai</b> Hongqiao Airport, China). See more current <b>weather</b>. Current <b>weather</b> in <b>Shanghai</b>, <b>Shanghai</b>, China. Check current conditions in <b>Shanghai</b>, <b>Shanghai</b>, China with radar, hourly, and more. <b>Shanghai</b> <b>Weather</b> Forecasts. <b>Weather Underground</b> provides local &amp; long-range <b>weather</b> forecasts, weatherreports, maps &amp; tropical <b>weather</b> conditions for the <b>Shanghai</b> area. ``` --------- Co-authored-by: Bagatur <baskaryan@gmail.com>	3 weeks ago
venkatram-dev	a09e2afee4	typo_summarization_tutorial (#25938) ... Thank you for contributing to LangChain! - [ ] **PR title**: docs: fix typo in summarization_tutorial - [ ] **PR message**: docs: fix couple of typos in summarization_tutorial - [ ] **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.	3 weeks ago
Alexander KIRILOV	6a8f8a56ac	community[patch]: added content_columns option to CSVLoader (#23809) ... **Description:** Adding a new option to the CSVLoader that allows us to implicitly specify the columns that are used for generating the Document content. Currently these are implicitly set as "all fields not part of the metadata_columns". In some cases however it is useful to have a field both as a metadata and as part of the document content.	3 weeks ago
Bruno Alvisio	ab527027ac	community: Resolve refs recursively when generating openai_fn from OpenAPI spec (#19002) ... - **Description:** This PR is intended to improve the generation of payloads for OpenAI functions when converting from an OpenAPI spec file. The solution is to recursively resolve `$refs`. Currently when converting OpenAPI specs into OpenAI functions using `openapi_spec_to_openai_fn`, if the schemas have nested references, the generated functions contain `$ref` that causes the LLM to generate payloads with an incorrect schema. For example, for the for OpenAPI spec: ``` text = """ { "openapi": "3.0.3", "info": { "title": "Swagger Petstore - OpenAPI 3.0", "termsOfService": "http://swagger.io/terms/", "contact": { "email": "apiteam@swagger.io" }, "license": { "name": "Apache 2.0", "url": "http://www.apache.org/licenses/LICENSE-2.0.html" }, "version": "1.0.11" }, "externalDocs": { "description": "Find out more about Swagger", "url": "http://swagger.io" }, "servers": [ { "url": "https://petstore3.swagger.io/api/v3" } ], "tags": [ { "name": "pet", "description": "Everything about your Pets", "externalDocs": { "description": "Find out more", "url": "http://swagger.io" } }, { "name": "store", "description": "Access to Petstore orders", "externalDocs": { "description": "Find out more about our store", "url": "http://swagger.io" } }, { "name": "user", "description": "Operations about user" } ], "paths": { "/pet": { "post": { "tags": [ "pet" ], "summary": "Add a new pet to the store", "description": "Add a new pet to the store", "operationId": "addPet", "requestBody": { "description": "Create a new pet in the store", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/Pet" } } }, "required": true }, "responses": { "200": { "description": "Successful operation", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/Pet" } } } } } } } }, "components": { "schemas": { "Tag": { "type": "object", "properties": { "id": { "type": "integer", "format": "int64" }, "model_type": { "type": "number" } } }, "Category": { "type": "object", "required": [ "model", "year", "age" ], "properties": { "year": { "type": "integer", "format": "int64", "example": 1 }, "model": { "type": "string", "example": "Ford" }, "age": { "type": "integer", "example": 42 } } }, "Pet": { "required": [ "name" ], "type": "object", "properties": { "id": { "type": "integer", "format": "int64", "example": 10 }, "name": { "type": "string", "example": "doggie" }, "category": { "$ref": "#/components/schemas/Category" }, "tags": { "type": "array", "items": { "$ref": "#/components/schemas/Tag" } }, "status": { "type": "string", "description": "pet status in the store", "enum": [ "available", "pending", "sold" ] } } } } } } """ ``` Executing: ``` spec = OpenAPISpec.from_text(text) pet_openai_functions, pet_callables = openapi_spec_to_openai_fn(spec) response = model.invoke("Create a pet named Scott", functions=pet_openai_functions) ``` `pet_open_functions` contains unresolved `$refs`: ``` [ { "name": "addPet", "description": "Add a new pet to the store", "parameters": { "type": "object", "properties": { "json": { "properties": { "id": { "type": "integer", "schema_format": "int64", "example": 10 }, "name": { "type": "string", "example": "doggie" }, "category": { "ref": "#/components/schemas/Category" }, "tags": { "items": { "ref": "#/components/schemas/Tag" }, "type": "array" }, "status": { "type": "string", "enum": [ "available", "pending", "sold" ], "description": "pet status in the store" } }, "type": "object", "required": [ "name", "photoUrls" ] } } } } ] ``` and the generated JSON has an incorrect schema (e.g. category is filled with `id` and `name` instead of `model`, `year` and `age`: ``` { "id": 1, "name": "Scott", "category": { "id": 1, "name": "Dogs" }, "tags": [ { "id": 1, "name": "tag1" } ], "status": "available" } ``` With this change, the generated JSON by the LLM becomes, `pet_openai_functions` becomes: ``` [ { "name": "addPet", "description": "Add a new pet to the store", "parameters": { "type": "object", "properties": { "json": { "properties": { "id": { "type": "integer", "schema_format": "int64", "example": 10 }, "name": { "type": "string", "example": "doggie" }, "category": { "properties": { "year": { "type": "integer", "schema_format": "int64", "example": 1 }, "model": { "type": "string", "example": "Ford" }, "age": { "type": "integer", "example": 42 } }, "type": "object", "required": [ "model", "year", "age" ] }, "tags": { "items": { "properties": { "id": { "type": "integer", "schema_format": "int64" }, "model_type": { "type": "number" } }, "type": "object" }, "type": "array" }, "status": { "type": "string", "enum": [ "available", "pending", "sold" ], "description": "pet status in the store" } }, "type": "object", "required": [ "name" ] } } } } ] ``` and the JSON generated by the LLM is: ``` { "id": 1, "name": "Scott", "category": { "year": 2022, "model": "Dog", "age": 42 }, "tags": [ { "id": 1, "model_type": 1 } ], "status": "available" } ``` which has the intended schema. - **Twitter handle:**: @brunoalvisio --------- Co-authored-by: Harrison Chase <hw.chase.17@gmail.com>	3 weeks ago
Nuno Campos	464dae8ac2	core: Include global variables in variables found by get_function_nonlocals (#25936) ... 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.	3 weeks ago
Luiz F. G. dos Santos	36bbdc776e	community: fix bug to support for `file_search` tool from OpenAI (#25927) ... - **Description:** The function `_is_assistants_builtin_tool` didn't had support for `file_search` from OpenAI. This was creating conflict and blocking the usage of such. OpenAI Assistant changed from`retrieval` to `file_search`. The following code ``` agent = OpenAIAssistantV2Runnable.create_assistant( name="Data Analysis Assistant", instructions=prompt[0].content, tools={'type': 'file_search'}, model=self.chat_config.connection.deployment_name, client=llm, as_agent=True, tool_resources={ "file_search": { "vector_store_ids": vector_store_id } } ) ``` Was throwing the following error ``` Traceback (most recent call last): File "/Users/l.guedesdossantos/Documents/codes/shellai-nlp-backend/app/chat/chat_decorators.py", line 500, in get_response return await super().get_response(post, context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/l.guedesdossantos/Documents/codes/shellai-nlp-backend/app/chat/chat_decorators.py", line 96, in get_response response = await self.inner_chat.get_response(post, context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/l.guedesdossantos/Documents/codes/shellai-nlp-backend/app/chat/chat_decorators.py", line 96, in get_response response = await self.inner_chat.get_response(post, context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/l.guedesdossantos/Documents/codes/shellai-nlp-backend/app/chat/chat_decorators.py", line 96, in get_response response = await self.inner_chat.get_response(post, context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [Previous line repeated 4 more times] File "/Users/l.guedesdossantos/Documents/codes/shellai-nlp-backend/app/chat/azure_open_ai_chat.py", line 147, in get_response chain = chain_factory.get_chain(prompts, post.conversation.id, overrides, context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/l.guedesdossantos/Documents/codes/shellai-nlp-backend/app/llm_connections/chains.py", line 1324, in get_chain agent = OpenAIAssistantV2Runnable.create_assistant( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/l.guedesdossantos/anaconda3/envs/shell-e/lib/python3.11/site-packages/langchain_community/agents/openai_assistant/base.py", line 256, in create_assistant tools=[_get_assistants_tool(tool) for tool in tools], # type: ignore ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/l.guedesdossantos/anaconda3/envs/shell-e/lib/python3.11/site-packages/langchain_community/agents/openai_assistant/base.py", line 256, in <listcomp> tools=[_get_assistants_tool(tool) for tool in tools], # type: ignore ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/l.guedesdossantos/anaconda3/envs/shell-e/lib/python3.11/site-packages/langchain_community/agents/openai_assistant/base.py", line 119, in _get_assistants_tool return convert_to_openai_tool(tool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/l.guedesdossantos/anaconda3/envs/shell-e/lib/python3.11/site-packages/langchain_core/utils/function_calling.py", line 255, in convert_to_openai_tool function = convert_to_openai_function(tool) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/l.guedesdossantos/anaconda3/envs/shell-e/lib/python3.11/site-packages/langchain_core/utils/function_calling.py", line 230, in convert_to_openai_function raise ValueError( ValueError: Unsupported function {'type': 'file_search'} Functions must be passed in as Dict, pydantic.BaseModel, or Callable. If they're a dict they must either be in OpenAI function format or valid JSON schema with top-level 'title' and 'description' keys. ``` With the proposed changes, this is fixed and the function will have support for `file_search`. This was the only place missing the support for `file_search`. Reference doc https://platform.openai.com/docs/assistants/tools/file-search - **Twitter handle:** luizf0992 --------- Co-authored-by: Harrison Chase <hw.chase.17@gmail.com>	3 weeks ago
Jacob Lee	f49cce739b	👥 Update LangChain people data (#25917) ... 👥 Update LangChain people data Co-authored-by: github-actions <github-actions@github.com>	3 weeks ago
Leonid Ganeline	96b99a5022	docs: `integrations google` missed references (#25923) ... Added missed integration links. Fixed inconsistent formatting.	3 weeks ago
Leonid Ganeline	086556d466	docs: `integrations` reference updates 14 (#25928) ... Added missed provider pages and links. Fixed inconsistent formatting.	3 weeks ago
Tyler Wray	1ff8c36aa6	docs: fix pgvector link (#25930) ... - **Description:** pg_vector link is 404'ing. This fixes it.	3 weeks ago
xander-art	6cd452d985	Feature/update hunyuan (#25779) ... Description: - Add system templates and user templates in integration testing - initialize the response id field value to request_id - Adjust the default model to hunyuan-pro - Remove the default values of Temperature and TopP - Add SystemMessage all the integration tests have passed. 1、Execute integration tests for the first time <img width="1359" alt="71ca77a2-e9be-4af6-acdc-4d665002bd9b" src="https://github.com/user-attachments/assets/9298dc3a-aa26-4bfa-968b-c011a4e699c9"> 2、Run the integration test a second time <img width="1501" alt="image" src="https://github.com/user-attachments/assets/61335416-4a67-4840-bb89-090ba668e237"> Issue: None Dependencies: None Twitter handle: None --------- Co-authored-by: Chester Curme <chester.curme@gmail.com>	3 weeks ago
Yuwen Hu	566e9ba164	community: add Intel GPU support to `ipex-llm` llm integration (#22458) ... **Description:** [IPEX-LLM](https://github.com/intel-analytics/ipex-llm) is a PyTorch library for running LLM on Intel CPU and GPU (e.g., local PC with iGPU, discrete GPU such as Arc, Flex and Max) with very low latency. This PR adds Intel GPU support to `ipex-llm` llm integration. **Dependencies:** `ipex-llm` **Contribution maintainer**: @ivy-lv11 @Oscilloscope98 **tests and docs**: - Add: langchain/docs/docs/integrations/llms/ipex_llm_gpu.ipynb - Update: langchain/docs/docs/integrations/llms/ipex_llm_gpu.ipynb - Update: langchain/libs/community/tests/llms/test_ipex_llm.py --------- Co-authored-by: ivy-lv11 <zhicunlv@gmail.com>	3 weeks ago
Bagatur	d19e074374	core[patch]: handle serializable fields that cant be converted to bool (#25903)	3 weeks ago
Kirushikesh DB	7f857a02d5	docs: HuggingFace pipeline returns the prompt if return_full_text is not set (#25916) ... Thank you for contributing to LangChain! **Description:** The current documentation of using the Huggingface with Langchain needs to set return_full_text as False otherwise pipeline by default returns both the prompt and response as output. Code to reproduce: ```python from langchain_huggingface import ChatHuggingFace, HuggingFacePipeline from langchain_core.messages import ( HumanMessage, SystemMessage, ) llm = HuggingFacePipeline.from_model_id( model_id="microsoft/Phi-3.5-mini-instruct", task="text-generation", pipeline_kwargs=dict( max_new_tokens=512, do_sample=False, repetition_penalty=1.03, # return_full_text=False ), device=0 ) chat_model = ChatHuggingFace(llm=llm) messages = [ SystemMessage(content="You're a helpful assistant"), HumanMessage( content="What happens when an unstoppable force meets an immovable object?" ), ] ai_msg = chat_model.invoke(messages) print(ai_msg.content) ``` Output: ``` <|system|> You're a helpful assistant<|end|> <|user|> What happens when an unstoppable force meets an immovable object?<|end|> <|assistant|> The scenario of an "unstoppable force" meeting an "immovable object" is a classic paradox that has puzzled philosophers, scientists, and thinkers for centuries. In physics, however, there are no such things as truly unstoppable forces or immovable objects because all physical entities have mass and interact with other masses through fundamental forces (like gravity). When we consider the laws of motion, particularly Newton's third law which states that for every action, there is an equal and opposite reaction, it becomes clear that if one were to exist, the other would necessarily be negated by the interaction. For example, if you push against a solid wall with great force, the wall exerts an equal and opposite force back on you, preventing your movement. In theoretical discussions, this paradox often serves as a thought experiment to explore concepts like determinism versus free will, the limits of physical laws, and the nature of reality itself. However, in practical terms, any force applied to an object will result in some form of deformation, transfer of energy, or movement, depending on the properties of both the force and the object. So while the idea of an unstoppable force and an immovable object remains a fascinating philosophical conundrum, it does not hold up under the scrutiny of physical laws as we understand them. ``` --------- Co-authored-by: Kirushikesh D B kirushi@ibm.com <kirushi@cccxl012.pok.ibm.com>	3 weeks ago
Yuxi Zheng	38dfde6946	docs: fix typo in Cassandra for ./cookbook/cql_agent.ipynb (#25922) ... 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: “syd” <“zheng.yuxi@outlook.com>	3 weeks ago
Borahm Lee	9cdb99bd60	docs: remove unused imports in Tutorials Basics (#25919) ... ## Description - `List` is not explicitly used, so the unnecessary imports will be removed.	3 weeks ago
Erick Friis	8732cfc6ef	docs: review process gh discussion (#25921)	3 weeks ago
Erick Friis	08b9715845	docs: pr review process (#25899) ... Co-authored-by: Bagatur <22008038+baskaryan@users.noreply.github.com>	3 weeks ago
ccurme	60054db1c4	infra[patch]: remove together from scheduled tests (#25909) ... These now run in https://github.com/langchain-ai/langchain-together	3 weeks ago
Emmanuel Leroy	654da27255	improve llamacpp embeddings (#12972) ... - **Description:** Improve llamacpp embedding class by adding the `device` parameter so it can be passed to the model and used with `gpu`, `cpu` or Apple metal (`mps`). Improve performance by making use of the bulk client api to compute embeddings in batches. - **Dependencies:** none - **Tag maintainer:** @hwchase17 --------- Co-authored-by: Harrison Chase <hw.chase.17@gmail.com> Co-authored-by: Chester Curme <chester.curme@gmail.com>	3 weeks ago
Sandeep Bhandari	f882824eac	Update tool_choice.ipynb spelling mistake of select (#25907) ... 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.	3 weeks ago
ℍ𝕠𝕝𝕝𝕠𝕨 𝕄𝕒𝕟	64b62f6ae4	community[neo4j_vector]: make embedding dimension check optional (#25737) ... **Description:** Starting from Neo4j 5.23 (22 August 2024), with vector-2.0 indexes, `vector.dimensions` is not required to be set, which will cause it the key not exist error in index config if it's not set. Since the existence of vector.dimensions will only ensure additional checks, this commit turns embedding dimension check optional, and only do checks when it exists (not None). https://neo4j.com/release-notes/database/neo4j-5/ **Twitter handle:** @HollowM186 Signed-off-by: Hollow Man <hollowman@opensuse.org> Co-authored-by: Erick Friis <erick@langchain.dev>	3 weeks ago
Christophe Bornet	0a752a74cc	community[patch], docs: Add API reference doc for GraphVectorStore (#25751)	3 weeks ago
Bagatur	28e2ec7603	ollama[patch]: Release 0.1.3 (#25902)	3 weeks ago
Bagatur	ca1c3bd9c0	community[patch]: bump + fix core dep (#25901)	3 weeks ago
Bagatur	fabe32c06d	core[patch]: Release 0.2.37 (#25900)	3 weeks ago
Richmond Alake	9992a1db43	cookbook: AI Agent Built With LangChain and FireWorksAI (#22609) ... Thank you for contributing to LangChain! - **AI Agent Built With LangChain and FireWorksAI**: "community notebook" - **Description:** Added a new AI agent in the cookbook folder that integrates prompt compression using LLMLingua and arXiv retrieval tools. The agent is designed to optimize the efficiency and performance of research tasks by compressing lengthy prompts and retrieving relevant academic papers. The agent also makes uses of MongoDB to store conversational history and as it's knowledge base using MongoDB vector store - **Twitter handle:** https://x.com/richmondalake --------- Co-authored-by: Erick Friis <erick@langchain.dev> Co-authored-by: Bagatur <baskaryan@gmail.com>	3 weeks ago
mehdiosa	c6f00e6bdc	community: Fix branch not being considered when using GithubFileLoader (#20075) ... - **Description:** Added `ref` query parameter so data is not loaded only from the default branch but any branch passed --------- Co-authored-by: Osama Mehdi <mehdi@hm.edu> Co-authored-by: Bagatur <22008038+baskaryan@users.noreply.github.com> Co-authored-by: Erick Friis <erick@langchain.dev>	3 weeks ago
Leonid Ganeline	54d2b861f6	docs: `integrations` reference updates 12 (#25676) ... Added missed provider pages and links. Fixed inconsistent formatting. Co-authored-by: Erick Friis <erick@langchain.dev>	3 weeks ago
Aditya	c8b1c3a7e7	docs: update documentation for Vertex Embeddings Models (#25745) ... - **Description:update documentation for Vertex Embeddings Models - **Issue:NA - **Dependencies:NA - **Twitter handle:NA --------- Co-authored-by: adityarane@google.com <adityarane@google.com>	3 weeks ago
Alex Sherstinsky	617a4e617b	community: Fix a bug in handling kwargs overwrites in Predibase integration, and update the documentation. (#25893) ... Thank you for contributing to LangChain! - [x] **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" - [x] **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! - [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.	3 weeks ago
Erick Friis	28f6ff6fcd	docs: remove incorrect vectorstore local column (#25895)	3 weeks ago
Anush	ade4bfdff1	qdrant: Updated class check in Self-Query Retriever factory (#25877) ... ## Description - Updates the self-query retriever factory to check for the new Qdrant vector store class. i.e. `langchain_qdrant.QdrantVectorstore`. - Deprecates `QdrantSparseVectorRetriever`, since the vector store implementation natively supports it now. Resolves #25798	3 weeks ago
Djordje	862ef32fdc	community: Fixed infinity embeddings async request (#25882) ... **Description:** Fix async infinity embeddings **Issue:** #24942 @baskaryan, @ccurme	3 weeks ago
rainsubtime	f75d5621e2	community:Fix a bug of LLM in moonshot (#25878) ... - **Description:** When useing LLM integration moonshot,it's occurring error "'Moonshot' object has no attribute '_client'",it's because of the "_client" that is private in pydantic v1.0 so that we can't use it.I turn "_client" into "client" , the error to be resolved! - **Issue:** the issue #24390 - **Dependencies:** none - **Twitter handle:** @Rainsubtime - [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/ Co-authored-by: Cyue <Cyue_work2001@163.com>	3 weeks ago
ZhangShenao	fd0f147df3	Improvement[Community] Add tool-calling test case for `ChatZhipuAI` (#25884) ... - Add tool-calling test case for `ChatZhipuAI`	3 weeks ago
k.muto	5bb810c5c6	docs: updated args_schema to be required when using callback handlers in custom tools. (#25887) ... - **Description:** if you use callback handlers when using tool, run_manager will be added to input, so you need to explicitly specify args_schema, but i was confused because it was not listed, so i added it. Also, it seems that the type does not work with pydantic.BaseModel. - **Issue:** None - **Dependencies:** None	3 weeks ago
默奕	6377185291	add neo4j query constructor for self query (#25288) ... - [x] **PR title - community: add neo4j query constructor for self query** - [x] **PR message** - **Description:** adding a Neo4jTranslator so that the Neo4j vector database can use SelfQueryRetriever - **Issue:** this issue had been raised before in #19748 - **Dependencies:** none. - **Twitter handle:** @moyi_dang - p.s. I have not added the query constructor in BUILTIN_TRANSLATORS in this PR, I want to make changes to only one package at a time. - [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: Bagatur <22008038+baskaryan@users.noreply.github.com> Co-authored-by: Chester Curme <chester.curme@gmail.com>	3 weeks ago
Ohad Eytan	b5d670498f	partners/milvus: allow creating a vectorstore with sparse embeddings (#25284) ... # Description Milvus (and `pymilvus`) recently added the option to use [sparse vectors](https://milvus.io/docs/sparse_vector.md#Sparse-Vector) with appropriate search methods (e.g., `SPARSE_INVERTED_INDEX`) and embeddings (e.g., `BM25`, `SPLADE`). This PR allow creating a vector store using langchain's `Milvus` class, setting the matching vector field type to `DataType.SPARSE_FLOAT_VECTOR` and the default index type to `SPARSE_INVERTED_INDEX`. It is only extending functionality, and backward compatible. ## Note I also interested in extending the Milvus class further to support multi vector search (aka hybrid search). Will be happy to discuss that. See [here](https://github.com/langchain-ai/langchain/discussions/19955), [here](https://github.com/langchain-ai/langchain/pull/20375), and [here](https://github.com/langchain-ai/langchain/discussions/22886) similar needs. --------- Co-authored-by: Erick Friis <erick@langchain.dev>	3 weeks ago