similar to: Is Rails Logger Thread Safe?

I feel the need to protest about a disturbing trend in the vibrant RoR community - name dilution. ActiveRecord is called that precisely because it is that. The name come from Martin Fowler, and it expresses a class which is a database record, only _active_ - that is with methods & behaviors (unlike a classical database record, which is completely passive.) If you look in the

I have been unable to install Microsoft Office 2000 under wine on several Fedora Linux machines. The problem seemed to start with the June 2004 release of wine and has persisted for every version I have tried up to and including the latest 12/01/2004 version. I have tried both RPM install and compiling from source with similar results. I have one machine running the May 2004 wine that

I am trying to leverage the daemons gem but I am confused about the proper way to set up logging. I am able pass options which configure stdout to go to a log file but it seems like all calls to Rails.logger are disabled as I see the following message in my output: usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/ active_support/buffered_logger.rb:99:in `write'': closed

I'm trying to install Office XP on Fedora 3, with the 12/1/2004 wine build from the source. I tried the suggestions given by Ronald Nave on Dec 2/2004 (installing DCOM98, windows installer), but to no avail, and I get the following errors, any help/suggestions are appreciated! ------------------------------------ fixme:wininet:FindFirstUrlCacheEntryA ((null), 0x7fd943b0, 0x5b41ea38): stub

I was reading here and there about the differences between Merb and Rails [1] and became curious about statements such as this: > It is threadsafe with configurable Mutex Locks (Routing is also > threadsafe) Having mucked with the routes system, I had this awful feeling that I don''t understand threading well enough to know if my contribution is "thread safe".

Hi all, I''m running into a very strange but incredibly annoying problem that I just can''t seem to solve. The exception is occurring from a seemingly innocuous line in my code, a simple ''logger.warn("some debug information")''. The backtrace follows: SecurityError (Insecure: can''t modify array)

Hi There Is active record 3.1.1 supposed to be threadsafe? In other words, should the following (concurrent access to a model) work? Thread.new do MyModel.where(some_condition).first end Thread.new do MyModel.where(some_condition).first end I ask because upon the answer, it depends which component should handle synchronization, and in consequence, which component to patch/fix. A bit of

Hey, We hit a bug today because Arel::Visitors::ToSql is not threadsafe. Here is what is happening: Arel::Visitors::ENGINE_VISITORS is a cache of visitors instances. These instances are not inherently threadsafe because it contains state ''@last_column'', ''@connection'' that is shared between threads. The other variables ''@pool'',

Hey I am playing with a LOT of threads right now, and I want to know if the threads all need their own little vorbis encoders running in them or what exactly is threadsafe in vorbis? So here are the functions that would be called from many threads of with buffer = vorbis_analysis_buffer( &m_vorbisDsp, 4*DATA_CHUNK_SIZE ); vorbis_analysis_wrote( &m_vorbisDsp, dataLength/dataSize );

On Fri, Mar 27, 2009 at 2:25 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: > On Fri, Mar 27, 2009 at 3:48 PM, Evan Cheng <evan.cheng at apple.com> wrote: >> Run with -debug-only=jit. > > OT: I take it the recommended model for tools that embed LLVM is for > them to accept all of LLVM's command line arguments on their own > command lines? Well, sort of...

Hi I have some questions regarding threads in Mongrel and Rails. According to the FAQ: "Ruby on Rails is not thread safe so there is a synchronized block around the calls to Dispatcher.dispatch. This means that everything is threaded right before and right after Rails runs. While Rails is running there is only one controller in operation at a time." Isn''t this going

Hi all, Both the rails book (1st Ed) and the docs on the rails site (*and* the Mongrel FAQ) tell me that rails (& ActionPack /ActiveRecord) is not threadsafe. Since I need lots of worker threads in the app I''m working on (details at the end of this mail) this poses quite a problem for me. Is the lack of thread safety a conscious design decision (kind of understandable for rails

I am running jruby (1.7.3) & rails 2.3.17 application whose apis are exposed to outside app. When I add "config.threadsafe!" in my development.rb/production.rb & hit lot many api requests in a second then I am getting following errors randomly for some of the api requests: 1. TypeError (NilClass can't be coerced into Float) 2. RuntimeError (can't add a new key

Hi all. I am creating a plugin that uses the daemons gem to run some code in the background. In that code, I call Rails.logger.info "message", but receive the following error. /opt/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/active_support/buffered_logger.rb:99:in `write'': closed stream (IOError) Anyone seen this before and have any idea what''s going on?

>From http://blog.codefront.net/2008/01/02/whats-new-on-edge-rails-the-pilot/ A native Mongrel handler has been introduced. This is so that it can be worked on independent of Mongrel?s release cycle (the Rails handler is currently in the Mongrel codebase). Jeremy Kemper (bitsweat) has already made a minor performance improvement by moving the mutex from the handler itself into the dispatcher.

I''m creating a message queue system, (think JMS message queue) Basically, I''ll be firing off an http request as soon as a row appears in a database. Now in past implementations I''ve done the following. 1. Polled the database every 0.10 seconds. 2. If something was there to work, I''d tag it as complete. 3. Create a separate thread. (no further database hits

Hi Running ./configure --prefix=/whatever I got stuck with checking for pkg-config... /usr/bin/pkg-config checking shout/shout.h usability... no checking shout/shout.h presence... no checking for shout/shout.h... no configure: error: must have libshout installed! Having edited configure line 20056 and changed shout/shout.h to /usr/include/shout.h , I run into the next problem:

On 2009-11-01 08:40, Jeffrey Yasskin wrote: > 2009/10/30 Török Edwin <edwintorok at gmail.com>: > >> On 2009-10-29 23:55, Jeffrey Yasskin wrote: >> >>> On Thu, Oct 29, 2009 at 2:30 PM, Nicolas Geoffray >>> <nicolas.geoffray at lip6.fr> wrote: >>> >>> >>>> Hi Jeffrey, >>>> >>>>

[caution: this is an IPv6 e-mail address. if you don't have IPv6-capable mail then best keep replies on the list only] > >existing getipnodebyname() call fails with IPv4 on my machine)... > Well, if you can make it work properly - send your patches in, please. The following enhancements to src/net/resolver.c (which looks identical across icecast, ices, libshout, and who knows what

Hi! As you might remember I''m having a problem of backgroundrb stopping calling my workers after some period of time. I tried adding logging to backgroundrb source code but it didn''t help. So, after digging through internet I''ve found several gdb tools and here''s what I''ve discovered: After attaching to a backgroundrb ruby process it turns out that it