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

Keep correct transaction when calling Bluebird promise.nodeify nodeback #233

Closed

Conversation

mdlavin
Copy link
Contributor

@mdlavin mdlavin commented Nov 23, 2016

When using Bluebird's promise.nodeify the current transaction is lost. The same support for asCallback should also be provied to nodeify since they are aliases of each other.

@mdlavin
Copy link
Contributor Author

mdlavin commented Nov 28, 2016

I don't think the build failures were introduced by my change, but let me know if there is something I need to change.

@lykkin
Copy link
Contributor

lykkin commented Nov 29, 2016

@mdlavin Thanks for the pr! No need to worry about the tests, the failures are due to environmental differences and we are going to fix those up shortly. The changes look good, we'll include this in the next release!

@lykkin
Copy link
Contributor

lykkin commented Dec 12, 2016

this pr was merged out of band in v1.35.0, thanks again for the pr, @mdlavin !

@lykkin lykkin closed this Dec 12, 2016
bizob2828 added a commit to bizob2828/node-newrelic that referenced this pull request Apr 19, 2024
Co-authored-by: Bob Evans <robert.evans25@gmail.com>
bizob2828 added a commit to bizob2828/node-newrelic that referenced this pull request Apr 23, 2024
Co-authored-by: Bob Evans <robert.evans25@gmail.com>
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.

2 participants