Implement Add-on activity log

[ParthS007]

Proposed changes

closes #10053

Add AddonActivityLog model

• Foreign key to Addon
• Foreign key to Component to see what component triggered that event.
• Event to see what action triggered that (some add-ons can be triggered by more of them)
• Timestamp
• Details as JSONField
• Create new instance on each add-on trigger
• Make add-ons log what they did
• Add a renderer for details to the BaseAddon class (subclasses might customize this)
• List paginated events delivery on add-on management page
• Add pruning of events after some time

Checklist

• Lint and unit tests pass locally with my changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have added documentation to describe my feature.
• I have squashed my commits into logic units.
• I have described the changes in the commit messages.

[ParthS007]

@nijel

Add pruning of events after some time

What is the criterion for pruning and how we plan to do this?

1. Have a management command to delete events
2. Have a task scheduled after a certain interval to prune automatically.

[nijel]

Have a periodic task for that, something similar like we do for an audit log:

weblate/weblate/accounts/tasks.py

Lines 38 to 45 in f61fea6

	@app.task(trail=False)
	def cleanup_auditlog() -> None:
	"""Cleanup old auditlog entries."""
	from weblate.accounts.models import AuditLog
	AuditLog.objects.filter(
	timestamp__lt=now() - timedelta(days=settings.AUDITLOG_EXPIRY)
	).delete()

[nijel]

I'd display the activity log on the add-on detail page, not on the list page. On the list page, all add-ons logs would be mixed up, what could make reading the log challenging with many add-ons installed.

[codecov]

Codecov Report

Attention: Patch coverage is 91.25000% with 7 lines in your changes are missing coverage. Please review.

Project coverage is 90.56%. Comparing base (6aee586) to head (3f2b279).
Report is 1891 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #11080      +/-   ##
==========================================
- Coverage   90.82%   90.56%   -0.26%     
==========================================
  Files         554      573      +19     
  Lines       57306    58626    +1320     
  Branches     9122     9376     +254     
==========================================
+ Hits        52046    53095    +1049     
- Misses       3640     3841     +201     
- Partials     1620     1690      +70     

Files	Coverage Δ
weblate/addons/migrations/0003_addonactivitylog.py	100.00% <100.00%> (ø)
weblate/addons/tasks.py	94.31% <100.00%> (+2.42%)	⬆️
weblate/addons/tests.py	99.76% <100.00%> (+0.03%)	⬆️
weblate/urls.py	81.70% <ø> (ø)
weblate/addons/models.py	89.09% <96.00%> (-2.58%)	⬇️
weblate/addons/views.py	83.96% <75.00%> (-5.91%)	⬇️

... and 310 files with indirect coverage changes

[nijel]

Looks good now, the only missing bit is ability to display log for add-ons which have no configuration.

[nijel]

Can you please add test for the new view?

[nijel]

Merged, thanks for your contribution!

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ RepositoryError: fatal: bad revision 'origin/l10n..' weblate.trans.tasks.perform_commit View Issue
• ‼️ FileParseError: 'NoneType' object has no attribute 'mode' /api/translations/{component__project__slug}/{c... View Issue
• ‼️ PermissionError: [Errno 13] Permission denied: '/home/cdn' weblate.trans.tasks.perform_commit View Issue
• ‼️ WeblateLockTimeoutError: Lock on lock:repo:17561 could not be acquired in 120s weblate.addons.tasks.postconfigure_addon View Issue
• ‼️ OperationalError: deadlock detected weblate.trans.tasks.perform_update View Issue

_{Did you find this useful? React with a 👍 or 👎}