VIT files always show as containing source even though source has been separated
Opened this issue · 1 comments
I'm not sure if this is a LabVIEW bug (e.g. if the source code is really still present for VIT files) or if pylavi is treating them incorrectly and falsely determining that source code is present.
In my case, I was not able to get the --no-code
test to pass for my .vit
files, so I had to use a --skip *.vit
option to skip them.
Here's an example run that failed on VITs: https://github.com/vipm-io/OpenG-Variant-Data-Library/actions/runs/7907953103/job/21586124086
I'll need to look into it further, but we are relying on specific flags and resources in the file. .vit
files are treated somewhat differently by LabVIEW and may either have the code (when they are not supposed to, being a bug in LabVIEW) or the flags might mean different things for .vit
files (bug in pylavi).