Repository navigation
remote_handler 0.4.1
[0.4.1] — 2026-07-09
A patch/minor increment on top of 0.4.0: two optional per-cluster config
knobs, a bug fix in trajectory sharding, and the SLURM-availability probe moved
behind the connection-resilience wrapper. No breaking changes.
Added
conda_env_dir— an optionalClusterConfigfield naming the directory
on the remote that holds the named conda environments, so activation no
longer assumes a default install location. Prompted for by
remote_handler configure clusterand threaded throughremote_env.slurm_header_add— reintroduced as an optionalClusterConfigfield for
extra lines injected verbatim into the generated SLURM job header (e.g.
account/partition/QoS directives). Exposed via the CLI and rendered by the
SLURM handler.
Changed
validate_slurm_availablemoved fromcluster_handlertoslurm_utilsand
now runs through the same resilient wrapper as other remote commands, so a
transient credential/connection failure while probingsbatchpauses and
retries instead of crashing.
Fixed
AtomsShardManagercrash on a default slice. Whenevery/start/end
were left at theirNonedefaults (asVASPHandlerand the other DFT
handlers do),combine_trajscomputediteration_idx * indices.step—
int * None— and raisedTypeErrorbefore any job was submitted. The
slice fields are now normalized (step→1,start→0) anditeration_index
is computed asstart + iteration_idx * step, which also fixes a latent
offset bug where a non-Nonestartwas ignored. Regression tests added.