Replace Base.cp with run(...).

[sriharshakandala]

Replace Base.cp with run(...) on non-Windows operating systems.
Base.cp seems to have a bug when copying large files. Using run fixes this behaviour.
This fixes the bug mentioned in #64

Checklist:

• I created a new folder $artifact_name
  • I added a README.md in that that folder that
    • describes the data and processing done to it
    • lists the sources of the raw data
    • lists the required citation, licenses
  • If applicable (e.g., for Creative Commons), I added a LICENSE file
  • I added the scripts that retrieve, process, and produce the artifact
  • I added the environment used for such scripts (typically, Project.toml
    and Manifest.toml)
  • I added the OutputArtifacts.toml file containing the information
    needed for package developers to add $artifact_name to their package
• I uploaded the artifact folder to the Caltech cluster (in
  /groups/esm/ClimaArtifacts/artifacts/$artifact_name)
• I added the relevant code to the Overides.toml on the Caltech Cluster
  (in /groups/esm/ClimaArtifacts/artifacts/Overrides.toml)
• I added a link to the main README.md to point to the new artifact

[Sbozzolo]

I think that this would break compatibility with windows

[sriharshakandala]

One option is to merge this for now, revert to Base.cp once the bug is fixed in Julia Base! Most of the systems we use are either Linux or MacOS.

[Sbozzolo]

I think we can check for windows and use Base.cp in that case.

[charleskawczynski]

I think we can check for windows and use Base.cp in that case.

That's what I was thinking, too. I'm trying to run the example with Base.cp(file_path, joinpath(output_dir, basename(file_path))) on my windows machine and I have the Abort this calculation, unless you know what you are doing. warning, and it kind of seems like it's hanging (or taking a long time to download). Maybe we can add an additional warning if this is run on windows?

[Sbozzolo]

I think we can check for windows and use Base.cp in that case.

That's what I was thinking, too. I'm trying to run the example with Base.cp(file_path, joinpath(output_dir, basename(file_path))) on my windows machine and I have the Abort this calculation, unless you know what you are doing. warning, and it kind of seems like it's hanging (or taking a long time to download). Maybe we can add an additional warning if this is run on windows?

It takes a long time downloading. The way I was monitoring it is by looking at the temporary file that gets created by Downloads (haing a better progress report would be very nice...).

The warning is because you probably already have something in your directory. For this artifact (made of only one download file), it is harmless.