blackmatch fuse doesn't know what to think about immutable directories

[zooko]

As reported by François over on comment:5:ticket:830:

Sat Jan  9 22:25:05 2010: exception:
Traceback (most recent call last):
  File "/home/francois/WORK/dev/tahoe/contrib/fuse/impl_c/blackmatch.py", line 177, in inner_logexc
    ret = meth(self, *args, **kwargs)
  File "/home/francois/WORK/dev/tahoe/contrib/fuse/impl_c/blackmatch.py", line 314, in done
    precondition(not self.read_heap, self.read_heap, self.target_size, self.get_size())
  File "/usr/local/lib/python2.6/dist-packages/allmydata_tahoe-1.5.0_r4054-py2.6.egg/allmydata/util/assertutil.py", line 46, in precondition
    raise AssertionError, "".join(msgbuf)
AssertionError: precondition: [(3832, 0, <Deferred at 0x3c94440>)] <type 'list'>, 264 <type 'int'>, 264 <type 'int'>

[warner]

this log fragment isn't very enlightening.. basically all it says is that it wasn't done reading when it should be been done. I see a lot of logging calls in the blackmatch code.. is there perhaps a real Failure logged anywhere? Maybe syslog or something?

Immutable directories have almost exactly the same API as mutable directories, but the blackmatch code has not been updated in forever, so I suspect that there's enough bitrot for the minor differences to cause a problem. I'd suspect something in its use of DirectoryURI: new code should be using less of that and more of client.create_node_from_uri.

[zooko]

We're not going to finish this for v1.6.1, but hopefully for v1.7.0!

[zooko]

I don't want to touch the fuse code until we have the fuse tests being automatically run by a CI (buildbot) server. So this ticket is blocked on #621 "Incorporate fuse tests into buildbot flow"

[exarkun]

This FUSE implementation has been removed (#1409).