Skip to content

[BUG] fossa-cli warns on paths that are known to be binaries #1638

@jeffalder

Description

@jeffalder

Describe the bug

Running fossa-cli on github actions yielded the following warning:

  Warn: read '/<project>/gradle/wrapper/gradle-wrapper.jar': stream did not contain valid UTF-8: ReadFile


  Warn: read '/<project>/.git/index': stream did not contain valid UTF-8: ReadFile


  Warn: read '/<project>/.git/objects/pack/pack-e93b1b8700c78154253154b3a16e94adc6d0bc31.idx': stream did not contain valid UTF-8: ReadFile


  Warn: read '/<project>/.git/objects/pack/pack-e93b1b8700c78154253154b3a16e94adc6d0bc31.rev': stream did not contain valid UTF-8: ReadFile


  Warn: read '/<project>/.git/objects/pack/pack-e93b1b8700c78154253154b3a16e94adc6d0bc31.pack': stream did not contain valid UTF-8: ReadFile

This is a gradle project, so fossa-cli should already know that gradle/wrapper/gradle-wrapper.jar is a binary file to be ignored (or at least treated as such).

Also, this is a git checkout. Packfiles and the index have known paths and known non-text formats.

To Reproduce
Steps to reproduce the behavior:

  1. Run fossa analyze ...
  2. See error

Expected behavior
I expect no warnings for files that are expected to be binary in a checkout.

Debug bundle
Please run fossa with the --debug flag and attach the resulting fossa.debug.zip file here.

I actually can't because GHE but it seems like this might be obvious? I dunno.

Additional context
I don't have the ability to pull artifacts because GHE. I can cat text files. I also have to use command-line to configure it; I can't use yaml easily.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions