Yes, this issue has been fixed in v0.3.6. You are using v0.3.5. The newer version is currently patron-only, but will eventually be released to everybody.
so it not me only issue? so it just the built end? phew i was worry. thx so much
