similar to: Testing Explain Logger Output

We still have the program called "KillTheDoctor" [1] in our source tree. Its original intention was to stop requiring user interaction for crashing regression tests under Windows (infamous Dr. Watson, nowadays "[program] has stopped working" [2]), I don't think it is useful anymore. It's also a very hacky approach, as admitted in the source comment itself ("I hate

I''ve seen a few examples of dummy Rails apps (for testing, so they live under test or spec dirs, typically) for use with the Appraisals gem that supposedly work with both Rails 3.x and Rails 4, but they seem hackish and not fully functional. It is somewhat expected, as it is a stripped down Frankenstein monster that is trying to be compatible with various versions of Rails 3 as well

I have installed active admin and also add my model -controller rate_professor there.......I can add/delete/edit data using active admin ...but if I click on submit button of my form in rate_professor controller ... I can see whatever I added in the index page ........but I don''t want to see that one.....I want to find the information(whatever I added by clicking submit button) on

I''m looking for a simple way to integrate minitest/spec with Rails 3.1. Anybody have it working? There''s an older article on MetaSkills about this but it adds stuff I don''t want. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

Hi! First of all, this is my first application on Rails, and i''m stuck at a migration. i created a demo app (the demo_app from michael hartl''s tutorial) as usual: rails new demo_app, rails generate scaffold User name:string email:string, and when i do rake db:migrate, this stack appears: rake db:migrate --trace ** Invoke db:migrate (first_time) ** Invoke environment

Not getting any love (tender or otherwise) on my pull request<https://github.com/rails/rails/pull/7035>so I thought you folks might like to chip in. What do you think? #cast and #cast! allow you to declare a mapping from generated column names to simplified database column types (i.e. those used in migrations). This way scopes with columns generated in their select lists can also include

Can someone please post or refer to detailed instructions for getting Rails going on Snow Leopard with ODBC to a MS SQL server? The Rails Wiki is pretty bad and I can''t seem to get it going! Thanks, Tom

Every now and then when I am working on making the SQL Server adapter pass all the ActiveRecord tests, I notice one that looks like a false positive in the core DBs. Here is one case in relations_test.rb. Can someone look at this and just tell me it is normal for other DBs and just odd for SQL Server? Or maybe it is just my understand of some SQL standard. I''m really not that SQL smart.

When calls were made to test 3.0.4.rc1, I followed up a few days afterward for the latest SQL Server adapter. Santiago was nice enough to pick up on my ticket for a calculation bug [1] and got it committed to master [2] and then 3-0-stable [3] so it can make it in the next release. I just ran my test suite on the tag of the repo and it appears these did not make it in the v3.0.4 release. How did

I left ":memory:" in database.yml for testing and the most simple tests in the Agile book do not work (see trace below for test_truth). Since that''s what comes with the distributed database.yml I suppose it''s me doing something wrong. Did someone get SQLite ":memory:" working? How does it grab the schema? -- fxn % rake test_units (in

Hi guys. I''m using a postgreSQL with multiple schemas. To change between schemas I use the ''SET schema TO ...'' statement. That works ok in rails 3.0. Rails 3.1 uses prepared statements and does not take into account the ''schema_search_path''. This is a big problem because the statement is prepared once and then the same prepared statement is executed

Hi, This is just kindof a RoR question, but since you all potentially do the same things as I do, I thought I''ll ask here.. Im trying to use the boolean type in the database. Migrations is no problem, it even converts the 0/1 values from my import CSV to false and true. However, I cannot make the :conditions part of a find work: Loading development environment (Rails 2.0.2) >> c

I am getting the following error using sqlite3. If I ran the same query directly in sqlite3 client, the data is saved without error. Same is happening for every table during inserts. SQLite3::SQLException: sessions.id may not be NULL: INSERT INTO sessions ("updated_at", "session_id", "data") VALUES(''2009-09-30 02:28:45'',

I have a simple project created around a very, very simple database: one main table packs with just three rows Column | Type | Modifiers --------+-----------------------------+---------------------------------------------------- id | integer | not null default nextval(''packs_id_seq''::regclass) nombre | character

Is there some reason that the Rails logger doesn''t log nil as the string "nil", like the Ruby logger does? It is a bit confusing. Ruby example: $ cat log.rb require ''logger'' logger = Logger.new(STDOUT) logger.info "test" logger.info true logger.info nil logger.info "end test" $ ruby log.rb I, [2006-11-15T16:45:00.348262 #2058] INFO

Any idea what would cause this? >> icps = Icp.find(:all) ActiveRecord::StatementInvalid: SQLite3::SQLException: unsupported file format: SELECT * FROM icps from c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_recor d/connection_adapters/abstract_adapter.rb:120:in `log'' from c:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_recor

Hi, I am receiving an LLVM Error from a custom 16-bit backend I am creating. I am having trouble understanding the error/problem and how to go about solving it. The error is: LLVM ERROR: Cannot select: t29: i32,ch = load<LD2[%x.addr], anyext from i16> t14, FrameIndex:i16<0>, undef:i16 t7: i16 = FrameIndex<0> t9: i16 = undef In function: mul_add Can anyone provide any

When I try to run my webserver in the production environment I just get an application error message. This is all I can find in the log: ActiveRecord::StatementInvalid /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.1/lib/active_record/ connection_adapters/sqlite_adapter.rb:274:in `table_structure'' /usr/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support/

I wrote the following script to run garbage collection on Backgroundrb workers older than 30 minutes: class WorkerCleaner def self.remove_stale_workers MiddleMan.gc!(Time.now - 60*30) end end I stuck is under /lib in my Rails app and run it using script/runner from a cron job. The only problem I''m seeing is that this script kills my backgroundrb_results and backgroundrb_logger

Hello, When trying to use logger into any RSpec I get: logger anyboundefined local variable or method `logger'' for #<#<Class:0x278bee0>:0x253cdec> Not sure if this is the spected behaviour (haven''t checked under the hood) It was just annoying not having a logger instance available as in Rails out of the tests. -- An?bal Rojas http://www.rubycorner.com