On 2018/07/26 09:24, Ian Sutton wrote: > htop was broken for a few months -- after the addition of a new > CPUSTATE (https://marc.info/?l=openbsd-cvs&m=152630109526317&w=2) > re-indexed the CPUSTATES in sched.h, htop's hard-coded values now > sampled the wrong metric, resulting in perpetually zero activity on the > meters.
Reminder to everyone who looks after ports using CPUSTATES things, it is possible that some might still misbehave. For many we'll have noticed or had reports by now, but it would be nice if users of the less common ports below could check things out on -current and make sure they still work. These are the ones that I identified as using CPUSTATES and haven't (to my memory) received any additional fixed. Most are probably OK but some might not be. devel/cmake devel/libgtop2 devel/libuv devel/py-uv devel/spidermonkey52 lang/erlang/16 lang/erlang/17 lang/erlang/18 lang/erlang/19 lang/moarvm lang/node mail/mozilla-thunderbird net/netrate net/zabbix plan9/plan9port sysutils/beats/filebeat sysutils/beats/heartbeat sysutils/beats/metricbeat sysutils/beats/packetbeat sysutils/bubblemon-dockapp sysutils/libstatgrab sysutils/libvirt sysutils/monit sysutils/py-psutil sysutils/symon sysutils/tmux-mem-cpu-load www/firefox-esr www/mozilla-firefox www/ruby-passenger www/seamonkey www/tor-browser/browser x11/dstat x11/gnome/builder x11/gnustep/timemon x11/i3status x11/icewm x11/kde/base3 x11/kde4/superkaramba x11/kde4/workspace x11/xfce4/xfce4-cpugraph x11/xfce4/xfce4-systemload x11/xfce4/xfce4-taskmanager
