-
Notifications
You must be signed in to change notification settings - Fork 24
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
Crash in Bootleg during request #174
Comments
Actually, after the first crash now any command causes a crash. I assume it is because of a CUDA error that was not recovered correctly. |
Yeah the error doesn't seem to be Bootleg related. There is this warning though:
What's going on here? |
This is quite interesting because we pass |
|
Alternatively, we can make truncation optional and add a flag for it so the user can decide what to do. Although, I prefer the first approach to avoid silent bugs. |
I agree that if truncation is necessary it is a bug, but the current failure mode takes down the whole server until it is manually restarted. We can raise an error if we catch it in the server code and report it correctly to the API caller (not a 500 error). Otherwise, logging a warning and truncating is better than nothing. |
The following command: "find me a movie with chris pratt" seems to reliably trigger a crash in Booleg with the currently deployed model on staging.
The text was updated successfully, but these errors were encountered: