Stream WG meeting - September 2017

[mcollina]

Hi Folks

Given our bimonthly meetings, it's time we start planning when we want to run the next streams-wg meeting :).

Agenda:

• Status of on the use of _readableState and _writableState in core [stream] Make _readableState and _writableState part of the public API node#7629.
• Schedule for bumping the major bumping the major #284
• Automatic string decoding for writable streams Feature request: automatic string decoding for writable streams node#7315
• stream.end(chunk, enc, cb) should always call the callback Writeable stream .end() has paradoxical logic node#5540
• Support the new error system from core support the new error system from core #297

Here is a doodle: https://doodle.com/poll/ydqhpfc3tksiqr4t

The meeting will take place over hangouts (links to follow) on Tuesday 12th of September at 16:00 GMT.

London time: 17:00
Paris time: 18:00
Portland time: 9:00

-- I hope the times are right. Please check.

Watch at: http://youtu.be/pzHK1iJVGic

cc @jessicaquynh @jasnell.

[yoshuawuyts]

@mcollina replied! - could you ping people once a date has been decided? Thanks!

Also cc/ @nodejs/streams

[lrlna]

@mcollina, filled out!

…

On Sat, 26 Aug 2017 at 21:58 Yoshua Wuyts ***@***.***> wrote: @mcollina <https://github.com/mcollina> replied! - could you ping people once a date has been decided? Thanks! Also cc/ @nodejs/streams <https://github.com/orgs/nodejs/teams/streams> — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#309 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHu3CLwQUVo5Gp4vk61tG7aTdkWzITaFks5scHjdgaJpZM4PDiIA> .

[mcollina]

Based on the doodle responses, the meeting will take place Tuesday 12th of September at 16:00 GMT.

I can send a calendar invite, and will ping again one or two days prior to the meeting!

[lrlna]

cool, thanks Matteo!

…

On Sat, 2 Sep 2017 at 09:32 Matteo Collina ***@***.***> wrote: Based on the doodle responses, the meeting will take place Tuesday 12th of September at 16:00 GMT. I can send a calendar invite, and will ping again one or two days prior to the meeting! — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#309 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHu3CNgxcaosFzDFmDYV7burxfKgXm-mks5seQSlgaJpZM4PDiIA> .

[mcollina]

Join link: https://hangouts.google.com/hangouts/_/qbw2a6usmvhrjgoylyjk2mdso4e

[mcollina]

cc @jessicaquynh?

[sonewman]

can i join?

[mcollina]

@sonewman yes!!!! Come in!

[mcollina]

PR to add the Error: nodejs/node#15042

[sonewman]

@mcollina sorry I didn't have so much to contribute, I will have to spend sometime familiarising myself with the code again before the next meeting!

[mcollina]

Here are my notes (feel free to edit)

Status of on the use of _readableState and _writableState in core

Hoping for a vote in the next TSC. For us it does not matter, it was requested by core.

Bumping the major

• we need to handle the new Error codes as semver-major?
• we will take our time if needed

Errors - #297

• custom error types are very hard to do in browsers, we cannot do them (Calvin, Yosh, Irina)
• codes we can do
• We can replace new error.Error(code) with buildError(code) and we would need to ship our messages bundled.
• We can then decide if it's semver-major or not (depends if we change the error messages).

Automatic string decoding for writable streams nodejs/node#7315

See our response in: nodejs/node#7315 (comment)

stream.end(chunk, enc, cb) should always call the callback nodejs/node#5540

See our response in: nodejs/node#5540 (comment)

[mcollina]

@sonewman no worries! Thanks for joining!