Opened at 2015-07-16T17:02:49Z
Closed at 2016-01-21T17:13:26Z
#2469 closed defect (fixed)
Magic Folder: better error reporting if metadata in client DMD entries is not as expected
| Reported by: | daira | Owned by: | daira |
|---|---|---|---|
| Priority: | normal | Milestone: | undecided |
| Component: | code-frontend-magic-folder | Version: | 1.10.1 |
| Keywords: | magic-folder error | Cc: | |
| Launchpad Bug: |
Description
Change History (6)
comment:1 Changed at 2015-12-03T19:28:09Z by daira
- Keywords magic-folder added; otf-magic-folder-objective4 removed
comment:2 Changed at 2016-01-18T21:41:40Z by dawuud
comment:3 Changed at 2016-01-18T22:48:10Z by dawuud
ok i've added some logging for the cases when the remote file has no 'version' in the metadata. If the file objects were uploaded with the magic-folder client then they should always have a 'version'.
https://github.com/david415/tahoe-lafs/tree/2469.error-when-invalid-metadata.0
All the tests pass but I'm not sure this is the right way to implement this. Should I instead modify the Downloader's _process method?
review needed.
comment:4 Changed at 2016-01-21T15:28:13Z by daira
Reviewed.
comment:5 Changed at 2016-01-21T17:12:23Z by dawuud
pushed changes here: https://github.com/david415/tahoe-lafs/tree/2438.magic-folder-stable.9
comment:6 Changed at 2016-01-21T17:13:26Z by dawuud
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
In addition to detecting errors in the metadata should we also report an error in the Tahoe mutable directory contains subdirectories? This should never happen since the hierarchy is flattened.