-
Notifications
You must be signed in to change notification settings - Fork 146
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
Sample command with mistral-7b failed #312
Comments
Hey @hayleyhu, thanks for reporting this. This is a surprising error. Could you try running the same command, but including the environment variable Example:
|
Hello @tgaddair ,
|
Hey @Nipi64310, thanks for providing this additional context. Unfortunately, it looks like the offending call to |
Hi @tgaddair , thanks for getting back to me. I've now updated to the latest Docker image and I can start it now. |
Hello @tgaddair ,
|
Hey @Nipi64310, can you share the output of
@hayleyhu can you try pulling the latest image and see if that resolves the unwrap() panic? |
Okay, I think I see what's happening here. The unwrap error is occurring because of PR #309, which was accidentally pushing cc @magdyksaleh Let's make sure we only push dev images with a specific tag for the branch. I'll see if there's something we can do to prevent this automatically. In the meantime, I'll see if we can retag the current latest with the last commit to main. |
@magdyksaleh confirmed the latest image has been fixed to be tagged from |
Hi @tgaddair , I specified
|
Thanks my original question was resolved! |
System Info
Nvidia GPU A100*8
Linux OS
Information
Tasks
Reproduction
Expected behavior
Server can start
The text was updated successfully, but these errors were encountered: