Opened at 2010-01-28T22:30:20Z
Closed at 2010-01-29T13:17:58Z
#931 closed enhancement (fixed)
show ?-IMM and ?-RO for immutable and read-only unknown nodes in directory listings
| Reported by: | davidsarah | Owned by: | davidsarah |
|---|---|---|---|
| Priority: | major | Milestone: | 1.6.0 |
| Component: | code-frontend-web | Version: | 1.5.0 |
| Keywords: | usability | Cc: | |
| Launchpad Bug: |
Description
In describing the fix for #833, Zooko said:
#833 also adds some very nice forward-compatibility features, so that when future versions of Tahoe-LAFS start uploading new kinds of capabilities, people using Tahoe-LAFS v1.6 will get a reasonable
indicator showing that there is something here that is immutable, but is from the future so you can't actually see it, instead of getting a traceback or some sort of behavior that violates the deep- immutability property.
However, #833 didn't actually change directory listings to show unknown caps as immutable (?-IMM) or read-only (?-RO). I have a patch to do that.
Attachments (1)
Change History (3)
Changed at 2010-01-28T22:31:14Z by davidsarah
comment:1 Changed at 2010-01-29T03:23:38Z by zooko
- Keywords review-needed removed
- Owner set to davidsarah
The ternary operator isn't available in Python 2.4 so we can't use it yet:
+ d.addCallback(_check_directory_html, "-IMM" if immutable else "-RO")
comment:2 Changed at 2010-01-29T13:17:58Z by zooko
- Resolution set to fixed
- Status changed from new to closed
fixed by 4560e021a9f9d311. Thank you!
Show -IMM and -RO suffixes for types of immutable and read-only unknown nodes in directory listings (with tests)