-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Possible race condition in metadata() when using Stream-based input #3451
Comments
Thanks for reporting, there was a possible race condition when awaiting Commit df97120 fixes this and adds a test that would previously have failed. This will be included as part of v0.31.3. |
Thanks for your answer. Just out of curiosity, why was the interpreter exiting without returning any error? I would have expected some sort of error, even like a segfault, but I was getting nothing in all the environment I tried |
The "finish" event was already firing before the listener was attached, so the Promise returned by I assume you invoked your sample by adding a call to |
Now I see. Thanks again, I appreciated your answer. |
v0.31.3 now available, thanks again for reporting. |
Considering the following code
When we await for the metadata of data2 the node interpreter will immediately exit without any error. I tried to debug it but I could not find the point in which the node interpreter is closed (I might assume this happens in native, but I'm not sure).
This issue never happens if we work on different images so the following code is totally fine and works as expected
The text was updated successfully, but these errors were encountered: