-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
nsqd: update and fix for latest go-options #738
Conversation
Actually cleans this up a bunch, RFR @jehiah |
ClientTimeout: 60 * time.Second, | ||
|
||
MaxHeartbeatInterval: 60 * time.Second, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removing these presents a challenge for those importing nsqd
directly though right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thinking on this a little more I think it'd be better to preserve the defaults here in NewOptions()
and just change the order in main()
to get NewOptions()
first and pass that in to nsqFlagset()
, so that the defaults come from the nsqd
package, not apps/nsqd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good points, agreed, will update.
5e9f536
to
5c6990a
Compare
updated |
@mreiferson can you look into why CI isn't happy yet? (LGTM otherwise) |
let's see how this run does |
👍 LGTM. squash? |
5df8ec8
to
b4ae7dc
Compare
🔨d |
this is a replacement for #736, thanks @FlamingTree!