#STOP sequence breaks POST request

6 messages · Page 1 of 1 (latest)

frozen forge
#

The following POST request breaks if you include the stop sequence. If you don't include it then it works just fine:

{
"model": "gpt-3.5-turbo-0613",
"messages": [{"role":"system","content":"you are an assistant, complete the chat."},{"role":"user","content":"Hey are you a robot?"}],
"max_tokens": 300,
"stop": ".",
"functions": [
  {
    "name": "being",
    "description": "Gets who or what someone is",
    "parameters": {
      "type": "object",
      "properties": {
        "source": {
          "type": "string",
          "description": "Who is asking?"
        },
        "target": {
          "type": "string",
          "description": "who is being asked?"
        }
      },
      "required": [
        "source",
        "target"
      ]
    }
  }
]
}

It seems function calling does not work with stop sequences. Anyone else agree?

sacred kite
#

Yes. The stop sequence is used to tell the model when to stop generating new tokens. You set "." as the stop sequence, the model will of course stop generating when meeting a full stop

knotty yew
#

stop should be an array of strings

frozen forge
frozen forge