[volunteergrid2-l] Bug in deep-check --repair ?

[Johannes Nix]

Hello,

maybe I found some bug in deep-check --repair (Version 1.9.1).
What I see when repairing something on TestGrid is an exception like

-----------------
 repair successful
ERROR: AssertionError()
"[Failure instance: Traceback: <type 'exceptions.AssertionError'>: "
/usr/local/lib/allmydata-tahoe-1.9.1/src/allmydata/mutable/filenode.py:560:upload
/usr/local/lib/allmydata-tahoe-1.9.1/src/allmydata/mutable/filenode.py:658:_do_serialized
/usr/local/lib/allmydata-tahoe-1.9.1/support/lib/python2.6/site-packages/Twisted-10.1.0-py2.6-linux-x86_64.egg/twisted/internet/defer.py:260:addCallback
/usr/local/lib/allmydata-tahoe-1.9.1/support/lib/python2.6/site-packages/Twisted-10.1.0-py2.6-linux-x86_64.egg/twisted/internet/defer.py:249:addCallbacks
--- <exception caught here> ---
/usr/local/lib/allmydata-tahoe-1.9.1/support/lib/python2.6/site-packages/Twisted-10.1.0-py2.6-linux-x86_64.egg/twisted/internet/defer.py:441:_runCallbacks
/usr/local/lib/allmydata-tahoe-1.9.1/src/allmydata/mutable/filenode.py:658:<lambda>
/usr/local/lib/allmydata-tahoe-1.9.1/src/allmydata/mutable/filenode.py:686:_upload
/usr/local/lib/allmydata-tahoe-1.9.1/src/allmydata/mutable/publish.py:407:publish
--

----------------

If I hunt that by testing each individual subdirectory, it turns out
it's always an empty directory. When I put something into it,
e.g. an empty file with name "0", the repair succeeds without
problems.

Is it this?

Johannes