Bug #20334: notification api promise was called incorrectly. - Foreman

Actions

Bug #20334

closed

notification api promise was called incorrectly.

Added by Ohad Levy over 7 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Notifications

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman/pull/4682

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

it seems notification api calls used a wrong promise syntax, which yield that the timer was never executed.

this was introduced in 13c542c2b626

Related issues 1 (0 open — 1 closed)

Actions

#1

Updated by Ohad Levy over 7 years ago

Related to Bug #20013: Notification polling duplicated on turbolinks navigation added

Actions

#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/4682 added

Actions

#3

Updated by Ohad Levy over 7 years ago

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

Applied in changeset be93e858253c54ea96908c10e779abc25f448ee0.

Actions

Also available in: Atom PDF