similar to: All the best to Carlhuda

Hello Rails people. I tried to push a Rails 3.1 app ( created using cedar stack) to Heroku and I encountered the following error Installing sqlite3 (1.3.4) with native extensions Unfortunately, a fatal error has occurred. Please report this error to the Bundler issue tracker at https://github.com/carlhuda/bundler/issues so that we can fix it. Thanks!

Found a great site for REALLY CHEAP airfair! I got 80% off a flight to Japan from Canada! Infact they have 80% of to all destinations! A must SEE. Best deals on really cheap airfair at http://www.buy-cheap-airline-tickets.info/Cheap_Airfare.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails:

I''ve discovered what I''m pretty confident is unexpected behavior in accepts_nested_attributes_for, and am developing a patch, but I''ve encountered a question about how the core team would prefer the implementation to look. Here''s the bug: when assigning to a belongs_to relationship (and I believe one-to-one, but I haven''t verified yet) if you mark the

Hi Using today''s rails edge with ruby 1.8.5 (2006-12-25 patchlevel 12) [i386-freebsd6], I''m experiencing a serious bug which doesn''t happen with rails 1.2.3: sending a 1026 char length data with POST method to / foo/bar sets the params to a strange { "/foo/bar" => nil, "controller" => "foo", :action => "bar",

Was going to have a variety of request params sent in and use a class_attribute that would define types of request parameters that are allowed. strong_parameters wouldn''t be too much trouble in such a case if it would allow me to manually permit some attributes (dynamically determined) in the controller but allow strong_parameters to enforce security of others. Is this something

Got a URL on that video? On 2011-06-26, at 8:32 AM, rubyonrails-core+noreply@googlegroups.com wrote: > Today''s Topic Summary > Group: http://groups.google.com/group/rubyonrails-core/topics > > initialization documentation [1 Update] > Topic: initialization documentation > Steve Schwartz <steve@alfajango.com> Jun 25 11:41AM -0400 ^ > > Neeraj Singh has

Hi all, I talked to Aaron briefly about this at RailsConf, but I just wanted to bring this up here before I start working on it in case anyone objects. I will be looking into moving the "Plural version of the model detected, using singularized version. Override with --force-plural." warning and the associated flag into the model generators. Currently this is only in the resource (and

I''m trying to figure out how attachments are supposed to work with MIME type-based responses. What makes attachments special is that in many cases they are allowed to be arbitrary files. It would be too restrictive to require that all possible types are registered (Mime::Type.register). Let''s say for GET requests on an attachment resource I want to return metadata if the

I can''t get a multiplatform bundler Gemfile to work in JRuby with a simple raisl3 app. See: http://github.com/carlhuda/bundler/issues/issue/502/#comment_336670 for more details. The only way to start the rails app in jruby seems to be to comment out the platform-specific parts for other Ruby VMs. -- You received this message because you are subscribed to the Google Groups "Ruby

Shouldn''t helper: all work in ActionMailer? Similar issue was discussed before: https://rails.lighthouseapp.com/projects/8994/tickets/3945-helper-all-on-by-default But as of rails 3.2.11 the problem is still there: class ContactMailer < ActionMailer::Base helper :all end Produces: LoadError (Missing helper file helpers/all_helper.rb): While it should load them all, since

The problem is: ActionMailer doesn''t include view helpers by default, and helper :all makes it to look for all_helper.rb Similar issue was discussed before: https://rails.lighthouseapp.com/projects/8994/tickets/3945-helper-all-on-by-default https://github.com/rails/rails/issues/928 https://github.com/rails/rails/issues/1582 Steve Klabnik told me to post here:

Requesting /attachments/1.all does not work in Rails 3. It was changed here: https://github.com/rails/rails/commit/7e280c3bff8ac25f1c1938aeaeb1d0b4c0fbb726 The use case is a show action such as: def show @attachment = Attachment.find(params[:id]) respond_to do |format| format.html format.any { download } end end The pros of using this approach is take advantage of Cancan and

Meet Singles In Your Area Arabs, American, Russian Singles >From All Over The World Waiting For You At Frinzo Join Frinzo And Start Your Love Life Now Join Frinzo Now For Free !! Enjoy exciting features offered by our site: * Profiles with galleries and audio/video * Personal weblogs and friends-lists * Audio/video chat, IM and recorder * SPAM-blocking and anti-SPAM system * ZIP-codes

... to fix a problem with PostgreSQL reconnect after connection loss & put test coverage in place to keep it working in the future. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/EecNy-qyKwgJ. To post to this group, send email to

Hi, I am trying the following in Ruby using InstantRails 1.7 on WindowsXP Publication.find(:all, :include => [:doc_type, :release_state] ) but I get the error: OCIError: ORA-00904: "DOC_TYPES"."PUBLICATION_ID": invalid identifier: SELECT publications.id AS t0_r0, publications.docid AS t0_r1, publications.doc_type_id AS t0_r2, publications.title AS t0_r3,

By default with Rails, Postgres will return the id of a newly inserted record using returning "id". Sometimes when working with Postgres, tables will have triggers on them that modify the row''s data while being saved. As such, it would be great to also provide an option for Postgres to also let insert/updates and deletes to use returning * (which will return the row as it

Hi guys, I''ve fixed a pretty annoying bug in Action caching that is detailed here: https://rails.lighthouseapp.com/projects/8994/tickets/6480-action-cache-filter-code-incorrectly-renders-nil-response-body-if-response-is-non-cacheable Would appreciate testers or a direct commit if it checks out :) Cheers, Chu Yeow -- You received this message because you are subscribed to the Google

I''m doing some work where I want to rescue ActiveRecord::RecordNotSaved from a save! call nested deep in the code. The thing is there could theoretically be failures here I want to pass through, and I want to inspect the record in order to decide. I figure a custom initializer on the exception class and a couple quick patches here and there in the code would make it minimally

HI all, A patch of mine from a few weeks ago made String#mb_chars use a proxy class for 1.9.x as well as 1.8. This proxy overrode some methods that were buggy in 1.9.1. but that work in 1.9.2. Since Rails officially now only supports 1.8.7 and 1.9.2, these methods should definitely no longer be overridden. Here''s the LH ticket:

Sorry if this question isn''t really "Ruby on Rails: Core" material. I feel it is, at least kind-of (also, I first tried asking in "Ruby on Rails: Talk" to no avail.). So, while writing a gem (engine) for rails, I found that I needed to have my app (in a pre-filter) directly query the router. In the "old" days, this was done using