Python API: Methods which discover that the connection was lost retry after restarting Zeitgeist, but fail
Bug #736176 reported by
Siegfried Gevatter
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zeitgeist Framework |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
From bug #727226: «Another outstanding problem is that, when a method fails and triggers the reconnect, it is run again straight away but it ends up failing another time. »
Related branches
| Changed in zeitgeist: | |
| importance: | Undecided → Low |
| Changed in zeitgeist: | |
| milestone: | none → 0.8.0 |
| Changed in zeitgeist: | |
| milestone: | 0.8.0 → 0.8.1 |
Revision history for this message
| Siegfried Gevatter (rainct) wrote | #1 |
| Changed in zeitgeist: | |
| importance: | Low → Medium |
| Changed in zeitgeist: | |
| status: | New → Fix Committed |
| Changed in zeitgeist: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
It also looks like we're missing signal reconnection.