Das Verwerfen von „Upgrade verfügbar“-Benachrichtigungen führt zu 422 Fehlern

zogstrip · 27. Dezember 2025 um 23:00

Entschuldigung dafür, @RBoy, wir brauchten eine kleine Nachverfolgung zu DEV: Admin-Benachrichtigungen beim Löschen von Problemprüfungs-Trackern entfernen

github.com/discourse/discourse

FIX: Dismissing admin notices fails with 422 when tracker has NULL target

main ← fix-dismissing-admin-notices-fails-with-422-when-tracker-has-null-target

opened 10:59PM - 27 Dec 25 UTC

ZogStriP

+40 -1

When dismissing an admin notice, the service would look up the associated `Probl…emCheckTracker` by identifier only. This could find a tracker with a `NULL` target, which then fails validation on update since target is now required (as of 8ca5fb706a). The root issue is that `problem_check_trackers.target` was added with `null: true` and while we later added a default value of `"__NULL__"` and a Ruby validation, we never enforced `NOT NULL` at the database level. This allowed records with `NULL` targets to persist or be recreated through code paths that explicitly passed nil. This commit: - Updates the dismiss service to look up trackers by both identifier AND target (extracted from the admin notice's details) - Removes any remaining records with `NULL` targets - Adds a `NOT NULL` constraint to prevent this from recurring Ref - https://meta.discourse.org/t/392248

Thema		Antworten	Aufrufe
'Dimiss Unread' Button is broken on latest Bug	3	913	5. Dezember 2016
Production.log give No method error and Discourse not working Support	9	1233	9. Januar 2020
Upgrade failed: null value in column "updated_at" violates not-null constraint Support	5	2644	10. August 2017
Maybe a bug on meta, post disappeared Site feedback	26	5074	16. April 2017
40 Fatals and 7 Errors in recent logs Support	13	1585	8. Juni 2024

Das Verwerfen von „Upgrade verfügbar“-Benachrichtigungen führt zu 422 Fehlern

Verwandte Themen