Skip to content
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

nsqadmin: display errors #421

Merged
merged 12 commits into from
Sep 17, 2015
Merged

Conversation

mreiferson
Copy link
Member

nsqadmin doesn't display when it's unable to query all the appropriate hosts to return stats. It should list them as errors at the top of the page.

(it can be missleading when the query to one host timesout but you don't realize it)

@mreiferson
Copy link
Member

work in progress:

screen shot 2015-08-29 at 2 57 54 pm

@mreiferson mreiferson force-pushed the nsqadmin_errors_421 branch from a7b6c0e to a0c34e9 Compare August 31, 2015 05:50
@jehiah
Copy link
Member Author

jehiah commented Aug 31, 2015

@mreiferson this approach looks good

@mreiferson mreiferson force-pushed the nsqadmin_errors_421 branch 4 times, most recently from 70d956b to 55a1597 Compare September 7, 2015 16:16
@mreiferson
Copy link
Member

@rolyatmax would you mind taking a look at the JS error handling approaches here? ❤️

@mreiferson
Copy link
Member

@jehiah want to give this a spin?

@@ -2,7 +2,7 @@ var Backbone = require('backbone');

var AppState = require('../app_state');

var Node = require('../models/node');
var Node = require('../models/node'); //eslint-disable-line no-undef

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should add:

  "globals": {
    "module": true,
    "require": true
  }

to your .eslintrc.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it because Node is a restricted keyword?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a restricted keyword.

Nodejs is a holy word - maybe that's what you're thinking of?

@mreiferson
Copy link
Member

updated @rolyatmax

@rolyatmax
Copy link

Updates look good to me. Have you tried producing all these error states? 😬

@mreiferson
Copy link
Member

most of them 👊

@rolyatmax
Copy link

Sweeeeet - I'll leave the Go review for a GoPro.

@mreiferson
Copy link
Member

@jehiah tested this a bunch against a real cluster - used https://github.com/apenwarr/sshuttle/ which is pretty amazing

@mreiferson mreiferson force-pushed the nsqadmin_errors_421 branch 3 times, most recently from f89e3c5 to 8b05ee1 Compare September 12, 2015 19:07
@mreiferson
Copy link
Member

OK, I think this is RFR @jehiah

@@ -13,7 +14,7 @@
<div id="container"></div>

<script type="text/javascript">
var USER_AGENT = 'nsqadmin';
var USER_AGENT = 'nsqadmin v{{.Version}}';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nsqadmin/{{.Version}} to follow rfc7231 section 5.5.3

@jehiah
Copy link
Member Author

jehiah commented Sep 17, 2015

LGTM aside from my nitpick. (sorry for the delay in review; i was offline for a few days)

@mreiferson
Copy link
Member

no worries, fixed and squashed in (remembered to update bin dater too this time)

RFM

jehiah added a commit that referenced this pull request Sep 17, 2015
@jehiah jehiah merged commit 885b06f into nsqio:master Sep 17, 2015
@mreiferson mreiferson deleted the nsqadmin_errors_421 branch September 17, 2015 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants