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
-71 instead of EPROTO error #31438
Comments
Can you maybe share more information about how to reproduce this? |
If you're using the |
Seems this is the cause, yes. |
You should probably check against the |
We found the culprit. It was caused by another module. Thanks for the clarificartion and information. |
I think what we miss here is some history / deprecation or breaking change info: https://nodejs.org/api/errors.html#errors_error_errno At least I see none like in other modules. Only 10 https://nodejs.org/api/fs.html#fs_fs_open_path_flags_mode_callback Unless we take a look at the changelog. |
It seems with Node 13(.6.0) error codes are numeric now which produces failing snapshot tests and assertions.
Before Node 13:
EPROTO
Starting with Node 13:
-71
Is there some information about this or was this just a bug and is this already fixed?
The text was updated successfully, but these errors were encountered: