Open GoogleCodeExporter opened 9 years ago
Looks like Tahoe must be returning some 'c_stat' attribute which isn't in the
expected integer format (but only for some files, not all of them).
Could you modify the 'set_st_attrs' function in fuse_ctypes.py (or fuse3.py
depending on which version you're testing with) and change the bit that says:
setattr(st, key, val)
to:
try:
setattr(st, key, val)
except:
print "Couldn't set %s attr %s to %s" % (type(key), key, val)
and then re-run your test?
Original comment by gc...@loowis.durge.org
on 15 Mar 2015 at 12:19
Couldn't set <type 'str'> attr st_size to None
Original comment by zl29ah@gmail.com
on 15 Mar 2015 at 12:32
Are you able to determine what size the files (or directories?) returning
errors are *supposed* to have?
I've never even used Tahoe myself, but digging into the code, maybe 'getinfo'
in fs/contrib/tahoelafs/__init__.py or '_info' in fs/contrib/tahoelafs/util.py
needs some extra special-case code to correctly handle the 'size' attribute as
returned from Tahoe?
Original comment by gc...@loowis.durge.org
on 15 Mar 2015 at 1:03
First of all, its tahoe-lafs itself that hangs. I don't know why.
The web interface reports size as "?", tho the files are opened fine :/
Original comment by zl29ah@gmail.com
on 15 Mar 2015 at 2:28
So perhaps this is a bug in tahoe-lafs then, which needs to be fixed there
rather than in pyfilesystem? *shrug*
Original comment by gc...@loowis.durge.org
on 15 Mar 2015 at 7:09
Seems like a deliberate design decision on their side:
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2332
Original comment by zl29ah@gmail.com
on 29 Mar 2015 at 11:48
Original issue reported on code.google.com by
zl29ah@gmail.com
on 15 Mar 2015 at 10:31