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

New denylist for october 17: #8372

Merged
merged 1 commit into from
Oct 17, 2023
Merged

Conversation

Vagabond
Copy link
Contributor

The primary change was to implement 'carryover' from the previous denylist. This means that any nodes/edges that did not have any data for them over the 2 week sampling period are carried forward. This prevents hotspots from simply being turned off for two weeks to escape the denylist and then being turned back on.

All other denylist parameters remain the same as the previous week, and no new classifiers are added.

The primary change was to implement 'carryover' from the previous
denylist. This means that any nodes/edges that did not have any data for
them over the 2 week sampling period are carried forward. This prevents
hotspots from simply being turned off for two weeks to escape the
denylist and then being turned back on.

All other denylist parameters remain the same as the previous week, and
no new classifiers are added.
@Vagabond Vagabond requested a review from madninja October 17, 2023 16:23
@madninja madninja merged commit cf8fb9d into main Oct 17, 2023
1 check passed
@madninja madninja deleted the adt/algorithmic-denylist-2023-10-17 branch October 17, 2023 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants