pry on 1.9.2-p290 gives #<LoadError: no such file to load -- coderay/tokens_proxy>

[tvon]

Works fine with 1.9.2-p180, but on updating to 1.9.2-p290 I get an error when attempting to output anything:

± pry -r ./config/environment
pry(main)> User.all
(pry) output error: #<LoadError: no such file to load -- coderay/tokens_proxy>

This is on Snow Leopard.

[banister]

Hi, can you reproduce this bug outside of rails?

[tvon]

Hmm, bad report on my part, it actually works in another 1.9.2-p290 rails project.

What's odd is that in the "broken" project it works fine using 1.9.2-p180.

It does work with "--no-color", which makes sense given the error, suggestions on how to track down the core issue?

[banister]

@tvon, at a guess it sounds like a CodeRay bug. It seems that CodeRay has finally got to version 1.0 (which was released yesterday) and there may still be some issues with it, could you try also filing the issue on https://github.com/rubychan/coderay/issues and see if he has any immediate ideas.

[tvon]

Aight, thanks.

Quick edit to confirm, the working gemset has code ray 0.9.8, the broken one has 1.0

[apneadiving]

same problem here using ree and pry 0.9.6

[banister]

@apneadiving, i filed an issue on CodeRay and i'll wait to see if he can push a fix in the next few hours, if he cant, i'll push a new gem downgrading the dependency to coderay 0.9.*

[korny]

Interesting. Maybe some problem with Rails?

CodeRay is using autoload: https://github.com/rubychan/coderay/blob/master/lib/coderay.rb#L137

Can you please check:

• whether there is a lib/coderay/tokens_proxy.rb file
• whether it was not loaded before you highlight anything, with $".grep(/tokens_proxy/) or something
• whether it is loaded after you evaluate CodeRay::TokensProxy

[korny]

btw: I think it's a bad idea to define your dependencies with ">=".

[banister]

@korny, @apneadiving,

I pushed a 0.9.6.2 gem that downgraded the dependency on CodeRay to ~>0.9.8

Let me know if this works for you

[korny]

I hope to get a fix/workaround for this ready in the next days. It seems Rails doesn't like libraries which use autoload.