为什么我的Sproutcore开发服务器断开连接“US-ASCII中的无效字节序列”？

Question

Here's the stack: Sproutcore 1.0.1046. Ruby 1.9.1, in RVM. Thin 1.2.7. Thor 0.13.8. Rack 1.2.1. Eventmachine 0.12.10. Erubis 2.6.6.

When I start the sc-server on any application, my first request to this server produces this in the console log:

ArgumentError: invalid byte sequence in US-ASCII

...followed by this stack trace . (I've listed gems which appear in the stack trace above, but there's a complete gemset list in the same gist as the stack trace.)

Research on the error message points out that this is a common problem with Ruby 1.9, but the stack trace suggests that the problem is in one of the gems somewhere.

I have:

• Upgraded my OS (Mac OS X 10.5 to 10.6) in order to get the latest gcc Apple provides.
• Reinstalled RVM.
• Reinstalled Ruby.
• Reinstalled all the relevant gems.

And yet I still have this problem on one system, but not on another. (NB there are several devs working on this code, and I'm the only one seeing this problem. I'm 99% certain it's not our code.) I guess what I'm saying is that I've cleared and rebuilt a lot of gems to try to isolate or remove this glitch, and yet I still haven't gotten rid of it.

Where should I look next?

Answer 1

你的bash环境中有一些特殊设置，设置ruby使用US-ASCII，这发生在我试图从远程终端执行sc-server时...我不确定它是什么，但它没有'使用UTF-8，当它遇到麻烦时。

Answer 2

您也可以更改Encoding.default_external

Answer 3

Thanks so much for the Encoding.default_external suggestion. I was having the same problem, despite correctly set magic comments and environment variables. In Rails 2.3.9 I added this before_filter in application_controller.rb, resolved the issue:

def set_encoding
  Encoding.default_external = 'UTF-8'
end

Answer 4

I had the same issue with RSS Feeds that I was displaying in a Rails 2.3.8 app with Ruby 1.9.2. My issue wasn't solved by the application_controller.rb before_filter technique mentioned here. The fix was to put the following into "RAILS_ROOT/config/initializers/string_encodings.rb":

Encoding.default_external = 'UTF-8'

That worked for me site-wide, instead of on a controller level.

Answer 5

In my case the ArgumentError occurred during a Capistrano deploy call that envolves ruby's net-ssh (ruby 1.9.2p290, net-ssh 2.3.0). None of the solutions afore mentioned worked and none of the other reasons I've read about so far: ie "strange character in key file", etc..

Finally, I found a none ASCII-character in a comment(!) line in my ASCII encoded ~/.ssh/config file. BINGO!