similar to: ruby 1.8.6 includes fastthread?

All, Mongrel 1.1.3 Rails 2.0.2 Ruby 1.8.6 Windows XP SP2 When I issue the command "ruby script/server" from any of my Rails projects on v. 2.0.2, I get a Windows dialog with the error: "The application has failed to start because MSVCR80.dll was not found. Re-installing the application may fix this problem." I''ve gone through the process of attempting to introduce

I''m confused. Wasn''t threading fixed in 1.8.6, negating the need for fastthread? Why is fastthread still a requirement of Mongrel? Just curious. :)

I have a simple Yes/No selection list that I am using in a number of places. Thinking that I could DRY things out a bit, I added it to application_helper.rb ... YES_NO = [ [ "Yes", true ], [ "No", false ] ].freeze So I figured I would use it there instead of in each model.rb where needed. anyway, in webrick screen, I am continually seeing this...

I''m struggling to get switchtower working, and from other posts about it I know it has something to do with ruby binding to open ssl. I''m just not sure what I should recompile/reinstall to get things to work. running: "rake remote_exec ACTION=setup" gives me ---> ...executing "mkdir -p -m 775 /usr/apps/hello-rails/releases /usr/apps/hello-rails/shared/system

Hello, I''m a big bookworm, so I decided to round up all the upcoming Ruby books in the market in one big blog post. At my count, there are _sixteen_ books to be released (in print) for the upcoming year, with some available in pdf form right now. Here''s the list: http://www.robsanheim.com/2006/03/23/ruby-and-ruby-on-rails-book-roundup/ Hope its helpful for fellow book nerds

Hi all Hope this isn''t too far off-topic on this list, as I think it would largely go ignored on the main rails list. I''m looking for the most pragmatic way to speed up our test suite. This is on an established project, and lets just say that we used way too many fixtures when we started =). For example: Finished in 128.870144 seconds. =============== 392 tests, 2106

On my current project I needed to create a stub that responded correctly to the id message. Here''s the change I put into my copy of head. Index: lib/mocha/mock_methods.rb =================================================================== --- lib/mocha/mock_methods.rb (revision 1114) +++ lib/mocha/mock_methods.rb (working copy) @@ -68,6 +68,7 @@ method_names =

Hi, I just did a clean install of Ruby 1.8.5 Rubygems 0.9.0 and the Mongrel and Mongrel_Cluster gems. I used only the Debian Etch package manager, nothing compiled myself. Now, on a testapp when I do a script/server, I get the: ** Ruby version is not up-to-date; loading cgi_multipart_eof_fix warning. But it''s not serving my app. Ruby is immediately on 100% CPU load (and 0.7%

I''ve just committed fastthread 0.5.3, which finally gives us a working SizedQueue (which hadn''t really ever worked in previous versions). Mostly it was just a matter of refactoring Queue and SizedQueue into a single class behind the scenes, so I could move the signalling of the SizedQueue-specific condition variable inside the queue''s critical section. Failing to do so

Hi, I wanted to try out Edge Rails 3 today and hit a serious problem trying to run mongrel. script/rails server mongrel just hangs. Interrupting and looking up the spot of the lockup revealed $LOAD_PATH.unshift ''projects/mongrel_experimental/lib/'' Mongrel::Gems.require ''mongrel_experimental'', ">=#{Mongrel::Const::MONGREL_VERSION}" at the bottom

Hi, I''m having difficulties getting mongrel running on my Debian Etch machine. It seems to install and is listed with my other gems, but things like... "mongrel_rails start ..." ... are not recognised. Perhaps this is something to do with the file "lib" not being found in the install process: ruby extconf.rb install mongrel --include-dependencies checking for main()

I just realized -- if fastthread can be included while Mutex-using code is already running, then the definition and replacement of the classes needs to happen atomically. Otherwise, it creates a race condition where a thread can e.g. end up seeing an incompletely defined Mutex class or none at all. fastthread 0.6.1 addresses this by defining the classes and then atomically swapping the constant

Hi, A quick search didn''t explain what fastthread is, and how it relates to mongrel. Why would I want to install fastthread? Thanks, Joe

It looks like I got too creative in 0.6.1 and consequently ran afoul of a bug in the Ruby interpreter. 0.6.2 works around the bug and should be entirely stable at this point. Thanks to Young Hyun for his help in coming up with test cases. == what? fastthread is a Ruby library which provides a faster (and non-memory-leaking) C implementation of the concurrency primitives from stdlib''s

Heya Folks- This is mainly for Zed and Mentalguy. I have been playing with the new release of rubygems 0.9.0.8 and I have a major problem with the requirement that fastthread needs to be required before thread. Just requiring rubygems and then requiring fastthread right after that will throw the error: ez _blog $ ruby require ''rubygems'' require

Well, just when I thought I was out of the fastthread business... Okay, in brief: fastthread is a Ruby extension which re-implements the primitives in Ruby''s thread.rb in C. It was merged into 1.8.6, replacing the old thread.rb implementation, but the version that was merged had a couple serious bugs. So -- now I release fastthread 1.0, which is basically the Ruby 1.8.6 version with

== NOW A new version of fastthread, the library providing better implementations of the classes in thread.rb, has been released. Please note that fastthread is only for Ruby 1.8, not JRuby or any other Ruby implementation (most of them don''t need it anyway!). == WHY The existing implementation of Mutex, Queue, etc. in thread.rb is slow. fastthread''s is faster (and bypasses

Hi All, I have an app making extensive use of Mutex and was concerned about the memory leak I have read about. I saw some sample code to reproduce the problem here: http://pastie.caboo.se/10194 So I thought I would run it myself to see the problem. I do not see a memory leak when using the sample code, but if I require "fastthread" before "thread" using fastthread (0.6.4.1)

Is anybody testing mongrel on ruby 1.9. I just tried installing mongrel on trunk 1.9 and trunk rubygems and got this error compiling fastthread: /Users/stephen/dev/ruby/1.9_trunk/bin/ruby extconf.rb install mongrel --no-rdoc creating Makefile make gcc -I. -I/Users/stephen/dev/ruby/1.9_trunk/include/ruby-1.9/i686-darwin8.10.1 -I/Users/stephen/dev/ruby/1.9_trunk/include/ruby-1.9 -I.

With Mongrel 0.3.18, I have not seen a single one of the hangs that I have been grousing about for the past N weeks. Thanks MenTaLguY and Zed! Q: Mongrel loads fastthread, Mongrel loads Rails, Rails loads OCI8, OCI8 requires ''thread''. That means OCI8 is using fastthread too, right? Steve