We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
meta.update()
meta = None
I believe this Commit langfuse/langfuse-python@da264a9 from last week has introduced a bug at https://github.com/langfuse/langfuse-python/blame/main/langfuse/callback/langchain.py#L722 by allowing returning None (edit: it seems the version before the commit has also allowed returning None, so it is interesting why I only see this now), which then fails at https://github.com/langfuse/langfuse-python/blame/main/langfuse/callback/langchain.py#L445, as None doesn't have an update() method
None
update()
Run a callback with no metadata or tags and you will hit an error:
File "/..../lib/python3.10/site-packages/langfuse/callback/langchain.py", line 443, in on_tool_start meta.update( └ None
No response
The text was updated successfully, but these errors were encountered:
meta
This was incorrectly filed against the langfuse repo. It has been reposted now against the langfuse-python repo : langfuse/langfuse-python#599
Sorry, something went wrong.
No branches or pull requests
Describe the bug
I believe this Commit langfuse/langfuse-python@da264a9 from last week has introduced a bug at https://github.com/langfuse/langfuse-python/blame/main/langfuse/callback/langchain.py#L722 by allowing returning
None
(edit: it seems the version before the commit has also allowed returningNone
, so it is interesting why I only see this now), which then fails at https://github.com/langfuse/langfuse-python/blame/main/langfuse/callback/langchain.py#L445, asNone
doesn't have anupdate()
methodTo reproduce
Run a callback with no metadata or tags and you will hit an error:
Additional information
No response
The text was updated successfully, but these errors were encountered: