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.

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

Make Uptime positive. #21

Merged
merged 1 commit into from
Mar 20, 2019
Merged

Make Uptime positive. #21

merged 1 commit into from
Mar 20, 2019

Conversation

hefee
Copy link
Contributor

@hefee hefee commented Mar 17, 2019

The uptime timestamp is a timestamp in the past.
That means now.Unix() is a newwer timestamp than node.Uptime.Unix().
Currently the logic we end up with following uptime values in json:
"2020-05-31T07:00:59+0200"

and those do not make sense at all.

The uptime timestamp is a timestamp in the past.
That means now.Unix() is a newwer timestamp than node.Uptime.Unix().
Currently the logic we end up with following uptime values in json:
  "2020-05-31T07:00:59+0200"

and those do not make sense at all.
@genofire genofire merged commit 0fdae06 into genofire:develop Mar 20, 2019
@genofire
Copy link
Owner

genofire commented Mar 20, 2019

Deployed, it need some time till it is fixed completely, but on a great way:

curl -s "https://multi.meshviewer.org/data/meshviewer.json" | jq ".nodes | map(.uptime)" | sed 's/-.*//g' | sort | uniq -c       :(
      1 [
      1 ]
      1   "2014
      2   "2016
      1   "2017
      1   "2018
  22868   "2019
    207   "2020
     31   "2021
     35   "2022
     13   "2023
      8   "2024
      2   "2025
      2   "2026
      5   "2028
      3   "2030
      7   "2031

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants