Helps:
How to test a javascript onLoad event in an iframe?
*crickets*
Interesting things:
Google Code Jam is today, some pivots will be taking part on it!
[Standup][SF] 04/13/12 – Google crickets
Friday, April 13, 2012
Monthly Archives: April 2012
Events at Pivotal NYC — Week of April 16th
Friday, April 13, 2012
This week at Pivotal NYC we have some exciting events in the space. RSVP details are included in each event listing. Please take the time to RSVP to the event.
Any questions on these events should be directed to the individual meetups.
Tuesday April 17th
Real Estate Tech Meetup is hosting their Inaugural NYCRETS Mixer. This event will be in the main space and starts at 6:30PM.
Please visit the Real Estate Technology Meetup Site and RSVP if interested.
Wednesday April 18th
On Wednesday the Tech in Motion NYC meetup will be hosting a session on Breaking Stereotypes in Technology
Those interested should visit the Tech in Motion meetup site to RSVP. The event starts at 6:30PM.
Interested in hosting an event at Pivotal Labs NY?
Please contact me: magda@pivotallabs.com
Standup 04/12/2012 -
Thursday, April 12, 2012
Interestings
Chrome JsonViewer plugin – pretty prints JSON useful for debugging. Also some people use Awesome Print for similar functionality
Arel now has distinct, otherwise a work-around like
#scope#.clone.tap { |arel| select_value = [ 'DISTINCT users.*'] }
is usedAmazon released CloudSearch today – an Amazon hosted search service
Helps
- How to use Twitter Bootstrap SASS semantically?
- “span3″ sucks
- “@extend span3″ breaks
Events
- Anyone interested in hardware hacking (arduino, etc…) see Fader or Berger
[Standup][SF] 11 April 2012 – <title>Hello World, I’m a baby</title>
Wednesday, April 11, 2012
Interesting Things
- Google Code Jam. Some clients and Pivots are going to be in the office on Friday for the Google Code Jam. Come out and hack!
- Epics have officially launched on Pivotal Tracker. More information on the Tracker blog
- Free HTML books for babies. Insightful, inspiring, clever, full of Helvetica. We laughed, we cried. If you missed the free copies, check them out online.
Chef cookbook linting with foodcritic
Tuesday, April 10, 2012
There’s a growing movement for testing chef cookbooks, which is great to see. I haven’t gotten to play with them all, but some that I’ve come across are the minitest chef handler, chefspec, and cucumber-chef.
The lowest hanging fruit however is linting, which is where foodcritic comes in. Foodcritic parses your cookbook, and warns you about many common errors.
Food critic will yell at you about all sorts of things – if you are accessing node attributes inconsistently, if you’re passing valid ruby as a not_if string, if you’re using /tmp instead of file_cache_path, and many more. For a full list, see the github pages
Automatically running foodcritic on your public cookbooks is easy with Travis CI. Just add a .travis.yml to your repo that looks like this:
script: "gem install foodcritic -v 1.1.0 && foodcritic -f any ."
rvm:
- 1.9.3
And follow the travis getting started guide. You’ll then get an email if you commit something that isn’t quite up to par.
You can see a pivotal_workstation run on travis. We’ve still got a little ways to go to get to green, but everything it’s telling us are things we’d like to do. (pull requests welcome!)
Standup 04/10/2011: How to succeed in business like a ninja
Tuesday, April 10, 2012
Interesting
- Facebook bought Instagram for $1 billion
Events
Today:
Brownbag Enterprise-Fu or How to succeed in business (like a ninja)
NYC.rb – Lean startup
Wednesday:
Libs@Lunch: book club has been moved to lunch time so more people can come
This week they will be finishing smalltalk best practices and will be choosing the next book
Lean UX roundtable – JB will be speaking, see him for more info or if you would like to attend
[Standup][SF] 04/10/12 – Mind the gap
Tuesday, April 10, 2012
Interestings:
Spacing matters. Leaving a space after a minus and before a number is entirely different from putting the minus right before the number. The former is binary arithmetic and the latter is a unary operator. For example:
[-1, 1, 2, 3].count - 1 #=> 3 (subtracting 1 from the array size) [-1, 1, 2, 3].count -1 #=> 1 (counting the number of occurrences of -1 in the array)
Introducing Epics: They’re like stories, but bigger
Tuesday, April 10, 2012
We’re proud to introduce a brand new feature to Pivotal Tracker: EPICS.
Epics are a powerful management tool providing teams with big picture detail. It sounds like an oxymoron, but that’s what Epics offer, the ability to zoom out and zoom in at the same time.
Now you can group dozens of stories into a bucket that represents a significant feature. Epics can hold digital assets, such as requirement docs and mockups as well as high-level discussions. You can also prioritize Epics and at a glance know the status of the stories within each Epic.
We’ve been in beta for a few months now and we’d like to thank everyone who volunteered to test drive this feature while it was being built. Here are some of the things these courageous people have shared with us:
“It’s now much easier to coordinate people working on multiple goals at the same time.”
Tikitu at Buzzcapture.
“We love the ability to radiate progress information and the ability to maintain a focused conversation on it.” Diogo at Sport Science School of Rio Maior, Portugal.
“…it is quite helpful in making it easier to see what’s being worked on” Frank at Disney
We hope you enjoy Epics. You can find more detailed information on our FAQ, getting started document or our short screencast.
We look forward to hearing from you on Facebook, Twitter or tracker@pivotallabs.com.
Warm regards,
The Tracker Team
P.s. The new shortcut key for Epics is ‘SHIFT’ + ‘e’ (you can find all the short cut keys at ‘SHIFT’ + ‘?’).
P.p.s. Please download our Epic Map below.
[Standup][SF] 9 April, 2012 – Scaling the CoderWall
Monday, April 9, 2012
Ask for Help
Has anyone used Pusher.com?
General consensus was that people have heard of the service, but no one has used it.
Interesting Things
Don’t use let(:test_*) in Rspec 1. If you do, Rspec will run the let block as an assertion. Rspec 1 was retrofitted with the
letframework, which creates named methods that can be lazily evaluated inside of test examples. Ruby’s Test::Unit, which powers Rspec 1, will run all let blocks unnecessarily if prefixed with “test_”. In some cases, this could make method spy expectations fail.Route specs do not test for the existence of controller actions. They only check for the mapping of routes to controller actions. This is partially due to the fact that a controller method isn’t necessary for rendering a page, so a route could legitimately point to a controller without the listed action and would still work. There is a Stack Overflow discussion that explains the logic behind that decision. Integration and controller specs were proposed as alternatives to routing specs.
Pivotal Labs is now 24th on the CoderWall leaderboard! Further proof that we’re the awesome sauce.
Setting up & Troubleshooting Bugzilla with Tracker
Friday, April 6, 2012
Bugzilla is a popular Tracker integration and fairly straightforward to set up. In general all you need is here: https://www.pivotaltracker.com/help/integrations?version=v3#bugzilla
But if you do receive an error message instead of bugs loading in your Bugzilla integration panel, here are some tips to get past them. The following also applies to other error messages, but these are the most common:
“Unable to load bugs – Please check your URL and remember to include http:// and exclude the xmlrpc.cgi.”
or
“Unable to load bugs – There was a problem processing your request.”
You can take the first error literally, but there are also some other causes for it which aren’t obvious.
- We only support versions 3.4.x and above. That said, at the time of writing, we recommend 4.0.9 as we’re looking into an issue with the the 4.2.0 release and possibly some preceding minor versions and release candidates.
- If you haven’t changed the integration’s “Bug ‘Status’ values to exclude” (currently RESOLVED, VERIFIED, CLOSED), these defaults could be trying to pull in too much data and hence failing. To check, log in to your Bugzilla instance and use the advanced search options to find a small number of bugs, to help you change the default values to exclude all but those, and see if they’ll be pulled in.
- You may need to install one or more optional Perl modules, i.e. SOAP-Lite and possibly Test-Taint. To determine if you have them installed (or to get the commands necessary to install them), go to the directory where you installed Bugzilla on your server and run the checksetup.pl script. It will tell you what modules are installed, and what optional modules can be installed (and what they will enable). Check to see if these modules are there and if not, install them.Once that’s done, you can test it using the following. To run this you’ll need access to a machine that has the CURL command. Create a file called version.xml with the following text:<?xml version=”1.0″ encoding=”UTF-8″?>
<methodCall>
<methodName>Bugzilla.version</methodName>
<params>
</params>
</methodCall>Then run this curl command:
curl -X POST -H"Content-Type: text/xml" -d @version.xml <url of your Bugzilla server>/xmlrpc.cgiTo see a successful version request, run the command against the Bugzilla “Landfill” test server. For example:
curl -X POST -H"Content-Type: text/xml" -d @version.xml https://landfill.bugzilla.org/bugzilla-4.0-branch/xmlrpc.cgiIf all is well, the response should look like this:
<?xml version="1.0" encoding="UTF-8"?><methodresponse><params><param /><value><struct><member><name>version</name><value><string>4.0.2</string></value></member></struct></value></param></params></methodresponse>If the response printed by the curl command accessing your Bugzilla server is like this, then the Tracker integration should be able to access your Bugzilla server. If this is not the kind of response you get, then your server is still not setup correctly. In general the response’s content should help you troubleshoot. For example, if contains, “The XML-RPC Interface feature is not available in this Bugzilla.” it means you need to enable the XMLRPC interface on your Bugzilla server.
However, if you are using version 4.0.5, a bad response (such as “Application failed during request deserialization: 32612: When using XML-RPC, you cannot send data as text/xml; charset=utf-8. Only text/xml and application/xml are allowed.”) could be the result of the following Bugzilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=731219
It’s been fixed in the patch referenced in the bug, but by the time you read this, there may be more recent updates. - Another problem can be with the data that is being transferred to Tracker, if there are one or more bugs which contain multibyte characters in the description or comments. This is usually a result of pasting text into a bug from rich text email or office documents. These characters cause the length of the data stream that the web server sends to us to be incorrect, and we are unable to parse the XML on our side. In that case, determining if your bugs have any multi-byte characters and removing them, should resolve the problem. We can provide steps to help you with this if you need them.
The above should cover the most common problems. Hope it helps.
Finally, we get asked if you can integrate Tracker with Bugzilla if it’s behind your firewall. Yes, we have API servers that you can allow through your firewalls for Pivotal Tracker integration with your Bugzilla server. Please refer to our Integrations help page for more information: http://www.pivotaltracker.com/help/integrations
If you have any questions, or there’s something this doesn’t cover, please send email to: tracker@pivotallabs.com