chrivers / chrivers/tricorder

Timestamp specification

Open
#2 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

`@nnnnnn` timestamp...
Milliseconds, right?
Should it be some fixed number of digits (Why? Does this arbitrarily limit my game time?) or any number?
Is it OK to give decimal milliseconds if I have microsecond or nanosecond accurate packet captures?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.