-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
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
LLM Chain with Hugging Face #8721
Comments
Hey @the-trading-ai If you open the LLM chain is there a larger error in there? Can you also share the workflow json so we can use it to reproduce the issue? |
Same problem here in using any type o Summarization Chain (1.29.1) : TypeError: message.toJSON is not a function |
I'm also seeing the same error on [email protected]:
|
^ This issue affects all LLM function -- including OpenAI (not just HuggingFace). |
Pretty sure this is the line that the error is referring to:
|
This code was introduced by this commit: As part of this PR: I'm going to upgrade to [email protected] and see if that fixes the issue. |
We will look into this in the morning and potentially put out a new released for now though you can go back to a previous release and you should be good to go. |
Getting a different error on [email protected] - FYI:
|
Ironically, the |
Confirmed that this issue is not present in [email protected] -- it does presently exist in all later versions. |
Fix got released with |
Good news, This should now be resolved. I am going to mark this as closed and if you are still seeing this issue let me know. |
@Joffcom , no dice. I'm still seeing these errors using the
|
^ This workflow works fine on [email protected] |
Hey @Joffcom and @janober , I think I sort of understand the issue. This error appears only for legacy workflows and legacy nodes. If I create a brand new workflow with the same identical nodes, this error doesn't exist. This tells me that there's some backwards compatibility issue that's breaking older workflows/nodes. Steps to reproduce:
As it stands right now, if there's no way to "auto-upgrade" legacy workflows/nodes to support new 1.30.1+ features, then all your existing users will be experiencing this same pain along the way. I'm not sure how to solve this issue, but FYI. Recreating the simple |
Oh, interesting... the newer |
Yup, confirmed. In [email protected]+, I had to manually regenerate the |
@dkindlund the good news is that sounds like a different issue so I believe the original issue here is solved and there is another one to look into. You also don't need to worry about tagging us if we are commenting we will get notifications on new posts we are also mainly around during Berlin office hours 🙂 We will look into this new issue on Monday morning. It may be worth opening a new issue so it doesn't get confused with the original issue here. |
Bug Description
When I connect a Chat with the LLM Chain Node and use Hugging Face, i got an error message : message.toJSON is not a function
To Reproduce
Expected behavior
The message form the model
Operating System
hosted
n8n Version
Latest 1.29
Node.js Version
hosted
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: