langchain

Commit Graph

Author	SHA1	Message	Date
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"]}) ```	9 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	10 months ago
William FH	93c7eb4e6b	[Tracing] String Stacktrace (#14131 ) Add full stacktrace	10 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
James Braza	bdb6ae2ed3	core[patch]: `BaseTracer` helper method for `Run` lookup (#14139 ) I observed the same run ID extraction logic is repeated many times in `BaseTracer`. This PR creates a helper method for DRY code.	10 months ago
Nuno Campos	0f255bb6c4	In Runnable.stream_log build up final_output from adding output chunks (#12781 ) Add arg to omit streamed_output list, in cases where final_output is enough this saves bandwidth <!-- Thank you for contributing to LangChain! 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, - Tag maintainer: for a quicker response, tag the relevant maintainer (see below), - 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` to check this locally. See contribution guidelines for more information on how to write/run tests, lint, etc: https://github.com/langchain-ai/langchain/blob/master/.github/CONTRIBUTING.md 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/extras` directory. If no one reviews your PR within a few days, please @-mention one of @baskaryan, @eyurtsev, @hwchase17. -->	10 months ago
Bagatur	e327bb4ba4	IMPROVEMENT: Conditionally import core type hints (#13700 )	11 months ago
Bagatur	c61e30632e	BUG: more core fixes (#13665 ) Fix some circular deps: - move PromptValue into top level module bc both PromptTemplates and OutputParsers import - move tracer context vars to `tracers.context` and import them in functions in `callbacks.manager` - add core import tests	11 months ago
Bagatur	d32e511826	REFACTOR: Refactor langchain_core (#13627 ) Changes: - remove langchain_core/schema since no clear distinction b/n schema and non-schema modules - make every module that doesn't end in -y plural - where easy have 1-2 classes per file - no more than one level of nesting in directories - only import from top level core modules in langchain	11 months ago

24 Commits (fbab8baac507a1f80bb26f9513195d18b0b217fc)