Skip to content

NodeServices: Can't pipe result stream from chained success callback #1736

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
ajtowf opened this issue Sep 7, 2016 · 1 comment
Closed

Comments

@ajtowf
Copy link

ajtowf commented Sep 7, 2016

Can't seem to pipe to result stream from success callback:

module.exports = result => {
    foo().then(resp => resp.stream.pipe(result.stream);
}

Invoking the callback immediately like below works just fine.

module.exports = result => {
    foo().pipe(result.stream);
}

Works fine locally, when deployed to azure we get TaskCancellationException.

Example project to reproduce https://github.com/ajtowf/nodeservices/
Live example with full stacktrace https://nodeservices.azurewebsites.net/

Am I missing something obvious here?

@ajtowf
Copy link
Author

ajtowf commented Sep 7, 2016

Created issue in JavaScriptServices repo instead, aspnet/JavaScriptServices#298, closing this one.

@ajtowf ajtowf closed this as completed Sep 7, 2016
ryanbrandenburg pushed a commit that referenced this issue Nov 27, 2018
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant