Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide unnecessary log snacker on service #1973

Closed
inureyes opened this issue Oct 18, 2023 · 1 comment · May be fixed by #1974
Closed

Hide unnecessary log snacker on service #1973

inureyes opened this issue Oct 18, 2023 · 1 comment · May be fixed by #1974
Assignees
Labels
area:ux UI / UX issue. effort:normal Need to understand a few modules / some extent of contextual or historical information. field:UI / UX impact:visible This change is visible to users. platform:general type:enhance Add new features urgency:5 It is imperative that action be taken right away.
Milestone

Comments

@inureyes
Copy link
Member

Main idea

Sometimes, if an error occurs on the server, client, etc., the query is exposed to the snack bar as-is when the exception is not handled. This is not a case where any further action is required, so a UI overhaul is needed to either limit the output or direct them to the log menu.

Related issue: lablup/backend.ai#1628

Alternative ideas

No response

Anything else?

No response

@inureyes inureyes self-assigned this Oct 18, 2023
@inureyes inureyes added type:enhance Add new features effort:normal Need to understand a few modules / some extent of contextual or historical information. area:ux UI / UX issue. urgency:5 It is imperative that action be taken right away. platform:general impact:visible This change is visible to users. field:UI / UX labels Oct 18, 2023
@inureyes inureyes added this to the 23.09 milestone Oct 18, 2023
@adrysn
Copy link
Member

adrysn commented Dec 16, 2023

Closing due to inactivity

@adrysn adrysn closed this as completed Dec 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:ux UI / UX issue. effort:normal Need to understand a few modules / some extent of contextual or historical information. field:UI / UX impact:visible This change is visible to users. platform:general type:enhance Add new features urgency:5 It is imperative that action be taken right away.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants