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
Observed in Kana's use case: when a prediction validation request is not validated (returning a 422), we do not log what the issue was.
We should log the details of the error (either here or in AtmosphereX) to be able to inform users when such error occurs, but it should not include the values from the request, only the keys which created the error (which I think is the default behaviour from the detail message created by the pydantic validation module).
The text was updated successfully, but these errors were encountered:
Observed in Kana's use case: when a prediction validation request is not validated (returning a 422), we do not log what the issue was.
We should log the details of the error (either here or in AtmosphereX) to be able to inform users when such error occurs, but it should not include the values from the request, only the keys which created the error (which I think is the default behaviour from the detail message created by the pydantic validation module).
The text was updated successfully, but these errors were encountered: