Stream: git-wasmtime

Topic: wasmtime / PR #15001 wasmtime-cache: handle clock drift S...

Wasmtime GitHub notifications bot (Oct 26 2026 at 22:47):

pchickey edited PR #15001.

Wasmtime GitHub notifications bot (Oct 26 2026 at 22:48):

pchickey edited PR #15001:

instead of panicking, an obscure case reachable with certain inputs for the allowed_clock_drift_for_files_from_future configuration field treats all times as equal when large drifts are allowed. This isnt strictly true, but for this corner case its good enough.

<!--
Please make sure you include the following information:

• If this work has been discussed elsewhere, please include a link to that
  conversation. If it was discussed in an issue, just mention "issue #...".

• Explain why this change is needed. If the details are in an issue already,
  this can be brief.

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please review the Bytecode Alliance's AI tool usage policy at
https://github.com/bytecodealliance/governance/blob/main/AI_TOOL_POLICY.md

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

Wasmtime GitHub notifications bot (Oct 26 2026 at 22:55):

pchickey updated PR #15001.

Wasmtime GitHub notifications bot (Oct 26 2026 at 22:57):

pchickey updated PR #15001.

Wasmtime GitHub notifications bot (Oct 26 2026 at 23:08):

alexcrichton added PR #15001 wasmtime-cache: handle clock drift SystemTime addition overflows to the merge queue.

Wasmtime GitHub notifications bot (Oct 26 2026 at 23:30):

alexcrichton removed PR #15001 wasmtime-cache: handle clock drift SystemTime addition overflows from the merge queue.

Wasmtime GitHub notifications bot (Oct 26 2026 at 23:30):

:check: alexcrichton merged PR #15001.

Last updated: Oct 31 2026 at 23:03 UTC