Local filesystem should also distinguish not-content from empty
Bug #418232 reported by
Facundo Batista
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu One Client |
Fix Released
|
High
|
Facundo Batista |
Bug Description
Otherwise, the following happens:
1. A file is created in server
2. SD receives the ListDir, and creates an file with 0 bytes in disk
3. Somebody stops and starts SD again
4. SD founds a file in 0 in local disk, and with content in server, and thinks it's a conflict.
Related branches
lp:~facundo/ubuntuone-client/no-more-initial-empty-files
- Guillermo Gonzalez: Approve
- John O'Brien (community): Approve
-
Diff: 82 lines3 files modifiedubuntuone/syncdaemon/filesystem_manager.py (+0/-12)
ubuntuone/syncdaemon/local_rescan.py (+9/-2)
ubuntuone/syncdaemon/sync.py (+0/-7)
tags: | added: ubuntuone-karmic |
Changed in ubuntuone-client: | |
status: | Confirmed → In Progress |
Changed in ubuntuone-client: | |
status: | In Progress → Fix Committed |
Changed in ubuntuone-client: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
On Mon, Aug 24, 2009 at 05:04:34PM -0000, Facundo Batista wrote:
> Public bug reported:
>
> Otherwise, the following happens:
>
> 1. A file is created in server
>
> 2. SD receives the ListDir, and creates an file with 0 bytes in disk
>
> 3. Somebody stops and starts SD again
>
> 4. SD founds a file in 0 in local disk, and with content in server, and
> thinks it's a conflict.
that's why I love working with you guys. That, and the fact that I
don't have to code this particular fix myself :)