Due to scheduling constraints, this bug will be addressed in the next version.
However, we still greatly appreciate your feedback. Thank you.
