it might be coming from an expand, and resetting results incorrect stride. caught by interpreted backend