mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
d@403a635aa8eaa8bfa8613acb6a375d9e06ed7001 2024-08-01 13:49:41 +00:00 • committed by admin
parent dc1f707875
commit 9728762a2c
1 changed files with 14 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
doc/bugs/Trust_but_Verify__58___RClone/comment_4_85ab0706894fba7807d3d0ac67cc8031._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="d@403a635aa8eaa8bfa8613acb6a375d9e06ed7001"
nickname="d"
avatar="http://cdn.libravatar.org/avatar/b79468a0d03ec3ec7acbae547c4fa994"
subject="comment 4"
date="2024-08-01T13:49:40Z"
content="""
Hi, Spencer, thank you for testing and reporting this!
I've been attempting to repro this failure with a (janky) end-to-end test in the rclone repo: [PR #7983](https://github.com/rclone/rclone/pull/7983). Unfortunately, I can't repro the data loss you've described despite running it 30+ times. However, if you're able to reliably repro, that indicates my e2e test is missing something.
One potential difference is that I'm invoking rclone to delete the content from Dropbox. It sounded like you might be deleting from a local directory managed by Dropbox's app, then waiting for a visual indication that it has synchronized with Dropbox's servers. Can you clarify how you're deleting the file?
"""]]