- Reset torch.cuda.reset_peak_memory_stats at fit start (gated by _is_cuda), so max_mem reflects this run's footprint rather than a process-lifetime / batch_size="auto"-probe peak (#2)
- Warn via rank_zero_warn + setdefault instead of silently overwriting a same-named user-logged metric (#3)
- Reword class docstrings from "GPU" to "CUDA" for accuracy — implementation is CUDA-only (#4)
- Add ProgressBar base to _GpuMemoryMetricsMixin, dropping the now-unresolvable type:ignore[misc] (#5, subsumes #17)
- Test peak-reset semantics across sequential get_metrics() calls (#6)
- Add missing Rich progress bar coverage for the cuda-present-but-not-initialized branch (#7)
- Test _is_cuda with None/non-torch.device input (#8)
- Add rounding-boundary test cases (0 bytes, 0.5MB boundary) (#9)
- Fold xla/tpu device-type case into the existing non-cuda parametrize (#10)
- Fix module docstring overstating on_test_end's gating mechanism (#14)
- Document max_mem as rank-local under DDP (#15)
- Match legacy "123 MB" spacing (space before unit) for restoration parity (#18)
---------
Co-authored-by: Jesús Royeth <JESUSROYETH@users.noreply.github.com>
Co-authored-by: Jirka Borovec <6035284+Borda@users.noreply.github.com>
Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>
Jesús Royeth
612d120de0