Handle CouchDB being down
Bug #397390 reported by
Stuart Langridge
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bindwood |
Fix Released
|
High
|
Zachery Bir | ||
Bug Description
At the moment we do not deal well with CouchDB not running. We blow up unpleasantly. Handle the situation where the detected port number doesn't actually have a couchdb there (for example, if you have no desktop couch and no system couch this will happen).
| tags: | added: story-0177 |
| tags: | added: desktop+ |
| Changed in bindwood: | |
| importance: | Undecided → High |
| milestone: | none → w19-karmic-alpha5 |
| status: | New → Triaged |
| assignee: | nobody → Zachery Bir (urbanape) |
| tags: | added: ubuntuone-karmic |
Revision history for this message
| Zachery Bir (urbanape) wrote | #1 |
| Changed in bindwood: | |
| status: | Triaged → Fix Committed |
| Changed in bindwood: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
In the new using-oauth branch, Bindwood silently does nothing when it can't find the proper CouchDB port (using dbus), and does *not* try to fall back on a system CouchDB port (5984).
I'll mark this as Fix Committed.