Skip to content

autotrainer 0.16.0

Choose a tag to compare

@github-actions github-actions released this 30 Aug 17:13
· 4 commits to 70c6fbf40538fc5c27ba86d7344a5f903fe25062 since this release

[0.16.0] - 2026-08-20

Added

  • Hardware Telemetry Curves & Resource Diagnostics (#hwChart):
    • Live system resource meter footer with green pulse status indicator in sidebar.
    • Dedicated hardware telemetry card displaying GPU VRAM (GB / %), GPU model name, and Host RAM / CPU utilization curves over training steps and epochs.
    • REST endpoint GET /api/hardware with cross-platform memory and GPU detection.
  • Run Tagging, Star Favoriting & Sidebar Organization:
    • Star favorite toggle (⭐) on individual runs with persistent metadata state.
    • Sidebar filter tabs: [ All ] and [ ⭐ Starred ] with glow accents.
    • Inline run tag chip management: + Tag creator, ✕ tag pill deletion, and dynamic sidebar tag filter pills bar.
    • REST endpoints: POST /api/runs/<run_id>/tags and POST /api/runs/<run_id>/favorite.
  • Hyperparameter & Metric Parallel Coordinates Chart (#parallelCanvas):
    • High-performance Canvas multi-axis parallel coordinates visualization in Compare Mode.
    • Visualizes complex relationships and trajectories across Learning Rate -> Batch Size -> First Loss -> Training Loss -> Validation Loss across multiple selected runs.
  • Run Annotations & Markdown Notes Drawer (#notesCard):
    • Embedded Markdown drawer with Edit and live Preview rendering tabs.
    • Auto-persisted to both run.json and <run_dir>/notes.md on disk.
    • REST endpoint POST /api/runs/<run_id>/notes.
  • 1-Click Run Deletion & Archive:
    • Clean deletion of experiment runs and log directories from disk with modal confirmation.
    • REST endpoints DELETE /api/runs/<run_id> and POST /api/runs/<run_id>/archive.
  • Refined KPI Stat Cards:
    • Displays FIRST LOSS, TRAINING LOSS, VALIDATION LOSS, and EPOCHS with glowing accents.

Security

The Web UI added in 0.15.0 served a filesystem-mutating API with no
authentication on every network interface. Each item below was confirmed by
exploiting a running server, and is now pinned by a test in
tests/test_ui_security.py.

  • Unauthenticated remote directory deletion. run_id was joined onto the
    logs root with no containment check, so DELETE /api/runs/../<path>
    resolved outside it and reached shutil.rmtree. A live server answered
    {"success": true} and the directory was gone. All six lookups — plus a
    seventh inlined in _get_run_data and two more behind the HTML/Markdown
    export writes, which made it an arbitrary-write primitive too — now go
    through one _safe_run_dir() that rejects separators and anything
    resolving outside a configured root.
  • autotrainer ui bound 0.0.0.0. On a shared SLURM login node that
    published rename/archive/delete to every user who could route to the port.
    It now binds 127.0.0.1; --host widens it deliberately and prints a
    warning naming what is exposed.
  • No authentication. A session token is now generated per run and printed
    as part of the URL, carried afterwards by an HttpOnly; SameSite=Strict
    cookie (also accepted as ?token= or X-Autotrainer-Token) and compared
    with secrets.compare_digest. --no-token opts out. SameSite plus an
    Origin check on mutating verbs closes the CSRF hole that let any page a
    user visited drive the delete endpoint.
  • POST /api/sources accepted any absolute path, turning the dashboard
    into a filesystem browser — a home directory listed 45 "runs". It now
    requires a directory that actually contains run folders.
  • Stored XSS via run tags. Tags were interpolated raw into innerHTML,
    including inside onclick="removeTagFromCurrentRun('${tag}')". Tags and
    usernames are escaped, escapeHtml now covers quotes, and the tag remove
    control binds a listener instead of building a JS string.

Fixed

  • AutotrainerCallback.on_epoch_end() crashed on its own defaults.
    Omitting train_loss — normal for a callback that only has a validation
    number — reached float(None) and raised TypeError, killing the run it
    was meant to be observing. log_epoch now treats every metric as optional
    and reads its three call shapes through one code path.
  • optimize=True silently disabled per-epoch reshuffling. prepare()
    wraps a sharded loader in _AutoEpochDataLoader so
    DistributedSampler.set_epoch() advances on its own, but the optimize
    loader-defaults step and the auto_bs sweep each build a fresh
    DataLoader, which the wrapper did not survive. set_epoch was then never
    called and every epoch replayed one fixed permutation on every rank —
    silently, with nothing raised. It fired on the most common configuration
    there is: multi-GPU, optimize=True (the default), and an untuned loader,
    since build_loader_defaults() only has work to do when num_workers is 0
    or pin_memory is off. The wrapper is now applied once, after every
    rebuild. Loaders the user sharded themselves are still passed through
    unwrapped, and shuffle=False still means a fixed order.
  • train() synced the GPU twice per step. loss.item() was called once
    for the running total and again for the summary; each is a device sync, so
    the loop stalled twice per iteration in the entry point whose selling point
    is throughput. Read once, reused.

Changed

  • Docs now describe the auto-managed epoch shuffling that 0.14.0 added.
    docs/guide/gpu-optimization.md still showed the pre-0.14.0 log line
    (- call autotrainer.set_epoch(loader, epoch) ...) where the code prints
    - epoch shuffling auto-managed, and the guides still presented the manual
    call as required. They now say it is optional for loaders prepare()
    sharded, and — worth knowing — that the automatic counter overwrites an
    explicit epoch number, so resuming at a specific epoch needs the loader you
    sharded yourself. set_epoch's own docstring says the same.
  • Removed the suhas and suhas-goravale-siddaramu optional-dependency
    groups
    from pyproject.toml. Both were ["psutil"] and shipped as real
    installable extras (pip install autotrainer[suhas]) in the published
    metadata. The autotrainer suhas CLI credits command is unrelated and
    stays.
  • ThroughputMonitor is now in __all__. It was documented in
    docs/guide/monitors.md with a worked example while absent from __all__,
    which the README declares the boundary of the stable public API — so the
    docs taught something the policy called internal. Also added to the README's
    entry-point table. tests/test_docs.py now checks this direction too; it
    only ever verified that __all__ members appear in the docs, never that
    documented names are exported.