search for: timetrack

I started what I thought was going to be a 30 minute project on the train this morning to write a little timetracker for myself. Amongst other things (don''t have a model called Task as it conflicts with Rake at the moment, don''t have a model called Action as it disappears in the hash when you submit a form :-), I had to use Webrick as Lighty complained about an unknown variable CWD. This...

...any (Oasis Digital) wants to hire a developer to create a work time tracking system, using Ruby, Rails, and MySQL. This will be an offsite / outsource project, not a full time position. You can download a project description, including a ?podcast? audio commentary, here: http://oasisdigital.com/timetracker/ I would ideally like to have development start by the end of January 2006, though it may take longer than that to find the right developer for the work. There is contact information in the download file, to propose your services or to ask questions. Kyle Cordes www.kylecordes.com www.oasisd...

...also loaded directly from Rails itself, not going through the Apache proxy. I think that eliminates both the network and Apache as sources of the delay. I think the delay is somewhere in Rails itself. Here''s my logs. First, the commands and date/time stamps from the prompt. [litho:~/apps/timetrack/current/log] jmartin$ date ; curl -b "cookie:val" http://127.0.0.1:10100/activity/list >/dev/null ; date ;curl -b "cookie:val" http://127.0.0.1:10100/activity/list >/dev/ null ; date Tuesday, February 1, 2011 2:28:38 PM GMT % Total % Received % Xferd Average Speed...

...lly are two blank lines after "Store listing was".] Failure Mode #2: script/ferret_speedtest2_reader:30:in `initialize'': IO Error occured at <except.c>:93 in xraise (IOError) Error occured in fs_store.c:127 - fs_each doing ''each'' in /Users/scott/dev/ruby/timetracker/tmp/ferret_speedtest_index: <Too many open files> from script/ferret_speedtest2_reader:30:in `new'' from script/ferret_speedtest2_reader:30:in `run_test_query'' Meanwhile, if I try eliminating this second failure mode by explicitly calling close on the IndexReader before...