Sunspot.session.session.send(:connection).update RSolr::Message::Generator.new.build { |b| b.optimize }

Anyone know of a simpler one?

 
dyld: Library not loaded: /usr/lib/libsqlite3.dylib
Referenced from: /System/Library/Frameworks/Security.framework/Versions/A/Security
Reason: Incompatible library version: Security requires version 9.0.0 or later, but libsqlite3.dylib provides version 1.0.0

Web searches produced a lot of information including some workarounds that didn’t. Finally I read that Selenium-RC 1.x has some hardcoded paths in it that mean it won’t work with Snow Leopard, and you need to get the Selenium-RC 2.x jar (alpha at this time). The easiest way to do this is to install the selenium-rc gem that Pivotal packaged.

[Update]

More recently, have been having issues running Cucumber/Webrat/Selenium on new MacOS systems. It turns out that Webrat contains an out-of-date version of the selenium server jar file. If you are using Webrat, you need to copy the good selenium-server.jar from the selenium-rc package over the version contained in the Webrat gem. Something like:

 
sudo cp /Library/Ruby/Gems/1.8/gems/selenium-rc-2.2.1/vendor/selenium-server.jar /Library/Ruby/Gems/1.8/gems/webrat-0.7.0/vendor/selenium-server.jar

1. Cucumber gem is attached to project: RM | Settings | Ruby SDK and Gems | Attach gems.
2. If you edited *.feature files in early version of RubyMine it may be mapped on Text file. So you should check that *.feature extension is mapped on “Cucumber scenario files” in RM | Settings | File Types | Recognized File Types.

per Roman at JetBrains

Which also provoked a great comment.

First spotted in a teachmetocode.com screencast.
Which references Spike’s original post.

When building an iCalendar (RFC 2445 / RFC 5545) feed, if you want to subscribe to that feed with Google Calendar, and you want to give your calendar a name, Google Calendar accepts the X-WR-CALNAME extension to the iCalendar standard, but it will only allow a text name if you add the parameter VALUE=TEXT, i.e.

X-WR-CALNAME;VALUE=TEXT:My Calendar Name

1. Multiple people are developing on the same project, pushing commits into the same (e.g. GitHub) repo.
2. Developer A is working, and commits locally.
3. Developer B converts a folder into a Git submodule.
4. Developer A tries to git pull… BOOM – unresolveable conflict, local repo is left in a mess.

The problem is that because Developer A has a local commit, this forces a merge. Git merge has absolutely no idea how to resolve a conflict between a folder and a submodule.

To fix this, divide the merge into two parts, so you can separate the actions of removing the folder, and adding the submodule:

• Figure out the SHA of the commit where the folder was removed; let’s call it abcdef (as far as I am aware you cannot remove a folder and add in the submodule in 1 commit, so there will always be 2 commits here).
• Reset your local repo back to HEAD
• Merge up to that commit: git merge.
• Merge the remaining commits

i.e.

 
git reset --hard HEAD
git merge abcdef
git merge

Alternatively, if only a few commits have been made and you are very lazy, you can do the following:

 
git merge origin~5
git merge origin~4
git merge origin~3
git merge origin~2
git merge origin~1
git merge

Note that if you don’t have local changes, this issue does not occur as the fast-forward mechanism just applies all the commits in sequence and everything is cool.