fix: millisecond precision timestamps and correct history ordering #58
Reference in New Issue
Block a user
Delete Branch "feat/jobs-system"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
datetime('now') only stores to the second, making same-second events
indistinguishable. Switched all instance_history and job_runs writes
to strftime('%Y-%m-%dT%H:%M:%f', 'now') for millisecond precision.
Reverted getInstanceHistory to ORDER BY changed_at DESC, id DESC so
newest events appear at the top and instance creation (lowest id,
earliest timestamp) is always at the bottom.
Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com
datetime('now') only stores to the second, making same-second events indistinguishable. Switched all instance_history and job_runs writes to strftime('%Y-%m-%dT%H:%M:%f', 'now') for millisecond precision. Reverted getInstanceHistory to ORDER BY changed_at DESC, id DESC so newest events appear at the top and instance creation (lowest id, earliest timestamp) is always at the bottom. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>