Jimmy Chen 1e9925435e Reuse fork choice read lock instead of re-acquiring it immediately (#4688) ... ## Issue Addressed I went through the code base and look for places where we acquire fork choice locks (after the deadlock bug was found and fixed in #4687), and discovered an instance where we re-acquire a lock immediately after dropping it. This shouldn't cause deadlock like the other issue, but is slightly less efficient.		2023-09-21 00:26:52 +00:00
..
src	Reuse fork choice read lock instead of re-acquiring it immediately (#4688)	2023-09-21 00:26:52 +00:00
tests	Fix bug in block root storage (#4663)	2023-08-28 05:34:28 +00:00
Cargo.toml	Prevent port re-use in HTTP API tests (#4745)	2023-09-20 01:19:03 +00:00