|
Tim |
Reported via the forum links below:
Quick workarounds can be found below.
"for me I had the same issue, but after deleting the HLA then readding it will run fine."
"I’ve run into this myself. It appears to be caused by adding new settings to an analyzer that’s currently loaded into a capture. Upon reload, it immediately raises this exception. The workaround is to delete the analyzer from the capture and re-add it. I would submit a bug report about this but I don’t know how to report against the Python libraries themselves (which do not appear to be part of the Saleae Github repo)."