mirror of
https://github.com/hwchase17/langchain.git
synced 2025-06-23 15:19:33 +00:00
docs: concepts callbacks fix admonition (#22048)
Correct the admonition text
This commit is contained in:
parent
53293dace8
commit
37cfc00310
@ -535,10 +535,15 @@ of the object.
|
|||||||
If you're creating a custom chain or runnable, you need to remember to propagate request time
|
If you're creating a custom chain or runnable, you need to remember to propagate request time
|
||||||
callbacks to any child objects.
|
callbacks to any child objects.
|
||||||
|
|
||||||
:::important
|
:::important Async in Python<=3.10
|
||||||
For code running python >=3.11, LangChain is able to automatically propagate
|
|
||||||
request time callbacks to child objects. This feature was added since
|
Any `RunnableLambda`, a `RunnableGenerator`, or `Tool` that invokes other runnables
|
||||||
added as users forgetting to propagate callbacks was a common problem.
|
and is running async in python<=3.10, will have to propagate callbacks to child
|
||||||
|
objects manually. This is because LangChain cannot automatically propagate
|
||||||
|
callbacks to child objects in this case.
|
||||||
|
|
||||||
|
This is a common reason why you may fail to see events being emitted from custom
|
||||||
|
runnables or tools.
|
||||||
:::
|
:::
|
||||||
|
|
||||||
## Techniques
|
## Techniques
|
||||||
|
Loading…
Reference in New Issue
Block a user