| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
'Calling transform done when still transforming' [](start = 27, length = 48)
don't need this anymore?
Sorry, something went wrong.
There was a problem hiding this comment.
@kunalspathak Thanks. It's done.
Sorry, something went wrong.
There was a problem hiding this comment.
[](start = 22, length = 1)
nit: can you move the space on above line?
Sorry, something went wrong.
There was a problem hiding this comment.
@kunalspathak Done.
Sorry, something went wrong.
There was a problem hiding this comment.
If I recall correctly, there are a couple of places in core with a similar error. A more generic error message may be appropriate.
Sorry, something went wrong.
There was a problem hiding this comment.
@jasnell Modified the error message to be more generic. Thanks
Sorry, something went wrong.
|
@sreepurnajasti - Changes incorporated from my feedback looks good although I kind of don't like ERR_CALLING_WS_LENGTH as the reader doesn't easily get the intent of the error message. I will leave it to @jasnell to comment on this. |
Sorry, something went wrong.
There was a problem hiding this comment.
I'd agree a better name for the error would be good. Maybe 'ERR_TRANSFORM_WITH_LENGTH_0'.
Sorry, something went wrong.
There was a problem hiding this comment.
@mhdawson Done
Sorry, something went wrong.
There was a problem hiding this comment.
Maybe to be consistent with my other suggestion:
'ERR_TRANSFORM_MULTIPLE_CALLBACK'.
Sorry, something went wrong.
There was a problem hiding this comment.
@mhdawson Fixed.
Sorry, something went wrong.
There was a problem hiding this comment.
Maybe to be consistent with my other suggestion:
'ERR_TRANSFORM_ALREADY_TRANSFORMING' String is already specific to transform so making that part of the ID makes sense to me.
Sorry, something went wrong.
There was a problem hiding this comment.
@mhdawson Done
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
CI good landing |
Sorry, something went wrong.
PR-URL: #13310 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
|
I'm strongly -1 on this one. This forces some good rework on readable-stream to pull those error data. May I ask for a revert? cc @nodejs/streams |
Sorry, something went wrong.
|
To be clear, this is something we should be doing asap, but we need to think a bit how we want to do it. |
Sorry, something went wrong.
|
:-/ ... reverting would be unfortunate. Perhaps instead, since this is semver-major and won't go out in a release any time soon, can we take a short bit of time to figure out the strategy for readable-stream? And if we can't identify a reasonable path forward, then revert... |
Sorry, something went wrong.
|
That's ok for me, there is no hurry to revert. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
lib/_stream_transform.js
ref: #11273