Yes. It should be fixed. If you upgrade and still get the error, let us
know!
On Thursday, February 7, 2013, Doug Livesey wrote:
> David Chelimsky wrote in post #971870:
> > On Sun, Jan 2, 2011 at 5:42 AM, Kristian Mandrup
> >
> >
> > wrote:
> >> I'm using the latest ruby 1.9.3-head and recentl
David Chelimsky wrote in post #971870:
> On Sun, Jan 2, 2011 at 5:42 AM, Kristian Mandrup
> wrote:
>> I'm using the latest ruby 1.9.3-head and recently whenever I run rspec
>> (2.2+) I get the following error:
>>
>> I have seen others have run into this issue, but to resolve it just
>> rolled back
On Sun, Jan 2, 2011 at 5:42 AM, Kristian Mandrup wrote:
> I'm using the latest ruby 1.9.3-head and recently whenever I run rspec
> (2.2+) I get the following error:
>
> I have seen others have run into this issue, but to resolve it just
> rolled back to a previous version of rspec or it there a be