Skip to content

Investigate/Fix accounting for UserReport V1 and V2 #5524

@Dav1dde

Description

@Dav1dde

UserReport V1 gets merged into the UserReport V2 data category for outcomes, but rate limits and accounting in general is not consistent for these two categories.

This means there is a opt-out for this accounting in Enforcement::apply_to_managed, we should properly investigate and fix the accounting/filtering.

The test tests/integration/test_user_report.py::test_user_report_error_quota is showcasing this behaviour, when a user report is dropped because of an error quota.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingfillerRequires little effort to resolve. Ready to be picked up anytime.maintenanceTasks with this label generally have a lower priority and due datestarter

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions