build(deps): dbos-transact 1.2.0, kin-openapi 0.147.0, sqlite 1.57.0 (supersedes #412) - #417
Merged
Merged
Conversation
… run-duration guard tolerates DBOS ms quantization Supersedes Dependabot #412, which failed CI on two independent axes: 1. go-get-proxied v1.4.1 raises its go directive to 1.26, dragging this module's directive past CI's pinned go-version '1.25' (GOTOOLCHAIN=local) and failing every Go job at package load. Held at v1.4.0 with a dependabot.yml ignore naming the lift condition (CI's Go moving to 1.26); the other three bumps keep go 1.25.7. 2. DBOS 1.2.0's faster completion timing exposes a storage-quantization artifact: sysdb stores created_at rounded to the nearest millisecond but completed_at truncated, so a sub-millisecond run can read as completing 1ms before it started. Mill's runDuration treated any negative span as clock skew and dropped the run from AvgDuration (SampleSize undercounted, ~1 in 20 locally at -count=20). runDuration now accepts up to 1ms negative span, clamped to zero, with the boundary pinned in TestRunDuration's table (1ms valid, 2ms invalid). go test ./... green; golangci-lint clean on both tag sets; TestHomeMetrics_AvgDurationAndLastTriggeredAt_WiredFromRealRuns green at -count=25 under DBOS 1.2.0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012im1JxQQV2ahnXzZDdVmZq
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
created_atrounded to the nearest millisecond butcompleted_attruncated, so a sub-millisecond run can read as completing 1ms before it started. 1.2.0's faster completion timing made this common (~1 in 20 locally).runDurationtreated any negative span as clock skew and silently dropped the run from Home's AvgDuration; it now accepts up to 1ms negative span, clamped to zero, with the boundary pinned in the table test (1ms valid, 2ms invalid).Testing
go test ./...green; golangci-lint clean on default and-tags server.TestHomeMetrics_AvgDurationAndLastTriggeredAt_WiredFromRealRunsgreen at-count=25under DBOS 1.2.0 (failed ~1/20 before the fix).🤖 Generated with Claude Code
https://claude.ai/code/session_012im1JxQQV2ahnXzZDdVmZq