Open martinhoeller opened 3 years ago
@martinhoeller Would you be able to provide package.swift file
and debug logs?
You can create debug logs by running: fossa analyze --output --debug
, this will create .fossa.debug.json file. You will need CLI version v2.17.0 or greater for this.
Upon further investigation it seems that fossa
is just completely ignoring excluded paths in .fossa.yml
. We configured it to ignore ./derivedData
, yet it is analyzing files in that directory. The same happens when passing the --exclude-path ./derivedData
parameter.
Hi @martinhoeller - fyi, I will be transferring this issue to fossa-cli repository, as spectrometer code is migrated to fossa-cli for all future development.
@martinhoeller could you provide the package.swift
file that the fossa-cli is unable to parse?
In relation to ignoring the excluded paths, please update to the latest version of the fossa-cli and let me know if you are still seeing these issues. We have made a lot of improvements to this feature.
When analyzing our project with many SPM dependencies we get a lot of different parsing errors. Some examples below:
Out of 47 dependencies, 21 produce those kind of warnings. I'm happy to provide an exhaustive list of all Swift packages that cause troubles, if needed.