[ 
https://issues.apache.org/jira/browse/NIFI-11560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17725935#comment-17725935
 ] 

Matt Gilman commented on NIFI-11560:
------------------------------------

Thanks for reporting. I just reproduced the issue. The relevant stack trace is:
{noformat}
nf-settings.js?2.0.0-SNAPSHOT:3074 Uncaught TypeError: 
reportingTaskBulletinsBySource.each is not a function
    at Object.setBulletins (nf-settings.js?2.0.0-SNAPSHOT:3074:48)
    at Object.update 
(nf-ng-canvas-flow-status-controller.js?2.0.0-SNAPSHOT:457:32)
    at FlowStatusCtrl.updateBulletins 
(nf-ng-canvas-flow-status-controller.js?2.0.0-SNAPSHOT:686:32)
    at Object.<anonymous> (nf-canvas.js?2.0.0-SNAPSHOT:327:63)
    at c (jquery.min.js:2:28447)
    at Object.fireWith [as resolveWith] (jquery.min.js:2:29192)
    at l (jquery.min.js:2:80176)
    at XMLHttpRequest.<anonymous> (jquery.min.js:2:82630){noformat}

> Bulletin causes UI to think it cannot refresh
> ---------------------------------------------
>
>                 Key: NIFI-11560
>                 URL: https://issues.apache.org/jira/browse/NIFI-11560
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Michael W Moser
>            Priority: Major
>
> This is a weird one, but here goes.
> Configure a MonitorDiskThreshold reporting task to monitor any disk with a 1% 
> threshold.  Start the reporting task and let the warning bulletin appear.  
> Refresh the Reporting Tasks table and the spinning refresh wheel at the 
> bottom never goes away.  You can stop the reporting task, but the UI doesn't 
> show that it stopped.  If you return the the canvas, its spinning refresh 
> wheel spins but you can do some canvas operations. If you use the browser 
> reload button, the large spinning wheel page does not go away and you cannot 
> see the canvas.  If you wait 5 minutes for the bulletin to disappear and use 
> the browser reload button again, then the NiFi canvas appears and all is good.
> I don't feel like this is a MonitorDiskThreshold problem, it's got to be 
> something else, but this reporting task was the easiest way to replicate this.
> I replicated this on the 2.0.0-SNAPSHOT main branch and on the 
> 1.22.0-SNAPSHOT support branch.  It does not happen in release 1.21.0, though.
> I was using Chrome 113.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to