You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The load_threshold value is being read as a string, instead of a number/float. Am I using the wrong syntax?
It was patched like this in Ubuntu (patch by @lucaskanashiro):
--- a/tuned/plugins/plugin_cpu.py+++ b/tuned/plugins/plugin_cpu.py@@ -394,7 +394,7 @@ class CPULatencyPlugin(hotplug.Plugin):
return
load = instance._load_monitor.get_load()["system"]
- if load < instance.options["load_threshold"]:+ if load < float(instance.options["load_threshold"]):
self._set_latency(instance.options["latency_high"])
else:
self._set_latency(instance.options["latency_low"])
But I was wondering if this shouldn't instead be fixed in whatever is reading the config file and populating instance.options. I'm poking around a bit, but thought I would open this bug too.
I have a custom profile with the following, used in a test case:
The
load_threshold
value is being read as a string, instead of a number/float. Am I using the wrong syntax?It was patched like this in Ubuntu (patch by @lucaskanashiro):
But I was wondering if this shouldn't instead be fixed in whatever is reading the config file and populating
instance.options
. I'm poking around a bit, but thought I would open this bug too.Reading up on ConfigParser, looks like there is no magic conversion going on.
The text was updated successfully, but these errors were encountered: