55 Commits (9b3a025f9c806a6f8a00030c7058c689536ae5a0)

Author	SHA1	Message	Date
Nuno Campos	338180f383	core: in astream_events v2 always await task even if already finished (#22916) ... - this ensures exceptions propagate to the caller	3 months ago
kiarina	8171efd07a	core[patch]: Fix FunctionCallbackHandler._on_tool_end (#22908) ... If the global `debug` flag is enabled, the agent will get the following error in `FunctionCallbackHandler._on_tool_end` at runtime. ``` Error in ConsoleCallbackHandler.on_tool_end callback: AttributeError("'list' object has no attribute 'strip'") ``` By calling str() before strip(), the error was avoided. This error can be seen at [debugging.ipynb](https://github.com/langchain-ai/langchain/blob/master/docs/docs/how_to/debugging.ipynb). - Issue: NA - Dependencies: NA - Twitter handle: https://x.com/kiarina37	3 months ago
Nuno Campos	bae82e966a	core: In astream_events v2 propagate cancel/break to the inner astream call (#22865) ... - previous behavior was for the inner astream to continue running with no interruption - also propagate break in core runnable methods	3 months ago
Eugene Yurtsev	5a7eac191a	core[patch]: Add missing type annotations (#22756) ... Add missing type annotations. The missing type annotations will raise exceptions with pydantic 2.	3 months ago
William FH	be79ce9336	[Core] Unified Enable/Disable Tracing (#22576)	4 months ago
Eugene Yurtsev	28f744c1f5	core[patch]: Correctly order parent ids in astream events (from root to immediate parent), add defensive check for cycles (#22637) ... This PR makes two changes: 1. Fixes the order of parent IDs to be from root to immediate parent 2. Adds a simple defensive check for cycles	4 months ago
Eugene Yurtsev	035a9c9609	core[minor]: Add parent_ids to astream_events API (#22563) ... Include a list of parent ids for each event in astream events.	4 months ago
Nicolas Nkiere	51005e2776	core[minor]: Add an async root listener and with_alisteners method (#22151) ... - [x] **Adding AsyncRootListener**: "langchain_core: Adding AsyncRootListener" - **Description:** Adding an AsyncBaseTracer, AsyncRootListener and `with_alistener` function. This is to enable binding async root listener to runnables. This currently only supported for sync listeners. - **Issue:** None - **Dependencies:** None - [x] **Add tests and docs**: Added units tests and example snippet code within the function description of `with_alistener` - [x] **Lint and test**: Run make format_diff, make lint_diff and make test	4 months ago
Harrison Chase	ee32369265	core[patch]: fix runnable history and add docs (#22283)	4 months ago
Bagatur	50186da0a1	infra: rm unused # noqa violations (#22049) ... Updating #21137	4 months ago
Nuno Campos	fb6108c8f5	core[patch]: In astream_events(version=v2) tap output of root run (#21977) ... - if tap_output_iter/aiter is called multiple times for the same run issue events only once - if chat model run is tapped don't issue duplicate on_llm_new_token events - if first chunk arrives after run has ended do not emit it as a stream event --------- Co-authored-by: Eugene Yurtsev <eyurtsev@gmail.com>	4 months ago
Nuno Campos	b1e7b40b6a	core: Tap output of sync iterators for astream_events (#21842) ... 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.	4 months ago
Eugene Yurtsev	67b6f6c82a	core[patch]: Check if event loop is closed in memory stream (#21841) ... Check if event stream is closed in memory loop. Using try/except here to avoid race condition, but this may incur a small overhead in versions prios to 3.11	4 months ago
William FH	8498b41cda	Finish agent migration doc (#21731)	4 months ago
Eugene Yurtsev	5c2cfabec6	core[minor]: Add v2 implementation of astream events (#21638) ... This PR introduces a v2 implementation of astream events that removes intermediate abstractions and fixes some issues with v1 implementation. The v2 implementation significantly reduces relevant code that's associated with the astream events implementation together with overhead. After this PR, the astream events implementation: - Uses an async callback handler - No longer relies on BaseTracer - No longer relies on json patch As a result of this re-write, a number of issues were discovered with the existing implementation. ## Changes in V2 vs. V1 ### on_chat_model_end `output` The outputs associated with `on_chat_model_end` changed depending on whether it was within a chain or not. As a root level runnable the output was: ```python "data": {"output": AIMessageChunk(content="hello world!", id='some id')} ``` As part of a chain the output was: ``` "data": { "output": { "generations": [ [ { "generation_info": None, "message": AIMessageChunk( content="hello world!", id=AnyStr() ), "text": "hello world!", "type": "ChatGenerationChunk", } ] ], "llm_output": None, } }, ``` After this PR, we will always use the simpler representation: ```python "data": {"output": AIMessageChunk(content="hello world!", id='some id')} ``` **NOTE** Non chat models (i.e., regular LLMs) are still associated with the more verbose format. ### Remove some `_stream` events `on_retriever_stream` and `on_tool_stream` events were removed -- these were not real events, but created as an artifact of implementing on top of astream_log. The same information is already available in the `x_on_end` events. ### Propagating Names Names of runnables have been updated to be more consistent ```python model = GenericFakeChatModel(messages=infinite_cycle).configurable_fields( messages=ConfigurableField( id="messages", name="Messages", description="Messages return by the LLM", ) ) ``` Before: ```python "name": "RunnableConfigurableFields", ``` After: ```python "name": "GenericFakeChatModel", ``` ### on_retriever_end on_retriever_end will always return `output` which is a list of documents (rather than a dict containing a key called "documents") ### Retry events Removed the `on_retry` callback handler. It was incorrectly showing that the failed function being retried has invoked `on_chain_end` https://github.com/langchain-ai/langchain/pull/21638/files#diff-e512e3f84daf23029ebcceb11460f1c82056314653673e450a5831147d8cb84dL1394	4 months ago
ccurme	6da3d92b42	(all): update removal in deprecation warnings from 0.2 to 0.3 (#21265) ... We are pushing out the removal of these to 0.3. `find . -type f -name "*.py" -exec sed -i '' 's/removal="0\.2/removal="0.3/g' {} +`	5 months ago
Nuno Campos	47ce8d5a57	core: tracer: remove numeric execution order (#21220) ... - this hasn't been used in a long time and requires some additional bookkeeping i'm going to streamline in the next pr	5 months ago
William FH	ab55f6996d	[Core] Tracing: update parent run_tree's child_runs (#21049)	5 months ago
Leonid Ganeline	1a2ff56cd8	core[patch[: docstring update (#21036) ... Added missed docstrings. Updated docstrings to consistent format.	5 months ago
William FH	4c437ebb9c	Use lstv2 (#20747)	5 months ago
Erick Friis	f0d5b59962	core[patch]: remove requests (#19891) ... Removes required usage of `requests` from `langchain-core`, all of which has been deprecated. - removes Tracer V1 implementations - removes old `try_load_from_hub` github-based hub implementations Removal done in a way where imports will still succeed, and usage will fail with a `RuntimeError`.	6 months ago
Mohammad Mohtashim	9ae2df36fc	Core[major]: Base Tracer to propagate raw output from tool for on_tool_end (#18932) ... This PR completes work for PR #18798 to expose raw tool output in on_tool_end. Affected APIs: * astream_log * astream_events * callbacks sent to langsmith via langsmith-sdk * Any other code that relies on BaseTracer! --------- Co-authored-by: Eugene Yurtsev <eyurtsev@gmail.com> Co-authored-by: Bagatur <baskaryan@gmail.com>	6 months ago
Mohammad Mohtashim	43db4cd20e	core[major]: On Tool End Observation Casting Fix (#18798) ... This PR updates the on_tool_end handlers to return the raw output from the tool instead of casting it to a string. This is technically a breaking change, though it's impact is expected to be somewhat minimal. It will fix behavior in `astream_events` as well. Fixes the following issue #18760 raised by @eyurtsev --------- Co-authored-by: Eugene Yurtsev <eyurtsev@gmail.com>	6 months ago
Eugene Yurtsev	8c71f92cb2	core: upgrade mypy to recent mypy (#18753) ... Testing this works per package on CI	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
Leonid Ganeline	2f2b77602e	docs: modules descriptions (#17844) ... Several `core` modules do not have descriptions, like the [agent](https://api.python.langchain.com/en/latest/core_api_reference.html#module-langchain_core.agents) module. - Added missed module descriptions. The descriptions are mostly copied from the `langchain` or `community` package modules.	7 months ago
Eugene Yurtsev	93472ee9e6	core[patch]: Replace memory stream implementation used by LogStreamCallbackHandler (#17185) ... This PR replaces the memory stream implementation used by the LogStreamCallbackHandler. This implementation resolves an issue in which streamed logs and streamed events originating from sync code would arrive only after the entire sync code would finish execution (rather than arriving in real time as they're generated). One example is if trying to stream tokens from an llm within a tool. If the tool was an async tool, but the llm was invoked via stream (sync variant) rather than astream (async variant), then the tokens would fail to stream in real time and would all arrived bunched up after the tool invocation completed.	7 months ago
William FH	7c03cc5ed4	Support serialization when inputs/outputs contain generators (#17338) ... Pydantic's `dict()` function raises an error here if you pass in a generator. We have a more robust serialization function in lagnsmith that we will use instead.	7 months ago
Leonid Ganeline	ae66bcbc10	core[patch]: docstring update (#16813) ... - added missed docstrings - formated docstrings to consistent form	8 months ago
Nuno Campos	19ff81e74f	Fix stream events/log with some kinds of non addable output (#17205) ... <!-- 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	65798289a4	core[minor]: Use batched tracing in sdk (#16305) ... Remove threadpool executor usage in langchain tracer, this is now handled by sdk	8 months ago
William FH	bdacfafa05	core[patch]: Remove deep copying of run prior to submitting it to LangChain Tracing (#16904)	8 months ago
Nuno Campos	e86fd946c8	In stream_event and stream_log handle closed streams (#16661) ... if eg. the stream iterator is interrupted then adding more events to the send_stream will raise an exception that we should catch (and handle where appropriate) <!-- 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
Eugene Yurtsev	177af65dc4	core[minor]: RFC Add astream_events to Runnables (#16172) ... This PR adds `astream_events` method to Runnables to make it easier to stream data from arbitrary chains. * Streaming only works properly in async right now * One should use `astream()` with if mixing in imperative code as might be done with tool implementations * Astream_log has been modified with minimal additive changes, so no breaking changes are expected * Underlying callback code / tracing code should be refactored at some point to handle things more consistently (OK for now) - ~~[ ] verify event for on_retry~~ does not work until we implement streaming for retry - ~~[ ] Any rrenaming? Should we rename "event" to "hook"?~~ - [ ] Any other feedback from community? - [x] throw NotImplementedError for `RunnableEach` for now ## Example See this [Example Notebook](dbbc7fa0d6/docs/docs/modules/agents/how_to/streaming_events.ipynb) for an example with streaming in the context of an Agent ## Event Hooks Reference Here is a reference table that shows some events that might be emitted by the various Runnable objects. Definitions for some of the Runnable are included after the table. | event | name | chunk | input | output | |----------------------|------------------|---------------------------------|-----------------------------------------------|-------------------------------------------------| | on_chat_model_start | [model name] | | {"messages": [[SystemMessage, HumanMessage]]} | | | on_chat_model_stream | [model name] | AIMessageChunk(content="hello") | | | | on_chat_model_end | [model name] | | {"messages": [[SystemMessage, HumanMessage]]} | {"generations": [...], "llm_output": None, ...} | | on_llm_start | [model name] | | {'input': 'hello'} | | | on_llm_stream | [model name] | 'Hello' | | | | on_llm_end | [model name] | | 'Hello human!' | | on_chain_start | format_docs | | | | | on_chain_stream | format_docs | "hello world!, goodbye world!" | | | | on_chain_end | format_docs | | [Document(...)] | "hello world!, goodbye world!" | | on_tool_start | some_tool | | {"x": 1, "y": "2"} | | | on_tool_stream | some_tool | {"x": 1, "y": "2"} | | | | on_tool_end | some_tool | | | {"x": 1, "y": "2"} | | on_retriever_start | [retriever name] | | {"query": "hello"} | | | on_retriever_chunk | [retriever name] | {documents: [...]} | | | | on_retriever_end | [retriever name] | | {"query": "hello"} | {documents: [...]} | | on_prompt_start | [template_name] | | {"question": "hello"} | | | on_prompt_end | [template_name] | | {"question": "hello"} | ChatPromptValue(messages: [SystemMessage, ...]) | Here are declarations associated with the events shown above: `format_docs`: ```python def format_docs(docs: List[Document]) -> str: '''Format the docs.''' return ", ".join([doc.page_content for doc in docs]) format_docs = RunnableLambda(format_docs) ``` `some_tool`: ```python @tool def some_tool(x: int, y: str) -> dict: '''Some_tool.''' return {"x": x, "y": y} ``` `prompt`: ```python template = ChatPromptTemplate.from_messages( [("system", "You are Cat Agent 007"), ("human", "{question}")] ).with_config({"run_name": "my_template", "tags": ["my_template"]}) ```	8 months ago
Nuno Campos	7ce4cd0709	Do not issue beta or deprecation warnings on internal calls (#15641)	9 months ago
Nuno Campos	ef22559f1f	Populate streamed_output for all runs handled by atransform_stream_with_config (#15599) ... This means that users of astream_log() now get streamed output of virtually all requested runs, whereas before the only streamed output would be for the root run and raw llm runs <!-- 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. -->	9 months ago
Bagatur	46446a100d	core[patch]: deprecate v1 tracer (#15608)	9 months ago
Bagatur	a7d023aaf0	core[patch], community[patch]: mark runnable context, lc load as beta (#15603)	9 months ago
Bagatur	b2f15738dd	core[patch], langchain[patch], community[patch]: Revert #15326 (#15546)	9 months ago
Nuno Campos	6810b4b0bc	Use tz-aware utc datetimes in tracer (#15187) ... <!-- 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. -->	9 months ago
Ankush Gola	f50dba12ff	Calculate trace_id and dotted_order client side (#15351) ... <!-- 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. -->	9 months ago
chyroc	0665a7da19	Docs: add param comment for `tracing_v2_enabled` (#15308) ... Co-authored-by: Harrison Chase <hw.chase.17@gmail.com>	9 months ago
Ankush Gola	7eec8f2487	Delete V1 tracer and refactor tracer tests to core (#15326)	9 months ago
chyroc	6fb3cc6f27	Fix: Use `Union` instead of `|` to improve compatibility, fix #15244 (#15245)	9 months ago
Harrison Chase	4ad77f777e	[core] prompt changes (#15186) ... change it to pass all variables through all the way in invoke	9 months ago
Leonid Ganeline	14d04180eb	docstrings `core` update (#14871) ... Added missed docstrings	9 months ago
William FH	93c7eb4e6b	[Tracing] String Stacktrace (#14131) ... Add full stacktrace	9 months ago
Eugene Yurtsev	37bee92b8a	Use deepcopy in RunLogPatch (#14244) ... This PR adds deepcopy usage in RunLogPatch. I included a unit-test that shows an issue that was caused in LangServe in the RemoteClient. ```python import jsonpatch s1 = {} s2 = {'value': []} s3 = {'value': ['a']} ops0 = list(jsonpatch.JsonPatch.from_diff(None, s1)) ops1 = list(jsonpatch.JsonPatch.from_diff(s1, s2)) ops2 = list(jsonpatch.JsonPatch.from_diff(s2, s3)) ops = ops0 + ops1 + ops2 jsonpatch.apply_patch(None, ops) {'value': ['a']} jsonpatch.apply_patch(None, ops) {'value': ['a', 'a']} jsonpatch.apply_patch(None, ops) {'value': ['a', 'a', 'a']} ```	10 months ago
Bagatur	b2280fd874	core[patch], langchain[patch]: fix required deps (#14373)	10 months ago
Jon Watte	e042e5df35	fix: call _on_llm_error() (#13581) ... Description: There's a copy-paste typo where on_llm_error() calls _on_chain_error() instead of _on_llm_error(). Issue: #13580 Dependencies: None Tag maintainer: @hwchase17 Twitter handle: @jwatte "Run `make format`, `make lint` and `make test` to check this locally." The test scripts don't work in a plain Ubuntu LTS 20.04 system. It looks like the dev container pulling is stuck. Or maybe the internet is just ornery today. --------- Co-authored-by: jwatte <jwatte@observeinc.com> Co-authored-by: Harrison Chase <hw.chase.17@gmail.com>	10 months ago