Closed kayrus closed 3 months ago
This is our last resort catch-all for API 500 errors. We had planned to remove this message in favor of just stating that there was a 500 error but if this is indeed the case here, that this incorrect query causes a 500 on the backend then we can't really do much. Anyway we'll have a look what's happening here.
We should avoid catching 500 errors and displaying a generic error message. Instead, we should display the actual error message from the API
Type
project1-uid: user1-id
in both read and write ACLs (mind whitespace)Type the
Check ACLs
button.See
error message.
Expected behavior: the error message must say that the ACLs are incorrect.