Skip to content
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

crypto: remove use of this._readableState #610

Closed
wants to merge 1 commit into from

Conversation

calvinmetcalf
Copy link
Contributor

Per #445 this removes a reference to this._readableState in hash._flush. It was
used to get the encoding on the readable side to pass to the writable side but
omiting it just causes the stream to handle the encoding issues.

Per nodejs#445 this removes a reference to this._readableState in hash._flush. It was
used to get the encoding on the readable side to pass to the writable side but
omiting it just causes the stream to handle the encoding issues.
@chrisdickinson
Copy link
Contributor

LGTM; I'd like to run this by @indutny before it goes in, though!

@indutny
Copy link
Member

indutny commented Jan 26, 2015

LGTM, if it works!

@calvinmetcalf
Copy link
Contributor Author

yeah the LazyTransform one will be the tricky one crypto

@Fishrock123
Copy link
Contributor

Tests appear to pass.

vkurchatkin pushed a commit that referenced this pull request Jan 28, 2015
Per #445 this removes a reference to this._readableState in hash._flush. It was
used to get the encoding on the readable side to pass to the writable side but
omitting it just causes the stream to handle the encoding issues.

PR-URL: #610
Reviewed-By: Chris Dickinson <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Vladimir Kurchatkin <[email protected]>
@vkurchatkin
Copy link
Contributor

LGTM and landed in 90ddb46

@calvinmetcalf calvinmetcalf deleted the readablestate branch January 28, 2015 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants