Re: [Radiant] A file or directory in the path name does not exist error after Radiant Install

2009-12-22 Thread Michael Johann
Hi Pete, there was a bug (JRUBY-4380) in Jruby 1.4.0. I provided some information and they fixed it. Later this day it will be pushed to the master branch of JRuby. Cheers Michael Am 21.12.2009 23:56, schrieb Pete Helgren: I installed Radiant on JRuby 1.4 and I get the following error when I

Re: [Radiant] A file or directory in the path name does not exist error after Radiant Install

2009-12-22 Thread Sean Cribbs
Pete, It is using the filesystem for cache storage. Make sure you have write permissions to tmp/cache and that it exists. Sean On 12/21/09 5:56 PM, Pete Helgren wrote: I installed Radiant on JRuby 1.4 and I get the following error when I attempt to access the web app: /!\ FAILSAFE /!\

Re: [Radiant] A file or directory in the path name does not exist error after Radiant Install

2009-12-22 Thread Pete Helgren
Excellent! Fixed and it *does* work like a charm. Thanks, Pete Michael Johann wrote: Hi Peter, this is a bug in JRuby where File.open throws an IOError instead of Errno::ENOENT. Rack-Cache can handle the situation if Errno::ENOENT is thrown but this never happens. I realized this a

Re: [Radiant] A file or directory in the path name does not exist error after Radiant Install

2009-12-22 Thread Pete Helgren
Thanks Sean. I'll keep that in mind. The fix was related to a JRuby bug that Michael pointed out. But knowing about the potential for a permissions issue is helpful to know. Pete Sean Cribbs wrote: Pete, It is using the filesystem for cache storage. Make sure you have write

Re: [Radiant] A file or directory in the path name does not exist error after Radiant Install

2009-12-21 Thread Michael Johann
Hi Peter, this is a bug in JRuby where File.open throws an IOError instead of Errno::ENOENT. Rack-Cache can handle the situation if Errno::ENOENT is thrown but this never happens. I realized this a few days before and will open an issue and contribute to JRuby in the next hours. A workaround