-
Notifications
You must be signed in to change notification settings - Fork 387
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
log failed tasks #1105
Comments
Also I noticed that there were only two log levels "dbg" and "err" ? I think "warn" and "info" could be useful to help troubleshoot better the issues. |
Hi, this is a breaking change for the upcoming Yazi v0.3 release. Please remove the |
thanks it helped. I will let you close or let open depending on what you think of this part of my message
|
Do you mean to move the errors from the task manager to the log file for async tasks, or to keep the errors in the task manager and also copy them to the log file? The reason I didn't add them to the error log before is that async tasks are often concurrent, making it hard to track their order in the log. But in the task manager, we can |
Added to the Feature Requests as Group tasks in Task Manager by "Running"/"Failed" |
Added some error notifications for the |
I'm going to lock this issue because it has been closed for 30 days. ⏳ |
Please describe the problem you're trying to solve
I am trying to implement the suggested solution #1103 so I updated to nightly yazi, doing so I noticed the "28 tasks" in taskbar. Typing
w
prompted the task list with this result:Typing "Enter" on one of the entry I got:
Would you be willing to contribute this feature?
Describe the solution you'd like
I tried to get more context via
less /home/teto/.local/state/yazi/yazi.log
but the file remains empty (I had previously removed it).I believe failed tasks should be logged in the log file. And maybe the UI could be improved to show more info:
Run preloader 'mime'
is supposed to help me.Here is the excerpt from my config:
is
mime
the name of a builtin preloader ?Additional context
once again thanks a lot for this amazing software that never ceases to amaze me
The text was updated successfully, but these errors were encountered: