[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3793: allocate_buckets() should always list all shares in its response
Tahoe-LAFS
trac at tahoe-lafs.org
Wed Sep 29 17:54:02 UTC 2021
#3793: allocate_buckets() should always list all shares in its response
--------------------------+-----------------------------------
Reporter: itamarst | Owner: itamarst
Type: task | Status: new
Priority: normal | Milestone: HTTP Storage Protocol
Component: unknown | Version: n/a
Resolution: | Keywords:
Launchpad Bug: |
--------------------------+-----------------------------------
Changes (by itamarst):
* type: defect => task
Old description:
> Currently, if you allocate buckets twice with the same inputs, without
> writing to any buckets, the result is `(allocated = empty set(),
> writeable buckets = empty dict())`. This is wrong, each share number
> should always be one of the two categories.
New description:
Original issue: Currently, if you allocate buckets twice with the same
inputs, without writing to any buckets, the result is `(allocated = empty
set(), writeable buckets = empty dict())`. This is wrong, each share
number should always be one of the two categories.
Later decided the above is wrong. See below comment 4 for new plan for
these semantics.
--
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3793#comment:6>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list