kos13
-
Posts
750 -
Joined
-
Last visited
-
Days Won
92
Posts posted by kos13
-
-
Android build will be delayed by a day. Sorry.
-
We have new build.
-
Please wait for the next build after 1.1.30 - it should fix the problem.
-
And thanks for your report to syncapp@bittorrent.com
-
This bug is fixed, we will update the Sync tomorrow. Sorry for problems.
-
Could you please send us logs?
We found one issue today and will release update tomorrow, but we want to make sure it will fix your issue.
-
Could you please send us logs?
We found one issue today and will release update tomorrow, but we want to make sure it will fix your issue.
-
This would be tough, since we need logs from sender and receiver. In p2p any of the 4 computers could be a sender, so let's try with some information and see if we will need more.
Thanks
kos
-
Could you please send us logs as described here we need logs to understand the issue.
And I am going to check status of your tickets.
-
This looks like a temporary file that is created by some of your program during editing.
-
There might be some timestamps adjustments, since it will be different on both ends due to a copy. But there will be no actual data transfer.
-
I meant was there at least one build that worked for you? I've sent you PM with link to older builds
-
Happy to discover there was a new version, upgraded to 1.1.30, still crashes on my debian box with geode CPU
http://forum.bittorr...-debian-wheezy/
I suspect it's a simple matter of a switch to the compiler that makes btsync incompatible with the CPU. Could you please try to make a binary that is compatibel with the geode.
Thanks in advance!
Did 1.0.x worked for you?
-
Yes, 1.1.30 works with 1.1.27.
-
And logs were sent to us, right?
-
Guys, please, please and again please send us logs. Here are the steps
Having logs will shorten time for the fix significantly. Otherwise I can't tell you anything, besides we are working on the issue and this looks like an issue.
-
Yes, it is both way synchronization.
-
I presume that an actual change history that can be merged from several distributed machines (a la git-annex or Sparkleshare) would be more robust against the kind of sync issues I keep having with btsync right now.
I agree with you that this is right way to go.
Then your design is flawed. An upgrade (regardless of how big the changes are) should never lead to data loss.
This is definitely a pain and not something we intentionally put to the system, however you have to understand that root cause of the issue - you upgrade machines in the middle of sync. I.e. two upgraded machines perform some changes and then you bring third machine that cannot be aware of these changes due to an incompatible protocol.
-
But that defeats the original purpose of btsync to have it run on many machines that independently sync each other.
Not really, the issue here is that 1.1.27 was a big update and wasn't backward compatible with previous versions. Due to incompatibility it wasn't really an upgrade. We stabilizing Sync and I hope there will be no more such incompatibility cases.
Sorry, I still think that using timestamp and file existence to find out what to sync is the wrong approach. I have been using btsync for a very short time now and already stumbled over sync issues because of this several times.
We know how to do it right, but first step we had to make is versioning. So stay tuned.
-
This is as designed. Keep in mind that upgrading due to a changes in protocol and indexing is similar to a new Sync version installation. So your case is I have Sync on three machines and deleted a file, then install Sync on a new machine where this file exists. So it will be treated as someone recovered the file.
It might be not exactly how you expect it to work, but this was a very though upgrade for us.
HTH
kos
-
Guys, just a reminder please submit us logs http://forum.bittorrent.com/topic/12658-if-you-have-syncapp-issue/ so we could effectively solve your problems.
-
Is is possible to get logs for this issue?
-
Guys, please send us logs for this problem. We are trying to reproduce issue, but logs will help us a lot.
-
That isn't a solution at all and the fact that this is an "official" workaround makes me trust in BTSync's security _a lot_ less. This is so trivially insecure it's laughable.
It is not an "official" workaround and this is not a solution at all. There is nothing that is built into Sync, that will help you to achieve what you are looking for.
I hoped that craziness of the solution will make it clear, that this is a joke and there is no other solution.
kos
Latest Sync Build: 1.1.70
in Sync General Discussion
Posted
You have to re-add folders. There were issues with DB on Windows machines.