Closed Panaetius closed 3 months ago
This is most likely the result of the Cypress e2e tests creating a new user and loading the UI (which loads user preferences).
We should suppress expected errors anyway and just log the HTTP status, e.g.
A lot of these pollute the schemathesis logs as well, when the important logs e.g. 500 are buried.
Data Service (especially on startup) creates quite a few of these errors, but seems to be running fine:
We should figure out what is actually calling this on a fresh deployment, and if we can fix this (can we just create default user preferences if there are none?)