Skip to content

fix(upgrade): use sha256 lock key hash in acquire_upgrade_lock in bootstrap-upgrade.sh - #2828

Open
vaibhavsrv wants to merge 2 commits into
Osmantic:mainfrom
vaibhavsrv:fix/bootstrap-upgrade-sha256-lock-key
Open

fix(upgrade): use sha256 lock key hash in acquire_upgrade_lock in bootstrap-upgrade.sh#2828
vaibhavsrv wants to merge 2 commits into
Osmantic:mainfrom
vaibhavsrv:fix/bootstrap-upgrade-sha256-lock-key

Conversation

@vaibhavsrv

Copy link
Copy Markdown
Contributor

Problem

In ods/scripts/bootstrap-upgrade.sh, acquire_upgrade_lock() computes the lock directory name using raw cksum. Output formatting and checksum algorithms for cksum differ between GNU coreutils on Linux and BSD cksum on macOS. If upgrade processes run across mixed host environments, inconsistent lock directory names allowed multiple model upgrade routines to run concurrently, risking corrupted GGUF downloads.

Fix

Update acquire_upgrade_lock() to use standard SHA-256 hashing (sha256sum 2>/dev/null || shasum -a 256 2>/dev/null || cksum) for cross-platform lock key generation in bootstrap-upgrade.sh.

Verification

Ran bash -n ods/scripts/bootstrap-upgrade.sh (passed cleanly). Verified lock key hashing on Linux and macOS. git diff --check passed cleanly.

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