You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Syft surfaces errors encountered with references to the file from which they originate -- this happens at the Syft level, but not lower level like stereoscope, which can have reference to the path(s). we want to generalize this behavior to occur for all errors returned from a file.Resolver, not just those encountered in the binary cataloger. #3410 was a quick fix to an immediate problem that is temporary until the changes described here get implemented.
Specifically, what was discussed:
modify stereoscope to include a "path error" of some sort -- one that has a path and an error, for example, when a cycle is returned to include the file which caused it, and update calls to return this error type as appropriate
make a file.Resolver decorator which converts stereoscope path errors to unknowns/coordinate errors on each error-returning implementation call
update the binary classifier to split coordinate errors and remaining, warn log remaining, and remove this behavior from the ProcessPathError
The text was updated successfully, but these errors were encountered:
Syft surfaces errors encountered with references to the file from which they originate -- this happens at the Syft level, but not lower level like stereoscope, which can have reference to the path(s). we want to generalize this behavior to occur for all errors returned from a
file.Resolver
, not just those encountered in the binary cataloger. #3410 was a quick fix to an immediate problem that is temporary until the changes described here get implemented.Specifically, what was discussed:
file.Resolver
decorator which converts stereoscope path errors to unknowns/coordinate errors on each error-returning implementation callThe text was updated successfully, but these errors were encountered: