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
Process does not terminate and the stream error handler is called
Steps To Reproduce
Run the following script. It will change the tmp folder permission, so that an error is triggered. It can happen in other circumstances too (of of disk space, etc.)
In certain cases this results in a lingering rejected promise handleContentP within lib/content/write.js
In the example, such case is when the readable stream has not ended.
This attaches a catch handler to the handleContentP promise, as in some cases the flush is not called before node decides that this is an unhandled promise rejection.
Is there an existing issue for this?
Current Behavior
Process terminates with error:
Expected Behavior
Process does not terminate and the stream error handler is called
Steps To Reproduce
Run the following script. It will change the
tmp
folder permission, so that an error is triggered. It can happen in other circumstances too (of of disk space, etc.)In certain cases this results in a lingering rejected promise
handleContentP
withinlib/content/write.js
In the example, such case is when the readable stream has not ended.
Environment
The text was updated successfully, but these errors were encountered: