Log file entries to detect buggy plugins or improve plugin configuration
Posted: 2022-05-06, 05:36 UTC
Sometimes plugins are simply the wrong ones for a certain file or even cause TC to hang/crash.
In such cases, it would be great to have *attempts* to use packer/lister/fs/content plugins recorded in the log file.
This allows the user to find buggy plugins or improve the TC plugin configuration/association.
Thus: In "Configuration -> Log file -> Log operations" there could be a new option with one check box (cb) for each plugin type:
Plugin usage: cb lister cb packer cb file system cb content
For the log file, I could then imagine lines like:
Or, to give an example:
For the success state:
"failure" indicates that the plugin did not cause TC to hang, but it was simply the wrong one for the file.
"success" indicates that the plugin could successfully handle the file
"" (no success state) in a last line or directly before "Program Start" (without a "Program shutdown" entry) in the log file implicitly indicates a TC crash due to that plugin...
In such cases, it would be great to have *attempts* to use packer/lister/fs/content plugins recorded in the log file.
This allows the user to find buggy plugins or improve the TC plugin configuration/association.
Thus: In "Configuration -> Log file -> Log operations" there could be a new option with one check box (cb) for each plugin type:
Plugin usage: cb lister cb packer cb file system cb content
For the log file, I could then imagine lines like:
Code: Select all
Plugin: <type>: Using [<pluginName>] on [<file>] -> <result>
Code: Select all
Plugin: lister: Using [wrongPlugin] on [c:\somepath\image.jpg] -> failure
Plugin: lister: Using [buggyPlugin] on [c:\somepath\image.jpg]
"failure" indicates that the plugin did not cause TC to hang, but it was simply the wrong one for the file.
"success" indicates that the plugin could successfully handle the file
"" (no success state) in a last line or directly before "Program Start" (without a "Program shutdown" entry) in the log file implicitly indicates a TC crash due to that plugin...