-
-
Notifications
You must be signed in to change notification settings - Fork 287
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
[BUG] Buffers modified inside multer storage class #1840
Comments
Hello @MatejSkrbis |
OK, I will try to make full example and upload it here. |
If you can init with the cli a small it’s fine and a controller to upload file with the storage engine it will be really appreciate ;) |
Here is small repo with test controller. You just need to install the modules build it and run it.
|
Ok I see the issue :) |
Release in progress @MatejSkrbis |
🎉 This issue has been resolved in version 6.110.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 7.0.0-beta.4 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Information
Previous version: 5.61.1
Current version: 6.105.4
I've had custom multer storage implementation for uploading files directly into azure storage blob. This worked fine in tsed v5, but stopped working in tsed v6. After debugging I figured out that all Buffer objects are somehow modified somewhen after initialization, breaking the code. (Blob client from azure is using some Buffers internally)
I'm not using the latest version of tsed as 6.105.4 is the latest where npm audit isn't producing errors.
Example
Here is the simplest example of custom multer storage that will fail on file upload.
This example will produce following error when trying to upload the file.
Acceptance criteria
The Buffer objects should probably not get modified as this will break some code.
The text was updated successfully, but these errors were encountered: