May 14, 9-10 PM (2)
May 14, 10-11 PM (1)
May 14, 11-12 AM (8)
May 15, 12-1 AM (2)
May 15, 1-2 AM (1)
May 15, 2-3 AM (1)
May 15, 3-4 AM (3)
May 15, 4-5 AM (0)
May 15, 5-6 AM (0)
May 15, 6-7 AM (3)
May 15, 7-8 AM (33)
May 15, 8-9 AM (1)
May 15, 9-10 AM (3)
May 15, 10-11 AM (30)
May 15, 11-12 PM (1)
May 15, 12-1 PM (2)
May 15, 1-2 PM (1)
May 15, 2-3 PM (2)
May 15, 3-4 PM (4)
May 15, 4-5 PM (2)
May 15, 5-6 PM (2)
May 15, 6-7 PM (4)
May 15, 7-8 PM (6)
May 15, 8-9 PM (0)
May 15, 9-10 PM (2)
May 15, 10-11 PM (1)
May 15, 11-12 AM (1)
May 16, 12-1 AM (2)
May 16, 1-2 AM (8)
May 16, 2-3 AM (3)
May 16, 3-4 AM (7)
May 16, 4-5 AM (33)
May 16, 5-6 AM (39)
May 16, 6-7 AM (13)
May 16, 7-8 AM (40)
May 16, 8-9 AM (22)
May 16, 9-10 AM (35)
May 16, 10-11 AM (23)
May 16, 11-12 PM (25)
May 16, 12-1 PM (36)
May 16, 1-2 PM (42)
May 16, 2-3 PM (26)
May 16, 3-4 PM (24)
May 16, 4-5 PM (21)
May 16, 5-6 PM (27)
May 16, 6-7 PM (31)
May 16, 7-8 PM (49)
May 16, 8-9 PM (10)
May 16, 9-10 PM (12)
May 16, 10-11 PM (7)
May 16, 11-12 AM (21)
May 17, 12-1 AM (10)
May 17, 1-2 AM (12)
May 17, 2-3 AM (2)
May 17, 3-4 AM (4)
May 17, 4-5 AM (6)
May 17, 5-6 AM (35)
May 17, 6-7 AM (23)
May 17, 7-8 AM (52)
May 17, 8-9 AM (91)
May 17, 9-10 AM (80)
May 17, 10-11 AM (34)
May 17, 11-12 PM (30)
May 17, 12-1 PM (66)
May 17, 1-2 PM (36)
May 17, 2-3 PM (21)
May 17, 3-4 PM (61)
May 17, 4-5 PM (33)
May 17, 5-6 PM (33)
May 17, 6-7 PM (38)
May 17, 7-8 PM (67)
May 17, 8-9 PM (23)
May 17, 9-10 PM (27)
May 17, 10-11 PM (12)
May 17, 11-12 AM (7)
May 18, 12-1 AM (33)
May 18, 1-2 AM (11)
May 18, 2-3 AM (33)
May 18, 3-4 AM (20)
May 18, 4-5 AM (9)
May 18, 5-6 AM (13)
May 18, 6-7 AM (21)
May 18, 7-8 AM (24)
May 18, 8-9 AM (17)
May 18, 9-10 AM (28)
May 18, 10-11 AM (33)
May 18, 11-12 PM (72)
May 18, 12-1 PM (39)
May 18, 1-2 PM (43)
May 18, 2-3 PM (31)
May 18, 3-4 PM (38)
May 18, 4-5 PM (33)
May 18, 5-6 PM (18)
May 18, 6-7 PM (35)
May 18, 7-8 PM (13)
May 18, 8-9 PM (12)
May 18, 9-10 PM (11)
May 18, 10-11 PM (4)
May 18, 11-12 AM (17)
May 19, 12-1 AM (6)
May 19, 1-2 AM (8)
May 19, 2-3 AM (7)
May 19, 3-4 AM (4)
May 19, 4-5 AM (10)
May 19, 5-6 AM (7)
May 19, 6-7 AM (57)
May 19, 7-8 AM (36)
May 19, 8-9 AM (42)
May 19, 9-10 AM (45)
May 19, 10-11 AM (36)
May 19, 11-12 PM (33)
May 19, 12-1 PM (32)
May 19, 1-2 PM (31)
May 19, 2-3 PM (48)
May 19, 3-4 PM (29)
May 19, 4-5 PM (25)
May 19, 5-6 PM (12)
May 19, 6-7 PM (22)
May 19, 7-8 PM (3)
May 19, 8-9 PM (6)
May 19, 9-10 PM (11)
May 19, 10-11 PM (5)
May 19, 11-12 AM (6)
May 20, 12-1 AM (4)
May 20, 1-2 AM (11)
May 20, 2-3 AM (7)
May 20, 3-4 AM (8)
May 20, 4-5 AM (7)
May 20, 5-6 AM (13)
May 20, 6-7 AM (28)
May 20, 7-8 AM (27)
May 20, 8-9 AM (39)
May 20, 9-10 AM (45)
May 20, 10-11 AM (78)
May 20, 11-12 PM (52)
May 20, 12-1 PM (36)
May 20, 1-2 PM (52)
May 20, 2-3 PM (23)
May 20, 3-4 PM (18)
May 20, 4-5 PM (18)
May 20, 5-6 PM (24)
May 20, 6-7 PM (26)
May 20, 7-8 PM (9)
May 20, 8-9 PM (15)
May 20, 9-10 PM (4)
May 20, 10-11 PM (2)
May 20, 11-12 AM (3)
May 21, 12-1 AM (5)
May 21, 1-2 AM (1)
May 21, 2-3 AM (5)
May 21, 3-4 AM (3)
May 21, 4-5 AM (2)
May 21, 5-6 AM (0)
May 21, 6-7 AM (30)
May 21, 7-8 AM (1)
May 21, 8-9 AM (5)
May 21, 9-10 AM (2)
May 21, 10-11 AM (0)
May 21, 11-12 PM (10)
May 21, 12-1 PM (1)
May 21, 1-2 PM (2)
May 21, 2-3 PM (1)
May 21, 3-4 PM (1)
May 21, 4-5 PM (1)
May 21, 5-6 PM (0)
May 21, 6-7 PM (1)
May 21, 7-8 PM (2)
May 21, 8-9 PM (1)
May 21, 9-10 PM (0)
3,226 commits this week May 14, 2022 - May 21, 2022
Add `guardDbDirWithRetry` wrapper for `guardDbDir` that catches exceptions.
Other small changes include:
* Added a trace event `TDBInitialisingFromLMDBDone`.
* Initialisation from an existing LMDB database does not rely on the
default `LMDBLimits` anymore, and is passed a limits argument instead.
TODO: We should decide whether we want to hardcode these limits to a
a substantially large one, or possibly we could link these limits to a
versioning number?
Add `guardDbDirWithRetry` wrapper for `guardDbDir` that catches exceptions.
Other small changes include:
* Added a trace event `TDBInitialisingFromLMDBDone`.
* Initialisation from an existing LMDB database does not rely on the
default `LMDBLimits` anymore, and is passed a limits argument instead.
TODO: We should decide whether we want to hardcode these limits to a
a substantially large one, or possibly we could link these limits to a
versioning number?
Make a disinction between on-disk database "settings" and "state.
Previously, the sequence number of the database is written to disk as
part of the on-disk database settings on every flush/write. Conceptually
however, the settings of a database should not change on every flush or
write. Instead, we make a dinstinction between on-disk database
"settings" and "state", where the state can be updated in every
write/flush, but the settings should generally be left untouched after
database initialisation or node start-up.