Skip to content

Releases: dbohdan/memsparkline

v0.9.1

21 Dec 08:25
Compare
Choose a tag to compare
  • Fixed memory usage not being measured recursively.

v0.9.0

13 Dec 08:21
Compare
Choose a tag to compare
  • memsparkline now passes through the exit code from the program it runs.

v0.8.1

02 Dec 11:39
Compare
Choose a tag to compare
  • Fixed the lack of option validation after -h/--help and -v/--version.

v0.8.0

01 Dec 13:00
Compare
Choose a tag to compare
  • Minor breaking change in the CLI: memsparkline will process the options -h/--help and -v/--version like other options. This means they must be given before the first positional argument. These options were special and processed in any position. It was supposed to make help easier to access, but in practice it caused problems more than it helped. What this change means is that the option -h in the command memsparkline ls -h used to make memsparkline print help and exit; now -h is passed to ls.

v0.7.1

23 Nov 13:34
Compare
Choose a tag to compare
  • Fixed division by zero when maximum memory usage is zero.
  • Removed redundancy from the error message for --dump errors.

v0.7.0

23 Nov 11:36
Compare
Choose a tag to compare
  • memsparkline has been ported from Python to Go.
  • Static binaries are now available.
  • Changed -d/--dump to append to the output file for consistency with -o/--output. You can accidentally lose old data if you expect --dump to behave like --output. Since we prefix every usage figure with a timestamp, it should be reasonably easy to separate the output from different runs.
  • NetBSD is not supported until gopsutil supports NetBSD.