Client side watchers may still be active when they report themselves as dead

Bug #1594663 reported by Menno Finlay-Smits
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Low
Unassigned

Bug Description

The client side watchers in api/watchers may still have goroutines running even when they have reported themselves as dead. This is because Done is called on the tomb without waiting for the goroutines started by commonWatcher.

This can be a source of subtle bugs and can make testing more difficult.

A possible solution would be to use catacombs and turn commonWatcher into a worker and each watcher type into workers with some interaction between them. The current approach of embedding commonWatcher into each watcher type and loosely sharing data and a tomb between them is quite messy at best.

description: updated
Changed in juju-core:
status: New → Triaged
Changed in juju-core:
milestone: none → 2.0.0
Changed in juju-core:
milestone: 2.0.0 → 2.0.1
affects: juju-core → juju
Changed in juju:
milestone: 2.0.1 → none
milestone: none → 2.0.1
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.0.1 → none
Revision history for this message
Anastasia (anastasia-macmood) wrote :

As this is a tech-debt item, I am lowering its Importance.

Changed in juju:
importance: High → Low
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.