Libxml in production

Ruby
1

I’m having an issue loading libxml in production. On the same machine:

Loading production environment (Rails 2.3.3)

require ‘libxml’
=> false

Loading development environment (Rails 2.3.3)

require ‘libxml’
=> []

The difference between my development.rb and production.rb that seems to
make the difference is this:

#production
config.cache_classes = true

#development
config.cache_classes = false

Anyone know why this might be the case?

2

I’m having an issue loading libxml in production. On the same machine:

Hi Vince,

If the return value of require is the issue then you don’t have one ;).
‘require’ has been known to return many things. Is the libxml you’re
requiring not working?

kaspar

3

Kaspar S. wrote:

If the return value of require is the issue then you don’t have one ;).
‘require’ has been known to return many things. Is the libxml you’re
requiring not working?

No, unfortunately not… I have a rake task that uses the vigetlabs-garb
gem which seems to be failing production but not in development.

The cache_classes difference seems to be the cause though I can’t be
certain it’s related to libxml. My only guess to this effect is that I
can’t require garb in production either and garb requires libxml.

4

On Tue, Aug 4, 2009 at 4:57 PM, Eric H. [email protected] wrote:

Loading development environment (Rails 2.3.3)
true value) no matter what.

Have you opened a bug for this?
Thanks,
Rob

5

On Aug 3, 2009, at 20:19, Vince W. wrote:

I’m having an issue loading libxml in production. On the same
machine:

Loading production environment (Rails 2.3.3)

require ‘libxml’
=> false

Loading development environment (Rails 2.3.3)

require ‘libxml’
=> []

Rails broke require*. It didn’t load libxml in either case.

  • Kernel#require returns either true or false, false when the feature
    was already loaded. After loading rails, Kernel#require returns an
    Array (a true value) no matter what.
6

On Mon, Aug 10, 2009 at 3:13 PM, Ryan D.
[email protected]wrote:

would it matter?

I’ve opened bugs on semantics that rails broke and core hasn’t even batted
an eye at it.

The core team has gotten better with bugs like this. Maybe they would
surprise you.

7

On Aug 10, 2009, at 07:51 , Rob S. wrote:

Rails broke require*. It didn’t load libxml in either case.

  • Kernel#require returns either true or false, false when the
    feature was
    already loaded. After loading rails, Kernel#require returns an
    Array (a
    true value) no matter what.

Have you opened a bug for this?

would it matter?

I’ve opened bugs on semantics that rails broke and core hasn’t even
batted an eye at it.