peer closed connection without sending complete message body

Open

#2,662 opened on Nov 9, 2023 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language: Python
Stars: 39.5k
Forks: 4.8k
PR merge metrics: No merged PRs in 30d

Description

![default](https://github.com/lm-sys/FastChat/assets/25118902/69d8a160-b5b1-4baf-a950-5c29ff031f04)
![_cgi-bin_mmwebwx-bin_webwxgetmsgimg__ MsgID=8586737492004307929 skey=@crypt_d41cdc7c_ba475bffb4d855fe0eac5270b478e924 mmweb_appid=wx_webfilehelper](https://github.com/lm-sys/FastChat/assets/25118902/f5b9bf8d-6f19-4357-864b-ab0bc3216df2)

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

The issue provides only screenshots and the error title, with no files, tests, or reproduction steps named. Start by reproducing the “peer closed connection without sending complete message body” failure and trace the relevant Python connection-handling path. Done means identifying the triggering request and adding a verified fix or regression test, but the expected behavior is not specified.

Written by the indexing model from the issue text.

Assessment

Tech stack: python
Domain: backend
Issue type: Bug
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Stale
Clarity: Needs clarification
Newbie friendliness: 18/100