platform filesystem monitor code does not log which monitor it used
Bug #1042336 reported by
Mike McCracken
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Ubuntu One Client | Status tracked in Trunk | |||||
| Stable-4-0 |
Fix Released
|
Undecided
|
Unassigned | |||
| Trunk |
Fix Released
|
High
|
Manuel de la Peña | |||
Bug Description
There are two fs monitor implementations in syncdaemon on darwin, and there is no easy way to tell which monitors are available, whether or not a connection was attempted to the root daemon, if there were any errors, and which monitor implementation was finally chosen.
Let's add a lot of logging - it happens rarely and it'll be hard to debug otherwise.
Related branches
lp:~mandel/ubuntuone-client/fs-darwin-logging
- Mike McCracken (community): Disapprove
-
Diff: 53 lines (+11/-1)1 file modifiedubuntuone/platform/filesystem_notifications/monitor/__init__.py (+11/-1)
lp:~mikemc/ubuntuone-client/log-monitor
- Roberto Alsina (community): Approve
-
Diff: 52 lines (+13/-3)1 file modifiedubuntuone/platform/filesystem_notifications/monitor/__init__.py (+13/-3)
| Changed in ubuntuone-client: | |
| status: | Confirmed → Fix Committed |
To post a comment you must log in.
