Glad You're Ready. Let's Get Started!

Let us know how we can contact you.

Thank you!

We'll respond shortly.

Standup 05/19/2009: Tool Annoyances; Better Firebug SASS Support

Ask for Help

“Who is getting svn: Server sent unexpected return value (403 Forbidden) in response to PROPFIND in SVN?”

Lots of people! This is a known bug when a SVN project has to traverse the repository using more than one user. Check out subversion: Issue 3242.

“Has anyone gotten ImageMagic to work with Phusion Passenger on CentOS?”

It seems to work with Mongrel, but not Passenger.

“Who is getting svn: Server sent unexpected return value (403 Forbidden) in response to PROPFIND in SVN?”

Interesting Things

  • Firebug 1.4 – Alpha

    • It has some cool new features, such as showing you CSS comments — handy for SASS debugging! Works in conjunction with enabling SASS line numbers in the CSS output.
    • It also supports FireDiff, which “records all of the changes made by firebug and the application itself to CSS and the DOM”.
  • NewRelic Side Effects? We have some background processes that get kicked off from after saves of some of our ActiveRecords. These processes use Active Resource to post back updates to these records. Unfortunately the transaction that creates the record initially doesn’t seem to have completed before the first post-backs attempt to update them. (race condition). After trying a bunch of stuff we randomly removed the NewRelic plugin and all of the sudden we had no more race conditions. Is the NewRelic plugin holding the DB transactions open too long?

  • MySQL index sample size: We discovered that MySQL’s ANALYZE TABLE uses a fixed sample size from the index regardless of the size of the table and thus can have really incorrect cardinality and which could lead to it choosing the wrong index. Also ANALYZE TABLE gets run often (opening new connections, first read of table) and due to the problem mentioned above can cause the system to switch from using the right index to the wrong index each time you look at it.

  1. I downloaded and installed the new firebug, but don’t see any CSS comments :-( Could you post or send me some more details so I could blog about this?

  2. Joe Moore says:

    Chris — This is how we got comments to work on one project; make sure you put this in your Rails::Initializer in environment.rb.

    config.after_initialize do
    require ‘haml’
    Sass::Plugin.options[:line_comments] = true
    Sass::Plugin.options[:line_numbers] = true

  3. Thanks Joe, sorry if I wasn’t clear. The comments are in my CSS, but I don’t see them in Firebug. I’m running the latest version (1.4X.0a28). Maybe you could post a screenshot of where they appear and anything you had to do to enable them?

    Much appreciated.

  4. Hey Joe,

    I’m hitting the same problem as Chris (I’m on Firebug 1.5x.0a24). I can only see the comments when I view a CSS file, then hit ‘edit’… Clunky!

Post a Comment

Your Information (Name required. Email address will not be displayed with comment.)

* Copy This Password *

* Type Or Paste Password Here *