-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't click to page 2 on reports #38
Comments
Same problem here. |
I think I'll be able to take a look at this during the weekend. Planning on doing some development then. |
Same problem |
1 similar comment
Same problem |
Same problem, UI throws ["select_nodes" ["=" "latest_report_status" "failed"]] is not well-formed: query operator 'select_nodes' is unknown - related? |
I'm also experiencing problems with 'select_nodes'. When clicking on a specific report for a node, I always get the error message:
and the rightmost pie chart (event status) remains empty . |
Any traction on this? Hell, i'd accept "Just ReWrite the query to replace the select_nodes clause with XXXXXXXXX" |
We're having the same problem. Any news? |
Faced the same problem. |
+1 |
I'm still getting it. I am wondering if the culprit is in the node-puppetdbquery project: Tried to change the dep version and rebuild the app, but i can't get grunt to successfully build puppetexplorer. |
I'm also experiencing this issue, are there plans to address this? Thanks! |
Run this in your Developer Tools > Console, and it'll work to at least view 1000 events on the first page.
|
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.
The text was updated successfully, but these errors were encountered: