6 Commits (5c2538b9f7fb64afed2a918b621d9d8681c7ae32)

Author	SHA1	Message	Date
William FH	5de59f9236	Core[Patch] Parse tool input after on_start (#16430) ... For tracing, if a validation error occurs, currently it is attributed to the previous step of the chain. It would be nice to have the on_start and on_error callbacks called for tools when there is a validation error that occurs to more easily attribute the root-cause	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
Harrison Chase	1afac77439	stop making copies of inputs (#15926)	8 months ago
Nuno Campos	eb5e250188	Propagate context vars in all classes/methods ... - Any direct usage of ThreadPoolExecutor or asyncio.run_in_executor needs manual handling of context vars	9 months ago
Bagatur	e327bb4ba4	IMPROVEMENT: Conditionally import core type hints (#13700)	10 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	10 months ago