lm-sys / lm-sys/FastChat

No available workers for vicuna-7b-v1.3

Open
#2,053 3 comments 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

Hi guys,

I was wondering what the following output is supposed to mean when running

python3 -m fastchat.serve.test_message --model-name vicuna-7b-v1.3
# OUTPUT
Models: []
worker_addr: 
No available workers for vicuna-7b-v1.3

The controller and the model worker seem to be running (sending out heartbeats 2023-07-22 07:26:33 | INFO | model_worker | Send heart beat. Models: ['vicuna-7b-v1.3']. Semaphore: None. call_ct: 0. worker_id: 7c4af17d. ), however when calling the model I receive a openai.error.APIError: Invalid response object from API: 'Internal Server Error' (HTTP response code was 500) error.
thx a lot!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running python3 -m fastchat.serve.test_message --model-name vicuna-7b-v1.3 and compare its output with the controller and model worker heartbeat logs shown here. Read the worker-discovery path around the controller, worker heartbeats, and test_message entry point; done means reproducing the failure and identifying why the worker is not available or why the request returns HTTP 500.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.