Invalid non-string/buffer chunk while writing file on server
See original GitHub issueWhile writing file:
Files.write(data,{
type: 'application/pdf',
fileName: 'sample.pdf',
meta: {
reference: "ref",
version: 1
}, function (error, fileRef) {
if (error) {
throw error;
} else {
console.log(fileRef.name + ' is successfully saved to FS. _id: ' + fileRef._id);
}
}
});
The error “Invalid non-string/buffer chunk” appear with a blank file in the path.
- Version of
Meteor-Files1.9.3 - Version of
Meteor1.6.1 - OS Linux (It work on Mac), Chrome browser
- It is Server issue?
Exception in callback of async function: TypeError: invalid non-string/buffer chunk
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Node.js TypeError: Invalid non-string/buffer chunk
Code Error Postman Error. I Found that I was parsing same key and value pair in Postman while hitting Application Programming ...
Read more >Javascript – Node.js TypeError: Invalid non-string/buffer chunk ...
ANSWER: I've finally got it, turns out I was also looking in the wrong place for the logger file. it places it in...
Read more >Invalid non-string/buffer chunk parseAsync #403
If the content of data.data is not a string or a Buffer, you can't pass it to the AsyncParser . I assume that...
Read more >Stream | Node.js v18 API
Data is buffered in Writable streams when the writable.write(chunk) method is called repeatedly. While the total size of the internal write buffer is...
Read more >Node.js v19.3.0 Documentation
An example of a web server written with Node.js which responds with 'Hello, World!' : Commands in this document start with $ or...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I try to reproduce this issus but i can not. I am on 1.6.1 in Linux before it was on 1.5.1 I will close it. If i get this problem again, i will contact with other informations
Please, support this project by: