search for: dd7lmggel7nbdgjk7y7tuq

Hi Folks, I believe I tracked down the problem with the leaked DB connections. The simple fix is to put: ActiveRecord::Base.threaded_connections = false In your environment.rb file right before environment.rb does any ActiveRecord use. For example, here''s mine: ActiveRecord::Base.threaded_connections = false ActiveRecord::Base.configurations =

Hi All, Alright, this release is getting closer. It''s nearly complete except the docs on my site aren''t written yet. There is however a full README with RDoc documentation and several packages including a gem release. Please check out the latest release at: * Announcement: http://www.zedshaw.com/ * README and RDoc:

Hi Everyone, I figured out this weekend that Ruby''s Thread implementation causes the Ruby/Event binding I wrote to completely stall and go dead. After reviewing the Ruby source and watching several strace runs, it''s clear that the Ruby Thread implementation uses select in a way that--while not being bad--just isn''t compatible with libevent. The second a thread is

IE6 happily sends unsafe* characters unencoded if you''ve typed them into the URL bar of your IE6 window. This could happen if you copy & paste a URL from an email or web page. Mongrel doesn''t seem to handle these properly. In 0.3.13.3 it would print out something like: Sun Oct 15 23:05:38 CST 2006: BAD CLIENT (192.168.1.2): Invalid HTTP format, parsing fails. 0.3.13.5

Do you want to get in... ...and got what it takes? I''m working as it-responsible (diplomatic service) for the Republic of Cyprus. Now I want to move on, I know that I have the next big thing in the dot com biz. It all begun from a dream that became a businessplan and also later on was nominated by UN World Summit Awards and won the title as best initiative in category ICT. In a few

I wrote an x-sendfile thing for the railshandler to get mongrel to catch the response header and stream out files from an application I''m writing but I''m pretty sure that zed said he''d built in x-sendfile somewhere already. I couldn''t find it, could someone lead me to it? Does mongrel work with SSL? If not is anyone interested in having someone write in SSL

Hello happy Railers, I used to develop with a local out-of-the-box Apache and load times were pretty slow (like a few seconds each page). "Well, it''s the price to pay for no compile / cache / etc..." I thought. Nonsense. Yesterday I installed SCGI, and now I''ve got the best of both worlds: rails development env uses my very latest modifications, while SCGI ensures I

Hello Everyone, Announcing the Ruby/Odeum library--a full text inverted indexer for Ruby: http://www.zedshaw.com/projects/ruby_odeum/ Ruby/Odeum is an extension that wraps Mikio Hirabayashi’s QDBM Odeum library for fast reverse indexing of documents. It supports indexing documents by their words, breaking the text into words, normalizing the words, searching, and attaching meta-data to each

I have a problem with running Rails 0.13.1 with scgi_rails 0.4.3 and Apache. After running for some time (more than a day), the SCGI process stops with the following error (from scgi.log): -- [ERR][24189] Collecting thread: Too many open files [ERR][24189] /usr/local/lib/ruby/gems/1.8/gems/scgi_rails-0.4.3/lib/scgi.rb:188:in `accept''

I''ve managed to get Rails working using Apache->Lighttpd->SCGI. Restarting everything is really difficult. This appears to be the process: - stop apache - stop lighttpd - stop scgi - make sure scgi still isn''t running (it sometimes does) - if it is, kill it - delete all session files (they often cause permission errors) - start scgi - start apache - start lighttpd - cross

hello. i''d like to share some feelings of mine after a couple of *weeks* intermittent attempts to have rails applications working on windows (XP) with fastcgi performances under apache (2.0). i''d say the software stack i''m using now will be fairly common as more and more new rails developers will join the bandwagon. what is stunning me is the fact that, even if

Hi, We have developed a small RoR app that runs fine on a standard IBM thinkpad (1GB mem) but runsmuch slower when on an IBM x460 Redhat machine (32GB ram). The x460 server has hardly any thing running on it at present, so that not the issue. We are busy checking the config and permissions of the user account used to run the app., but I was wondering if you guys have heard anything about redhat

Hi Folks, Just a quick message saying that, after much demand, I wrote a quick write-up for the RoR + XUL thing I did yesterday: http://www.zedshaw.com/blog/programming/ruby_xul.html It lays out the few simple things I did, has a bit of rant on an unrelated topic, and other stuff but it''s short still. On a related note, I''d like to thank "xal" on IRC for reminding

Hi All, At the risk of starting a major flame war and giving Java player-haters more fuel for their ire, I''ve done a performance comparison between Ruby/Odeum and Lucene: http://www.zedshaw.com/projects/ruby_odeum/performance.html Please don''t take this as a "Java sucks Ruby rulez" posting, or that I''ve done any sort of scientific analysis here.

Hello, An announcement for another version of Ruby/Odeum 0.4. http://www.zedshaw.com/projects/ruby_odeum/index.html http://www.zedshaw.com/downloads/ruby_odeum/ruby_odeum-0.4.tar.bz2 http://www.zedshaw.com/downloads/ruby_odeum/ruby_odeum-0.4.gem ***This release will break your existing code.*** Read the ResultSet documentation for how to make your changes. Important features of this release

Hi, I''ve had several reports of people with problems using lighttpd 1.4.1 or 1.4.2 with my recently released SCGI Rails runner. I''ve been testing these versions of lighttpd and I see the following problems: 1. When run with -D option, a CTRL-C will often times give a segfault. This is linux for me, any others? It most often happens right after try an SCGI handled request.

Howdy Folks, This release is after painstaking analysis of a memory leak that was reported by Bradley Taylor, reduced by myself, and then fixed after much work. You should all thank Bradley for finding the bizarre fix. It turns out the Ruby has a memory leak when you use pretty much any thread locking primitive other than Sync (Mutex, Monitor, etc.): http://pastie.caboo.se/10194 The fix (for