Posssible to make this more error tolerant?

[DavidUXer]

I"m really loving the idea of this, because when it works it works amazingly well! But I'm having major problems with errors. I'm probably an edge case since I have about 17k recipe notes (don't ask), all tagged. I exported and tried to upload 1000 but got "undefined entity" and "unhandled exception" errors. Even in verbose mode it didn't tell me what the problem notes were, and it's way more than one note, because as I sliced and diced my exports, and this error would come up over and over again. I finally managed to get down to 12 notes that worked, found a problem note by exclusion, but I continuously run into errors if I try for more than say 25-40 notes. So there are a lot of problem notes. Obviously, uploading my 17k notes 10 at a time is unworkable, so I'm wondering if there's a way for the app to ignore some of these errors and just keep going, and better yet output a file listing the problem notes.

For reference, here's the kind of output I'm getting:

INFO: 'Evernote ENEX Import' page found
INFO: Processing notebook '41-60'...
Traceback (most recent call last):
File "enex2notion_main_.py", line 4, in
File "enex2notion\cli.py", line 47, in main
File "enex2notion\cli.py", line 32, in cli
File "enex2notion\cli.py", line 42, in _process_input
File "enex2notion\cli_upload.py", line 53, in upload_notebook
File "enex2notion\enex_parser.py", line 23, in count_notes
File "enex2notion\enex_parser_xml.py", line 23, in iter_process_xml_elements
File "xml\etree\ElementTree.py", line 1227, in iterator
File "xml\etree\ElementTree.py", line 1302, in read_events
File "xml\etree\ElementTree.py", line 1274, in feed
xml.etree.ElementTree.ParseError: undefined entity  : line 2327, column 623
[29732] Failed to execute script 'main' due to unhandled exception!

[vzhd1701]

This should be fixed in the latest version. Also added --skip-failed.