* Gemfile updated to set proper versions of supporting gems for doc generation
* Fixes to load_yaml in Config
* OCSP handling extensively refactored and most of the logic moved into the r509 OCSP responder project.
* Cert#subject_component no longer improperly upcases elements
* SAN is now supported in self-signed certificates
* Cert#san_names returns an empty array if no san_names exist
* Cert#fingerprint is now an available method
* Cert#subject_names returns a concatenation (de-duped) of CN and SANs
* General refactoring in several areas to improve code quality
* Csr now takes :san_names in constructor instead of :domains. This is more consistent
* Files renamed to lowercase to match Ruby conventions
* Cert#in_validity_range? method added
* Fixed some order dependent tests

The majority of work went into improving the OCSP codebase, which was moved into the r509-ocsp-responder project, but that’s a subject for another blog entry!

Check it out, file issues, fork, and contribute!

These scripts assume you have rspec writing to rspec_results.html. To do this by default add a .rspec file in your project dir with “-f doc -f h -o rspec_results.html” inside.

pre-commit

#!/usr/bin/env ruby
require 'pty'
html_path = "rspec_results.html"  
#PTY.spawn trick from
#http://stackoverflow.com/questions/1154846/continuously-read-from-stdout-of-external-process-in-ruby
begin
	PTY.spawn( "rake spec" ) do |stdin, stdout, pid|
	begin
		stdin.each { |line| print line }
	rescue Errno::EIO
		end
	end
rescue PTY::ChildExited
	puts "The child process exited!"
end
 
# find out how many errors were found  
html = open(html_path).read  
examples = html.match(/(\d+) examples/)[0].to_i rescue 0  
failures = html.match(/(\d+) failures/)[0].to_i rescue 0  
if failures == 0 then
	failures = html.match(/(\d+) failure/)[0].to_i rescue 0  
end
pending = html.match(/(\d+) pending/)[0].to_i rescue 0  
 
if failures.zero?  
  puts "0 failed! #{examples} run, #{pending} pending"  
  puts "View rspec results at #{File.expand_path(html_path)}"  
  sleep 1
  exit 0
else  
  puts "\aDID NOT COMMIT YOUR FILES!"  
  puts "View rspec results at #{File.expand_path(html_path)}"  
  puts  
  puts "#{failures} failed! #{examples} run, #{pending} pending"  
  `open #{html_path}`
  exit 1  
end

prepare-commit-msg

#!/usr/bin/env ruby
html_path = "rspec_results.html"
# find out how many errors were found  
html = open(html_path).read
examples = html.match(/(\d+) examples/)[0].to_i rescue 0
failures = html.match(/(\d+) failures/)[0].to_i rescue 0
if failures == 0 then
        failures = html.match(/(\d+) failure/)[0].to_i rescue 0
end
pending = html.match(/(\d+) pending/)[0].to_i rescue 0
 
 
message_file = ARGV[0]
message = File.read(message_file)
index = message.index('# Please enter the commit message for your changes. Lines starting')
message.insert(index-1, "\n\n#{failures} failed! #{examples} run, #{pending} pending")
open(message_file,'w') { |f|
        f.puts(message)
}

var debug = false;
 
var sendChat = false;
 
logger('loading userscript');
 
function bindDOM() {
    logger('binding');
    $('.messages').bind('DOMNodeInserted',parseChat);
    $(window).blur(function() {
        sendChat = true;
    });
    $(window).focus(function() {
        sendChat = false;
    });
}
 
function parseChat(event) {
    var message = event.target;
    var author = $(message).find('.speaker').text();
    var body = $(message).find('.text').text();
    if (body.indexOf('started playing') == 1) {
        var artist = body.match(/by (.*)/)[1];
        var song = body.match(/"(.+)"/)[1];
        logger('growling now');
        logger(artist);
        logger(song);
        showGrowl(artist,song);
    } else {
        body = body.substr(2);
        if (sendChat) {
            showGrowl(author,body);
        }
    }
}
 
function showGrowl(title,description) {
    window.fluid.showGrowlNotification({
        title: title, 
        description: description, 
        priority: 1, 
        sticky: false,
        identifier: "sh.langui.turntable"
    });
}
 
function idlePreventer() {
    logger('invoking idle preventer');
    $('.addSongsButton').click();
    $('.cancelButton').click();
}
 
function logger(data) {
    if(debug) {
        console.log(data);
    }
}
 
setTimeout(bindDOM,5000);
setInterval(idlePreventer,300000);

You’ll need a licensed version of Fluid to use this userscript.

chflags nohidden ~/Library

Thanks to Matt Pennig for the command.

I like to use kcachegrind for doing profiling of my ruby code via ruby-prof. This works fantastically if you’re on a platform that has KDE installed. However, most of my development is done on OSX, and while you can install kcachegrind via macports, it takes hours and hours because it has to build KDE, as well. Much to my surprise, the fine folks who wrote kcachegrind also made a QT version, qcachegrind. I was able to build this on OSX in about 10 minutes without too much effort, only having to install QT and GraphViz. Yippie!

I should note that I’m running OSX 10.6.7, with Xcode 4. My default gcc/g++ version is 4.2. I’m sure it will build just fine on earlier versions of Xcode, but I haven’t tested it.

Step 1: Install QT

You could do this via “brew install qt” if you have homebrew, but this takes a long time, so I downloaded the binary distribution of version 4.7.3 for OSX 10.5/10.6 from this page. Installing is easy: open up the dmg, and install QT via the mpkg file contained within.

Step 2: Install Graphviz

Second, you should install Graphviz so that qcachegrind can generate pretty call graphs for you. Like before, you could install this via “brew install graphviz”, but this also takes a really long time and I’m super impatient, so I just downloaded the latest binary installer from this page.

sudo ln -s /usr/local/bin/dot /usr/bin/dot

Step 3: Building qcachegrind

This is actually simple. Check out the source code for kcachegrind and switch to the qcachegrind directory:

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdesdk/kcachegrind kcachegrind
cd kcachegrind/qcachegrind

You build the application by running ‘qmake’, a QT utility that can generate a boring-old Makefile, if we ask it nicely enough. By default, qmake wanted to build an xcode project on my box. I pointed it at spec profile that generates a Makefile that will build using g++, and things seemed to work fine. You can see all the profiles available in this directory: /usr/local/Qt4.7/mkspecs. This command also managed to spit out a whole bunch of errors and warnings, yet everything seemed to build properly.

qmake -spec 'macx-g++'
make

Step 4: Enjoy!

You should now have a beautiful little “qcachegrind.app” sitting in your build directory. You can run this directly via “open qcachegrind.app”, or you can drop it in your /Applications directory for easy access.

Update (Aug 30, 2011):

• I removed the step where I would apply a patch that added the ability to open any file name. The qcachegrind source has since been updated to include a functionally identical change.
• There are several comments about installing Qt via brew, and trying to build qcachegrind using that, yet failing. John Rood, looking to enable other gluttons for punishment, suggested installing Qt like so will get you on your way

  brew install qt --with-qt3support

  (I haven’t tested this out, myself).

• For those who have installed Qt via brew and are having problems: try uninstalling it if you’re not using it for anything else (‘brew uninstall qt’). You may or may not have to reinstall the binary version, afterward; I’m not sure.

Fortunately the extension for Chrome required only minimal changes to get it working in Safari. The most significant change is that the Safari extension uses a toolbar button to activate. The fork is available on Github and supports Chrome and Safari. Hopefully someone finds it helpful!