error verbosity: include filename in output, make traceback less prominent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
i've got a backup of a large samba share which every now and then fails, apparently because
of files being modified/truncated while duplicity is accessing them: duplicity
dies with a permission denied on reading (all fair and square).
the bug here is that the exception info is extremely verbose wrt. duplicity's calling stack but
completely lacks information useful to the user - like the name/path of the file that causes the
problem.
the information given with the default verbosity level should at least include the relevant information
(like the path here), and ideally not expose too much of the innards to an end user - the traceback
isn't useful unless you're a duplicity developer and might be restricted to higher verbosity levels.
here's the relevant output:
---
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Fri Oct 9 23:25:48 2009
Traceback (most recent call last):
File "/usr/bin/
with_
File "/usr/bin/
fn()
File "/usr/bin/
incremental
File "/usr/bin/
globals.
File "/usr/bin/
globals.
File "/usr/lib/
data = block_iter.
File "/usr/lib/
result = self.process(
File "/usr/lib/
data, last_block = self.get_
File "/usr/lib/
buf = fp.read(read_size)
File "/usr/lib/
buf = self.infile.
File "/usr/lib/
buf = self.infile.
IOError: [Errno 13] Permission denied
---
Changed in duplicity: | |
status: | New → Triaged |
importance: | Undecided → Medium |
importance: | Medium → Wishlist |
summary: |
- error verbosity: too much and still too little (useful info) + error verbosity: include filename in output, make traceback less + prominent |