| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| const fs = require('fs'); | ||
| http.createServer((request, response) => { | ||
| const raw = fs.createReadStream('index.html'); | ||
| // instruct the proxy to store both a compressed and uncompressed version of the resource |
There was a problem hiding this comment.
Hi, @mukulkhanna! Welcome and thanks for the pull request! This line above is (probably) going to cause the linter to complain. Could you wrap the comment at 80 characters and capitalize the first letter of the first word? (Might as well put a period/full-stop at the end while you're at it.)
Sorry, something went wrong.
There was a problem hiding this comment.
Oh, and you can check the linting with make lint (or vcbuild lint on Windows).
Sorry, something went wrong.
There was a problem hiding this comment.
Hi @Trott.
Sure, will do asap, thank you.
Sorry, something went wrong.
Sorry, something went wrong.
@Trott , |
Sorry, something went wrong.
Co-Authored-By: mukulkhanna <mukul18khanna@gmail.com>
Correct. CI is currently locked down while it is being used to prepare the security release that is scheduled to come out in the next several hours. |
Sorry, something went wrong.
|
Lite CI: https://ci.nodejs.org/job/node-test-pull-request-lite-pipeline/2709/ (Results should be reported in the GitHub widget below.) |
Sorry, something went wrong.
|
The 'first' commit message is failing the test. Is this the first commit of this pull request or is this about the most recent commit in the pull request. |
Sorry, something went wrong.
It's the first word of the last commit, but don't worry about it. Whoever lands this commit will need to squash the commits into one and modify the commit message to conform to our requirements anyway. The Travis stuff is advisory, but the other two checks from Jenkins are green and those are the ones that matter. |
Sorry, something went wrong.
Actually the Travis failure is the first commit: https://travis-ci.com/nodejs/node/jobs/180651661#L476-L486 *** Commit message for d510b68c0d is:
doc: added example for setting Vary: Accept-Encoding header in zlib.md
+npx -q core-validate-commit --no-validate-metadata d510b68c0d167d26964da3a8d3aa37df4ecb2866
✖ d510b68c0d167d26964da3a8d3aa37df4ecb2866
✔ 0:0 skipping fixes-url fixes-url
✔ 0:0 blank line after title line-after-title
✔ 0:0 line-lengths are valid line-length
✔ 0:0 valid subsystems subsystem
✖ 0:38 First word after subsystem(s) in title should be lowercase. title-format
⚠ 0:50 Title should be <= 50 columns. title-length
In this case core-validate-commit is incorrectly treating Accept-Encoding as a first word after subsystem(s) as it comes after a second :. I'll raise a PR to fix core-validate-commit. (Edit: nodejs/core-validate-commit#48) |
Sorry, something went wrong.
@richardlau Ooh, I didn't even consider that it's a bug. (And I'm the one that initially set up Travis to always lint the first commit and no other commit! You'd think I'd remember that. 😆) Nice catch! Sorry for the bad information! |
Sorry, something went wrong.
|
@Trott Can I close this pull request or should I wait for it to be merged ? |
Sorry, something went wrong.
Leave this pull request open. Thanks! |
Sorry, something went wrong.
FTR I've pushed out a fix to core-validate-commit and reran the failing the Travis job (which now passes 🎉). |
Sorry, something went wrong.
PR-URL: nodejs#26308 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
|
Landed in 86f13d6. Thanks for the contribution! 🎉 |
Sorry, something went wrong.
PR-URL: #26308 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
| Back | FazBrowse Home | New Git URL |
Resolving issue #25495.
Added example to set Vary: Accept-Encoding header with explanatory comment to doc/api/zlib.md
Checklist