Changes between Initial Version and Version 1 of Ticket #1634, comment 2


Ignore:
Timestamp:
2012-12-19T22:54:19Z (12 years ago)
Author:
ClashTheBunny
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1634, comment 2

    initial v1  
    1818
    1919The change to fix this should either be in TahoeLAFS to output something like 0 for a null sized file, or at least an integer, like "-1", or PyFS should be updated to check "size" for null and replace it with 0 or a "-1".
     20
     21UPDATE:
     22
     23I did get it to do it again on Windows, and it seems to be the same error:
     24{{{
     25Traceback (most recent call last):
     26  File "_ctypes/callbacks.c", line 314, in 'calling callback function'
     27  File "C:\Python27\lib\site-packages\fs\expose\dokan\__init__.py", line 256, in
     28 wrapper
     29    return func(self,*args)
     30  File "C:\Python27\lib\site-packages\fs\expose\dokan\__init__.py", line 173, in
     31 wrapper
     32    res = func(*args,**kwds)
     33  File "C:\Python27\lib\site-packages\fs\errors.py", line 191, in wrapper
     34    return func(*args,**kwds)
     35  File "C:\Python27\lib\site-packages\fs\expose\dokan\__init__.py", line 604, in
     36 FindFilesWithPattern
     37    data = self._info2finddataw(fpath,finfo,None)
     38  File "C:\Python27\lib\site-packages\fs\expose\dokan\__init__.py", line 794, in
     39 _info2finddataw
     40    data.nFileSizeHigh = info.get("size",0) >> 32
     41TypeError: unsupported operand type(s) for >>: 'NoneType' and 'int'
     42}}}
     43
     44Also, this may be a good idea to fix in the web interface.  I don't know why size is ? for MDMF files when I look at a DIRCAP through the web interface.  Is my file there?  Is it corrupted?  Is it just hard to calculate the size?  Maybe a message other than "?" would be better