# Sounds like a bug that was introduced in 2.x. You might want to create an issue on the repo with clear steps to reproduce the issue