and may I please know how the feature has been implemented? or the issue is raised as a bug and you will be fixing it in some newer build?
It's implemented (not fixed, it's not a bug) already. The change will be included into the next major release.
Please note this error is related to put and not the get command. I noticed using get with a non-existent file pattern already throws an error. But same is not true for put
That should not be so . The
getwith file mask not matching any file should not throw an error. Please post a complete log file showing that.