7e7e765cba
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.) |
||
---|---|---|
.. | ||
Committer.hs | ||
ConfigMonitor.hs | ||
Cronner.hs | ||
DaemonStatus.hs | ||
Glacier.hs | ||
Merger.hs | ||
MountWatcher.hs | ||
NetWatcher.hs | ||
PairListener.hs | ||
ProblemFixer.hs | ||
Pusher.hs | ||
SanityChecker.hs | ||
TransferPoller.hs | ||
Transferrer.hs | ||
TransferScanner.hs | ||
TransferWatcher.hs | ||
Watcher.hs | ||
WebApp.hs | ||
XMPPClient.hs | ||
XMPPPusher.hs |