[GH-ISSUE #357] buggy "has not seen IP updates since a long time, staleness: 1"? #277

New issue

Closed

opened 2026-02-26 10:30:29 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 10:30:29 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Sep 11, 2018).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/357

Originally assigned to: @ThomasWaldmann on GitHub.

A user has notified me by email on 9.9.2018 that:

I had created this host just few days ago (4 or 5) I don't remember exactly
so it had never been updated during this period but it's not a very long time.

So guess we should check the related code whether there is a bug.

Originally created by @ThomasWaldmann on GitHub (Sep 11, 2018). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/357 Originally assigned to: @ThomasWaldmann on GitHub. A user has notified me by email on 9.9.2018 that: ``` I had created this host just few days ago (4 or 5) I don't remember exactly so it had never been updated during this period but it's not a very long time. ``` So guess we should check the related code whether there is a bug.

kerem closed this issue

2026-02-26 10:30:29 +03:00

kerem commented

2026-02-26 10:30:30 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 18, 2018):

The problem is that the v4/v6 update time is only set when a real update is done.
Just creating a host does not set these timestamps, so they are considered as 1.1.1970.

We could just set both to the current time. It's not really correct either, but better than 1970.

@ThomasWaldmann commented on GitHub (Oct 18, 2018): The problem is that the v4/v6 update time is only set when a real update is done. Just creating a host does not set these timestamps, so they are considered as 1.1.1970. We could just set both to the current time. It's not really correct either, but better than 1970.

kerem referenced this issue

2026-02-26 10:31:30 +03:00

[PR #277] [MERGED] update badges, new readthedocs.io url #440