diff options
author | Joey Hess <joey@kitenet.net> | 2013-11-02 15:10:29 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2013-11-02 15:10:29 -0400 |
commit | 6c84eaf5a01046a0fa175d75e7027f686e00a6ee (patch) | |
tree | f17a9dbbe95514ec5b2950b954b2279fb1b4d349 /doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn | |
parent | 15b4cd87363a872d0d165fa1c02c48a8cb63cccf (diff) |
Improve local pairing behavior when two computers both try to start the pairing process separately.
I was able to reproduce something very like this bug by starting
pairing separately on both computers under poor network conditions (ie,
weak wifi on my front porch). Neither computer showed an alert for the
PairReq messages it was seeing (intermittently) from the other.
So, I've made a new PairReq message that has not been seen before
always make the alert pop up, even if the assistant thinks it is
in the middle of its own pairing process (or even another pairing
process with a different box on the LAN).
(This shouldn't cause a rogue PairAck to disrupt a pairing process part
way through.)
Diffstat (limited to 'doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn')
-rw-r--r-- | doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn index 1751429be..63f423e2c 100644 --- a/doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn +++ b/doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn @@ -23,3 +23,17 @@ I'm on Ubuntu Raring 13.04. I installed git-annex 4.20131024 from the Precise P ...and so on and so on... # End of transcript or log. """]] + +> I was able to reproduce something very like this by starting +> pairing separately on both computers under poor network conditions (ie, +> weak wifi on my front porch). +> +> So, I've made a new PairReq message that has not been seen before +> always make the alert pop up, even if the assistant thinks it is +> in the middle of its own pairing process (or even another pairing process +> with a different box on the LAN). +> +> (This shouldn't cause a rogue PairAck to disrupt a pairing process part +> way through.) +> +> [[done]] --[[Joey]] |