WSOD revisited
-
Continuing the discussion from Congratulations on your glorious two minutes of uptime:
Nothing in the logs here, this error is killing me
Speaking of which, are you still interested in WSODs?
http://what.thedailywtf.com/logs/show/2e4899fb61cb24db8b2c039654b7c514
ActionView::Template::Error (incompatible character encodings: ASCII-8BIT and UTF-8)/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/core_ext/string/output_safety.rb:155:in `concat' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/core_ext/string/output_safety.rb:155:in `safe_concat' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.8/lib/action_view/buffers.rb:18:in `safe_concat' /var/www/discourse/app/views/topics/show.html.erb:13:in `block in _app_views_topics_show_html_erb___4266154527998687967_69918557134620' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/relation/delegation.rb:46:in `each' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.8/lib/active_record/relation/delegation.rb:46:in `each' /var/www/discourse/app/views/topics/show.html.erb:9:in `_app_views_topics_show_html_erb___4266154527998687967_69918557134620' [...]Refresh displayed the page.
-
Continuing the discussion from Congratulations on your glorious two minutes of uptime:
Speaking of which, are you still interested in WSODs?
I saw one just a few minutes ago also.
-
Same for me.
-
I saw one just a few minutes ago also.
http://what.thedailywtf.com/logs/show/58d25ac6f692c7740ee48de754c3e1c4
Same error. Not that I think you'd be able to view it..
Same for me.
Couldn't find one for you in the past 18 or so minutes.
-
-
Couldn't find one for you in the past 18 or so minutes.
OK, it may have been a company proxy thing then.
-
Is there a way to get the stack trace of where an object was created?
-
Still interested, looking through these now.
-
http://what.thedailywtf.com/logs/show/dcd0b84f61aa34f7d5192fbc08bf86fa
Just now. Opening 16 tabs (not that I think it'd be relevant given the error message.) Refresh worked.
-
403 - Permission denied.
:-(
-
Admin only. It's just a ruby stacktrace. Just posting in case @sam's still interested in them.
-
i had guessed. doesn't stop the fox from being curious! ;-)
-
Not very interesting to most I'd imagine.
-
Not very interesting to most I'd imagine.
indeed, but then i'm not most. ;-)
hmm character encodings are hard....
-
character encodings are hard...
But Ruby makes them harder. It does this by not being properly rigorous about what happens when multiple encodings are about. Because Ruby's only ever used to work on applications that use a single encoding and never for web applications where users might be located all over the world!
-
well yes, and it can't even do the somehwt sensible, if WTFy, thing of auto casting ASCII 8BIT to Unicode, because ASCII is just a subset of UTF8.
granted you can't do that if any of the characters in ASCII8BIT have their high bit set, but i'm willing to bet good money that in the WSOD crashes they never are set to the "cast" would be valid.
-
-
Ruby 2.2 is out very very soon (probably in 3 days or so) I will try to get an image up with it and see if somehow this bug is corrected in it, I know its a long shot, but worth it.
-
Ruby 2.2 is out very very soon (probably in 3 days or so) I will try to get an image up with it and see if somehow this bug is corrected in it, I know its a long shot, but worth it.
Danger, Will Robinson!
Going to a brand new version will pretty much guarantee that you are going to be exposed to “interesting” new bugs; stuff that just has odd interactions. By all means test on your own, but deploying that is likely to be much harder than expected.
-
ASCII-8BIT is actually "ascii plus we allow random garbage values that don't map to anything". You can put arbitrary binary data in there and it'll just error out when you try to convert it to unicode if it wasn't actually ASCII.
-
I'm not really tracking the times but I'm seeing WSOD more frequently in the last few days than I used to on desktop.
-
It would definitely have to bake on meta for at least 2-4 weeks before testing here.
-
I'd call it more of a simmering roast
-
before testing here.
I thought the point of requesting to move to beta was that we'd no longer be doing testing.
-
Sadly this particular error only happens here which makes stuff much harder for me.
