-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Call stack overflows when turning Future to Promise #963
Comments
I didn't really give much information, did I? In hindsight, I don't know why I posted this issue on this tracker actually. Things could be going wrong on any of these levels:
I didn't think of the second step as potentially causing the problem. However, in the meantime, I have discovered rust-lang/futures-rs#1283 and seeing that the compatibility layer is mentioned in the recurring stack trace I posted, I'm going to assume for now that that is what causing this issue. I'll try to come up with a minimal example and see if rust-lang/futures-rs#1286 fixes it. Thanks for your help. :-) I think you can close this and if it would appear that the problem isn't caused by that bug in the |
Ok cool sounds good to me, thanks for the continued investigation! If this does end up being in wasm-bindgen though just lemme know and I'll reopen |
Since I updated some dependencies, whenever I try to execute some promises that were converted from Futures, I've been getting this error:
I'm not entirely certain, but the stack trace makes me suspect that this isn't directly the fault of my part of the code. On the other hand, I've read in the documentation that "if the future provided panics then the returned Promise will not resolve", so I'm guessing that is what is going wrong here.
I was under the impression that #954 would fix this, or would rather somehow expose what the panic was, or at least change something, but that didn't seem the case.
Apart from this issue, does anyone have an idea on how to discover what is actually panicking here?
The text was updated successfully, but these errors were encountered: