You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Incorrect calculation of notification id leads to duplicate entries #13
The static function get_notification_id calculates the id incorrectly.
It uses ext_name instead of name
The version information provided by the cronjob is actually an array. The version information stored, however, is only a string. Depending on what is provided, the information differs and therefore the id is calculated differently (including a suppresed error notice of array to string conversion).
Multiple possible solutions:
Calculate ID using internal static function to find the correct new version (slow, seems to cause issues with unittests, yields same ID every call)
simply use a serialized version of the complete array for ID calculation (simple, but has the same problem of different ids)
Move version extraction to cronjob / helper class (should simplify id calculation in notification, yields the same id on every call)
If the same ID is given on every call this is correct behavior. But it changes the behavior of this extension since right now, administrators are reminded frequently about the same outdated extension. So this should be corrected, but maybe it would be best to remark the notification as unread or delete and reapply it. Maybe this can also be used as a basis for a user defined setting on how frequently he wishes to be notified.
Die Notification-ID wird aus name und der extrahierten Version berechnet und ist bei gleichen Daten stabil; die Berechnung kommt ohne bcmath aus und liefert dieselben IDs wie zuvor (gegen die alte Funktion mit 200.000 Eingaben verglichen). Regressionstest in #19: Wiederholte Cron-Läufe mit denselben Daten erzeugen pro Benutzer genau eine Benachrichtigung, eine neuere Version eine neue.
Activity
gn36 commentedon Oct 18, 2026
Die Notification-ID wird aus
nameund der extrahierten Version berechnet und ist bei gleichen Daten stabil; die Berechnung kommt ohne bcmath aus und liefert dieselben IDs wie zuvor (gegen die alte Funktion mit 200.000 Eingaben verglichen). Regressionstest in #19: Wiederholte Cron-Läufe mit denselben Daten erzeugen pro Benutzer genau eine Benachrichtigung, eine neuere Version eine neue.Generated by Claude Code