stop should either be excluded, set to [] or utilized. Setting it to null caused errors
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 4.3k
- PR merge metrics
- No merged PRs in 30d
Description
In the prompt stop is set to null. stop should either be excluded, set to [] or utilized.
{"messages": [{"role": "system", "content": "ChatDev is a software company powered by multiple intelligent agents, such as chief executive officer, chief human resources officer, chief product officer, chief technology officer, etc, with a multi-agent organizational structure and the mission of 'changing the digital world through programming'.\n......"}, {"role": "user", "content": "ChatDev ..."}], "model": "gpt-3.5-turbo-16k", "frequency_penalty": 0.0, "logit_bias": {}, "max_tokens": 15821, "n": 1, "presence_penalty": 0.0, "stop": null, "stream": false, "temperature": 0.2, "top_p": 1.0, "user": ""}HTTP/1.0 200 OK
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the code that constructs the prompt or API request shown in the issue, then trace how the stop parameter becomes null. Compare the request with the referenced koboldcpp issue; done means stop is omitted, set to [], or used without causing the reported errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100