puppetexplorer icon indicating copy to clipboard operation
puppetexplorer copied to clipboard

Can't click to page 2 on reports

Open kspears opened this issue 10 years ago • 13 comments

I was trying to view additional pages of a long puppet report and when I click the next button (or one of the number buttons) I see the page load the new data into the table and then it reloads the data from page one. Watching the network XFR in chrome I see it load the page and then immediately loads page one: events?include_total=true&limit=50&offset=50&order_by= events?include_total=true&limit=50&offset=0&order_by=

Also not sure if it's related but I see a bunch of canceled XHR when I first load up the reports page. I've attached some screenshots showing the behavior I'm seeing.

This is a new puppet install, running puppetdb 3.1.

canceled_events dual_calls

kspears avatar Oct 13 '15 21:10 kspears

Same problem here.

clabu avatar Nov 02 '15 14:11 clabu

I think I'll be able to take a look at this during the weekend. Planning on doing some development then.

dalen avatar Nov 04 '15 15:11 dalen

Same problem

roidelapluie avatar Mar 01 '16 09:03 roidelapluie

Same problem

kirillk77 avatar Mar 01 '16 17:03 kirillk77

Same problem, UI throws ["select_nodes" ["=" "latest_report_status" "failed"]] is not well-formed: query operator 'select_nodes' is unknown - related?

greigm avatar Jul 27 '16 19:07 greigm

I'm also experiencing problems with 'select_nodes'. When clicking on a specific report for a node, I always get the error message:

["select_nodes" ["=" "catalog_environment" "production"]] is not well-formed: query operator 'select_nodes' is unknown

and the rightmost pie chart (event status) remains empty .

reuterbal avatar Oct 07 '16 12:10 reuterbal

Any traction on this? Hell, i'd accept "Just ReWrite the query to replace the select_nodes clause with XXXXXXXXX"

vml-loshea avatar Oct 10 '16 13:10 vml-loshea

We're having the same problem. Any news?

pegasd avatar Dec 20 '16 08:12 pegasd

Faced the same problem.

lestex avatar Jan 17 '17 15:01 lestex

+1 Might be no longer giving this error as soon as events are available

Wesseldr avatar Feb 14 '17 01:02 Wesseldr

I'm still getting it. I am wondering if the culprit is in the node-puppetdbquery project: https://github.com/dalen/node-puppetdbquery/blob/73a6acc605678b94829bcb6a9ccf7b83d91aec01/lib/evaluator.js#L90

Tried to change the dep version and rebuild the app, but i can't get grunt to successfully build puppetexplorer.

Loshea avatar Apr 21 '17 13:04 Loshea

I'm also experiencing this issue, are there plans to address this? Or are we waiting for a release from the react branch?

Thanks!

cargiris avatar Aug 03 '17 16:08 cargiris

Run this in your Developer Tools > Console, and it'll work to at least view 1000 events on the first page.

var Scope = angular.element($("div.ng-scope")).scope(); Scope.perPage = 1000; Scope.changePage(1);

dddomin3 avatar Aug 03 '17 16:08 dddomin3