Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Usage problems

See original GitHub issue

Hi, I’m using dat cli v12.0.0 and node v4.2.6 on a local ubuntu machine and a remote debian server. I executed:

On the local machine:

Then on the remote machine:

All good. Then, while keeping the dat share command running on the local machine, on another bash tab I executed:

Then on the remote machine:

Problem…the file is not updated to the latest version.

Back on the local machine:

Bigger problem, the source folder got reverted to the previous state!

I can’t figure out the problem…any help would be much appreciated, thanks!

Issue Analytics

State:
Created 7 years ago
Comments:23

Top GitHub Comments

1reaction

joehandcommented, Feb 22, 2017

Hi @joehand, I’ve done the same tests again and its working!

Sweet! Thanks for sticking with us through these replication bugs.

However, I added a couple more steps and there are still some issues. Same scenario as before: 2 machines, one running dat share on the source folder, the other with a destination folder after running dat clone.

Right now, once a file is downloaded dat marks it as downloaded and will never update it again until there is an update at the source. We weren’t really sure how to handle this situation but we should definitely provide some way to get back in sync, similar to a git reset HEAD.

We will be changing how metadata is stored soon (in files instead of a database) that will make it easier to address this. In the meantime, you can delete the database (in .dat of the destination dir) and clone again:

rm -rf /home/jamie/folder/.dat
dat clone <link> /home/jamie/folder

This will reset the metadata, index the destination directory, and download anything missing.

0reactions

jaime-ezcommented, Feb 22, 2017

Hi @joehand, I’ve done the same tests again and its working!

However, I added a couple more steps and there are still some issues. Same scenario as before: 2 machines, one running dat share on the source folder, the other with a destination folder after running dat clone.

When running dat sync at destination folder, if a make a change to the file at destination the file remains unaltered. That is the file at destination is no longer synced with the file at source. Is this how it is supposed to be?
If I make a change to the file at destination folder and then run dat pull the file remains unchanged again…
If I delete the file at the destination folder and then run dat pull the file is not retrieved:

If I go back to the source machine and modify the file at source the behavior described at 1, 2, 3 changes and it works as expected: the file is updated correctly at destination.

Note: all the file changes were done adding or deleting strings ath the end of the file

Cheers