HandBrake / HandBrake/HandBrake

Minor feature request: Add the "Reason Why" to failed Queue Items or in general, add a Status-field to the Queue-Item-Summary

Open
#2,586 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement
Dominant language
C
Stars
24.4k
Forks
1.7k
Avg merge
5d 1h
Merged PRs (30d)
8

Description

Description of the feature or enhancement you'd like to see in HandBrake:

In case an queued job fails, one has to work himself through the Activity Log to figure out why. But since the app already found out why, why not show this as a "Status" or "Result" as the latest Summary Item? - from my point of view, and if all users have >= Full-HD displays, there is plenty space and either a Result: Succeeded or the specific error message (which can be found in the Activity Log anyways), are displayed.

Depending on the size of the job - or so to say the length of each item specific Activity Log - this would save some time... and still, if the error is more complex, a user can dig deeper.

From my point of view, this shouldn't be such a big deal just due to the fact that the error is already handled at the point the item is marked failed, nor? :)

What version of HandBrake are you currently running (e.g., 1.3.0)?

Nightly 20200115194359-1994200-master (2020011501)

What operating system and version are you running (e.g., Ubuntu 19.10, macOS 10.15 Catalina, Windows 10 1909)?

Windows 10 v1909 x64 all recent updates etc.

HandBrake Activity Log:

If this request is related to an error or unsupported file, an Activity Log will help us track down what exactly is not working properly or not implemented. Please read https://handbrake.fr/docs/en/latest/help/activity-log.html for more information.

Please replace this text with the Activity Log, or upload the log file to Github by dragging and dropping the file on this post.
Leave the ~ marks above and below.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue identifies no files, tests, or entry points; start by locating the queue-item summary and failure-result handling in the HandBrake desktop UI. Done means failed queue items show their reason or a status/result, successful items show a success result, and detailed diagnostics remain available in the Activity Log.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.