Merge lp:~cmiller/desktopcouch/remote-oauth-for-replication into lp:desktopcouch
Proposed by
Chad Miller
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Stuart Langridge | ||||
Approved revision: | 77 | ||||
Merged at revision: | not available | ||||
Proposed branch: | lp:~cmiller/desktopcouch/remote-oauth-for-replication | ||||
Merge into: | lp:desktopcouch | ||||
Diff against target: |
120 lines 4 files modified
desktopcouch/pair/couchdb_pairing/couchdb_io.py (+7/-6) desktopcouch/pair/couchdb_pairing/dbus_io.py (+7/-1) desktopcouch/records/server_base.py (+0/-2) desktopcouch/replication.py (+11/-4) |
||||
To merge this branch: | bzr merge lp:~cmiller/desktopcouch/remote-oauth-for-replication | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Stuart Langridge (community) | Approve | ||
Eric Casteleijn (community) | Approve | ||
Ubuntu One hackers | Pending | ||
Review via email: mp+12672@code.launchpad.net |
Commit message
Use the oauth tokens we stored at pairing time to talk to the remote end.
(LP: #439412)
Retreive oauth information from pairing records and give it back in the info
about pairings.
Log exceptions in replication and catch them, instead of letting them percolate
up to the caller.
To post a comment you must log in.
I don't understand why this:
101 + try: exception( "failed to unpair from other end.")
102 + raise last_exception
103 + except:
104 + logging.
105 + continue
Why raise an exception and then immediately catch it again?