| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Just wanted to note on here it looks like just a rebase, without addressing the review comments yet. I presume that will come in follow up commits? |
Sorry, something went wrong.
Yes, working on that now. |
Sorry, something went wrong.
|
@dougwilson I found all the comments I think needed to be fixed, except 2 perhaps that I'll work on tonight.
|
Sorry, something went wrong.
|
@dougwilson Is there anything more you see for this PR to have? |
Sorry, something went wrong.
|
I was under the impression you were going to make changes in regards to the two bullet points above, which is what I'm waiting on. I never saw any additional comments after that message. Are you still working on them? |
Sorry, something went wrong.
|
Eh! Sorry; I did leave the on('data') callback as is in the test, but I removed all the logs and I believe covered everything you had commented on in the previous test. For the second bullet point I quite literally have no clue off the top of my head how to even cover that in an edge case test. |
Sorry, something went wrong.
|
Seems like this one got stuck right? |
Sorry, something went wrong.
There was a problem hiding this comment.
Hi @Icehunter and @dougwilson,
IMHO, there are two issues covered by this PR.
I addressed the on('data') callback as mentioned in #128 (comment) and #170 (comment) with the following suggestions.
It now asserts that the data is correct.
Go to the Files tab and Add suggestion to batch so that it becomes a singular commit.
You might also want to correct the indentations within the function closeHttp2 at line 733.
I believe with this, all outstanding review comments in #128 are addressed and this PR should be ready and supersede #128.
Sorry, something went wrong.
|
@Icehunter, you might want to correct the indentations at line 740-744 and line 747-753. compression/test/compression.js Lines 737 to 756 in 38fe9fd |
Sorry, something went wrong.
|
@Icehunter, for the clarity that #129 is not in this PR, the description should change:
|
Sorry, something went wrong.
The change just removes the usage of undocumented http API and instead uses the proper writeHead method
… in node v10.4 onwards
Co-authored-by: Lam Wei Li <lam_wei_li@hotmail.com>
Updated and rebased again :) |
Sorry, something went wrong.
|
@dougwilson When you are free, can you review this PR? I didn't have access in the forked repository to run the GH actions. So I forked the PR. |
Sorry, something went wrong.
|
@dougwilson, have you got the time to take a look at this PR? |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
(can't approve cause I don't have explicit access to this repository)
😮💨
Sorry, something went wrong.
|
sorry @Icehunter, Can you fix the code style? |
Sorry, something went wrong.
Sure thing. |
Sorry, something went wrong.
|
Dropping some context from slack re: this PR
Idk that I can say that issue #122 "supporting http2" is closed after landing #170, because I personally haven't reviewed the code or tested for http2 edgecases. However, removing an http internal to replace w/ a public interface which is equivalent is 💯 It doesn't look like _implicitHeader implementation has changed much since Node v0.4.12: Here it is in v23: |
Sorry, something went wrong.
|
This history is long w/ 19 commits, @bjohansebas when/if you merge I'd suggest squashing via the dropdown to keep the history clean history.md isn't updated in this PR, we've talked about dropping that file (at least blake is planning to do so) but just a reminder in case you want to make sure you don't forget changelog update |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
updated PR with rebase from express/compress:master to handle #128