-
Notifications
You must be signed in to change notification settings - Fork 230
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
first run at 6.4.0 #225
first run at 6.4.0 #225
Conversation
90bf802
to
5ee4ca6
Compare
and a few tests that use encodings not all versions of node have, no actual changes to streams here so no rush |
5ee4ca6
to
613315e
Compare
ok the issue with the preprocessing test was basically it was relying on some specific tty stuff that was kinda tangential to streams specifically |
if others are on the same page about being able to ditch that preprocess test I can merge this |
@calvinmetcalf LGTM As a side note, that test is not targeting Can we avoid pulling it the next time? That test also relies on two As a side note, that test it was introduced by @vsemozhetbyt in nodejs/node#7741 and nodejs/node@ea725ed cc @addaleax |
oh right need to remove those |
we'd avoid pulling it in if it wasn't named 'stream' it's just a function of the fact that it was touching 3 diff modules and it had to pick one |
@calvinmetcalf we should move it then. |
I’m not sure what the process for pulling in tests is but if moving that one test in the node repo makes anything easier for anyone that shouldn’t be a problem? |
not a big deal any more, I just put something in the code that doesn't pull On Wed, Aug 31, 2016 at 3:11 PM Anna Henningsen notifications@github.com
|
this is a transient error, I'll plan on merging this latter if nobody objects |
and there is a new es6 feature being used in tests and a couple more fixtures!