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
When setting up the local dev env without docker, the image upload is not working.
Error message: GraphQL error: a ReadStream cannot be created from a destroyed WriteStream.
The cropping of images is not working as well.
When using docker, everything is working fine.
Steps to reproduce the behavior
Create a new post
Fill in all necessary fields
Upload an image, crop it and click on confirm
Save the post
Expected behavior
The image should be saved in the backend/public/uploads folder. A success message should be toasted.
Version & Environment
Local development without docker on current master. I tried earlier versions back to 2 months and the same problem occurs. I tried the behavior on the master of the HC repository and the same error occurs. So it has nothing to do with the cloning.
Additional context
file: backend/src/schema/resolvers/images/images.js
The promise in line 115 provokes the error.
The text was updated successfully, but these errors were encountered:
I do not know how to treat this best. We can close it, but it is realted to #4082 . May be we reopen it, when we really want to upgrade our node version, @Tirokk
Uh oh!
There was an error while loading. Please reload this page.
🐛 Bugreport
When setting up the local dev env without docker, the image upload is not working.
Error message:
GraphQL error: a ReadStream cannot be created from a destroyed WriteStream
.The cropping of images is not working as well.
When using docker, everything is working fine.
Steps to reproduce the behavior
Expected behavior
The image should be saved in the
backend/public/uploads
folder. A success message should be toasted.Version & Environment
Local development without docker on current master. I tried earlier versions back to 2 months and the same problem occurs. I tried the behavior on the master of the HC repository and the same error occurs. So it has nothing to do with the cloning.
Additional context
file:
backend/src/schema/resolvers/images/images.js
The promise in line 115 provokes the error.
The text was updated successfully, but these errors were encountered: