You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A frequent issue we have is that copy (particularly during package) does not match the files it is intended to match, but often too many files are packaged. To allow to investigate this better, it would be good if, optionally, the files matched by each call should be logged. Currently, only the overall set of files matched by all call options, and the output is aggregated by extension if there are more than a few files.
The text was updated successfully, but these errors were encountered:
Hi @uilianries, thanks for the suggestion, however this is missing a critical information, namely which call of copy caused the particular files to be copied, i.e. in particular the values of the pattern and src parameters. This is particularly hard to debug if something is wrong.
A frequent issue we have is that copy (particularly during package) does not match the files it is intended to match, but often too many files are packaged. To allow to investigate this better, it would be good if, optionally, the files matched by each call should be logged. Currently, only the overall set of files matched by all call options, and the output is aggregated by extension if there are more than a few files.
The text was updated successfully, but these errors were encountered: