Skip to content

Fix YAML scientific notation bug in run hash (2.0.2) - #4

Merged
AndrewSillifant merged 3 commits into
mainfrom
2.0.2
Mar 6, 2026
Merged

Fix YAML scientific notation bug in run hash (2.0.2)#4
AndrewSillifant merged 3 commits into
mainfrom
2.0.2

Conversation

@AndrewSillifant

Copy link
Copy Markdown
Collaborator

Summary

  • Fix run hash generation where hex strings like 764303e9 are parsed as scientific notation (7.64303e+9) by YAML 1.1 parsers, causing invalid Kubernetes job names
  • Hash now always starts with a letter by sliding the 8-char window through the SHA-256 digest
  • Bump version to 2.0.2

Test plan

  • 138 unit tests passing
  • New test verifies 100 random hashes all start with a letter
  • Verified end-to-end against 8 SQL Server hosts — build, run, results, report, clean all succeed

Use absolute GitHub URL instead of relative path that breaks on PyPI.
Hex hashes like '764303e9' are parsed as floating point (7.64303e+9)
by YAML 1.1 parsers, causing invalid Kubernetes job names. Ensure
the hash always starts with a letter by sliding the 8-char window.

Bump version to 2.0.2.
@AndrewSillifant
AndrewSillifant merged commit 2ea7e5a into main Mar 6, 2026
9 checks passed
@AndrewSillifant
AndrewSillifant deleted the 2.0.2 branch March 6, 2026 19:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant