How will this affect the next version number?
New feature (increment MINOR version)
Is your feature request related to a problem?
We just need to make a design decision on behavior when a broken symlink is encountered. Currently, it causes a FileNotFoundError.
Describe the solution you'd like
See @TonyB9000's comment here:
I think it is sufficient to simply note the failed "add" of the file whose size could not be determined (broken symlink, etc.) If the user were relying upon an "abort" here, that won;t happen, and could lead to a lot of wasted effort, so (ideally) a command line flag like "--exit_on_failure" (which I demanded of "e3sm_to_cmip") allows the user freedom in this regard. That addition would retain the legacy (e2c) behavior by default. In this case, however, we might do the reverse (a flag for "--continue_on_error"), retaining the legacy "exception/abort" as a default.
Describe alternatives you've considered
No response
Additional context
No response
How will this affect the next version number?
New feature (increment MINOR version)
Is your feature request related to a problem?
We just need to make a design decision on behavior when a broken symlink is encountered. Currently, it causes a
FileNotFoundError.Describe the solution you'd like
See @TonyB9000's comment here:
Describe alternatives you've considered
No response
Additional context
No response