mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Feature request] Ability to hide/swipe/remove toast messages #107
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#107
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @raviwarrier on GitHub (Nov 29, 2021).
These fill up the screen and so it would be nice if we could swipe/cross them away.
Move the toast to the bottom right/left corner (especially the persistent ones like 'scanning library')
@raviwarrier commented on GitHub (Nov 29, 2021):
Updated screenshot:
@advplyr commented on GitHub (Nov 29, 2021):
You should be able to click on the toast to dismiss it, same with all other toasts.
This is definitely a bug though. There should only ever be 1 scan running for a library at a time. Are you seeing any error messages in the logs?
@raviwarrier commented on GitHub (Nov 29, 2021):
I couldn't find an 'x' on the toasts (perhaps it was the same color as the bg or small or invisible, i can't say). will check the next time I scan my library.
The cancel button didn't work (was not clickable)
@advplyr commented on GitHub (Nov 29, 2021):
There is a bigger problem here which is why are there so many scans open? It would be helpful if you could see if there are any error logs.
@raviwarrier commented on GitHub (Nov 30, 2021):
There were quite a few errors in the logs for ~/metadata/logs/daily but none for scans. I couldn't really make sense of it, but here it is, in case you need it for your investigation - https://pastebin.com/EsztUE8T
@MidnightSnowleopard commented on GitHub (Jan 2, 2022):
My experience for those messages has been that the scan took up a large amount of system resources apparently to the point where the connection to the server was dropped. This caused a re-connection but the previous scanning library message stays in place likely because the library is still scanning and never received notification that the connection broke or the scan finished. Re-connecting again during the scan creates another notification of a library scan in progress thus leading to the increasing number of them without removal.
@advplyr commented on GitHub (Apr 24, 2022):
Scanner performance issues are consolidated here #444 which was the reason for the socket disconnections.
Toasts can be cleared by clicking on them.