Skip to content

Releases: nerves-time/nerves_time

v0.4.8

28 Apr 23:31
Compare
Choose a tag to compare
  • Fixes
    • Fix "Cannot initialize rtc" error that's in v0.4.7. (thanks @joshk)
    • Add "[NervesTime]" to log messages to make it easier to identify where they
      come from.

v0.4.7

28 Apr 13:59
Compare
Choose a tag to compare
  • Updates
    • Don't create communications socket file if not starting ntpd so that it
      doesn't need to be cleaned up. (thanks @joshk)
    • Add and clean up missing typespecs

v0.4.6

03 Jun 20:48
Compare
Choose a tag to compare
  • Updates
    • Build cleanly on Elixir 1.15. This raises the minimum supported Elixir
      version to 1.11 since we no longer test on early versions.

v0.4.5

04 Mar 20:39
Compare
Choose a tag to compare
  • New feature
    • Support blocking NervesTime startup until initialized with a valid time.
      See Startup doc and
      NervesTime.Waiter for more info (thanks @LostKobrakai ❤️)

v0.4.4

19 Nov 21:52
Compare
Choose a tag to compare
  • Updates
    • Allow muontrap v1.0.0 to be used.

v0.4.3

16 Jul 13:52
Compare
Choose a tag to compare

This release only reduces Makefile prints and has no code changes. It is a safe
update.

v0.4.2

01 Aug 13:13
Compare
Choose a tag to compare
  • New feature
    • Added NervesTime.set_system_time/1 to manually set the system clock.
      Thanks to Eric Rauer for this.

v0.4.1

10 Mar 09:20
Compare
Choose a tag to compare
  • Bug fixes
    • Fix crash when setting time.

v0.4.0

10 Mar 09:20
Compare
Choose a tag to compare
  • New features

    • Added NervesTime.RealTimeClock behaviour to support external RTC
      implementations. The default RTC is still FileTime. I.e., approximate an RTC
      by periodically updating the modified time on a file and reading it back at
      boot. See https://github.com/nerves-time for
      example RTC implementations.
  • Bug fixes

    • NervesTime.synchronized?/0 will stay true once NTP synchronizes. It will
      not revert to false unless a crash happens and the NTP code restarts. This
      should address some confusion, since in practice the function was being used
      to check whether the system time could be used. Bouncing the answer between
      true and false depending on ntp reports was confusing since the system time
      had already been set once and was plenty close to the real time.

v0.3.2

16 Oct 00:58
Compare
Choose a tag to compare
  • Improvements
    • Further reduce ntpd's logging. It is just too much especially when the
      internet is down.