Skip to content
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

Fix time range being incorrectly reported to start at 0 #6

Merged
merged 5 commits into from
Nov 19, 2024
Merged

Fix time range being incorrectly reported to start at 0 #6

merged 5 commits into from
Nov 19, 2024

Commits on Nov 15, 2024

  1. Use header timestamp as fallback for determining message timestamp

    @achim-k
    achim-k committed Nov 15, 2024
    Configuration menu
    Copy the full SHA
    a4fb47c View commit details
    Browse the repository at this point in the history

Commits on Nov 18, 2024

  1. Revert "Use header timestamp as fallback for determining message time… 

    …stamp"

This reverts commit a4fb47c.
    @achim-k
    achim-k committed Nov 18, 2024
    Configuration menu
    Copy the full SHA
    10c0e28 View commit details
    Browse the repository at this point in the history

  2. Determine time range by using data/log messages only

    @achim-k
    achim-k committed Nov 18, 2024
    Configuration menu
    Copy the full SHA
    2afaa9b View commit details
    Browse the repository at this point in the history

  3. fix lint

    @achim-k
    achim-k committed Nov 18, 2024
    Configuration menu
    Copy the full SHA
    b6e91ab View commit details
    Browse the repository at this point in the history

Commits on Nov 19, 2024

  1. min fix

    @achim-k
    achim-k committed Nov 19, 2024
    Configuration menu
    Copy the full SHA
    d58915c View commit details
    Browse the repository at this point in the history