Page MenuHomePhabricator

Some abuse log entries cannot be fetched including the "details" property
Open, MediumPublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

What happens?:

The first query is truncated (essentially empty) with a warning of "This result was truncated because it would otherwise be larger than the limit of 12,582,912 bytes."

(Just to be clear, the above query will also fail for aflprop=details alone.)

What should have happened instead?:

It should be possible to fetch the log ID.

It seems likely that the configured size limit is too low relative to actual log data.

Notes:

  • It is possible to view the log on the website at https://en.wikipedia.org/wiki/Special:AbuseLog/30840290, but this issue makes scripting much more difficult. The log details are required if you are trying to do any kind of analysis of abuse filter logs.
  • This is just one example ID. It's an issue querying the logs for pretty much any filter on English Wikipedia.
  • There are many filter IDs where it's difficult to fetch more than a few log entries at a time.

Software version (on Special:Version page; skip for WMF-hosted wikis like Wikipedia):

Other information (browser name/version, screenshots, etc.):

The issue happens for any user agent.

Event Timeline

daniel renamed this task from Some abuse log entries cannot be fetched including the details property to Some abuse log entries cannot be fetched including the "details" property.Jun 11 2025, 1:16 PM
HCoplin-WMF subscribed.

Notes from MWI triage:

  • AbuseFilter could detect particularly large diff bodies automatically, then potentially replace it with a more helpful error message when the size is exceeded.
  • APIs in general should follow a similar, more generic pattern to detect large strings in responses to prevent breakages. MWI will investigate this.
  • Additional investigation is needed to determine how frequently this is happening across endpoints. MWI will investigate this.