Describe the bug
'panic: assignment to entry in nil map [recovered, repanicked]
goroutine 1787 [running]:
sync.(*WaitGroup).Go.func1.1()
sync/waitgroup.go:251 +0x45
panic({0xc098e0?, 0x137fa10?})
runtime/panic.go:860 +0x13a
github.com/VictoriaMetrics/VictoriaLogs/lib/logstorage.(*statsUniqValuesProcessor).mergeState(0x334119ffe000, 0x334119db7730?, {0xe17dc0?, 0x334119cea600?}, {0xe1efc0?, 0x33411a136000?})
github.com/VictoriaMetrics/VictoriaLogs@v1.47.1-0.20260225221819-a408207c2242/lib/logstorage/stats_uniq_values.go:155 +0x1d4
github.com/VictoriaMetrics/VictoriaLogs/lib/logstorage.(*pipeStatsGroup).mergeState(...)
github.com/VictoriaMetrics/VictoriaLogs@v1.47.1-0.20260225221819-a408207c2242/lib/logstorage/pipe_stats.go:950
github.com/VictoriaMetrics/VictoriaLogs/lib/logstorage.(*pipeStatsGroupMap).mergeState(0x33411a412040, 0x33411a274708, 0x33411a25e040, 0x334119d0a000)
github.com/VictoriaMetrics/VictoriaLogs@v1.47.1-0.20260225221819-a408207c2242/lib/logstorage/pipe_stats.go:513 +0x5c2
github.com/VictoriaMetrics/VictoriaLogs/lib/logstorage.(*pipeStatsProcessor).mergeShardsParallel.func2()
github.com/VictoriaMetrics/VictoriaLogs@v1.47.1-0.20260225221819-a408207c2242/lib/logstorage/pipe_stats.go:1226 +0x10f
sync.(*WaitGroup).Go.func1()
sync/waitgroup.go:258 +0x4a
created by sync.(*WaitGroup).Go in goroutine 1806
sync/waitgroup.go:238 +0x73`
i see that it's fixed in victorialogs 1.52.0, while VT still uses 1.51.0 VL backend.
To Reproduce
This issue explains how to reproduce this exact problem
VictoriaMetrics/VictoriaLogs#1383
Version
victoriametrics/victoria-traces:v0.10.0
Logs
No response
Screenshots
No response
Used command-line flags
No response
Additional information
No response
Describe the bug
'panic: assignment to entry in nil map [recovered, repanicked]
goroutine 1787 [running]:
sync.(*WaitGroup).Go.func1.1()
sync/waitgroup.go:251 +0x45
panic({0xc098e0?, 0x137fa10?})
runtime/panic.go:860 +0x13a
github.com/VictoriaMetrics/VictoriaLogs/lib/logstorage.(*statsUniqValuesProcessor).mergeState(0x334119ffe000, 0x334119db7730?, {0xe17dc0?, 0x334119cea600?}, {0xe1efc0?, 0x33411a136000?})
github.com/VictoriaMetrics/VictoriaLogs@v1.47.1-0.20260225221819-a408207c2242/lib/logstorage/stats_uniq_values.go:155 +0x1d4
github.com/VictoriaMetrics/VictoriaLogs/lib/logstorage.(*pipeStatsGroup).mergeState(...)
github.com/VictoriaMetrics/VictoriaLogs@v1.47.1-0.20260225221819-a408207c2242/lib/logstorage/pipe_stats.go:950
github.com/VictoriaMetrics/VictoriaLogs/lib/logstorage.(*pipeStatsGroupMap).mergeState(0x33411a412040, 0x33411a274708, 0x33411a25e040, 0x334119d0a000)
github.com/VictoriaMetrics/VictoriaLogs@v1.47.1-0.20260225221819-a408207c2242/lib/logstorage/pipe_stats.go:513 +0x5c2
github.com/VictoriaMetrics/VictoriaLogs/lib/logstorage.(*pipeStatsProcessor).mergeShardsParallel.func2()
github.com/VictoriaMetrics/VictoriaLogs@v1.47.1-0.20260225221819-a408207c2242/lib/logstorage/pipe_stats.go:1226 +0x10f
sync.(*WaitGroup).Go.func1()
sync/waitgroup.go:258 +0x4a
created by sync.(*WaitGroup).Go in goroutine 1806
sync/waitgroup.go:238 +0x73`
i see that it's fixed in victorialogs 1.52.0, while VT still uses 1.51.0 VL backend.
To Reproduce
This issue explains how to reproduce this exact problem
VictoriaMetrics/VictoriaLogs#1383
Version
victoriametrics/victoria-traces:v0.10.0
Logs
No response
Screenshots
No response
Used command-line flags
No response
Additional information
No response