[
https://issues.apache.org/jira/browse/STORM-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042551#comment-14042551
]
ASF GitHub Bot commented on STORM-370:
--------------------------------------
GitHub user kishorvpatil opened a pull request:
https://github.com/apache/incubator-storm/pull/160
[STORM-370] Add check for empty table before sorting dom in UI
To avoid ```tablesorter``` from throwing exception - requires additional
check to ensure that table sorter is not invoked on empty recordset.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kishorvpatil/incubator-storm
fix-blank-ui-comps
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-storm/pull/160.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #160
----
commit 31c786c6634052d89ca62c57c428d95124a3a465
Author: Kishor Patil <[email protected]>
Date: 2014-06-24T18:51:01Z
Add check for empty table before sorting
----
> Component page UI details are blank
> -----------------------------------
>
> Key: STORM-370
> URL: https://issues.apache.org/jira/browse/STORM-370
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Affects Versions: 0.9.2-incubating
> Reporter: Kishor Patil
> Labels: master, security
>
> Symptom: On component page - most of the details are blank. If the component
> json response has some of list elements empty ( e.g. boltStats, executors
> or spoutStats, outputStats inputStats).
> In such situation, I noticed earlier the component page call to js
> tablesorter throws exception ( - wherever table has 0 rows). This
> exception stops further rendering of elements.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
