oxidecomputer / oxidecomputer/buildomat
stop telling half-truths about time in the detailed job view
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Historically the wollongong web interface (used by GitHub-driven jobs to display job events) has displayed only the time field from the event record.
This is at times misleading; e.g., when trying to correlate timestamps in log files from the job against the event stream itself. The time you usually want in this case is actually stored in time_remote, using the agent's local clock. We should provide a first class facility for seeing both time and time_remote in a way that makes sense to the user, and which makes it clear where the timestamp came from and what value it has in determining when something happened.
In addition, we should also expose the time_factory time (see #24) and the agent monotonic delta time (#25) as well.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the detailed job view and its event record, then review issues #24 and #25 for the meanings of time_factory and the agent monotonic delta time. Done means the view exposes time, time_remote, time_factory, and the monotonic delta while clearly identifying each timestamp's source and significance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100