Skip to content

Update strobealign index to format version 5 for strobealign 0.17.0#296

Open
wwood wants to merge 2 commits into
mainfrom
claude/update-strobealign-db-7hos5n
Open

Update strobealign index to format version 5 for strobealign 0.17.0#296
wwood wants to merge 2 commits into
mainfrom
claude/update-strobealign-db-7hos5n

Conversation

@wwood

@wwood wwood commented Jun 26, 2026

Copy link
Copy Markdown
Owner

Regenerated tests/data/7seqs.fna.r100.sti using strobealign 0.17.0, which
writes index format version 5. The old index was version 3, incompatible
with strobealign >=0.17.0, causing test_strobealign_pregenerated_index to fail.

Also bumped the minimum strobealign version in pixi.toml to >=0.17.0 to
match the index format.

Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01BUkWFEp9YRYAVwvVDFudGU

Regenerated tests/data/7seqs.fna.r100.sti using strobealign 0.17.0, which
writes index format version 5. The old index was version 3, incompatible
with strobealign >=0.17.0, causing test_strobealign_pregenerated_index to fail.

Also bumped the minimum strobealign version in pixi.toml to >=0.17.0 to
match the index format.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BUkWFEp9YRYAVwvVDFudGU

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5da16a4d5f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread pixi.toml Outdated
bwa-mem2 = "*"
dashing = ">=0.4.0,<1.0" # dashing 1.0 build gives illegal instruction errors
strobealign = ">=0.14.0" # tests use a pregenerated v3 database
strobealign = ">=0.17.0" # tests use a pregenerated v5 database

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Update the frozen Pixi lockfile too

This constraint doesn't affect the locked Linux CI path because .github/workflows/test-coverm.yml:28 runs pixi run --frozen cargo test, and Pixi documents --frozen as installing from the lockfile without updating it. Since this commit leaves pixi.lock pinning bioconda/linux-64/strobealign-0.14.0 at pixi.lock:62, the frozen job will still install 0.14 and the new v5 pregenerated index remains unreadable; please regenerate and commit pixi.lock together with this manifest change.

Useful? React with 👍 / 👎.

Instead of storing a version-specific strobealign index in git (which
breaks whenever strobealign is upgraded to a format that's incompatible
with the stored file), generate the index at runtime before the test
runs. This way the index always matches the currently-installed
strobealign version.

Also reverts the strobealign version constraint in pixi.toml back to
>=0.14.0 (the >=0.17.0 bump caused a dependency conflict with
dashing 0.4.0 over zlib version requirements).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BUkWFEp9YRYAVwvVDFudGU
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.

2 participants