You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user accidentally passes a non-Promise-returning function (or a function that throws a synchronous exception) to .use, .use will throw an exception and never release its resource.
One way this came up for me was using .use to access some property on the resource that is a cached value of some recent external state (e.g. statistics from a database server).
If a user accidentally passes a non-Promise-returning function (or a function that throws a synchronous exception) to
.use
,.use
will throw an exception and never release its resource.One way this came up for me was using
.use
to access some property on the resource that is a cached value of some recent external state (e.g. statistics from a database server).For example:
Calling the above function will throw
TypeError: fn(...).then is not a function
and the resource will never be released. This happens here.The text was updated successfully, but these errors were encountered: