confirmed, and a fix is on the way
The problem is that the hub address is not set and unfortunately the hubinfo command isn't handling that very well,
So to get rid if your problem, use !set hub_address to set you correct hub address and the error message should go away
/1d