File copying inconsistency across different environments

[threesflux]

Hello all,

I recently had some trouble in a Dakota study I was running in which Dakota would not properly copy the contents of subfolders of a directory when using the copy_files option in work_directory. When I came across this, I then produced an MWE using the following interface block and some dummy files:

    analysis_drivers "python driver.py"
        fork work_directory named 'workdir'
            directory_tag
            directory_save
            copy_files 'driver.py' 'module'

There are dummy files/folders in the module folder, and the driver is a dummy driver that simply prints a fixed output to the results file Dakota specifies. When I run my example on windows, the files within subfolders (e.g. module/data/sample.json) are copied into the work directories correctly, but when I run in Linux environments, it fails. Specifically, module and all of its files will be copied, and the subfolders themselves will be copied nominally, but they will all be completely empty (E.g. module/data/ exists but its files are not present in the work directory).

At first, I thought there was an issue with my environment since I am using WSL (specifically an Ubuntu distro) rather than a native installation. But then I tried a Dakota environment I created through docker on a different install of linux, and the issue persisted. This is leading me to believe that it is not just a one-off issue. Does anyone have any experience with something similar? I found what I think to be the source of the copying mechanism in src/WorkdirHelper.cpp, but nothing odd stood out. There are no error prints or warnings from Dakota saying that my files could not be found/copied.

For background, this is with Dakota CLI version 6.22.0 - built with source on the linux distros and via installer on windows

[jadamstephens]

I can reproduce this problem. We'll look into it. Thanks for reporting.