mirror of
https://github.com/OffchainLabs/prysm.git
synced 2026-01-06 20:13:59 -05:00
SortedForkSchedule should never be empty for a properly initialized network schedule, but the handler already had a branch to support an empty result. Without an early return, we wrote a JSON response and then still accessed schedule[0], which could panic and double-write the HTTP response in misconfigured setups. --------- Co-authored-by: Radosław Kapka <rkapka@wp.pl>
112 B
112 B
Fixed
- avoid panic when fork schedule is empty #16175