---
title: "2026-08-27 Histo vxData SDK 3 upgrade"
description: "Upgraded histo to vxdata-sdk 3.0.0 and opened a focused dependency PR."
image: "https://docs.virdx.dev/img/virdx-social-card.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.virdx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-08-27 Histo vxData SDK 3 upgrade

## Work Done

- Updated the direct `vxdata-sdk` constraint in `virdx/histo` from `>=2.1.0,<3` to `>=3,<4`.
- Ran the targeted `pixi upgrade vxdata-sdk`; the lock resolves `vxdata-sdk` and `vxdata-schemas` 3.0.0 plus the SDK's new transitive dependencies.
- Ran focused vxData query and pull-step tests: 15 passed.
- Opened [virdx/histo PR #282](https://github.com/virdx/histo/pull/282).

## Lessons Learned: Pitfalls

- Pixi canonicalized `>=3,<4` to `>=3.0.0,<4` during upgrade, so the requested spelling had to be restored afterward; `pixi lock --check` confirmed the lock remained current.
- The full mypy task fails on macOS at existing Linux-only `os.sched_getaffinity` use in `scripts/domain_representation/bench_cell_seg_sweep.py`; no unrelated source fix was added.
- Pixi rewrote some lock metadata from compressed mappings to hash mappings, but did not upgrade unrelated package versions.

## Lessons Learned: Improvements

- Repo guidance could record that `pixi upgrade` can canonicalize version constraints and rewrite lock metadata even for a targeted dependency.
- The mypy task could use a platform guard or macOS-compatible typing pattern for `os.sched_getaffinity` so documented local validation works on macOS.

Source: https://docs.virdx.dev/knowledge/inbox/2026-08-27-histo-vxdata-sdk-3-upgrade/index.mdx