Skip to content

🐛 [Bug] Image upload is not working in local development environment #4081

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

Closed
Mogge opened this issue Dec 16, 2020 · 4 comments · Fixed by #5897
Closed

🐛 [Bug] Image upload is not working in local development environment #4081

Mogge opened this issue Dec 16, 2020 · 4 comments · Fixed by #5897
Assignees
Labels
bug Something isn't working

Comments

@Mogge
Copy link
Contributor

Mogge commented Dec 16, 2020

🐛 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

  1. Create a new post
  2. Fill in all necessary fields
  3. Upload an image, crop it and click on confirm
  4. 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.

@Mogge Mogge added the bug Something isn't working label Dec 16, 2020
@Mogge Mogge self-assigned this Dec 16, 2020
@Mogge
Copy link
Contributor Author

Mogge commented Dec 17, 2020

Further examination:

@Mogge
Copy link
Contributor Author

Mogge commented Dec 17, 2020

This leads me to the conclusion that updating our node version is no good idea until this is fixed.

@Tirokk
Copy link
Member

Tirokk commented Dec 21, 2020

This is solved by PR #4083 I understand right? @Mogge

@Mogge
Copy link
Contributor Author

Mogge commented Dec 21, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants