[tahoe-lafs-trac-stream] [tahoe-lafs] #1800: storage indices are sometimes logged as binary
tahoe-lafs
trac at tahoe-lafs.org
Thu Oct 31 16:02:46 UTC 2013
#1800: storage indices are sometimes logged as binary
------------------------------+--------------------------------------------
Reporter: davidsarah | Owner: zooko
Type: defect | Status: new
Priority: normal | Milestone: 1.11.0
Component: code-mutable | Version: 1.9.2
Resolution: | Keywords: logging mutable usability easy
Launchpad Bug: |
------------------------------+--------------------------------------------
Changes (by daira):
* milestone: soon => 1.11.0
Old description:
> In [ticket:1670#comment:19], there's an incident log that contains binary
> storage indices in the (human-readable) log message. They should be
> zbase32.
>
> The offending code starts at
> [source:src/allmydata/mutable/publish.py at 5585#L1129], but the bug is on
> line 1138 (it should be {{{base32.b2a(other_roothash)}}}).
New description:
In [ticket:1670#comment:19], there's an incident log that contains binary
storage indices in the (human-readable) log message. They should be
zbase32.
The offending code starts at
[source:src/allmydata/mutable/publish.py at 5585#L1129], but the bug is on
line 1138 (it should be {{{base32.b2a(other_roothash)}}}).
--
Comment:
Zooko already had a patch for this (see #1670).
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1800#comment:2>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list