Previously, when there was a problem with a table that shall be parsed by the crawler (e.g. wrong datatype, bad format of a date and so on) there was simply the statement: 'Cannot parse FILENAME'
Now the message that is contained in the ValueError is actually printed (not only in debugging logs).
Also, the check_datatypes method was missing an appropriate call to logging.warning.
Load a table using the webinterface where the table causes a ValueError in one of the converter functions.
Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines
For further good practices have a look at our review guidelines.