Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

invalid literal #29

Closed
reagle opened this issue May 27, 2016 · 8 comments
Closed

invalid literal #29

reagle opened this issue May 27, 2016 · 8 comments

Comments

@reagle
Copy link

reagle commented May 27, 2016

Was testing the most recent version and got the following error:

Traceback (most recent call last):
  File "/home/reagle/bin/bsync", line 866, in <module>
    show_conflict(f1, f2, path)
  File "/home/reagle/bin/bsync", line 479, in show_conflict
    p1 = getfilemode(f1.type, f1.perms)+" "+f1.size+"B ("+getdatestr(f1)+")"
  File "/home/reagle/bin/bsync", line 469, in getfilemode
    return type + stat.filemode(int(perms, 8))[1:]
ValueError: invalid literal for int() with base 8: ''
@pdxvr
Copy link

pdxvr commented Nov 19, 2018

I get this all the time too. I haven't figured it out yet, but it would be nice to. I usually just delete my snapshots but that's a little risky

@pdxvr
Copy link

pdxvr commented Dec 7, 2018

I've had to stop using this as I started getting this all of the time. I don't think it's a hard fix, but I don't know Python. I understand what the error is and what it's doing, I just don't have the Python to fix it myself.

@dooblem
Copy link
Owner

dooblem commented Mar 4, 2019

Hello @reagle @pdxvr

Can you help me to reproduce? I not too confidential you may send me the .bsync-snap files.

On what filesystems are the files?

@dooblem dooblem closed this as completed Mar 4, 2019
@dooblem dooblem reopened this Mar 4, 2019
@reagle
Copy link
Author

reagle commented Mar 4, 2019

I haven't used bsync since 2016 when I reported this.

@pdxvr
Copy link

pdxvr commented Mar 5, 2019

I stopped using this after my last post, however I'm willing to give it another run if you have the patience to wait until I'm able to reproduce the error.

@dooblem
Copy link
Owner

dooblem commented Mar 5, 2019

Thanks @pdxvr . would be great. You may take your time as I did ;)

@dooblem
Copy link
Owner

dooblem commented Mar 5, 2019

This is probably because you have a filesystem on fat.
Check #38 . at least now it should not crash.
I'm closing this in favor of #38

@dooblem dooblem closed this as completed Mar 5, 2019
@pdxvr
Copy link

pdxvr commented Mar 6, 2019

I just ran the older version and got this error, installed the newest version and it worked. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants