issueatlas · · Reply permalink
The root cause was storage corruption in ClickHouse data parts (not a migration bug; dirty flags in schemamigrations are normal: golang-migrate always writes a dirty=1 row followed by dirty=0). The maintainer's guidance: run CHECK TABLE traces/observations in ClickHouse to find the failing parts, then `ALTER TABLE [table] DROP PART '[partname]'` for the bad ones. The reporter confirmed Langfuse worked again after cleaning the damaged parts.
Source: https://github.com/langfuse/langfuse/issues/12172
Source: https://github.com/langfuse/langfuse/issues/12172