Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Latest hpricot installed always loaded on rake tasks, despite config.gem version

#2469

Despite which hpricot version is on gem.config at environment.rb, the latest version is always loaded on rake tasks.

The problem seems to at misk.rake, as it requires 'active_support' which then loads the latest hpricot gem before the environment is loaded.

http://github.com/rails/rails/bl...

Reported by samuel365 (at gmail) · April 9th, 2009 @ 10:31 PM

State: stale
Milestone: 3.x
Assigned to: nobody
Importance: none

Activity

  1. Matt Jones
    Matt Jones

    Which version of hpricot do you have installed? More recent versions include fast_xs, which most modern versions of rake will attempt to load if available. When I've seen this in the past, that's been the source of this issue.

    June 6th, 2009 @ 08:48 PM

  2. samuel365 (at gmail)
    samuel365 (at gmail)

    I'm now using the latest version (0.8.1), so this is not a problem to me anymore.

    But as I said, the problem seemed to be on that line... as there it was loading 'active_support' and then the latest version of hpricot before the environment gem configs were loaded.

    Does that "require 'active_support'" really belong to there?

    June 6th, 2009 @ 09:04 PM

  3. Mislav
    Mislav
    • Tag set to activesupport, bug, fast_xs, hpricot, incompatibility, load

    Rails really shouldn't try to load the "fast_xs" extension. Pitfalls are described on Pivotal labs blog (and comments)

    October 8th, 2009 @ 02:20 PM

  4. Jeremy Kemper
    Jeremy Kemper
    • Milestone changed from 2.x to 3.x

    May 4th, 2010 @ 06:48 PM

  5. rails
    rails
    • State changed from new to open
    • Importance changed from to

    This issue has been automatically marked as stale because it has not been commented on for at least three months.

    The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

    Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

    February 26th, 2011 @ 12:00 AM

  6. rails
    rails
    • State changed from open to stale

    February 26th, 2011 @ 12:00 AM