default maximum-immutable-share-size is probably off-by-one #1781

Closed
opened 2012-06-23 23:39:18 +00:00 by davidsarah · 5 comments
davidsarah commented 2012-06-23 23:39:18 +00:00
Owner

At source:src/allmydata/storage_client.py#L181:

"maximum-immutable-share-size": 2**32,

I think this is the default used for old servers that didn't explicitly declare a maximum immutable share size, and that it should really be 2^32^ - 1.

At source:src/allmydata/storage_client.py#L181: ``` "maximum-immutable-share-size": 2**32, ``` I think this is the default used for old servers that didn't explicitly declare a maximum immutable share size, and that it should really be 2^32^ - 1.
tahoe-lafs added the
code
minor
defect
1.9.1
labels 2012-06-23 23:39:18 +00:00
tahoe-lafs added this to the 1.10.0 milestone 2012-06-23 23:39:18 +00:00

I agree. I'm going to change it after we release 1.10.

I agree. I'm going to change it after we release 1.10.
warner modified the milestone from 1.10.0 to 1.11.0 2013-03-21 00:12:53 +00:00
davidsarah commented 2013-03-23 02:41:28 +00:00
Author
Owner

If we agree this change is correct, it can't hurt to change it now, right? It seems to have very low regression risk.

If we agree this change is correct, it can't hurt to change it now, right? It seems to have very low regression risk.
davidsarah commented 2013-03-23 03:12:46 +00:00
Author
Owner
<https://github.com/davidsarah/tahoe-lafs/commit/1781-maximum-immutable-share-size> Does this need a test?
warner was assigned by tahoe-lafs 2013-03-23 03:13:50 +00:00
David-Sarah Hopwood <david-sarah@jacaranda.org> commented 2013-03-23 18:07:20 +00:00
Author
Owner

In changeset:68b7f9e979158dcb:

Correct off-by-one in maximum-immutable-share-size for old servers. fixes #1781

Signed-off-by: David-Sarah Hopwood <david-sarah@jacaranda.org>
In changeset:68b7f9e979158dcb: ``` Correct off-by-one in maximum-immutable-share-size for old servers. fixes #1781 Signed-off-by: David-Sarah Hopwood <david-sarah@jacaranda.org> ```
tahoe-lafs added the
fixed
label 2013-03-23 18:07:20 +00:00

nope, no test needed. I've landed it for 1.10. Thanks!

nope, no test needed. I've landed it for 1.10. Thanks!
warner modified the milestone from 1.11.0 to 1.10.0 2013-03-23 18:07:59 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1781
No description provided.