You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error field of the OpenAI health check is currently a stringified Go error, which is tricky for the frontend to parse. It would be nicer for the frontend if we returned something better, such as the actual response body as an any type. This could even appear in a separate nullable field, in case there is no response body (e.g. if the HTTP request failed to send for some reason). The details would then look something like...
{
"configured": true,
"ok": false,
"error": "unexpected status code 401: {<the `response` object below>}",
"response": {
"error": {
"message": "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}
}
The text was updated successfully, but these errors were encountered:
The
error
field of the OpenAI health check is currently a stringified Go error, which is tricky for the frontend to parse. It would be nicer for the frontend if we returned something better, such as the actual response body as anany
type. This could even appear in a separate nullable field, in case there is no response body (e.g. if the HTTP request failed to send for some reason). The details would then look something like...The text was updated successfully, but these errors were encountered: