Skip to content
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

(firestore-genai-chatbot) Consistently erroring with 400 Bad Request #476

Open
joehan opened this issue Apr 17, 2024 · 1 comment
Open
Assignees

Comments

@joehan
Copy link

joehan commented Apr 17, 2024

[REQUIRED] Step 2: Describe your configuration

  • Extension name: firestore-genai-chatbot
  • Extension version: Latest
  • Configuration values (redact info where appropriate):
    • Not provided

[REQUIRED] Step 3: Describe the problem

Duplicate of internal bug b/330838846, more details provided there

Customer installed the Firebase extension "Chatbot with Gemini", and it initially functioned correctly, but after a while, it stopped working entirely ,and all function calls failed with the error message: "ClientError: [VertexAI.ClientError]: got status: 400 Bad Request." [1].

Questions:

  • What could be causing this error?
  • Is there any way to see more detail on the Bad Request error? Is the API returning any more detail than that?
  • How should context be provided when using this extension?
@cabljac
Copy link
Collaborator

cabljac commented Apr 19, 2024

do we have access to their config, and any details on the input?

Context can either be provided in the config, or (if overrides are configured on) in the parent doc of the chat collection (needs to be a subcollection in this case)

e.g if you put "act like a pirate" in the config parameter context and your collection path was chats/{cid}/messages

then you put "don't act like a pirate" in the context field of the document chats/123, in theory it shouldn't respond like a pirate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants