If we lose the connection during the login job, we need to
make sure that connectionLost is emitted by the pool so that ResourceTask
will call cancelTask. Otherwise the resource will be stuck forever...
Details
Details
Initially, playing with switching between WIFI networks at the right time (difficult).
Then, calling SessionPool::onConnectionLost() by hand from LoginJob (great idea from Sandro).
Now tested by the new unittest.
Diff Detail
Diff Detail
- Repository
- R44 KDE PIM Runtime
- Branch
- Applications/18.04
- Lint
No Linters Available - Unit
No Unit Test Coverage