Successful scan but error message shown / Parsing error: at position <xyz>, opcode b'\t' unknown

[juhoinkinen]

Hi and thanks for the nice work!

When scanning a joblib dumped file (with modelscan 0.8.0 on Python 3.10 or 3.12), I get this kind of output:

2024-08-21 15:08:47.696180: I external/local_xla/xla/tsl/cuda/cudart_stub.cc:32] Could not find cuda drivers on your machine, GPU will not be used.
2024-08-21 15:08:47.700676: I external/local_xla/xla/tsl/cuda/cudart_stub.cc:32] Could not find cuda drivers on your machine, GPU will not be used.
2024-08-21 15:08:47.712877: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:485] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-08-21 15:08:47.732596: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:8454] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-08-21 15:08:47.738037: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1452] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-08-21 15:08:47.751010: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-08-21 15:08:48.683951: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
No settings file detected at /home/path/to/modelscan-settings.toml. Using defaults. 

Scanning /home/path/to/model.joblib using modelscan.scanners.PickleUnsafeOpScan model scan

--- Summary ---

 No issues found! 🎉

--- Errors --- 

Error 1:
The following error was raised during a pickle scan: 
Parsing error: at position 358, opcode b'\t' unknown

I first thought that the scan crashed because of the error, but then on second thought, because the output states "No issues found!", that the scan actually continued run through the file and detected no issues, and only (some part around?) the indicated position was not parsed (and thus scanned?).

Could someone confirm that the file was scanned apart the indicated position? Any hints about the cause for the parsing error?