zeropluszero

Members
  • Posts

    35
  • Joined

  • Last visited

Posts posted by zeropluszero

  1. Hello RomanZ, thank you for taking time to respond to our problems :)

    I can confimr no issue using "$" sign in folders name or files name, at least with my tests. But i do continue to have issues regarding the temporary "*.sv$" files that corrupt my files ;( Is there any chance that behaviour will be reported in the known issues so the dev could work on it ?

     

    Thanks !

  2. I have a list of files that won't sync now. They all start with -$ and then a filename. I don't see these files in the folder btsync thinks they are in. I have no open files, so that's not the issue. Is this part of the known bug where filenames with certain characters don't sync?

     

    It seems that overall this version is slightly better than .83, but still buggy. One peer reports that it is fully synced and the other lists files awaiting transfer. Sizes are still misreported on some folders. Some folders show a size of 0. Thanks for making this version a little better than the last version of 1.4, but 1.4 overall seems to be a drastic step backward. Why did the sync engine get so buggy just because the front end chagned? Shouldn't the UI be independent of the backend? I still have high hopes for btsync (nothing matches the speed), but I currently have 0 confidence that I my data is correctly syncing across all the nodes.

     

    What you described with your files containing $ sign could explain why i cant add some extension "*.sv$" in the ignorelist !

    Let's hope this is actually a known bug indeed :)

  3. RomanZ, on 17 Oct 2014 - 4:42 PM, said:snapback.png

    @juggler

    It is still there. We'll fix it soon.

     

    @eltopo

    We'll take a look on what happens, thanks for reporting.

     

    @Devonavar

    Sync 1.4 should handle gracefully any xattrs it can't save on target peer. They are saved into .sync folder and PC which is unable to store them as xattrs / alt streams will still be able to sync them to other machines.

     

    @richdotward

    Every Sync release is verified by QA. Though, there are certain limitations:

    1) As Sync supports a wide variety of platforms and configurations, it is impossible to check every possible configuration.

    2) We cannot include every and other bug reported by users due to limited man force.

     

    For the blank UI issue - please take a look at this topic, it might help.

     

    @hurik

    Yes, it is.

     

    @zeropluszero

    We are are working on the fix to make ignoreList working very early on file change, so it should resolve your issue.

     

    Unfortunately, the 1.4.93 doesn't fix the sv$ temporary file issue ;(

  4. @juggler

    It is still there. We'll fix it soon.

     

    @eltopo

    We'll take a look on what happens, thanks for reporting.

     

    @Devonavar

    Sync 1.4 should handle gracefully any xattrs it can't save on target peer. They are saved into .sync folder and PC which is unable to store them as xattrs / alt streams will still be able to sync them to other machines.

     

    @richdotward

    Every Sync release is verified by QA. Though, there are certain limitations:

    1) As Sync supports a wide variety of platforms and configurations, it is impossible to check every possible configuration.

    2) We cannot include every and other bug reported by users due to limited man force.

     

    For the blank UI issue - please take a look at this topic, it might help.

     

    @hurik

    Yes, it is.

     

    @zeropluszero

    We are are working on the fix to make ignoreList working very early on file change, so it should resolve your issue.

    Thank you for your response ! will look forward to your new release, hoping that will fix this issue :)

  5. Hi everyone. I'm facing an issue with the 1.4 version, but very specific to a file type. I work with autodesk 3ds max software, who use some *.sv$" temporary files to write the "*.max" files. Using the 1.3 version, i've just add in ignore list the sv$, and it worked like a charm ! Since the 1.4 version, that doesn't work anymore, adding or removing the sv$ in the ignorelist corrupt the sv$ file and 3ds max refuse to write the max file ... Anybody having this issue or a possible workaround (since going back to 1.3 seems veeeerrrry unpleasant)

     

    Cheers !

  6. Hi Bittorrent Sync team, thank you so much for this amazing soft :)

     

    I would love to have the ability to point a file that fail to sync between computers.

    From time to time i have trouble syncing through hamachi networks, but the app only give a size remaining to transfer, making it very difficult to point ...

    Double clicking that information could lead to the files maybe ??

     

    Regards,