Ignoring unfinished downloads on plugged-in drives

The situation

A drive keeper was trying to process files on a plugged-in drive, but it failed when it encountered an unfinished download file. The keeper had already finished processing most of the files, but it was still trying to hear the unfinished download, which caused an error. There were also many unfinished downloads that had already been kept as recordings. The keeper uses a list of patterns to skip certain files, and it was already skipping some types of unfinished downloads. The goal is to prevent the keeper from trying to hear unfinished downloads on plugged-in drives. The keeper's behavior is guided by a set of rules that determine which files to skip, and these rules are read from a configuration file. The configuration file already contains some rules for skipping unfinished downloads, but they are not being applied to the drive keeper.

What they weighed

• Add rules for unfinished-download endings to the drive keeper

  Chosen

• Special-case unfinished downloads in the keeper code

What they decided

Add rules for unfinished-download endings to the drive keeper

Why

The keeper should not try to hear unfinished downloads because they are not recordings. Adding rules for unfinished-download endings to the drive keeper is a simple solution that does not require changing the code. The existing rules for skipping unfinished downloads can be used as a model for the new rules. This solution also ensures that the keeper will not try to hear unfinished downloads on plugged-in drives without having to modify the code.

The first step

Update the configuration file with the new rules and restart the keeper

How they would know it worked

The keeper will skip unfinished downloads and not try to hear them

How it turned out

Not known yet. The result is added here when it comes in.