[
https://issues.apache.org/jira/browse/AMBARI-8604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-8604:
----------------------------------------
Attachment: AMBARI-8604.patch
> Alerts UI: Manage Alert-Groups dialog launched 2nd time has issues
> ------------------------------------------------------------------
>
> Key: AMBARI-8604
> URL: https://issues.apache.org/jira/browse/AMBARI-8604
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8604.patch
>
>
> Launching the _Manager Alert Groups_ dialog multiple times results in broken
> selection of alert-definitions. There are the following messages in the JS
> console when this happens.
> {code}
> DEPRECATION: Something you did caused a view to re-render after it rendered
> but before it was inserted into the DOM. Because this is avoidable and the
> cause of significant performance issues in applications, this behavior is
> deprecated. If you want to use the debugger to find out what caused this, you
> can set ENV.RAISE_ON_DEPRECATION to true.
> at Ember.View.states.inBuffer.rerender
> (http://c6401:8080/javascripts/vendor.js:15498:11)
> at Ember.View.Ember.Object.extend.invokeForState
> (http://c6401:8080/javascripts/vendor.js:14134:17)
> at Ember.View.Ember.Object.extend.rerender
> (http://c6401:8080/javascripts/vendor.js:14177:17)
> at Ember.View.states.inBuffer.$
> (http://c6401:8080/javascripts/vendor.js:15491:10)
> at Ember.View.Ember.Object.extend.invokeForState
> (http://c6401:8080/javascripts/vendor.js:14134:17)
> at Ember.View.Ember.Object.extend.$
> (http://c6401:8080/javascripts/vendor.js:14353:17)
> at observer (http://c6401:8080/javascripts/vendor.js:20304:23)
> at invoke (http://c6401:8080/javascripts/vendor.js:5036:19)
> at Object.invokeOnceTimer
> (http://c6401:8080/javascripts/vendor.js:5463:23)
> vendor.js:1769 DEPRECATION: Something you did caused a view to re-render
> after it rendered but before it was inserted into the DOM. Because this is
> avoidable and the cause of significant performance issues in applications,
> this behavior is deprecated. If you want to use the debugger to find out what
> caused this, you can set ENV.RAISE_ON_DEPRECATION to true.
> at Ember.View.states.inBuffer.rerender
> (http://c6401:8080/javascripts/vendor.js:15498:11)
> at Ember.View.Ember.Object.extend.invokeForState
> (http://c6401:8080/javascripts/vendor.js:14134:17)
> at Ember.View.Ember.Object.extend.rerender
> (http://c6401:8080/javascripts/vendor.js:14177:17)
> at Ember.View.states.inBuffer.$
> (http://c6401:8080/javascripts/vendor.js:15491:10)
> at Ember.View.Ember.Object.extend.invokeForState
> (http://c6401:8080/javascripts/vendor.js:14134:17)
> at Ember.View.Ember.Object.extend.$
> (http://c6401:8080/javascripts/vendor.js:14353:17)
> at observer (http://c6401:8080/javascripts/vendor.js:20421:85)
> at invoke (http://c6401:8080/javascripts/vendor.js:5036:19)
> at Object.invokeOnceTimer
> (http://c6401:8080/javascripts/vendor.js:5463:23)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
