Ask for Help
“We’re trying to get the Google Docs API working on our project but we keep hitting unauthorized/bad request responses. Help!”
One thought: some ruby OAuth implementations are known to fail. Try shelling out and running a command line OAuth to make sure this isn’t an incompatibility with your ruby OAuth library.
Ruby is slower than node.js.
Two loops and a square root turns out to be a recipe for ruby slowness. The v8 engine wins again!
Ubiquitous Singaporean Chile (”Sambal Chilli”) now available – briefly – in the San Francisco lounge (courtesy of Nate Clark).
To quote Nate: “It’s usually Shrimp based but this is the Vegetarian version which I find to be pure and good.”
Gogaruco sign up is now open.. and the early bird tickets are gone. Sign up soon!
(Title: Standup 7/18/2011: I Bless the Rains Down in Africa)
Ask for Help
“I want a super-lightweight rack-based CMS/blogging setup. Any thoughts?”
Try out Toto a light-weight git-powered blog engine.
Ask For Help
We’re running into a problem where MongoMapper is somehow setting the value of a ‘many’ relationship to null in the parent document, which then makes MongoMapper blow up when trying to load the parent doc from mongo. There’s an argument to be made that MongoMapper shouldn’t blow up, but it’s understandable that it’s confused when the key exists – here’s a spec demonstrating what happens when the null exists in
The big question is what is creating these values. All our inserts are through MongoMapper, so we’re blaming a bug we can’t reproduce in MongoMapper for the moment.
How to fill up your Redis instance (part 2). Resque stores all records of failed jobs – including full backtraces – on Redis. Pushing a bug that generates lots of these can rapidly fill up your Redis instance. The solution? Send your Resque errors directly to hoptoad (which has better error management infrastructure anyway).
To get it running:
$ gem install fuubar
$ repsec --format Fuubar --color spec
Kevin Kelly, Founding Executive Editor of Wired Magazine and noted technologist will be at Pivotal Labs tomorrow (Thursday January 13th, 2011) at 6:30pm to talk about his latest book What Technology Wants.
For details look here.
Ask for Help
“Does Active Record have batched insert? I need to dump 10,000 rows into the database in process and I don’t want it to take 45 seconds.”
The upshot: use a raw SQL
For a day as interesting as today (1/11/11 anyone?) there were surprisingly few interesting things of note.
Ask for Help
A pivot asks: “Anyone know anything about data warehousing & ETL?”
A handful of pivots raise their hands.
Another pivot asks: “How about Radiant CMS?”
More pivots raise their hands.
before(:all) in Rspec raise an exception the return code coming back is 0. This breaks CI.
before(:suite) — this runs, just once, before all other befores.
In MongoMapper if you have a key (field) with type Hash, and set a default value, that default value points to a reference instantiated at class loading time. Instances inherit a reference to the same object (instead of a copy) which means any changes to to an instance with the default value propagate to all future instances using default. The immediate work-around is to wrap the value in a lambda, but within hours of reporting the bug there was a fix on HEAD.
splunk users meetup here (at Pivotal Labs in SF) on Wednesday January 12th. More details on meetup.com.
A global Rspec
before(:each) defined in
spec_helper.rb apparently does not have access to fixtures. One admittedly klunky workaround involves
config.include a Module, and then a
class_eval inside the included hook of the module. This has the unfortunate property that the
before(:each) will run multiple times, once at every test level, instead of just once at the top level — though this can be fixed by looking at the length of ancestors in the included hook in the module and only doing the
before(:each) if you are on the first level. Others argued that fixtures should be available in a
before(:each) and that the problem is a load-order issue.