Skip to content

Errors not being exposed in the UI #2997

@cesnietor

Description

@cesnietor

When an error occurs, tipically a 500 error, there is no visual feedback on what went wrong.
Currently we need to go to the browser's Inspector to see what went wrong which makes debugging more difficult.

This can happen due to e.g. a wrong policy, an ldap user with not enough permissions, etc.
e.g.

Screenshot 2023-08-14 at 4 58 50 PM

Expected Behavior

500 errors should be shown in the UI could be a snack bar or something related.

Current Behavior

Errors are not being shown

Possible Solution

Show snackbar on all non 200 codes for all requests unless 400 codes and permission denied errors are already being handled.

Steps to Reproduce (for bugs)

Example with wrong Policy

  • Go to Access Keys
  • Add new Access Key
  • click on created object
  • A policy builder should pop up
  • Type only {
  • Click on Set
  • An error should occur due to the invalid policy
  • [Error] The error is not being shown, only on inspector you'd see the 500

Context

Regression

Your Environment

  • MinIO version used (minio --version): RELEASE.2023-08-09T23-30-22Z
  • Server setup and configuration:
  • Operating System and version (uname -a):

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions