Description
There is currently no checking on the number of input paths supplied in a list to FileSourceImpl and its subclasses. This can lead to a confusing error when the empty list is deserialized from CrunchInputs, as an attempt is made to create a Path from an empty string.
The various paths that construct FileSourceImpl subclasses should defensively protect against creating a file source with an empty list of paths.