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
fs: fix writev empty array error behavior #41919
Conversation
|
Are |
|
They throw a catchable error which is a lot less bad but the behavior for empty arrays should probably be adjusted there too (probably in a separate PR). I think we need to think how we do argument handling because it's currently very easy to make Node abort by passing a problematic argument. That is - a lot more than just writeev is affected and I'd guess most methods break on problematic input (subclasses or types or proxies) |
|
Landed in a137eca |
PR-URL: nodejs#41919 Fixes: nodejs#41910 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Robert Nagy <ronagy@icloud.com> Reviewed-By: Minwoo Jung <nodecorelab@gmail.com>
PR-URL: nodejs#41919 Fixes: nodejs#41910 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Robert Nagy <ronagy@icloud.com> Reviewed-By: Minwoo Jung <nodecorelab@gmail.com>
Fixes: #41910
Alternatively - we can error on an empty array but I like this behavior better.
cc @nodejs/fs @jasnell
The text was updated successfully, but these errors were encountered: