生成管理器中的 Rails、Passenger、Encoding::CompatibilityError
红宝石 1.9.2 铁轨3.0.9 ssl_要求 1.3.2 Passenger 3.0.8
更新 ssl_requirement 后，部署应用程序时，我现在在生成管理器中遇到 Encoding::CompatibilityError 异常
更多详细信息跟踪表明，在启动时加载所需的 gem 期间涉及 ssl_requirement：
ssl_requirement.gemspec:11: invalid multibyte char (US-ASCII)
/home/bill/.bundler/ruby/1.9.1/ssl_requirement-0db844a72f88/bartt-ssl_requirement.gemspec:11: invalid multibyte char (US-ASCII)
/home/bill/.bundler/ruby/1.9.1/ssl_requirement-0db844a72f88/bartt-ssl_requirement.gemspec:11: syntax error, unexpected $end, expecting ']'
...}, %q{bartt}, %q{Thorben Schröder}]
... ^) (process 29902, thread #<Thread:0x00000001274858>):
我在应用程序中的每个位置添加了神奇的编码标签，根据几个谷歌搜索结果，我的所有初始化程序等都有正确的 UTF-8 声明，但无法使 500错误消失。我还应该做什么？谢谢
Ruby 1.9.2
Rails 3.0.9
ssl_requirement 1.3.2
passenger 3.0.8
After updating ssl_requirement, when deploying the app I'm now getting Encoding::CompatibilityError in spawn manager exceptions
The more details trace indicates that ssl_requirement is involved, during loading of required gems on startup:
ssl_requirement.gemspec:11: invalid multibyte char (US-ASCII)
/home/bill/.bundler/ruby/1.9.1/ssl_requirement-0db844a72f88/bartt-ssl_requirement.gemspec:11: invalid multibyte char (US-ASCII)
/home/bill/.bundler/ruby/1.9.1/ssl_requirement-0db844a72f88/bartt-ssl_requirement.gemspec:11: syntax error, unexpected $end, expecting ']'
...}, %q{bartt}, %q{Thorben Schröder}]
... ^) (process 29902, thread #<Thread:0x00000001274858>):
I added the magic encoding tags everywhere in the app, per several google search results, and all my initializers, etc have the proper declarations for UTF-8, but can't make the 500 error go away. What else should I do? Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
通过将 ssl_requirement 回退到 1.3.1，然后对 1.3.2 中我需要的更改进行猴子修补，解决了这个问题。问题现在已经解决，尽管我想实现一个不包括修补先前版本的真正解决方案。
Solved this by backing ssl_requirement back down to 1.3.1, then monkey patching in the changes I needed from 1.3.2. Problem solved for now, although I'd like to implement a real solution that doesn't include patching the prior version.