Bike 2.0 (Preview 290)

I think this bug is fixed in latest Bike 2.0 (Preview 296)