langchain

Commit Graph

Author	SHA1	Message	Date
Ángel Igareta	31a641a155	core: fix return of draw_mermaid_png and change to not save image by default (#19950 ) - Description: Improvement for #19599: fixing missing return of graph.draw_mermaid_png and improve it to make the saving of the rendered image optional Co-authored-by: Angel Igareta <angel.igareta@klarna.com>	6 months ago
Nuno Campos	2ae6dcdf01	core: Assign missing message ids in BaseChatModel (#19863 ) - This ensures ids are stable across streamed chunks - Multiple messages in batch call get separate ids - Also fix ids being dropped when combining message chunks 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, hwchase17.	6 months ago
Mayank Solanki	d5c412b0a9	core: Add docs for RunnableConfigurableFields (#19849 ) - [x] docs: core: Add docs for `RunnableConfigurableFields` - Description: Added incode docs for `RunnableConfigurableFields` with example - Issue: #18803 - Dependencies: NA - Twitter handle: NA --------- Co-authored-by: Chester Curme <chester.curme@gmail.com>	6 months ago
Ángel Igareta	c2ccf22dfd	core: generate mermaid syntax and render visual graph (#19599 ) - Description: Add functionality to generate Mermaid syntax and render flowcharts from graph data. This includes support for custom node colors and edge curve styles, as well as the ability to export the generated graphs to PNG images using either the Mermaid.INK API or Pyppeteer for local rendering. - Dependencies: Optional dependencies are `pyppeteer` if rendering wants to be done using Pypeteer and Javascript code. --------- Co-authored-by: Angel Igareta <angel.igareta@klarna.com> Co-authored-by: Bagatur <22008038+baskaryan@users.noreply.github.com>	6 months ago
aditya thomas	263ee78886	core[runnables]: docstring for class RunnableSerializable, method configurable_fields (#19722 ) Description: Update to the docstring for class RunnableSerializable, method configurable_fields Issue: [Add in code documentation to core Runnable methods #18804](https://github.com/langchain-ai/langchain/issues/18804) Dependencies: None --------- Co-authored-by: Chester Curme <chester.curme@gmail.com>	6 months ago
aditya thomas	ec4dcfca7f	core[runnables]: docstring of class RunnableSerializable, method configurable_alternatives (#19724 ) Description: Update to the docstring for class RunnableSerializable, method configurable_alternatives Issue: [Add in code documentation to core Runnable methods #18804](https://github.com/langchain-ai/langchain/issues/18804) Dependencies: None --------- Co-authored-by: Chester Curme <chester.curme@gmail.com>	6 months ago
jhicks2306	bcb8ab5216	docs: Improve docstring for Runnable bind method (#19659 ) Added example to the docstring of the "bind" method of Runnable. This makes it easier to understand the purpose of the method when reviewing in code editors. E.g. VS Code below. <img width="833" alt="Screenshot 2024-03-27 at 16 24 18" src="https://github.com/langchain-ai/langchain/assets/45722942/ad022d4e-7bc0-4f4b-aa7a-838f1816cc52"> --------- Co-authored-by: Chester Curme <chester.curme@gmail.com>	6 months ago
Christophe Bornet	1f422318b7	core[minor]: Use BaseChatMessageHistory async methods in RunnableWithMessageHistory (#19565 ) Co-authored-by: Eugene Yurtsev <eyurtsev@gmail.com>	6 months ago
Guangdong Liu	c93d4ea91c	docs: Add in code documentation to core Runnable map methods (docs only) (#19517 ) - Issue: #18804 - @baskaryan, @eyurtsev	6 months ago
aditya thomas	aa68fd7e91	core[runnables]: docstring for class runnable, method with_listeners() (#19515 ) Description: Docstring for method with_listerners() of class Runnable Issue: [Add in code documentation to core Runnable methods #18804](https://github.com/langchain-ai/langchain/issues/18804) Dependencies: None	6 months ago
Guangdong Liu	560e2182d8	docs: docstring Runnable `pipe` and `pick` methods (docs only) (#19395 ) - Issue: #18804 - @eyurtsev @ccurme PTAL --------- Co-authored-by: Bagatur <baskaryan@gmail.com> Co-authored-by: Bagatur <22008038+baskaryan@users.noreply.github.com>	6 months ago
Devesh Rahatekar	3c4529ac69	core: Updated docstring for RunnablePick (#18832 ) Description: : Updated the docstring for RunnablePick. Added Overview and an Example for RunnablePick class. Issue: : #18803	6 months ago
Guangdong Liu	2c835baae4	code[patch]: Add in code documentation to core Runnable with_retry method (docs only) (#19192 ) - Description: Add in code documentation to core Runnable with_retry method (docs only) - Issue: #18804 @baskaryan @eyurtsev PTAL --------- Co-authored-by: ccurme <chester.curme@gmail.com>	6 months ago
William FH	780337488e	[Enhancement] Add support for directly providing a run_id (#18990 ) The root run id (~trace id's) is useful for assigning feedback, but the current recommended approach is to use callbacks to retrieve it, which has some drawbacks: 1. Doesn't work for streaming until after the first event 2. Doesn't let you call other endpoints with the same trace ID in parallel (since you have to wait until the call is completed/started to use This PR lets you provide = "run_id" in the runnable config. Couple considerations: 1. For batch calls, we split the trace up into separate trees (to permit better rendering). We keep the provided run ID for the first one and generate a unique one for other elements of the batch. 2. For nested calls, the provided ID is ONLY used on the top root/trace. ### Example Usage ``` chain.invoke("foo", {"run_id": uuid.uuid4()}) ```	6 months ago
Nikhil Kumar	a1b26dd9b6	docs: Add docs for RouterRunnable (#19191 ) - [x] Docs for `RouterRunnable`: core: Add docs for `RouterRunnable` - [x] Add docs for `RouterRunnable`: - Description: Add docs for `RouterRunnable`, which was previously missing documentation - Issue: #18803 - Dependencies: N/A - Twitter handle: None	6 months ago
Guangdong Liu	4468e5bdbe	docs: Add in code documentation to core Runnable with_fallbacks method (docs only) (#19104 ) - Description: [a description of the change] Add in code documentation to core Runnable with_fallbacks method (docs only) - Issue: the issue #18804 @eyurtsev PTAL	6 months ago
Eugene Yurtsev	06165efb5b	core[patch]: RunnablePassthrough transform to autoupgrade to AddableDict (#19051 ) Follow up on https://github.com/langchain-ai/langchain/pull/18743 which missed RunnablePassthrough Issues: https://github.com/langchain-ai/langchain/issues/18741 https://github.com/langchain-ai/langgraph/issues/136 https://github.com/langchain-ai/langserve/issues/504	6 months ago
Guangdong Liu	d4b025c812	code[patch]: Add in code documentation to core Runnable assign method (docs only) (#18951 ) PR message: *Delete this entire checklist* and replace with - Description: [a description of the change](docs: Add in code documentation to core Runnable assign method) - Issue: the issue #18804	6 months ago
YHW	69a8ef2693	core: Runnable pass kwargs to _astream_log_implementation in astream_log (#19055 ) - Description: When calling the `_stream_log_implementation` from the `astream_log` method in the `Runnable` class, it is not handing over the `kwargs` argument. Therefore, even if i want to customize APIHandler and implement additional features with additional arguments, it is not possible. Conversely, the `astream_events` method normally handing over the `kwargs` argument. - Issue: https://github.com/langchain-ai/langchain/issues/19054 - Dependencies: - Twitter handle: if your PR gets announced, and you'd like a mention, we'll gladly shout you out! Co-authored-by: hyungwookyang <hyungwookyang@worksmobile.com>	6 months ago
Nuno Campos	2b7c3c548d	core[minor]: Add Runnable.batch_as_completed (#17603 ) This PR adds `batch as completed` method to the standard Runnable interface. It takes in a list of inputs and yields the corresponding outputs as the inputs are completed.	6 months ago
Ammar	34b31a8cc7	core: add in-code docs for RunnableAssign class (#18826 ) Description: Improves the docstring for `RunnableAssign` by providing a concise description and a self-contained code example. Issue: #18803	7 months ago
Erick Friis	bbb609ac9d	core[patch]: fix arbitrary config keys (#18827 )	7 months ago
Eugene Yurtsev	6caceb5473	core[patch]: Automatic upgrade to AddableDict in transform and atransform (#18743 ) Automatic upgrade to transform and atransform Closes: https://github.com/langchain-ai/langchain/issues/18741 https://github.com/langchain-ai/langgraph/issues/136 https://github.com/langchain-ai/langserve/issues/504	7 months ago
Eugene Yurtsev	8c71f92cb2	core: upgrade mypy to recent mypy (#18753 ) Testing this works per package on CI	7 months ago
Leonid Ganeline	a89f007947	docs: `runnable` module description (#17966 ) Added a module description. Added `batch` description.	7 months ago
Nuno Campos	7891934173	Fix missing labels (#18356 ) 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, hwchase17.	7 months ago
William FH	fdab931fd3	[Core] Patch: rm dumpd of outputs from runnables/base (#18295 ) It obstructs evaluations when your return a pydantic object.	7 months ago
Nuno Campos	6da08d0f22	Add PNG drawer for Runnable.get_graph() (#18239 ) 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, hwchase17.	7 months ago
Nuno Campos	d9fd1194f5	Remove check preventing passing non-declared config keys (#18276 ) 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, hwchase17.	7 months ago
Isaac Francisco	733367b795	docs: deprecation of OpenAI functions agent, astream_events docstring (#18164 ) Co-authored-by: Hershenson, Isaac (Extern) <isaac.hershenson.extern@bayer04.de> Co-authored-by: Bagatur <baskaryan@gmail.com>	7 months ago
Nuno Campos	cd3ab3703b	Improve runnable generator error messages (#18142 ) h/t @hinthornw 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, hwchase17.	7 months ago
Nuno Campos	62a30efb12	Fix bug with using configurable_fields after configurable_alternatives (#18139 ) Closes #17915	7 months ago
Eugene Yurtsev	68527b809d	core[patch]: Runnable with message history to use add_messages (#17958 ) This PR updates RunnableWithMessageHistory to use add_messages which will save on round-trips for any chat history abstractions that implement the optimization. If the optimization isn't implemented, add_messages automatically invokes add_message serially.	7 months ago
Erick Friis	ed789be8f4	docs, templates: update schema imports to core (#17885 ) - chat models, messages - documents - agentaction/finish - baseretriever,document - stroutputparser - more messages - basemessage - format_document - baseoutputparser --------- Co-authored-by: Bagatur <baskaryan@gmail.com>	7 months ago
ccurme	1b0802babe	core: fix .bind when used with RunnableLambda async methods (#17739 ) Description: Here is a minimal example to illustrate behavior: ```python from langchain_core.runnables import RunnableLambda def my_function(args, kwargs): return 3 + kwargs.get("n", 0) runnable = RunnableLambda(my_function).bind(n=1) assert 4 == runnable.invoke({}) assert [4] == list(runnable.stream({})) assert 4 == await runnable.ainvoke({}) assert [4] == [item async for item in runnable.astream({})] ``` Here, `runnable.invoke({})` and `runnable.stream({})` work fine, but `runnable.ainvoke({})` raises ``` TypeError: RunnableLambda._ainvoke.<locals>.func() got an unexpected keyword argument 'n' ``` and similarly for `runnable.astream({})`: ``` TypeError: RunnableLambda._atransform.<locals>.func() got an unexpected keyword argument 'n' ``` Here we assume that this behavior is undesired and attempt to fix it. Issue:* https://github.com/langchain-ai/langchain/issues/17241, https://github.com/langchain-ai/langchain/discussions/16446	7 months ago
Nuno Campos	223e5eff14	Add JSON representation of runnable graph to serialized representation (#17745 ) Sent to LangSmith Thank you for contributing to LangChain! Checklist: - [ ] PR title: Please title your PR "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 template message and replace it with the following bulleted list - 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! - [ ] Pass lint and test: Run `make format`, `make lint` and `make test` from the root of the package(s) you've modified to check that you're passing lint and testing. See contribution guidelines for more information on how to write/run tests, lint, etc: https://python.langchain.com/docs/contributing/ - [ ] 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. 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, hwchase17.	7 months ago
Nuno Campos	07ee41d284	Cache calls to create_model for get_input_schema and get_output_schema (#17755 ) 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, hwchase17.	7 months ago
Erick Friis	3a2eb6e12b	infra: add print rule to ruff (#16221 ) Added noqa for existing prints. Can slowly remove / will prevent more being intro'd	8 months ago
Leonid Ganeline	ae66bcbc10	core[patch]: docstring update (#16813 ) - added missed docstrings - formated docstrings to consistent form	8 months ago
Mohammad Mohtashim	e35c7fa3b2	[Langchain_core]: Added Docstring for RunnableConfigurableAlternatives (#17263 ) I noticed that RunnableConfigurableAlternatives which is an important composition in LCEL has no Docstring. Therefore I added the detailed Docstring for it. @baskaryan, @eyurtsev, @hwchase17 please have a look and let me if the docstring is looking good. --------- Co-authored-by: Bagatur <baskaryan@gmail.com>	8 months ago
Nuno Campos	ae56fd020a	Fix condition on custom root type in runnable history (#17017 ) <!-- Thank you for contributing to LangChain! Please title your PR "<package>: <description>", where <package> is whichever of langchain, community, core, experimental, etc. is being modified. Replace this entire comment with: - Description: a description of the change, - Issue: the issue # it fixes if applicable, - Dependencies: any dependencies required for this change, - Twitter handle: we announce bigger features on Twitter. If your PR gets announced, and you'd like a mention, we'll gladly shout you out! Please make sure your PR is passing linting and testing before submitting. Run `make format`, `make lint` and `make test` from the root of the package you've modified to check this locally. See contribution guidelines for more information on how to write/run tests, lint, etc: https://python.langchain.com/docs/contributing/ 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. If no one reviews your PR within a few days, please @-mention one of @baskaryan, @eyurtsev, @hwchase17. -->	8 months ago
Mohammad Mohtashim	f8943e8739	core[patch]: Add doc-string to RunnableEach (#16892 ) Add doc-string to Runnable Each --------- Co-authored-by: Eugene Yurtsev <eyurtsev@gmail.com> Co-authored-by: Eugene Yurtsev <eugene@langchain.dev>	8 months ago
ccurme	ec0ae23645	core: expand docstring for RunnableGenerator (#16672 ) - Description: expand docstring for RunnableGenerator - Issue: https://github.com/langchain-ai/langchain/issues/16631	8 months ago
ccurme	a989f82027	core: expand docstring for RunnableParallel (#16600 ) - Description: expand docstring for RunnableParallel - Issue: https://github.com/langchain-ai/langchain/issues/16462 Feel free to modify this or let me know how it can be improved!	8 months ago
Eugene Yurtsev	42db96477f	docs: Update in code documentation for runnable with message history (#16585 ) Update the in code documentation for Runnable With Message History	8 months ago
Nuno Campos	3f38e1a457	Remove double line (#16426 ) <!-- Thank you for contributing to LangChain! Please title your PR "<package>: <description>", where <package> is whichever of langchain, community, core, experimental, etc. is being modified. Replace this entire comment with: - Description: a description of the change, - Issue: the issue # it fixes if applicable, - Dependencies: any dependencies required for this change, - Twitter handle: we announce bigger features on Twitter. If your PR gets announced, and you'd like a mention, we'll gladly shout you out! Please make sure your PR is passing linting and testing before submitting. Run `make format`, `make lint` and `make test` from the root of the package you've modified to check this locally. See contribution guidelines for more information on how to write/run tests, lint, etc: https://python.langchain.com/docs/contributing/ 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. If no one reviews your PR within a few days, please @-mention one of @baskaryan, @eyurtsev, @hwchase17. -->	8 months ago
Nuno Campos	226fe645f1	core[patch] Do not try to access attribute of None (#16321 )	8 months ago
Chase VanSteenburg	1011b681dc	core[patch]: Fix f-string formatting in error message for configurable_fields (#16411 ) - Description: Simple fix to f-string formatting. Allows more informative ValueError output. - Issue: None needed. - Dependencies: None. - Twitter handle: @FlightP1an	8 months ago
James Braza	e1c59779ad	core[patch]: Remove `print` statement on missing `grandalf` dependency in favor of more explicit ImportError (#16326 ) After this PR an ImportError will be raised without a print if grandalf is missing when using grandalf related code for printing runnable graphs.	8 months ago
Nuno Campos	ef75bb63ce	core[patch] Fix tracer output of streamed runs with non-addable output (#16324 ) - Used to be None, now is just the last chunk <!-- Thank you for contributing to LangChain! Please title your PR "<package>: <description>", where <package> is whichever of langchain, community, core, experimental, etc. is being modified. Replace this entire comment with: - Description: a description of the change, - Issue: the issue # it fixes if applicable, - Dependencies: any dependencies required for this change, - Twitter handle: we announce bigger features on Twitter. If your PR gets announced, and you'd like a mention, we'll gladly shout you out! Please make sure your PR is passing linting and testing before submitting. Run `make format`, `make lint` and `make test` from the root of the package you've modified to check this locally. See contribution guidelines for more information on how to write/run tests, lint, etc: https://python.langchain.com/docs/contributing/ 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. If no one reviews your PR within a few days, please @-mention one of @baskaryan, @eyurtsev, @hwchase17. -->	8 months ago

1 2 3

103 Commits (22fd844e8a7b3abc2709736d68a79e00c14b99e2)