-
Notifications
You must be signed in to change notification settings - Fork 31
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
Interleaved/Partial log output #26
Comments
/cc @pedro |
Oh man, +1. This has been haunting us for quite a while - latest attempt was to reset the Scrolls Mutex on Unicorn fork but that didn't seem to improve the situation. @mikehale do you have more info on the apps that had this issue? Are they 1.8.7? Unicorn? |
I was seeing it on an heroku/backstop, which uses thin, ruby 1.9.2, and sinatra. |
I'll be honest I have no idea how to reproduce this. I never saw it while I was at Heroku and I haven't put Scrolls through any rigorous logging at GitHub. If you find something let me know. |
Going to close this due to not enough information. If you see it again, let's reopen and see if we can reproduce. |
To be fair I'm not certain if this is a scrolls issue or something related to the heroku logging infrastructure. I have seen it on a platform app and a bare metal app using unicorn.
Example output:
I would expect to see something like:
The text was updated successfully, but these errors were encountered: