mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
null is not an object (evaluating 'l.userContext.join') when using system prompt with external API (OpenAI, Groq etc) #986
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#986
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JamesBedwell on GitHub (May 21, 2024).
Bug Report
Description
Bug Summary:
When using a system prompt in combination with an external API such as OpenAI or Groq, the following error appears:
Steps to Reproduce:
Set up an external API endpoint such as OpenAI or Groq, set a system prompt in Settings > General, and send any message to a model on the external API (tested on Groq's llama-3-70b-8192 and OpenAI's gpt4 and gpt4o).
Expected Behavior:
Get a response from the AI which considers the system prompt
Actual Behavior:
Error message appears:
Environment
Open WebUI Version: v0.1.125
Ollama (if applicable): N/A
Operating System: macOS Sonoma and iOS 17
Browser (if applicable): Safari on macOS and iOS
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
Installation Method
Docker
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
@justinh-rahb commented on GitHub (May 21, 2024):
As usual with any new release, we often do some fixes afterwards that push direct to
mainand build new Docker images. If you haven't already done so as of 3hrs ago please try re-pulling again.@JamesBedwell commented on GitHub (May 21, 2024):
Running watchtowerrr to update the docker image fixed it, thanks so much!On 21 May 2024, at 4:10 PM, Justin Hayes @.***> wrote:
As usual with any new release, we often do some fixes afterwards that push direct to main and build new Docker images. If you haven't already done so as of 3hrs ago please try re-pulling again.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>