You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pixi run build-docs command for cuda-core doesn't work correctly (this may be true of other packages, but I only tested this one).
It rebuilds cuda_bindings from scratch every time, even if there were no changes.
It doesn't rebuild cuda_core at all, even if there were changes.
This means one must rebuild cuda_core manually to generate docs that reflect new changes.
It should either rebuild everything or rebuild nothing. I'm not sure why it does what it does. (And I'm not a regular user of our pixi configs, but I'm starting to file bugs so I can become one).
I wasn't able to repro having cuda_bindings rebuilt from scratch every time though, where multiple pixi run invocations for me did not rebuild cuda-bindings after the 1st invocation.
I think this might have failed to build because the command is 'pixi run docs-build', not the "build-docs" you put in.
When I pixi clean, then 'pixi run docs-build' in the cuda_core directory, it solves and prepares all the packages (like cuda-bindings, pathfinder, &c), which might have made you think it was building the documentation from them. But, it only runs sphinx on the documentation for cuda_core.
Activity
[-]pixi run build-docs[/-][+]pixi run build-docs doesn't update content[/+]kkraus14 commentedon May 14, 2026
Unfortunately, I think this is a pixi bug / limitation where I've raised an issue upstream: prefix-dev/pixi#6122
kkraus14 commentedon May 14, 2026
I wasn't able to repro having
cuda_bindingsrebuilt from scratch every time though, where multiplepixi runinvocations for me did not rebuild cuda-bindings after the 1st invocation.jpascucci-nv commentedon Sep 8, 2026
I think this might have failed to build because the command is 'pixi run docs-build', not the "build-docs" you put in.
When I pixi clean, then 'pixi run docs-build' in the cuda_core directory, it solves and prepares all the packages (like cuda-bindings, pathfinder, &c), which might have made you think it was building the documentation from them. But, it only runs sphinx on the documentation for cuda_core.
mdboom commentedon Oct 2, 2026
Ok, happy to close this for now.