Skip to content

fix(reminders): rescan definitions before startup alerts#1653

Merged
Aaronontheweb merged 4 commits into
devfrom
fix/reminder-startup-rescan-schema-alerts
Jul 15, 2026
Merged

fix(reminders): rescan definitions before startup alerts#1653
Aaronontheweb merged 4 commits into
devfrom
fix/reminder-startup-rescan-schema-alerts

Conversation

@Aaronontheweb

Copy link
Copy Markdown
Collaborator

Failure

Startup_emits_alert_for_legacy_reminder_missing_trust_fields intermittently observed an empty notification sink even after the actor answered its readiness query. The mailbox barrier proves PreStart completed, so this is not an assertion-delay problem: startup relied on a schema scan performed earlier by the store constructor and then consumed a one-shot rejection list.

Fix

Rescan reminder definitions at the actor startup boundary, immediately before consuming and emitting schema alerts. This uses the existing ReminderDefinitionStore.List() path, which records legacy trust-field rejections and de-duplicates them by reminder ID.

Validation

  • dotnet test src/Netclaw.Actors.Tests/Netclaw.Actors.Tests.csproj -c Release --filter FullyQualifiedName~Startup_emits_alert --no-restore
  • dotnet slopwatch analyze
  • pwsh ./scripts/Add-FileHeaders.ps1 -Verify

@Aaronontheweb
Aaronontheweb force-pushed the fix/reminder-startup-rescan-schema-alerts branch from e9fd87b to 835b00c Compare July 15, 2026 14:55
@Aaronontheweb
Aaronontheweb merged commit a626d18 into dev Jul 15, 2026
21 checks passed
@Aaronontheweb
Aaronontheweb deleted the fix/reminder-startup-rescan-schema-alerts branch July 15, 2026 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant