Collectives™ on Stack Overflow
Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about Collectives
Teams
Q&A for work
Connect and share knowledge within a single location that is structured and easy to search.
Learn more about Teams
console.log("solving Model");
reasoner.solve(Model, (err, stdout, stderr, isSatisfiable) => {
console.log("isSatisfiable");
console.log(isSatisfiable);
if (err) {
// manage error
console.log("model error");
future_response.return("model error");
} else {
// manage solution
console.log(stdout);
console.log(isSatisfiable);
future_response.return(stdout);
console.log("Model solved");
return future_response.wait();
from what I have read I should find a way to rewrite the
stdout
to support bigger buffer length, could someone please advice how I could do it? I believe that the library
spawn
is what I should use, right?
I use node version 12.16.1 and meteor
You need to use and set the
maxBuffer
option when using child_process.exec. From the :
documentation
It is - the differences between spawn() and exec() of Node's child_process. Use spawn() when you want the child process to return huge binary data to Node, use exec() when you want the child process to return simple status messages.
Thanks for contributing an answer to Stack Overflow!
-
Please be sure to
answer the question
. Provide details and share your research!
But
avoid
…
-
Asking for help, clarification, or responding to other answers.
-
Making statements based on opinion; back them up with references or personal experience.
To learn more, see our
tips on writing great answers
.
