When both Foolscap and HTTP API are used on same StorageServer, there are some bad interactions

[itamarst]

Getting the following traceback, suggesting bad interaction in cleanup code (HTTP API is probably assuming only it can create buckets, or something):

  /home/itamarst/devel/tahoe-lafs/venv3/lib/python3.8/site-packages/twisted/internet/defer.py(662)_runCallbacks()
-> current.result = callback(current.result, *args, **kw)
  /home/itamarst/devel/tahoe-lafs/venv3/lib/python3.8/site-packages/foolscap/broker.py(584)<lambda>()
-> d.addCallback(lambda res: self._doCall(delivery))
  /home/itamarst/devel/tahoe-lafs/venv3/lib/python3.8/site-packages/foolscap/broker.py(619)_doCall()
-> return obj.doRemoteCall(delivery.methodname, args, kwargs)
  /home/itamarst/devel/tahoe-lafs/venv3/lib/python3.8/site-packages/foolscap/referenceable.py(61)doRemoteCall()
-> res = meth(*args, **kwargs)
  /home/itamarst/devel/tahoe-lafs/src/allmydata/storage/immutable.py(513)remote_abort()
-> return self._bucket_writer.abort()
  /home/itamarst/devel/tahoe-lafs/src/allmydata/storage/immutable.py(491)abort()
-> self.ss.bucket_writer_closed(self, 0)
  /home/itamarst/devel/tahoe-lafs/src/allmydata/storage/server.py(411)bucket_writer_closed()
-> handler(bw)
> /home/itamarst/devel/tahoe-lafs/src/allmydata/storage/http_server.py(191)remove_write_bucket()
-> storage_index, share_number = self._bucketwriters.pop(bucket)

[itamarst]

I believe this was fixed by ​https://github.com/tahoe-lafs/tahoe-lafs/pull/605

[itamarst]

Closed by ​https://github.com/tahoe-lafs/tahoe-lafs/pull/1220