Disable inline expired event deletion to prevent crashes (v0.52.9)

- Disable goroutine that deleted expired events during query processing
- This was causing "assignment to entry in nil map" Badger panics under load
- Expired events will remain until proper background cleanup is implemented
- Added TODO comments explaining the issue and fix needed

Files modified:
- pkg/database/query-events.go: Disable inline expired event deletion
- pkg/version/version: Bump to v0.52.9

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

pkg/database/query-events.go

@@ -590,14 +590,14 @@ func (d *D) QueryEventsWithOptions(c context.Context, f *filter.F, includeDelete
 		if f.Limit != nil && len(evs) > int(*f.Limit) {
 			evs = evs[:*f.Limit]
 		}
-		// delete the expired events in a background thread
+		// TODO: DISABLED - inline deletion of expired events causes Badger race conditions
-		go func() {
+		// under high concurrent load ("assignment to entry in nil map" panic).
-			for i, ser := range expDeletes {
+		// Expired events should be cleaned up by a separate, rate-limited background
-				if err = d.DeleteEventBySerial(c, ser, expEvs[i]); chk.E(err) {
+		// worker instead of being deleted inline during query processing.
-					continue
+		// See: pkg/storage/gc.go TODOs for proper batch deletion implementation.
-				}
+		if len(expDeletes) > 0 {
+			log.D.F("QueryEvents: found %d expired events (deletion disabled)", len(expDeletes))
 		}
-		}()
 	}
 
 	return

pkg/version/version

@@ -1 +1 @@
-v0.52.8
+v0.52.9