darwin mime types differ from unix mime types
at asserts/test/test_format_file.py:
def test_has_compiled_binaries_open():
"""Test has_compiled_binaries."""
assert file.has_compiled_binaries(COMPILED_BINARY).is_open()
assert file.has_compiled_binaries(COMPILED_BINARY_1).is_open()
assert file.has_compiled_binaries(COMPILED_BINARY_2).is_open()
first and second pass (they detect the .jar as vulnerable) third fails (they do not detect the .class as vulnerable)
on linux:
asserts$ file -i test/static/format/file/open/*
test/static/format/file/open/MyJar.class: application/x-java-applet; charset=binary
test/static/format/file/open/MyJar.jar: application/java-archive; charset=binary
the same myme types that the check is expecting to find and therefore to mark as open
on darwin:
https://logs.nix.ci/?key=nixos/nixpkgs.78111&attempt_id=568c25ea-23cb-4e49-a06e-66e338a1d18e
pending to fire up a macos machine and see what's going on
this is the only thing that separates us from releasing fluidasserts-nix on darwin (macos) systems (as per the log)
Edited by Kevin Amado