-
Notifications
You must be signed in to change notification settings - Fork 34
The app crashes after running for a minute #22
Comments
If possible, can you share a snippet of the log lines that are causing this problem? |
These all seem problematic " Schema | Name | Type | Info " " lib/peanut_forwarder.rb:23:in `call'" " config/initializers/patches/logger.rb:5:in `call_with_quiet_assets'" |
(that is the content of matches[4]) |
Great - thanks! I'll get a patch out this afternoon. |
I'm unable to reproduce this issue in testing. I'll add some code to catch exceptions in log parsing, but I can't see why that code would fail on your examples. For instance, parsing
Which is nonsense, but doesn't crash. |
If I tweak the rescue to include the line:
I get this:
Here is a gist in case there are any funny characters that get stripped in the quote above: https://gist.github.com/toreriklinnerud/dee24c47aff68b219e46 |
This reproduces it
|
Ah, then we definitely have a mismatch somewhere. I tested it locally and in a one-off process against the live Heroku app:
On Heroku, I'm running |
I am running Ruby 2 locally. I guess the error handling of Hash[] is different. This fixes it for me:
|
Interesting! Thanks for digging in to this. I would definitely accept a pull request that adds Ruby 2.0 support. Otherwise, I'll leave this open until I fix the issue or explicitly note lack of 2.0.0 compatibility in the README. |
Let me see what I can do :) |
/Users/tel/code/log2viz/app.rb:136:in `[]': invalid number of elements (0 for 1..2)
This is the offending line (app.rb):
The text was updated successfully, but these errors were encountered: