-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
Log file is empty after fatal error #689
Comments
may have something to do with the fact that the app do not close after having this error (which is odd) and I had used Ctrl+C to close it |
can you send me the stdout? (If it contains private info you can send it via deltachat otherwise posting here should be fine) |
the log is not the big thing but here I attach it(also there were a line saying something like "you can see the log at ...." pointing to the log file: |
ah it's likely something with deltachat-node |
I don't really know how we can solve this, I mean we can't really catch when a require statement fails. |
We can't solve this. If the application can't start, we can't create a log that depends on the application running or at least starting properly. |
the log file is created!!! it is just empty! the app is printing the message to stderr, maybe even to the log and the issue is that it isn't flushed
|
Still we can't fix this, the best we could do would be detecting if every dependency is there before requiring them. But I actually think solving the missing dependency has more priority. |
The point is the logfile probably gets created before deltachat-node gets loaded up. We can't really check on whether a require fails as far as I knowso we can't add it to the log. |
|
Maybe we could move the exception handler to before the |
Yes, that's a good idea.
Sorry @adbenitez, my bad! |
I had faced issue #401, the app had shown the error trace in the stdout and pointed me to a log file, but this log file is empty.
The text was updated successfully, but these errors were encountered: