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
On closure inspection though I noticed that only the requests that included station_observations.PRECIP_TOTAL were failing, and that taking one of these request and removing that portion meant it passed:
The station in question does not have variable PRECIP_TOTAL. So this request is definitely an error condition. But I'd argue that we should catch the fact that the client is requesting non-existent variables and return an HTTP 400 error.
I noticed a large number of HTTP 500 errors in the PDP Backend logs:
I confirmed this was still occurring by running these requests manually:
On closure inspection though I noticed that only the requests that included
station_observations.PRECIP_TOTAL
were failing, and that taking one of these request and removing that portion meant it passed:Unfortunately there were no errors or stack traces in the container log.
The text was updated successfully, but these errors were encountered: