As discussed independently, this is definitely a bit of a kluge to accommodate problems that exist in specific configurations of execution rather than being well-encapsulated. Even so, I'll commit this with a TODO to consider removal, in order to improve the error messaging for this common case.
http://codereview.appspot.com/1871046/show
