bytecodealliance / bytecodealliance/wizer
Monotonic clock offsetting
Open
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
We just landed a change to StarlingMonkey to support handling the invariants of the monotonic clock by defining an offset based on the difference between the Wizer time monotonic clock and the runtime monotonic clock.
Ideally this should always be maintained in Wizer workflows - so it could be worth investigating this further.
Downstream fix: https://github.com/bytecodealliance/StarlingMonkey/commit/72e7481f2a4d5a33ea0218c439b9a1dcead77321
Contributor guide
Assessment
This issue has not been assessed yet.