Skip to content

Update README.md#127

Open
ryan-steel wants to merge 3 commits into
eclipse-score:mainfrom
etas-contrib:update-readme
Open

Update README.md#127
ryan-steel wants to merge 3 commits into
eclipse-score:mainfrom
etas-contrib:update-readme

Conversation

@ryan-steel

Copy link
Copy Markdown
Contributor

Improvement

Description

Updates README.md to contain relevant info for the repo. Uses lifecycle as a guide.

Related ticket

closes #124 (improvement ticket)

@github-actions

github-actions Bot commented Jul 15, 2026

Copy link
Copy Markdown

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ⚠️ Needs Review

Click to expand output
[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: 032328dc-0cc9-4f3e-94d9-a86d921bf2f3
Computing main repo mapping: 
WARNING: /home/runner/work/time/time/MODULE.bazel:13:7: The attribute 'compatibility_level' in module() is a no-op and will be removed in a future Bazel release. Please remove it from your MODULE.bazel file.
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 3 packages loaded
Loading: 3 packages loaded
    currently loading: 
Loading: 3 packages loaded
    currently loading: 
Loading: 3 packages loaded
    currently loading: 
Loading: 3 packages loaded
    currently loading: 
Loading: 3 packages loaded
    currently loading: 
Analyzing: target //:license-check (4 packages loaded, 0 targets configured)
Analyzing: target //:license-check (4 packages loaded, 0 targets configured)

Analyzing: target //:license-check (48 packages loaded, 10 targets configured)

Analyzing: target //:license-check (87 packages loaded, 10 targets configured)

Analyzing: target //:license-check (140 packages loaded, 2324 targets configured)

Analyzing: target //:license-check (153 packages loaded, 5569 targets configured)

Analyzing: target //:license-check (154 packages loaded, 9108 targets configured)

Analyzing: target //:license-check (164 packages loaded, 9264 targets configured)

Analyzing: target //:license-check (165 packages loaded, 9284 targets configured)

Analyzing: target //:license-check (165 packages loaded, 9284 targets configured)

Analyzing: target //:license-check (165 packages loaded, 9284 targets configured)

Analyzing: target //:license-check (166 packages loaded, 9284 targets configured)

Analyzing: target //:license-check (169 packages loaded, 11296 targets configured)

INFO: Analyzed target //:license-check (170 packages loaded, 11422 targets configured).
[12 / 16] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache, processwrapper-sandbox ... (2 actions running)
INFO: From Generating Dash formatted dependency file ...:
INFO: Successfully converted 2 packages from Cargo.lock to bazel-out/k8-fastbuild/bin/formatted.txt
[14 / 16] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 28.284s, Critical Path: 2.40s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 16 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

@github-actions

Copy link
Copy Markdown

The created documentation from the pull request is available at: docu-html

@ryan-steel ryan-steel added the documentation Improvements or additions to documentation label Jul 15, 2026
@ryan-steel ryan-steel self-assigned this Jul 15, 2026
@ryan-steel
ryan-steel marked this pull request as ready for review July 15, 2026 14:45
Comment thread README.md Outdated
Comment thread README.md
- **SteadyTime**: Monotonic time for duration measurements and timeouts
- **HighResSteadyTime**: High-precision monotonic time for precise timing applications
- **VehicleTime**: PTP-synchronized time for distributed automotive applications requiring initialization
- **Unified API**: Type-safe `Clock<Tag>::GetInstance().Now()` returns `ClockSnapshot<TimePoint, Status>` with atomic time + metadata reads

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure, we need to mention it here.
it is the implementtion details, not the actual fucntionality

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

Comment thread README.md
- **HighResSteadyTime**: High-precision monotonic time for precise timing applications
- **VehicleTime**: PTP-synchronized time for distributed automotive applications requiring initialization
- **Unified API**: Type-safe `Clock<Tag>::GetInstance().Now()` returns `ClockSnapshot<TimePoint, Status>` with atomic time + metadata reads
- **Event Subscription**: `Subscribe<EventType>()` / `Unsubscribe<EventType>()` for status changes and PTP protocol data

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is being used currently in PTP based timebase. I havea feeling, the current formulation is missleading

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure I understand your point but updated the wording to "timebase"

Comment thread README.md
- **Unified API**: Type-safe `Clock<Tag>::GetInstance().Now()` returns `ClockSnapshot<TimePoint, Status>` with atomic time + metadata reads
- **Event Subscription**: `Subscribe<EventType>()` / `Unsubscribe<EventType>()` for status changes and PTP protocol data
- **Time Infrastructure**
- **TimeDaemon**: Plugin-based time distribution daemon with IPC message broker

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need to mention here message broker?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

Comment thread README.md
- **Event Subscription**: `Subscribe<EventType>()` / `Unsubscribe<EventType>()` for status changes and PTP protocol data
- **Time Infrastructure**
- **TimeDaemon**: Plugin-based time distribution daemon with IPC message broker
- **TimeSlave**: PTP protocol implementation with offset calculation and rate adjustment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is not the PTP protocol implementaiton only.
Could you elaborate bit more?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added more detail

Comment thread README.md
- **Time Infrastructure**
- **TimeDaemon**: Plugin-based time distribution daemon with IPC message broker
- **TimeSlave**: PTP protocol implementation with offset calculation and rate adjustment
- **Test Utilities**: Mock backends and `ScopedClockOverride` for comprehensive testing

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is applicable to the interfaces only, but iun the full list.

Suggerstion, to update the list in general

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved to clock domain section

Comment thread README.md
> NOTE: This is just proposal, the final decision is on module maintainer how
> the module code needs to be built.
```bash
bazel test //...

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here as well, suggest to specify the score and examples subfoldeers in oder to minimize the risk not to touch the filex, which should be not be run.
also add the config

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Comment thread README.md
bazel test //tests/...
**Linux AArch64**:
```bash
bazel build --config=time-arm64-linux //...

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here and everywhere: add the sibfolders

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Comment thread README.md
- **Rust:** `clippy`, `rustfmt`, `Rust Unit Tests`
- **CI/CD:** GitHub Actions for automated builds and tests
```bash
bazel test --config=time-x86_64-linux --config=asan_ubsan_lsan --build_tests_only //...

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the asan_ubsan_lsan donfig alrady contains the time-x86_64-linux one?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at .bazelrc, I think no, it just sets sanitizer flags, debug symbols and test filters

Comment thread README.md
## 💡 Examples

- A **centralized docs structure** is planned.
Working examples demonstrating clock usage patterns, testing approaches, and integration techniques. See [examples/](examples/) for complete usage examples.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would believe, i nthe examples/ there is no documentation available. at lease in the root folder.
then either need to add docs there or add some usefull info and explanation here

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added more detail

Comment thread README.md
│ ├── time/ # Clock domains (SystemTime, SteadyTime, etc.)
│ ├── time_daemon/ # Time distribution daemon
│ ├── time_slave/ # PTP synchronization implementation
│ └── ts_client/ # Time status utilities (internal)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is not hte utility
it is the library to communicate with time slave

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

@ryan-steel
ryan-steel requested a review from lavrovvalera July 21, 2026 09:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

score/time: Improve README.md with module-specific content

3 participants