-
Notifications
You must be signed in to change notification settings - Fork 4
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
Logfile NOT optional; Logging does not work #2
Comments
@andrewkim47 try now, and do this:
|
That command creates the log file, and then writes the opening dialog to file before erroring out. The logfile contains:
It then errors out with the message:
A 4-argument [no log] command still returns the same "usage suggestion" error. returns the a similar error to the logyes
it looks like logfile does not get defined as True on line37. is parts counted correctly? |
You forgot to put a buffer in. you still need a buffer On March 8, 2016 at 9:21:08 PM, andrewkim47 ([email protected]) wrote: That command creates the log file, and then writes the opening dialog to file before erroring out. The logfile contains: '/Users/akim/NodeForwarder2/nf.js', body-parser deprecated bodyParser: use individual json/urlencoded middlewares nf.js:88:9 returns the a similar error to the logyes body-parser deprecated bodyParser: use individual json/urlencoded middlewares nf.js:88:9 — |
|
Oops. Now that I put in a correct arguments, I still see 2 issues:
My arduino is simply writing millis() to Serial. But the log file's contents are:
Errors out with the same "logfile not defined"
Omitting the pipe to a logfile is the only way to get the "old" behavior of terminal output. But you still need the logyes argument. |
NodeForwarder requires all 5 arguments. Omission of a Logfile argument returns the Usage suggestion:
For example, the command:
leads to:
When a logfile is inputted, there is a different error:
The text was updated successfully, but these errors were encountered: