[WEBUI] Irix mode (per core instead of per CPU percentage) not togglable

[Blackinator]

Is the Irix/Solaris mode toggle supported in webserver mode? I currently cannot get it to work.
I've tried:

• setting -0 or --disable-irix in the GLANCES_OPT env variable for the Docker container
• pressing '0' in the browser with the webui open
• using a few different versions of the Docker image: latest, latest-full, dev and ubuntu-latest-full

I did verify that the mode can be disabled if I run glances as a standard command, through the console inside the container. Pressing '0' works as a toggle, and passing -0 or --disable-irix as an argument works to disable the mode on launch.

I'm currently running glances through Docker on Alpine Linux. In case it's pertinent, here's the docker-compose.yaml file I'm running:

services:
  glances:
    image: nicolargo/glances:latest-full
    container_name: glances
    restart: unless-stopped
    pid: host
    privileged: true
    volumes:
      - ${DOCKER_HOST_PATH}:/var/run/docker.sock
      - /etc/os-release:/etc/os-release:ro
      - ~/.cont_data/glances/glances.conf:/etc/glances/glances.conf
    environment:
      - "GLANCES_OPT=-w --disable-irix"
    network_mode: host

I did look around to see if there was a mention of this toggle specifically not being implemented in webservice mode and couldn't see any, although it's absolutely possible I may have missed something. Apologies in advance if I turns out I just can't read XD

[nicolargo]

Hi @Blackinator

it's completely true. The current version of the WebUI did not support the Irix option.

It will be corrected in the next millestone.

Thanks for the head up !

Nicolas

[Blackinator]

Thanks, I appreciate the response!

[nicolargo]

Implementation done on the develop branch.

@Blackinator Any chance to test it on your side ?

[Blackinator]

Hi, thanks for the quick work!

It works great! The '0' key works and the command line arguments are working as well, both in webserver mode. I did think I was going crazy at first, as the newest dev Docker image seemed to exhibit the same behaviour as before, but I went and installed from the develop branch in this repo (which is basically what you said, so it's now confirmed I cannot read XD) using pip, and all was good.

Oh, and I almost forgot to mention, I tested both the dev Docker image and the develop branch after resetting the browser cache for the site.