-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Backport 12162 to 6.x #12504
Backport 12162 to 6.x #12504
Conversation
Well that's too bad. I thought I ran the linter to make sure it was working. Guess I did not. |
35ccdd7
to
fcc759f
Compare
OK, fixed. At least the lint rules are fixed anyway. Sorry about that. |
Cool. Trying CI one more time.. https://ci.nodejs.org/job/node-test-pull-request/7541/ |
Is the FreeBSD test-net-write-after-close failure a known flaky on the v6.x branch? Seems unrelated to this... |
@Trott it isn't flaky AFAIK... will run tests again on release branch to check |
404d1bc
to
99dab5b
Compare
Only CI failure is build/infra related. |
PR-URL: nodejs#12162 Reviewed-By: Teddy Katz <teddy.katz@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
ESLint 3.19.0 allows the specification of selectors that represent disallowed syntax. Replace our custom rule for timer arguments with a pair of `no-restricted-syntax` option objects.
fcc759f
to
d533e92
Compare
CI again post-rebase: https://ci.nodejs.org/job/node-test-pull-request/7679/ |
CI looks good. Just the usual clang bot failure on v6.x. (At least, I think it's the usual. Regardless, it's build-related, not related to this change.) |
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.
LGTM
ESLint 3.19.0 allows the specification of selectors that represent disallowed syntax. Replace our custom rule for timer arguments with a pair of `no-restricted-syntax` option objects. PR-URL: #12504 Reviewed-By: Myles Borins <myles.borins@gmail.com>
landed in 9218661...cf26d15 |
ESLint 3.19.0 allows the specification of selectors that represent disallowed syntax. Replace our custom rule for timer arguments with a pair of `no-restricted-syntax` option objects. PR-URL: #12504 Reviewed-By: Myles Borins <myles.borins@gmail.com>
Backport-PR-URL: nodejs/node#12504 PR-URL: nodejs/node#12162 Reviewed-By: Teddy Katz <teddy.katz@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
ESLint 3.19.0 allows the specification of selectors that represent disallowed syntax. Replace our custom rule for timer arguments with a pair of `no-restricted-syntax` option objects. PR-URL: nodejs/node#12504 Reviewed-By: Myles Borins <myles.borins@gmail.com>
backport of #12162 to 6.x
@MylesBorins