Roman Khavronenko 2a7424a621 vmalert: fix nil map assignment (#4392) ... The storage instance with nil map params was created for remote-read purposes. And before change 7a9ae9de0d this map was ignored in ApplyParams. Now, it started to be used and vmalert panics in runtime. The fix properly inits map for at `NewVMStorage` and verifies it is not nil on assignment in `ApplyParams`. Signed-off-by: hagen1778 <roman@victoriametrics.com> --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit de94812088) Signed-off-by: hagen1778 <roman@victoriametrics.com>		2023-06-05 11:28:00 +02:00
..
vmagent	lib/flagutil/bytes.go: properly handle values bigger than 2GiB on 32-bit architectures	2023-01-10 19:36:23 -08:00
vmalert	vmalert: fix nil map assignment (#4392)	2023-06-05 11:28:00 +02:00
vmauth	all: update Go builder from v1.19.3 to v1.19.4	2022-12-11 00:23:32 -08:00
vmbackup	lib/flagutil/bytes.go: properly handle values bigger than 2GiB on 32-bit architectures	2023-01-10 19:36:23 -08:00
vmbackupmanager	docs: update -help output for vmbackup, vmbackupmanager, vmgateway and vmrestore components	2022-06-21 15:49:26 +03:00
vmctl	all: update Go builder from v1.19.3 to v1.19.4	2022-12-11 00:23:32 -08:00
vmgateway	docs: update -help output for vmbackup, vmbackupmanager, vmgateway and vmrestore components	2022-06-21 15:49:26 +03:00
vminsert	app: fix make publish-* after ed93330e66	2022-07-14 11:01:34 +03:00
vmrestore	lib/flagutil/bytes.go: properly handle values bigger than 2GiB on 32-bit architectures	2023-01-10 19:36:23 -08:00
vmselect	app/vmselect/promql: prevent from cannot unmarshal timeseries from rollupResultCache panic after the upgrade to v1.89.0	2023-03-12 19:11:30 -07:00
vmstorage	lib/flagutil/bytes.go: properly handle values bigger than 2GiB on 32-bit architectures	2023-01-10 19:36:23 -08:00
vmui	deployment/docker: update base docker image from 3.17.3 to 3.18.0	2023-05-12 17:34:27 -07:00