Based on the investigation results of T342786, we need to add CheckUser as a dependency on Nuke.
Acceptance criteria:
- Check user is added as a dependency. If there is any broken functionality, it should be fixed.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| In Progress | Niharika | T324492 Temporary accounts - MVP | |||
| Open | None | T326816 Update features for temporary accounts | |||
| Open | None | T339244 Update Moderator Tools-owned products that may be affected by IP Masking | |||
| Open | None | T326935 Prepare Nuke extension for IP Masking | |||
| Open | None | T342785 Enable Nuking of pages created by all temporary accounts which were used by an IP address | |||
| Open | None | T349577 Update Nuke code to query CheckUser | |||
| Open | None | T349575 Add CheckUser as a dependency | |||
| Open | None | T349573 Install CheckUser locally |
Event Timeline
Comment Actions
I'm pretty sure Nuke doesn't need to check IP addresses on Recent Changes. It should work using actor only. Looking at the code, I think usages of rc_user_text should be replaced by an actor name
Comment Actions
Per T342785, we're planning to extend Nuke to enable users to nuke all pages created by temporary accounts originating from a particular IP address. Because of this, we'll need to query the CU table to fetch temporary accounts used by an IP.