Timestamp Errors with rsync over Samba

I was using rsync to copy files over Samba GVFS with no issues between two Leap 42.3 machines. But, ever since I upgraded my destination machine to Leap 15.1, rsync has been reporting an error for most if not every file copy:

# cd /run/user/###/gvfs/smb-share:server=host,share=share,user=user/path/to/dir/
# rsync /path/to/dir/ ./
rsync: failed to set times on "/run/user/###/gvfs/smb-share:server=host,share=share,user=user/path/to/dir/.temp.file": Input/output error (5)
# ls --full-time ./ /path/to/dir/
-rw-r--r-- 1 user users 1 2019-01-01 00:00:02.000000000 +0000 ./test.file
-rw-r--r-- 1 user users 1 2019-01-01 00:00:03.856692582 +0000 /path/to/dir/test.file

Note that in spite of the error, something managed to set the timestamp within two seconds of the original (rounded to the second), yet my destination’s SMB configuration does not have

dos filetime resolution = yes

If I try to copy the file via cp, cp doesn’t report an error, but also doesn’t preserve the timestamp.

# date -Iseconds -u
# cp --preserve=timestamps /path/to/dir/test.file ./
# ls --full-time ./ /path/to/dir/
-rw-r--r-- 1 user users 1 2019-07-17 01:10:54.342579932 +0000 ./test.file
-rw-r--r-- 1 user users 1 2019-01-01 00:00:03.856692582 +0000 /path/to/dir/test.file

I have been managing fine with this error, but I am trying to determine what changed and if I can restore this workflow to a state where I don’t encounter these errors.