ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-22527) Error while viewing topology details - Storm View
Date Tue, 28 Nov 2017 10:50:00 GMT


Hadoop QA commented on AMBARI-22527:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in contrib/views/storm.

Console output:

This message is automatically generated.

> Error while viewing topology details - Storm View
> -------------------------------------------------
>                 Key: AMBARI-22527
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.6.1
>         Environment: ambari-server --version
>            Reporter: Sanket Shah
>            Assignee: Sanket Shah
>            Priority: Blocker
>             Fix For: 2.6.1
>         Attachments: AMBARI-22527.patch
> {noformat}
> Uncaught Error: Minified React error #130; visit[]=object&args[]=%20Check%20the%20render%20method%20of%20%60e%60.
for the full message or use the non-minified dev environment for full errors and additional
helpful warnings.
>     at n (vendor.bundle.js:4)
>     at a (vendor.bundle.js:6)
>     at Object.updateChildren (vendor.bundle.js:2)
>     at v._reconcilerUpdateChildren (vendor.bundle.js:3)
>     at v._updateChildren (vendor.bundle.js:3)
>     at v.updateChildren (vendor.bundle.js:3)
>     at v._updateDOMChildren (vendor.bundle.js:2)
>     at v.updateComponent (vendor.bundle.js:2)
>     at v.receiveComponent (vendor.bundle.js:2)
>     at Object.receiveComponent (vendor.bundle.js:2)
> {noformat}
> On the latest build, due to few npm packages being updated dynamically, Storm view is
running into above mentioned error.

This message was sent by Atlassian JIRA

View raw message