Unhandled exception in libraryscan during audiobook library full scan

[VeloWulf]

I have just run this image up fresh and done an ebook library scan, which completed successfully. When I then run an audiiobook libraryu scan I get the following error and the system reports an Author Refresh in progress pop up but nothing is happening

"Unhandled exception in libraryScan: Traceback (most recent call last): File "/app/lazylibrarian/lazylibrarian/librarysync.py", line 680, in LibraryScan pattern = re.compile(matchString, re.VERBOSE | re.IGNORECASE) File "/usr/lib/python3.6/re.py", line 233, in compile return _compile(pattern, flags) File "/usr/lib/python3.6/re.py", line 301, in _compile p = sre_compile.compile(pattern, flags) File "/usr/lib/python3.6/sre_compile.py", line 562, in compile p = sre_parse.parse(p, flags) File "/usr/lib/python3.6/sre_parse.py", line 855, in parse p = _parse_sub(source, pattern, flags & SRE_FLAG_VERBOSE, 0) File "/usr/lib/python3.6/sre_parse.py", line 416, in _parse_sub not nested and not items)) File "/usr/lib/python3.6/sre_parse.py", line 759, in _parse raise source.error(err.msg, len(name) + 1) from None sre_constants.error: redefinition of group name 'part' as group 4; was group 1 at position 65" (2020-08-11 19:36:36 | ERROR | AUDIOBOOK_SCAN | librarysync.py | LibraryScan | 1315)

Repo: https://gitlab.com/LazyLibrarian/lazylibrarian : Branch: master : Updated: Mon Aug 10 19:12:30 2020
Current Version: 3c505f04 : Latest Version: 3c505f04

Source: Linuxserver.io docker container
Goodreads api only

To help with identifying and fixing issues, please include as much information as possible, including:

LazyLibrarian version number (at the bottom of config page)

Operating system used (windows, mac, linux, NAS type)

Interface in use (default, bookstrap)

Which api (Goodreads, GoogleBooks, both)

Source of your LazyLibrarian installation (git, zip file, 3rd party package) -

Relevant debug log with api keys and any passwords redacted

Please note - usually a single line of log is not sufficient. The lines just before the error occurs can give useful context and greatly assist with debugging.

There is a built-in debug log creator on the logs page which makes it easy to provide this information

• To use it, first go to the log page and make sure debug logging is OFF
• Now press the "Start debug log" button
• Go and do whatever you need to recreate the error
• Go back to the log page and press "Save debug log"
• You can now turn debug logging off again if you want
• The saved log file will be found in your lazylibrarian log directory called debug.zip
• It will contain all lines logged since you pressed "Start debug log" with any passwords and api keys removed
• Attach the zip file to your bug report.