Show more VM details in the limactl list command

[afbjorklund]

Add cpus / memory / disk, in addition to the arch.

NAME         STATUS     SSH                ARCH      CPUS    MEMORY    DISK      DIR
alpine       Stopped    127.0.0.1:60020    x86_64    4       4GiB      100GiB    /home/anders/.lima/alpine
default      Running    127.0.0.1:60022    x86_64    4       4GiB      100GiB    /home/anders/.lima/default

Use numbers for the machine-readable representation.

{
  "name": "alpine",
  "status": "Stopped",
  "dir": "/home/anders/.lima/alpine",
  "arch": "x86_64",
  "cpus": 4,
  "memory": 4294967296,
  "disk": 107374182400,
  "sshLocalPort": 60020
}
{
  "name": "default",
  "status": "Running",
  "dir": "/home/anders/.lima/default",
  "arch": "x86_64",
  "cpus": 4,
  "memory": 4294967296,
  "disk": 107374182400,
  "sshLocalPort": 60022,
  "hostAgentPID": 271631,
  "qemuPID": 271649
}

[AkihiroSuda]

Why not int

[afbjorklund]

I think the alternative would have been uint64, but it doesn't fit into a JavaScript integer.
Basically using the same as the go-units library, so that the conversion goes smoother...

// BytesSize returns a human-readable size in bytes, kibibytes,
// mebibytes, gibibytes, or tebibytes (eg. "44kiB", "17MiB").
func BytesSize(size float64) string

[afbjorklund]

Not sure either of them actually work, so probably have to use string or maps...

Can use int64 and do the conversion in the command instead, if it improves things.

[jandubois]

The PR looks fine to me. Maybe using string would be better, so very large values can be round-tripped through JavaScript without losing precision, but don't really have strong feelings either way.

[afbjorklund]

They used strings in podman, but then they also used uint64 for cpus (in case you have more than 2147483647 ?)

So while it is true that you can't have more than 9007199254740992 bytes, that's also a lot of memory/disk (8 PiB)
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INTEGER

[afbjorklund]

Possibly should "hide" the docker dependency, in some local string/int64 conversion function ?

[AkihiroSuda]

LGTM, thanks.

We should detect the terminal width and limit the number of the columns correspondingly, but it can be worked out later.