Actually, I have no idea why I added
computeData.scope != scopeAndOptions.scope
By removing it all tests pass. I actually had to add .scope in to Scope::computeData to get this to work ... making computeData a less than ideal API.
This seems to be a bug. Care to report it so it will be fixed in 2.1? Thanks!