This bug should be fixed in release 2.18.0 of vsearch now available:

https://github.com/torognes/vsearch/releases/tag/v2.18.0

- Torbjørn

Reply via email to