summaryrefslogtreecommitdiff
path: root/doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn')
-rw-r--r--doc/bugs/Local_pairing_fails:_received_PairMsg_loop.mdwn14
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]]