Bug #20013

Notification polling duplicated on turbolinks navigation

Added by matan werbner 11 months ago. Updated 7 months ago.

Status:Closed
Priority:Normal
Assigned To:matan werbner
Category:Notifications
Target version:-
Difficulty: Bugzilla link:
Found in release: Pull request:https://github.com/theforeman/foreman/pull/4588
Story points-
Velocity based estimate-
Release1.16.0Release relationshipAuto

Description

since notification component is re-mounted, polling is re-initialised whenever turbolinks navigation occurs.


Related issues

Related to Foreman - Bug #20334: notification api promise was called incorrectly. Closed 07/18/2017

Associated revisions

Revision 13c542c2
Added by matan werbner 10 months ago

Fixes #20013 - Notification singleton polling

History

#1 Updated by Ohad Levy 11 months ago

does this effect other components such as toast notifications? or maybe even host power ?

#2 Updated by The Foreman Bot 11 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4588 added

#3 Updated by Ohad Levy 10 months ago

  • Release set to 1.16.0

#4 Updated by matan werbner 10 months ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#5 Updated by Ohad Levy 9 months ago

  • Related to Bug #20334: notification api promise was called incorrectly. added

#6 Updated by Daniel Lobato Garcia 7 months ago

  • Category set to Notifications

Also available in: Atom PDF