Log checkpoints could be helpful to pinpoint a certain time while inspecting logs.
One disruptive behavior of current checkpoint mechanism is it is not case sensitive; which may lead to a family of unexpected behavior.
Consider the following scenario after walt log add-checkpoint EXP1 is used to indicate the beginning of first experiment:
user@waltsrvr:~$ walt log list-checkpoints
timestamp name
-------------------------- ----
2018-01-01 01:01:01.513851 EXP1
user@waltsrvr:~$ walt log show --history EXP1: --streams mystream
Failed: no checkpoint with this name 'exp1'.
Invalid HISTORY_RANGE. See 'walt help show log-history' for more info.
This unexpected behavior could be fixed by either enabling case sensitivity or, recording added checkpoints in small-letters.
Log checkpoints could be helpful to pinpoint a certain time while inspecting logs.
One disruptive behavior of current checkpoint mechanism is it is not case sensitive; which may lead to a family of unexpected behavior.
Consider the following scenario after
walt log add-checkpoint EXP1is used to indicate the beginning of first experiment:This unexpected behavior could be fixed by either enabling case sensitivity or, recording added checkpoints in small-letters.