-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
fix: explicit fingerprinter param in custom dupefilter #73
Conversation
Perhaps its best to pin down the versions in Piplock file? |
@SheezZarR Yeah good idea - mind pinning the versions as part of this PR? |
@jasonbosco i have updated the file.
I am using local typesense server of version 0.25.2-1. (here) |
Hey @SheezZarR, thanks for submitting this PR. The two related tests should fail because of Typesense version differences, I'll check it out myself shortly to verify so |
Can verify that this is a |
@tharropoulos thanks a lot for helping out! |
@SheezZarR I wonder if the linting rules got updated because the linter was not pinned. If the failing lint checks are from code that wasn't modified in this PR, feel free to pin the linter to the previous version as well. I've also merged #74 that @tharropoulos put together. So if you merge |
@jasonbosco thanks I was a bit clumsy on this one. Hope the update will fix the problem |
@jasonbosco CI/CD keeps failing in my fork in Github Actions. I'll report back when to run the Action in here. I find it a bit strange because tests and linting are green locally.
|
Some weird shenanigans with the lock-file. |
Thank you again for the PR @SheezZarR! |
The changes are now in |
@jasonbosco yah, the scrapper works now! 👍 |
Change Summary
The scraper uses
Scrapy = ">=2.2.1"
as its dependency. Recent update from 2.11.* to 2.12.1 introduced a new requirement (see here):Hence I updated the signature of the class
CustomDupeFilter
. The explicit return statement is due to pyright complaints.PR Checklist