Disqus - Latest Comments for drbrain

Re: The Travis CI Blog: Upcoming Build Environment Updates

drbrain — Fri, 02 May 2014 20:22:35 -0000

It seems that ruby 1.8.7 went missing around the time of this update. A week ago I would get 1.8.7-p374 for "1.8.7", now I get REE which is very much not what I want (since REE is broken for running the rubygems tests).

Re: Running Changed Tests

drbrain — Fri, 14 Jun 2013 18:48:36 -0000

Why not use autotest (part of ZenTest)?

Re: 3.6.1. Rate Limits - OpenStack Compute Developer Guide - API v2

drbrain — Wed, 08 May 2013 21:02:19 -0000

According to https://github.com/openstac... it seems this sentence is misleading. It implies (to me) that the rate limits are applied due to URL restrictions rather than time restrictions.

I think "Rate limits from matching verbs and URLs are combined and the most restrictive timing is used to determine the limit." is closer to the implementation.

Re: 3.6.1. Rate Limits - OpenStack Compute Developer Guide - API v2

drbrain — Wed, 08 May 2013 20:38:10 -0000

> Rate limits are applied in order relative to the verb, going from least to most specific.

What are the criteria are used to define specificity of a match? Without this information it is impossible to build a client that understands the rate limits without reading the API source code to create a matching implementation.

For example, if there is a POST limit with a regex of "/os-security-group" (without s) of 20 per minute and a POST limit with a regex of "/os-security-groups" (with s) of 10 per minute is 10 per minute or 20 per minute used for "POST /v2/tenant/os-security-group-rules HTTP/1.1"?

Re: Unexpected Ruby behaviour - Sergey Potapov

drbrain — Tue, 14 Aug 2012 18:21:05 -0000

In the ruby core and standard library it does not mean "pay attention!", it has a well-defined application.

Other libraries can do what they please with the !, but we're not looking at other libraries here.

Re: Unexpected Ruby behaviour - Sergey Potapov

drbrain — Mon, 13 Aug 2012 16:59:52 -0000

A method ending in a ! does not mean "modifies the receiver" it means "there is an alternate method that does not modify the receiver".

There are plenty of methods in the core libraries that modify the receiver that don't end in ! and the methods that do end in ! have a non-! counterpart.

Re: Retry a block of Ruby code should it fail

drbrain — Fri, 10 Feb 2012 07:42:29 -0000

Why rm_rf instead of rm_r? Behavior difference notwithstanding, you can use the retry keyword with the latter without jumping through these extra hoops.

Re: 10 poorly chosen Ruby gem names

drbrain — Wed, 08 Feb 2012 18:31:05 -0000

It's http://en.wikipedia.org/wik... not http://en.wikipedia.org/wik...

And it's http://en.wikipedia.org/wik... not http://en.wikipedia.org/wik...

Re: Never create Ruby strings longer than 23 characters

drbrain — Thu, 05 Jan 2012 17:18:29 -0000

The next pointer for struct _GtkTextLineSegment 136 creates a large memory penalty of at least 32 bytes per segment (I didn't track down all the union members) that ruby does not have through shared strings and now embedded strings.

Ruby decided that using less memory is more important even if you have to memcpy() every now and then.

Re: Testing Doesn’t Scale

drbrain — Tue, 20 Sep 2011 17:09:02 -0000

In every app I've worked on I've found that it's not the testing that doesn't scale, it's the poor test implementation that doesn't scale. Usually this involves ripping out mocks and similar strategies that were supposed to make testing faster but didn't when actually measured, and implementing strategies that used measurement to properly eliminate or avoid the slow parts.

There's no mention of measuring the speed of your tests in your post at all. How do you know the problem is testing and not the way you're doing testing when you don't show that you've profiled your tests to determine the slow spots and fixed your tests appropriately?

For some benchmarks I'll put down rdoc with 1300 tests and 3000 assertions that run in 7s (acceptable at 200 tests/s). RubyGems has 1000 tests and 3000 assertions that run in 60s (very slow at only 16 tests/s). The last Rails app I worked on grew to serving one billion requests per week and the test suite ran in under 60 seconds (down from about two minutes with less coverage when I started).

Before I started working on any of these projects they had very few tests and the ability to make non-breaking changes in them was impossibly slow. Now they have large tests suites and it's easy and fast, so I think you're doing something wrong.

Re: Loading plugins with Rubygems

drbrain — Wed, 10 Aug 2011 18:20:29 -0000

When writing plugins/pluggable gems I let the person deciding which plugins to use manage that through `gem install blorf-some_plugin` instead of `gem install blorf-some_plugin` plus require 'blorf-some_plugin'

Why have the user take the extra step?

Re: Loading plugins with Rubygems

drbrain — Wed, 10 Aug 2011 16:13:24 -0000

How do you determine which files to require in the first place?

Re: Daniel Fischer's Blog - Upgrading from Snow Leopard to Lion

drbrain — Fri, 22 Jul 2011 20:50:27 -0000

RubyGems already makes it easy to rebuild your gems, see `gem help pristine`.

There's no reason to install bundler to do this.

Re: Daniel Fischer's Blog - Upgrading from Snow Leopard to Lion

drbrain — Fri, 22 Jul 2011 20:49:37 -0000

RubyGems already makes rebuilding your gems easy, `gem pristine`.

No need to use bundler (or the bundle typo-fix gem).

Re: Narf: A Ruby Micro Test Framework

drbrain — Fri, 01 Apr 2011 14:12:33 -0000

The least you could have done was not reuse the name of another ruby project:

http://raa.ruby-lang.org/pr...

Re: A Beginner Guide to Creating Class Macros

drbrain — Tue, 29 Mar 2011 16:27:29 -0000

These aren't macros, ruby doesn't have macros.

Re: Ruby Enterprise Edition 1.8.7-2011.03 released

drbrain — Thu, 24 Feb 2011 21:35:35 -0000

The last time 1.8.8 was brought up on the ruby-core mailing list the future of the 1.8 branch was undecided. I felt there was a strong lean towards not releasing a 1.8.8 as 1.9.2 was a better target. Has this changed but not been announced on the ruby-core mailing list?

Re: Introducing Gem Testers

drbrain — Wed, 02 Feb 2011 17:13:20 -0000

With hoe 2.9 it's easy to opt-in to gem-testers, just upgrade and `rake release`. There is no step three!

Re: GE 'Energy Smart' 9W LED Lightbulb (Product Review)

drbrain — Mon, 31 Jan 2011 17:49:35 -0000

Are the bulbs dimmable?

Re: Gem Development Best Practices

drbrain — Tue, 25 Jan 2011 21:27:58 -0000

No, don't set the date. RubyGems does this for you.

Re: Francis Hwang: AOL HQ

drbrain — Wed, 24 Nov 2010 15:47:45 -0000

AT&T Interactive is doing the same thing by allowing many of us to work on open source on company time. Most prominently Aaron Patterson gets to work on Rails.

I'm glad some of Corporate America is intent on keeping themselves relevant to the tech community.

Re: Francis Hwang: I hate these people.

drbrain — Mon, 26 Jul 2010 13:44:51 -0000

Since Peter and what's-his-name have opted for having large muscles I doubt Francis will have to run very far (or fast). Excellent plan!

Re: Francis Hwang: Meerkats & melons, together at least

drbrain — Thu, 08 Jul 2010 17:54:15 -0000

I guess I should go there more often, it's just a couple bus rides away.

Re: Francis Hwang: On the backchannel, and civility

drbrain — Tue, 25 May 2010 20:47:55 -0000

RubyKaigi did something very interesting... for lightning talks they had a separate display running that showed the backchannel and counted up the number of stars people gave for each talk. The primary goal was to show the translations for the speakers, but introduced here I think it might cut down on meanness.

Re: Using p4merge with Git - { |one, step, back| }

drbrain — Sun, 06 Sep 2009 15:35:21 -0000

Looks like p4merge is only available for Windows. On OS X there's FileMerge which is launched via opendiff. cmd becomes:

/usr/bin/opendiff "$PWD/$BASE" "$PWD/$LOCAL" -ancestor "$PWD/$REMOTE" -merge "$PWD/$MERGED"