Thanks for the report. The bug was fixed in commit [720f2a] and is included in release v2.15.0

 

Related

Commit: [720f2a]