Ticket #4907 (closed defect: fixed)

Opened 7 years ago

Last modified 7 years ago

PS doesn't try to reconnect Gabble if initial connect attempt failed

Reported by: gdesmott Owned by: robot101
Priority: normal Milestone: Update.1
Component: presence-service Version: Development source as of this date
Keywords: review+ Update.1? Cc: smcv, morgs
Action Needed: Verified: no
Deployments affected: Blocked By:


To reproduce: - edit your ~/.sugar/default/config and set an unexisting jabber server - Launch sugar. Gabble can't connect to its server - After 5 seconds, the timer is activated but start() won't try to reconnect because self._conn is not None


ps-reconnect.patch (1.0 kB) - added by gdesmott 7 years ago.

Change History

Changed 7 years ago by gdesmott

Changed 7 years ago by smcv

11:41 < smcv> cassidy: change the second part to "if not dbus_name and 
              self._conn is not None", otherwise +1
11:42 < smcv> cassidy: (with dbus_name we're testing for e.g. ":1.9" vs "", so 
              a truth test is what we want - but when comparing to None, always 
              use "is [not] None" because it's more efficient and is what you 
              actually mean)

However, the 5 second retry frequency is likely to flood the network, so this bug shouldn't be fixed until #2522 also is (fixing both of them in the same PS release would be ideal).

Changed 7 years ago by gdesmott

  • keywords review+ added

Changed 7 years ago by gdesmott

  • owner changed from smcv to ApprovalForUpdate
  • component changed from telepathy-gabble to presence-service

Now #2522 was fixed and approved for Update.1, what about this fix?

Changed 7 years ago by robot101

  • keywords Update.1? added
  • milestone changed from Never Assigned to Update.1

Changed 7 years ago by jg

  • owner changed from ApprovalForUpdate to gdesmott

Is this in Joyride? If not, please put it there and test it for update.1.

Once tested in Joyride, reassign to Approval for update.....

Changed 7 years ago by robot101

  • owner changed from gdesmott to ApprovalForUpdate

It's in Joyride since 0.27.20071114git128c59c612 and has been tested. That one release had four fixes in, for #4936, #4896, #2522 and this bug. It just needs tagging for Update.1.

Changed 7 years ago by jg

  • owner changed from ApprovalForUpdate to robot101

this is believed included in update.1 build 637, please verify that it is fixed and then close this bug.

Changed 7 years ago by gdesmott

  • status changed from new to closed
  • resolution set to fixed

Seems ok in update1-639

Note: See TracTickets for help on using tickets.