-
Notifications
You must be signed in to change notification settings - Fork 0
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
Sweep: Pass server-side error messages through to the API response #1
Comments
Here's the PR! #4.💎 Sweep Pro: I used GPT-4 to create this ticket. You have 114 GPT-4 tickets left.
Step 1: 🔍 Code SearchI found the following snippets in your repository. I will now analyze these snippets and come up with a plan. Some code snippets I looked at (click to expand). If some file is missing from here, you can mention the path in the ticket description.Lines 418 to 598 in 278428b
Lines 218 to 369 in 278428b
psychic/client/python/psychicapi/psychic.py Lines 90 to 260 in 278428b
psychic/client/python/psychicapi/psychic.py Lines 190 to 366 in 278428b
psychic/dashboard/src/pages/query.tsx Lines 26 to 173 in 278428b
Step 2: 🧐 Snippet AnalysisFrom looking through the relevant snippets, I decided to make the following modifications:
Step 3: 📝 PlanningI have created a plan for writing the pull request. I am now working my plan and coding the required changes to address this issue. Here is the planned pull request: Pass server-side error messages through to the API response
Step 4: ⌨️ CodingI have finished coding the issue. I am now reviewing it for completeness. Step 5: 🔁 Code ReviewSuccess! 🚀 I'm a bot that handles simple bugs and feature requests but I might make mistakes. Please be kind! |
Right now any exceptions that occur server-side are not passed through to the API response. Instead, all server-side errors return error code
500
with no additional details. This can be frustrating for errors that are easily resolved, for example expired API keys or invalid values for certain parameters.We should pass all server-side error messages through to the API response, and use the appropriate error codes depending on the nature of the exception.
The text was updated successfully, but these errors were encountered: