Merge lp:~mterry/duplicity/pydrive-cache-fix into lp:~duplicity-team/duplicity/0.8-series
Proposed by
Michael Terry
Status: | Merged |
---|---|
Merged at revision: | 1502 |
Proposed branch: | lp:~mterry/duplicity/pydrive-cache-fix |
Merge into: | lp:~duplicity-team/duplicity/0.8-series |
Diff against target: |
24 lines (+4/-3) 1 file modified
duplicity/backends/pydrivebackend.py (+4/-3) |
To merge this branch: | bzr merge lp:~mterry/duplicity/pydrive-cache-fix |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
duplicity-team | Pending | ||
Review via email: mp+375465@code.launchpad.net |
Description of the change
The pydrive backend had another of the ongoing bytes/string issues. :)
This time, it was saving a bytes filename in its internal cache after each volume upload. Then when asked for a list of files later, it would add the byte-filenames from its cache to the results. And we'd end up thinking there were two of the same filename on the backend, which would cause a crash at the end of an otherwise successful backup, because the collections code would assert on the filenames being unique.
To post a comment you must log in.