Verified the issue still exists in v9.4.0

Patch #41 no longer applies