will this be fixed in a future stable version 3.2.17?