database · inferred from evidence
Redis
An in-memory data structure store used as a database, cache, and message broker.
- RedisVL TextQuery/AggregateHybridQuery: literal AND treated as required term when stopwords disabled
`TextQuery` and `AggregateHybridQuery` joined full-text clauses with `filter_expression` using a literal `AND` (e.g. `[text-query] AND [filter-expression]`). When stopwords were disabled, Redis Search treated the literal `AND` as a required
- RedisVL: documents not immediately searchable after load on Redis 8.8+
On Redis 8.8+, `index.load(records)` followed immediately by `index.query(query)` could miss documents that were just written. Redis 8.8 changed the RediSearch worker pool default: `search-workers` now defaults to the core count instead of
- Prefect 3 server memory grows until OOM with default in-memory messaging
Self-hosted Prefect 3 servers showed memory climbing steadily until Kubernetes OOM-killed the pod, a regression from Prefect 2 which was flat. The reporter ran without Redis and noted Prefect 2 had no such problem. Prefect maintainers and c
- Lago events ingested but events_count stays 0 in current usage API
Events POSTed to /api/v1/events were accepted (returned a lago_id) and visible in the developer events UI, but the current usage API kept returning events_count = 0 for a count_agg billable metric (code chat_number). Another user hit the sa
- Self-hosted Inngest logs flooded with rejecting event; event key not recognized
Self-hosted Inngest (docker compose, `inngest start`) with INNGEST_EVENT_KEY and INNGEST_SIGNING_KEY set and Postgres/Redis configured. Server boots fine and functions run, but the logs are flooded every minute with: `rejecting event; event