Former Java engineer turned Ruby engineer who is trying to understand Ruby and Rails, MacOS and a lot of other things. Worked at Flywheel, FNBO, ACI Worldwide.
Oh! Sorry I thought you had the issue on your actual blog :-)
The fact is not an error you can generate on command makes it harder to debug but you should probably wait for the next crash (I know :D) and then open an issue to rack-mini-profiler with the traceback, which I assume is logged on the console.
Former Java engineer turned Ruby engineer who is trying to understand Ruby and Rails, MacOS and a lot of other things. Worked at Flywheel, FNBO, ACI Worldwide.
Hi Christine, thanks for the update!
I think being derailed is perfectly normal, one can't be in the zone constantly :-D
I googled the error a bit but I didn't find a clear answer, I have a question though: why are you using a profiler on production :) ?
This is just my local dev environment that is running into the issue. I believe the profiler is just used in my local procfile for foreman.
Oh! Sorry I thought you had the issue on your actual blog :-)
The fact is not an error you can generate on command makes it harder to debug but you should probably wait for the next crash (I know :D) and then open an issue to rack-mini-profiler with the traceback, which I assume is logged on the console.
Does it make sense?
Yep, thanks to the advice.