You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Function Calling Filter Pipeline have been erroring in the "inlet" portion. I have been documenting in the Discord troubleshooting section.
Some examples of the logs that I had been receiving:
`Connection error: Object of type ModelModel is not JSON serializable
ERROR [open_webui.routers.tasks] Error generating chat completion: (500, 'list index out of range')
Connection error: 500 Server Error: Internal Server Error for url: http://pipelines:9099/test-pipeline/filter/inlet
INFO: 192.168.1.1:0 - "POST /api/v1/tasks/auto/completions HTTP/1.1" 500 Internal Server Error`
As a part of the troubleshooting process, I created a single pipeline that had the functionality of calling functions. I initially used the Function Calling Blueprint, and I got the error again.
I then started pulling parts from within the Blueprint to isolate the issue, and I found that the problem comes from how the Params are passed to the call_function part of the code.
I plan to submit a PR with the fix for this in the coming days.
The text was updated successfully, but these errors were encountered:
The Function Calling Filter Pipeline have been erroring in the "inlet" portion. I have been documenting in the Discord troubleshooting section.
Some examples of the logs that I had been receiving:
`Connection error: Object of type ModelModel is not JSON serializable
ERROR [open_webui.routers.tasks] Error generating chat completion: (500, 'list index out of range')
Connection error: 500 Server Error: Internal Server Error for url: http://pipelines:9099/test-pipeline/filter/inlet
INFO: 192.168.1.1:0 - "POST /api/v1/tasks/auto/completions HTTP/1.1" 500 Internal Server Error`
As a part of the troubleshooting process, I created a single pipeline that had the functionality of calling functions. I initially used the Function Calling Blueprint, and I got the error again.
I then started pulling parts from within the Blueprint to isolate the issue, and I found that the problem comes from how the Params are passed to the
call_function
part of the code.I plan to submit a PR with the fix for this in the coming days.
The text was updated successfully, but these errors were encountered: