Skip to content
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

Coordinate manual reporting/scanning with bodyfetcher.py scanning (e.g. prevent reporting of a post which is currently being scanned) #7552

Open
makyen opened this issue Feb 12, 2023 · 1 comment
Labels
status: confirmed Confirmed as something that needs working on.

Comments

@makyen
Copy link
Contributor

makyen commented Feb 12, 2023

There's currently no coordination between manual scanning initiated via any chat commands, via the MS API, and the scanning performed in bodyfetcher.py other than the chat based scan/report will reply that a post has already been reported, if a scan has previously completed and the post was reported.

Along with a variety of other issues, this can result in a post being scanned and reported multiple times.

@makyen
Copy link
Contributor Author

makyen commented Feb 12, 2023

One possible solution to this is to break at least some of the check/scan logic out of bodyfetcher.py, such that scanning and reporting initiated from other sources also uses the existing logic, including the post processing lock, recently scanned posts, etc. It's probably also desirable to have manual scans included in stats, at least to some extent.

@stale stale bot added the status: stale label Jun 18, 2023
@Spevacus Spevacus added status: confirmed Confirmed as something that needs working on. and removed status: stale labels Aug 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: confirmed Confirmed as something that needs working on.
Development

No branches or pull requests

2 participants