Thanks for the report. We will take a look. It seems like a bug in the hub sdk.