Project

General

Profile

Actions
Copy link

Bug #20013

closed

Notification polling duplicated on turbolinks navigation

Added by matan werbner over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
matan werbner
Category:
Notifications
Target version:
1.16.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/4588
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

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

Related issues 2 (0 open — 2 closed)

Related to Foreman - Bug #20334: notification api promise was called incorrectly.ClosedOhad Levy07/18/2017Actions
Is duplicate of Foreman - Bug #18327: Notification polling request should not be initiated if there is an open turbolinks operationDuplicateGail Steiger01/31/2017Actions
Actions
Copy link
 #1

Updated by Ohad Levy over 7 years ago

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

Actions
Copy link
 #2

Updated by The Foreman Bot over 7 years ago

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

Updated by Ohad Levy over 7 years ago

  • Translation missing: en.field_release set to 240
Actions
Copy link
 #4

Updated by matan werbner over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Ohad Levy over 7 years ago

  • Related to Bug #20334: notification api promise was called incorrectly. added
Actions
Copy link
 #6

Updated by Daniel Lobato Garcia over 7 years ago

  • Category set to Notifications
Actions
Copy link
 #7

Updated by Ohad Levy over 6 years ago

  • Is duplicate of Bug #18327: Notification polling request should not be initiated if there is an open turbolinks operation added
Actions
Copy link

Also available in: Atom PDF