The hash included `ts` in the input despite the docstring promising it was "independent of ts/actor/session". On Windows, millisecond timer resolution caused two calls within the same tick to get different timestamps, producing different hashes for identical cmd+params. Remove `ts` from the hash input to match documented behavior. Revert continue-on-error on windows-portability now that the root cause is fixed. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| CODEOWNERS | ||
| FUNDING.yml | ||
| PULL_REQUEST_TEMPLATE.md | ||