-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Validate node version at runtime #12976
Labels
good first issue
low hanging fruit
release_note:enhancement
Team:Operations
Team label for Operations Team
Comments
I'm a beginner in contributing to kibana. I'm planning to work on this issue. Do you want an early failure or warning? |
mistic
added a commit
to mistic/kibana
that referenced
this issue
May 23, 2018
mistic
added a commit
to mistic/kibana
that referenced
this issue
May 23, 2018
…view Node version validator elastic#12976 pr review 2
mistic
added a commit
to mistic/kibana
that referenced
this issue
May 23, 2018
mistic
added a commit
to mistic/kibana
that referenced
this issue
May 24, 2018
mistic
added a commit
to mistic/kibana
that referenced
this issue
May 24, 2018
…view Node version validator elastic#12976 pr review 3
mistic
added a commit
to mistic/kibana
that referenced
this issue
May 24, 2018
…tic/kibana into node-version-validator-elastic#12976
@mistic, can we close this? |
Yes ofc @tylersmalley I forgot to do it. Closed! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
low hanging fruit
release_note:enhancement
Team:Operations
Team label for Operations Team
We get a decent number of issues filed relating to the wrong version of node running. At this time we make use of SSL constants that will cause issues in < 6, and there are some breaking changes in > 6 that will cause the process to fail. An early failure or warning would help with clearly identifying these errors.
The text was updated successfully, but these errors were encountered: