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
I've now observed different behavior on ibutsu, with no changes to the production containers from when this was written.
The mentioned filters now work intermittently, but will still cause type errors. Still unable to actually reproduce locally, even after loading results that didn't contain the metadata field being searched.
Alright, so some sanity has been found after some digging, learning, and a conversation with @rsnyman.
The root of this issue is the gateway timeout in the haproxy route in OCP. The backend/api query is taking too long, and the route times out and throws a 504.
The HttpClient functions, and fetch, aren't setup to cleanly handle this, so a TypeError occurs in the frontend.
Three actions are planned in order to better deal with this:
Modify the OCP template spec for the backend route to increase the timeout
Optimize/Improve performance of the result queries
Better handling of potential gateway timeouts in the result-list page
mshriver
changed the title
TypeError from floatish filtering
TypeError from gateway timeouts
Aug 10, 2022
When filtering metadata fields like
metadata.SomethingVersion
for semantic versions like1.2.3
, a TypeError is produced, and no results fetched.@rsnyman suggested these values are getting processed as floats, and the filter is trying to typecast. It should be interpreted as a string.
The text was updated successfully, but these errors were encountered: