New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

`logScope` doesn't preserve order of fields #108

Open

arnetheduck opened this issue Jan 3, 2022 · 0 comments

Member

arnetheduck commented Jan 3, 2022

INF 2022-01-03 16:57:11.631+01:00 State replayed                             topics="chaindag" ancestor=874fd407:2866783 targetStateRoot=2fc2f5f3 slots=33 target=874fd407:2866783@2866816 replayDur=307ms49us379ns blocks=0 current=c60f4822:2866762@2866784 found=true assignDur=4ms771us220ns ancestorStateRoot=0b37c3e6

  logScope:
    blocks = ancestors.len
    slots = getStateField(state.data, slot) - ancestor.slot
    current = shortLog(current)
    ancestor = shortLog(ancestor)
    target = shortLog(bs)
    ancestorStateRoot = shortLog(ancestorRoot)
    targetStateRoot = shortLog(getStateRoot(state.data))
    found
    assignDur
    replayDur

the ordering of the fields should be preserved as it matters for the user experience

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment