Skip to content
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

Better Error Reporting #3288

Open
gmatht opened this issue Oct 18, 2024 · 1 comment
Open

Better Error Reporting #3288

gmatht opened this issue Oct 18, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@gmatht
Copy link

gmatht commented Oct 18, 2024

Please describe the feature you want
In many cases Tabby should be able to report what is wrong on the server console (perhaps only if -v is on the commandline), in the content of the HTTP error response, on the Web UI and/or in a .log file inside ~/.tabby.

Additional context
For example, If we do not run tabby serve with --model the Tabby server will start up without any error messages but reject all requests with a 501 Error. I did not find any explaination for this in any output or log files. It could have reported an error message like "No --model parameter was specified on the Tabby server command line. Re-run Tabby with a --model parameter to fulfill completion requests".


Please reply with a 👍 if you want this feature.

@gmatht gmatht added the enhancement New feature or request label Oct 18, 2024
@wsxiaoys
Copy link
Member

related #3239

@wsxiaoys wsxiaoys self-assigned this Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants