-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a code matcher for approximate files matching #342
Comments
Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
* Fix tests Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
* Fix tests Signed-off-by: Jono Yang <jyang@nexb.com>
* Move match.py to match_test_utils.py as we are now just using those functions for testing match functionality than actually using it for matching Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
* Use new test data Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
…342 Signed-off-by: Jono Yang <jyang@nexb.com>
This has been merged into main. We have created a new table for storing approximate file fingerprints and updated the indexing functions to index those values from scans. We have also updated the fingerprinting functions in scancode-toolkit to also generate fingerprints for text files. With these changes, we now able to perform approximate file matching in the matching pipeline run by matchcode. https://github.com/nexB/purldb/blob/main/matchcode_pipeline/pipelines/matching.py#L109 Test instructions after installing and running PurlDB with it's accompanying ScanCode.io worker, and MatchCode.io:
|
See also:
The text was updated successfully, but these errors were encountered: