Skip to content

Add thread safety to Clock - #1

Merged
KaiOelfke merged 3 commits into
mainfrom
agent/thread-safe-clock
Jul 26, 2026
Merged

Add thread safety to Clock#1
KaiOelfke merged 3 commits into
mainfrom
agent/thread-safe-clock

Conversation

@KaiOelfke

Copy link
Copy Markdown
Owner

Summary

  • update the personal fork from official Kronos 4.3.0 to the current official main, including 4.3.1
  • apply the public thread-safety patch from MobileNativeFoundation/Kronos PR Add thread safety to Clock MobileNativeFoundation/Kronos#110
  • protect shared stable-time reads and writes used by Clock.now and Clock.sync with an unfair lock

This keeps the fork independent of any employer-owned repository. The patch provenance is entirely public upstream code.

Validation

  • Swift package builds successfully
  • all Clock, NTP client, packet, and time-storage tests pass
  • the complete suite passes 20 of 21 tests; the unchanged DNSResolverTests.testResolveOneIP fails because time.apple.com resolves to zero IPv4 addresses in the current environment

didix21 and others added 3 commits June 3, 2024 10:41
…xcodeproj (MobileNativeFoundation#117)

- Add new script Copy Bundle Resource on Krono's Build Phase and include
  the PrivacyInfo.xcprivacy, otherwise when running xcodebuild
  create-xcframework command the manifest isn't included on
  Kronos.xcframework.

Signed-off-by: Dídac Coll <didac.coll@qustodio.com>
Signed-off-by: Michal Šrůtek <35694712+michalsrutek@users.noreply.github.com>
Signed-off-by: Seweryn Plażuk <seweryn.plazuk@gmail.com>
@KaiOelfke
KaiOelfke merged commit 9d7c7cd into main Jul 26, 2026
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.

3 participants