1b79b4b in kimap makes connectionLost useful again, as the best way
to detect that we managed to connect (so the server actually exists and is
(or was) reachable) and then lost connection. Use that instead of the state change
to distinguish from the wrong hostname case (where we don't want to retry, we'd loop
forever doing that).
Details
Details
Expand existing unittest to test 3 different cases of connection lost,
all after the initial connect. The next method (shouldNotifyFailureToConnect)
ensures that the "wrong hostname" case still works.
Diff Detail
Diff Detail
- Repository
- R44 KDE PIM Runtime
- Branch
- Applications/18.04
- Lint
No Linters Available - Unit
No Unit Test Coverage