tahoe check reports incorrect encoding #1914

Open
opened 2013-02-05 20:17:26 +00:00 by PRabahy · 1 comment
PRabahy commented 2013-02-05 20:17:26 +00:00
Owner

It appears that if tahoe is unable to download any shares, it reports the incorrect encoding.

Steps to reproduce:

  1. Run "tahoe check public:"
    1a. ...good-shares: 1 (encoding is 1-of-1)...
  2. Disconnect from network
  3. Run "tahoe check public:" again
    3a. ...good-shares: 0 (encoding is 3-of-10)...

Expected result:
3a. ...good-shares: 0 (encoding is unknown)...

It appears that if tahoe is unable to download any shares, it reports the incorrect encoding. Steps to reproduce: 1. Run "tahoe check public:" 1a. ...good-shares: 1 (encoding is 1-of-1)... 2. Disconnect from network 3. Run "tahoe check public:" again 3a. ...good-shares: 0 (encoding is 3-of-10)... Expected result: 3a. ...good-shares: 0 (encoding is unknown)...
tahoe-lafs added the
unknown
normal
defect
1.9.2
labels 2013-02-05 20:17:26 +00:00
tahoe-lafs added this to the undecided milestone 2013-02-05 20:17:26 +00:00
davidsarah commented 2013-02-06 06:41:05 +00:00
Author
Owner

When checking using an immutable URI, the encoding is in the URI, so is known. In the case of a mutable URI, I agree that it should say "encoding is unknown".

When checking using an immutable URI, the encoding is in the URI, so is known. In the case of a mutable URI, I agree that it should say "encoding is unknown".
tahoe-lafs added
code-frontend-web
and removed
unknown
labels 2013-02-06 06:41:05 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 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#1914
No description provided.