Error about Unknown node feature: metrcis adding 0 value

What happened?

Ubuntu
Linux Kernel

22.04.3 LTS
5.15.0-78-generic x86_64

Kubernetes
k8s_cni_version
Docker
Helm

1.21.0
0.7.5
20.10.12-0ubuntu1~22.04.3
3.5.4

I make build-manifest OPTS="ESTIMATOR_SIDECAR_DEPLOY"
And change the model server image to the quay.io/sustainable_computing_io/kepler_model_server:v0.6 and exporter image to quay.io/sustainable_computing_io/kepler:latest-libbpf in the daemonset.
Finally, change log level to v5.
The following is my kepler exporter log
I0829 03:43:02.332357       1 gpu.go:46] Failed to init nvml, err: could not init nvml: error opening libnvidia-ml.so.1: libnvidia-ml.so.1: cannot open shared object file: No such file or directory
I0829 03:43:02.338686       1 qat.go:35] Failed to init qat-telemtry err: could not get qat status exit status 127
I0829 03:43:02.347937       1 exporter.go:158] Kepler running on version: 4b8a281
I0829 03:43:02.348008       1 config.go:270] using gCgroup ID in the BPF program: true
I0829 03:43:02.348079       1 config.go:272] kernel version: 5.15
I0829 03:43:02.348169       1 exporter.go:170] LibbpfBuilt: true, BccBuilt: false
I0829 03:43:02.348201       1 exporter.go:189] EnabledBPFBatchDelete: true
I0829 03:43:02.348260       1 config.go:143] ENABLE_EBPF_CGROUPID: true
I0829 03:43:02.348277       1 config.go:144] ENABLE_GPU: true
I0829 03:43:02.348287       1 config.go:145] ENABLE_QAT: false
I0829 03:43:02.348306       1 config.go:146] ENABLE_PROCESS_METRICS: false
I0829 03:43:02.348341       1 config.go:147] EXPOSE_HW_COUNTER_METRICS: false
I0829 03:43:02.348357       1 config.go:148] EXPOSE_CGROUP_METRICS: true
I0829 03:43:02.348365       1 config.go:149] EXPOSE_KUBELET_METRICS: true
I0829 03:43:02.348374       1 config.go:150] EXPOSE_IRQ_COUNTER_METRICS: true
I0829 03:43:02.348417       1 config.go:151] EXPOSE_ESTIMATED_IDLE_POWER_METRICS: false. This only impacts when the power is estimated using pre-prained models. Estimated idle power is meaningful only when Kepler is running on bare-metal or with a single virtual machine (VM) on the node.
I0829 03:43:02.348489       1 rapl_msr_util.go:129] failed to open path /dev/cpu/0/msr: no such file or directory
I0829 03:43:02.348569       1 power.go:71] Unable to obtain power, use estimate method
I0829 03:43:02.348640       1 csv_cred.go:68] failed to read csv file: node name understudent not found in file /etc/redfish/redfish.csv
I0829 03:43:02.348699       1 redfish.go:173] failed to initialize node credential: no supported node credential implementation
I0829 03:43:02.348743       1 power.go:56] use acpi to obtain power
I0829 03:43:02.348950       1 acpi.go:67] Could not find any ACPI power meter path. Is it a VM?
I0829 03:43:02.349009       1 bpf_perf.go:82] hardeware counter metrics config false
I0829 03:43:02.349023       1 bpf_perf.go:84] hardeware counter metrics not enabled
I0829 03:43:02.349054       1 bpf_perf.go:100] irq counter metrics config true
I0829 03:43:02.376817       1 utils.go:56] Available ebpf metrics: [bpf_cpu_time_us bpf_net_tx_irq bpf_net_rx_irq bpf_block_irq]
I0829 03:43:02.376855       1 utils.go:57] Available counter metrics: []
I0829 03:43:02.376858       1 utils.go:58] Available cgroup metrics from cgroup: [cgroupfs_memory_usage_bytes cgroupfs_kernel_memory_usage_bytes cgroupfs_tcp_memory_usage_bytes cgroupfs_cpu_usage_us cgroupfs_system_cpu_usage_us cgroupfs_user_cpu_usage_us cgroupfs_ioread_bytes cgroupfs_iowrite_bytes block_device                                                s_used]
I0829 03:43:02.376878       1 utils.go:59] Available cgroup metrics from kubelet: [kubelet_cpu_usage kubelet_memory_bytes]
I0829 03:43:02.376986       1 model.go:176] Model Config CONTAINER_TOTAL: {ModelType:Ratio ModelOutputType:DynPower TrainerName: EnergySource:acpi SelectFilter: InitModelURL: InitModelFilepath: IsNodePowerModel:false ContainerFeatureNames:[] NodeFeatureNames:[] SystemMetaDataFeatureNames:[] SystemMetaDataFeatureValues:[]}
I0829 03:43:02.377018       1 model.go:94] Using Power Model Ratio
I0829 03:43:02.377039       1 container_energy.go:109] Using the Ratio/DynPower Power Model to estimate Container Platform Power
I0829 03:43:02.377050       1 model.go:176] Model Config CONTAINER_COMPONENTS: {ModelType:Ratio ModelOutputType:DynPower TrainerName: EnergySource:rapl SelectFilter: InitModelURL: InitModelFilepath: IsNodePowerModel:false ContainerFeatureNames:[] NodeFeatureNames:[] SystemMetaDataFeatureNames:[] SystemMetaDataF                                                eatureValues:[]}
I0829 03:43:02.377059       1 model.go:94] Using Power Model Ratio
I0829 03:43:02.377064       1 container_energy.go:118] Using the Ratio/DynPower Power Model to estimate Container Component Power
I0829 03:43:02.377073       1 model.go:176] Model Config PROCESS_TOTAL: {ModelType:Ratio ModelOutputType:DynPower TrainerName: EnergySource:acpi SelectFilter: InitModelURL: InitModelFilepath: IsNodePowerModel:false ContainerFeatureNames:[] NodeFeatureNames:[] SystemMetaDataFeatureNames:[] SystemMetaDataFeatureValues:[]}
I0829 03:43:02.377082       1 model.go:94] Using Power Model Ratio
I0829 03:43:02.377087       1 process_power.go:108] Using the Ratio/DynPower Power Model to estimate Process Platform Power
I0829 03:43:02.377094       1 model.go:176] Model Config PROCESS_COMPONENTS: {ModelType:Ratio ModelOutputType:DynPower TrainerName: EnergySource:rapl SelectFilter: InitModelURL: InitModelFilepath: IsNodePowerModel:false ContainerFeatureNames:[] NodeFeatureNames:[] SystemMetaDataFeatureNames:[] SystemMetaDataFea                                                tureValues:[]}
I0829 03:43:02.377100       1 model.go:94] Using Power Model Ratio
I0829 03:43:02.377105       1 process_power.go:117] Using the Ratio/DynPower Power Model to estimate Process Component Power
I0829 03:43:02.377115       1 model.go:176] Model Config NODE_TOTAL: {ModelType:LinearRegressor ModelOutputType:AbsPower TrainerName: EnergySource:acpi SelectFilter: InitModelURL: InitModelFilepath: IsNodePowerModel:false ContainerFeatureNames:[] NodeFeatureNames:[] SystemMetaDataFeatureNames:[] SystemMetaDataF                                                eatureValues:[]}
I0829 03:43:02.377346       1 lr.go:188] LR Model (AbsPower): loadWeightFromURLorLocal(): &map[platform:{{4067.51980453514 map[] map[kubelet_cpu_usage:{8.225074882327771 61.882611238231696<PHONE_NUMBER>9213587} kubelet_memory_bytes:{9.011536046098989e+06 4.377864223762704e+14 11.4818854701994}]}}] (error: <nil>)
I0829 03:43:02.377386       1 model.go:120] Using Power Model AbsPower
I0829 03:43:02.377396       1 node_platform_energy.go:53] Using the LinearRegressor/AbsPower Power Model to estimate Node Platform Power
I0829 03:43:02.377405       1 model.go:176] Model Config NODE_COMPONENTS: {ModelType:EstimatorSidecar ModelOutputType:AbsPower TrainerName: EnergySource:rapl SelectFilter: InitModelURL:https://raw.githubusercontent.com/sustainable-computing-io/kepler-model-db/main/models/Linux-4.15.0-213-generic-x86_64_v0.6/rapl/AbsPower/KubeletOnly/GradientBoostingRegressorTrainer_1.zip InitModelFilepath: IsNodePowerModel:false ContainerFeatureNames:[] NodeFeatureNames:[] SystemMetaDataFeatureNames:[] SystemMetaDataFeatureValues:[]}
I0829 03:43:03.904356       1 model.go:144] Using Power Model AbsPower
I0829 03:43:03.904382       1 node_component_energy.go:54] Using the EstimatorSidecar/AbsPower Power Model to estimate Node Component Power
I0829 03:43:03.904390       1 exporter.go:212] Initializing the GPU collector
I0829 03:43:09.905557       1 watcher.go:66] Using in cluster k8s config
I0829 03:43:09.906214       1 reflector.go:221] Starting reflector <unspecified> (0s) from github.com/sustainable-computing-io/kepler/pkg/kubernetes/watcher.go:122
I0829 03:43:09.906251       1 reflector.go:257] Listing and watching <unspecified> from github.com/sustainable-computing-io/kepler/pkg/kubernetes/watcher.go :122
I0829 03:43:10.006102       1 shared_informer.go:285] caches populated
libbpf: loading /var/lib/kepler/bpfassets/amd64_kepler.bpf.o
libbpf: elf: section(3) tracepoint/sched/sched_switch, size 2344, link 0, flags 6, type=1
libbpf: sec 'tracepoint/sched/sched_switch': found program 'kepler_trace' at insn offset 0 (0 bytes), code size 293 insns (2344 bytes)
libbpf: elf: section(4) .reltracepoint/sched/sched_switch, size 352, link 29, flags 40, type=9
libbpf: elf: section(5) tracepoint/irq/softirq_entry, size 144, link 0, flags 6, type=1
libbpf: sec 'tracepoint/irq/softirq_entry': found program 'kepler_irq_trace' at insn offset 0 (0 bytes), code size 18 insns (144 bytes)
libbpf: elf: section(6) .reltracepoint/irq/softirq_entry, size 16, link 29, flags 40, type=9
libbpf: elf: section(7) .maps, size 352, link 0, flags 3, type=1
libbpf: elf: section(8) license, size 4, link 0, flags 3, type=1
libbpf: license of /var/lib/kepler/bpfassets/amd64_kepler.bpf.o is GPL
libbpf: elf: section(19) .BTF, size 5759, link 0, flags 0, type=1
libbpf: elf: section(21) .BTF.ext, size 2120, link 0, flags 0, type=1
libbpf: elf: section(29) .symtab, size 1056, link 1, flags 0, type=2
libbpf: looking for externs among 44 symbols...
libbpf: collected 0 externs total
libbpf: map 'processes': at sec_idx 7, offset 0.
libbpf: map 'processes': found type = 1.
libbpf: map 'processes': found key [6], sz = 4.
libbpf: map 'processes': found value [10], sz = 88.
libbpf: map 'processes': found max_entries = 32768.
libbpf: map 'pid_time': at sec_idx 7, offset 32.
libbpf: map 'pid_time': found type = 1.
libbpf: map 'pid_time': found key [6], sz = 4.
libbpf: map 'pid_time': found value [12], sz = 8.
libbpf: map 'pid_time': found max_entries = 32768.
libbpf: map 'cpu_cycles_hc_reader': at sec_idx 7, offset 64.
libbpf: map 'cpu_cycles_hc_reader': found type = 4.
libbpf: map 'cpu_cycles_hc_reader': found key [2], sz = 4.
libbpf: map 'cpu_cycles_hc_reader': found value [6], sz = 4.
libbpf: map 'cpu_cycles_hc_reader': found max_entries = 128.
libbpf: map 'cpu_cycles': at sec_idx 7, offset 96.
libbpf: map 'cpu_cycles': found type = 2.
libbpf: map 'cpu_cycles': found key [6], sz = 4.
libbpf: map 'cpu_cycles': found value [12], sz = 8.
libbpf: map 'cpu_cycles': found max_entries = 128.
libbpf: map 'cpu_ref_cycles_hc_reader': at sec_idx 7, offset 128.
libbpf: map 'cpu_ref_cycles_hc_reader': found type = 4.
libbpf: map 'cpu_ref_cycles_hc_reader': found key [2], sz = 4.
libbpf: map 'cpu_ref_cycles_hc_reader': found value [6], sz = 4.
libbpf: map 'cpu_ref_cycles_hc_reader': found max_entries = 128.
libbpf: map 'cpu_ref_cycles': at sec_idx 7, offset 160.
libbpf: map 'cpu_ref_cycles': found type = 2.
libbpf: map 'cpu_ref_cycles': found key [6], sz = 4.
libbpf: map 'cpu_ref_cycles': found value [12], sz = 8.
libbpf: map 'cpu_ref_cycles': found max_entries = 128.
libbpf: map 'cpu_instr_hc_reader': at sec_idx 7, offset 192.
libbpf: map 'cpu_instr_hc_reader': found type = 4.
libbpf: map 'cpu_instr_hc_reader': found key [2], sz = 4.
libbpf: map 'cpu_instr_hc_reader': found value [6], sz = 4.
libbpf: map 'cpu_instr_hc_reader': found max_entries = 128.
libbpf: map 'cpu_instr': at sec_idx 7, offset 224.
libbpf: map 'cpu_instr': found type = 2.
libbpf: map 'cpu_instr': found key [6], sz = 4.
libbpf: map 'cpu_instr': found value [12], sz = 8.
libbpf: map 'cpu_instr': found max_entries = 128.
libbpf: map 'cache_miss_hc_reader': at sec_idx 7, offset 256.
libbpf: map 'cache_miss_hc_reader': found type = 4.
libbpf: map 'cache_miss_hc_reader': found key [2], sz = 4.
libbpf: map 'cache_miss_hc_reader': found value [6], sz = 4.
libbpf: map 'cache_miss_hc_reader': found max_entries = 128.
libbpf: map 'cache_miss': at sec_idx 7, offset 288.
libbpf: map 'cache_miss': found type = 2.
libbpf: map 'cache_miss': found key [6], sz = 4.
libbpf: map 'cache_miss': found value [12], sz = 8.
libbpf: map 'cache_miss': found max_entries = 128.
libbpf: map 'cpu_freq_array': at sec_idx 7, offset 320.
libbpf: map 'cpu_freq_array': found type = 2.
libbpf: map 'cpu_freq_array': found key [6], sz = 4.
libbpf: map 'cpu_freq_array': found value [6], sz = 4.
libbpf: map 'cpu_freq_array': found max_entries = 128.
libbpf: sec '.reltracepoint/sched/sched_switch': collecting relocation for section(3) 'tracepoint/sched/sched_switch'
libbpf: sec '.reltracepoint/sched/sched_switch': relo #0: insn #17 against 'cpu_cycles_hc_reader'
libbpf: prog 'kepler_trace': found map 2 (cpu_cycles_hc_reader, sec 7, off 64) for insn #17
libbpf: sec '.reltracepoint/sched/sched_switch': relo #1: insn #36 against 'cpu_cycles'
libbpf: prog 'kepler_trace': found map 3 (cpu_cycles, sec 7, off 96) for insn #36
libbpf: sec '.reltracepoint/sched/sched_switch': relo #2: insn #50 against 'cpu_cycles'
libbpf: prog 'kepler_trace': found map 3 (cpu_cycles, sec 7, off 96) for insn #50
libbpf: sec '.reltracepoint/sched/sched_switch': relo #3: insn #55 against 'cpu_ref_cycles_hc_reader'
libbpf: prog 'kepler_trace': found map 4 (cpu_ref_cycles_hc_reader, sec 7, off 128) for insn #55
libbpf: sec '.reltracepoint/sched/sched_switch': relo #4: insn #68 against 'cpu_ref_cycles'
libbpf: prog 'kepler_trace': found map 5 (cpu_ref_cycles, sec 7, off 160) for insn #68
libbpf: sec '.reltracepoint/sched/sched_switch': relo #5: insn #82 against 'cpu_ref_cycles'
libbpf: prog 'kepler_trace': found map 5 (cpu_ref_cycles, sec 7, off 160) for insn #82
libbpf: sec '.reltracepoint/sched/sched_switch': relo #6: insn #87 against 'cpu_instr_hc_reader'
libbpf: prog 'kepler_trace': found map 6 (cpu_instr_hc_reader, sec 7, off 192) for insn #87
libbpf: sec '.reltracepoint/sched/sched_switch': relo #7: insn #104 against 'cpu_instr'
libbpf: prog 'kepler_trace': found map 7 (cpu_instr, sec 7, off 224) for insn #104
libbpf: sec '.reltracepoint/sched/sched_switch': relo #8: insn #117 against 'cpu_instr'
libbpf: prog 'kepler_trace': found map 7 (cpu_instr, sec 7, off 224) for insn #117
libbpf: sec '.reltracepoint/sched/sched_switch': relo #9: insn #122 against 'cache_miss_hc_reader'
libbpf: prog 'kepler_trace': found map 8 (cache_miss_hc_reader, sec 7, off 256) for insn #122
libbpf: sec '.reltracepoint/sched/sched_switch': relo #10: insn #134 against 'cache_miss'
libbpf: prog 'kepler_trace': found map 9 (cache_miss, sec 7, off 288) for insn #134
libbpf: sec '.reltracepoint/sched/sched_switch': relo #11: insn #148 against 'cache_miss'
libbpf: prog 'kepler_trace': found map 9 (cache_miss, sec 7, off 288) for insn #148
libbpf: sec '.reltracepoint/sched/sched_switch': relo #12: insn #156 against 'cpu_freq_array'
libbpf: prog 'kepler_trace': found map 10 (cpu_freq_array, sec 7, off 320) for insn #156
libbpf: sec '.reltracepoint/sched/sched_switch': relo #13: insn #170 against 'cpu_freq_array'
libbpf: prog 'kepler_trace': found map 10 (cpu_freq_array, sec 7, off 320) for insn #170
libbpf: sec '.reltracepoint/sched/sched_switch': relo #14: insn #182 against 'cpu_freq_array'
libbpf: prog 'kepler_trace': found map 10 (cpu_freq_array, sec 7, off 320) for insn #182
libbpf: sec '.reltracepoint/sched/sched_switch': relo #15: insn #206 against 'cpu_freq_array'
libbpf: prog 'kepler_trace': found map 10 (cpu_freq_array, sec 7, off 320) for insn #206
libbpf: sec '.reltracepoint/sched/sched_switch': relo #16: insn #215 against 'pid_time'
libbpf: prog 'kepler_trace': found map 1 (pid_time, sec 7, off 32) for insn #215
libbpf: sec '.reltracepoint/sched/sched_switch': relo #17: insn #223 against 'pid_time'
libbpf: prog 'kepler_trace': found map 1 (pid_time, sec 7, off 32) for insn #223
libbpf: sec '.reltracepoint/sched/sched_switch': relo #18: insn #235 against 'pid_time'
libbpf: prog 'kepler_trace': found map 1 (pid_time, sec 7, off 32) for insn #235
libbpf: sec '.reltracepoint/sched/sched_switch': relo #19: insn #241 against 'processes'
libbpf: prog 'kepler_trace': found map 0 (processes, sec 7, off 0) for insn #241
libbpf: sec '.reltracepoint/sched/sched_switch': relo #20: insn #261 against 'processes'
libbpf: prog 'kepler_trace': found map 0 (processes, sec 7, off 0) for insn #261
libbpf: sec '.reltracepoint/sched/sched_switch': relo #21: insn #287 against 'processes'
libbpf: prog 'kepler_trace': found map 0 (processes, sec 7, off 0) for insn #287
libbpf: sec '.reltracepoint/irq/softirq_entry': collecting relocation for section(5) 'tracepoint/irq/softirq_entry'
libbpf: sec '.reltracepoint/irq/softirq_entry': relo #0: insn #5 against 'processes'
libbpf: prog 'kepler_irq_trace': found map 0 (processes, sec 7, off 0) for insn #5
libbpf: map 'processes': created successfully, fd=10
libbpf: map 'pid_time': created successfully, fd=11
libbpf: map 'cpu_cycles_hc_reader': created successfully, fd=12
libbpf: map 'cpu_cycles': created successfully, fd=13
libbpf: map 'cpu_ref_cycles_hc_reader': created successfully, fd=14
libbpf: map 'cpu_ref_cycles': created successfully, fd=15
libbpf: map 'cpu_instr_hc_reader': created successfully, fd=16
libbpf: map 'cpu_instr': created successfully, fd=17
libbpf: map 'cache_miss_hc_reader': created successfully, fd=18
libbpf: map 'cache_miss': created successfully, fd=19
libbpf: map 'cpu_freq_array': created successfully, fd=20
I0829 03:43:10.013848       1 libbpf_attacher.go:143] failed to get perf event cpu_instructions_hc_reader: failed to find BPF map cpu_instructions_hc_reader: no such file or directory
I0829 03:43:10.014143       1 libbpf_attacher.go:157] Successfully load eBPF module from libbpf object
I0829 03:43:10.036770       1 node_metric.go:274] Unknown node feature: bpf_cpu_time_us, adding 0 value
I0829 03:43:10.036786       1 node_metric.go:274] Unknown node feature: bpf_net_tx_irq, adding 0 value
I0829 03:43:10.036790       1 node_metric.go:274] Unknown node feature: bpf_net_rx_irq, adding 0 value
I0829 03:43:10.036793       1 node_metric.go:274] Unknown node feature: bpf_block_irq, adding 0 value
I0829 03:43:10.036796       1 node_metric.go:274] Unknown node feature: cgroupfs_memory_usage_bytes, adding 0 value
I0829 03:43:10.036799       1 node_metric.go:274] Unknown node feature: cgroupfs_kernel_memory_usage_bytes, adding 0 value
I0829 03:43:10.036802       1 node_metric.go:274] Unknown node feature: cgroupfs_tcp_memory_usage_bytes, adding 0 value
I0829 03:43:10.036805       1 node_metric.go:274] Unknown node feature: cgroupfs_cpu_usage_us, adding 0 value
I0829 03:43:10.036807       1 node_metric.go:274] Unknown node feature: cgroupfs_system_cpu_usage_us, adding 0 value
I0829 03:43:10.036810       1 node_metric.go:274] Unknown node feature: cgroupfs_user_cpu_usage_us, adding 0 value
I0829 03:43:10.036813       1 node_metric.go:274] Unknown node feature: cgroupfs_ioread_bytes, adding 0 value
I0829 03:43:10.036816       1 node_metric.go:274] Unknown node feature: cgroupfs_iowrite_bytes, adding 0 value
I0829 03:43:10.036819       1 node_metric.go:274] Unknown node feature: block_devices_used, adding 0 value
I0829 03:43:10.036821       1 node_metric.go:274] Unknown node feature: kubelet_cpu_usage, adding 0 value
I0829 03:43:10.036827       1 node_metric.go:274] Unknown node feature: kubelet_memory_bytes, adding 0 value
I0829 03:43:10.036830       1 node_metric.go:274] Unknown node feature: block_devices_used, adding 0 value
I0829 03:43:10.045648       1 node_metric.go:404] Energy stat: map[0:1224246 (1224246)] (0)
I0829 03:43:10.045738       1 node_metric.go:404] Energy stat: map[0:3672738 (3672738)] (0)
I0829 03:43:10.045771       1 node_metric.go:404] Energy stat: map[0:0 (0)] (0)
I0829 03:43:10.045797       1 node_metric.go:404] Energy stat: map[0:513369 (513369)] (0)
I0829 03:43:10.045845       1 node_metric.go:274] Unknown node feature: bpf_cpu_time_us, adding 0 value
I0829 03:43:10.045875       1 node_metric.go:274] Unknown node feature: bpf_net_tx_irq, adding 0 value
I0829 03:43:10.045906       1 node_metric.go:274] Unknown node feature: bpf_net_rx_irq, adding 0 value
I0829 03:43:10.045933       1 node_metric.go:274] Unknown node feature: bpf_block_irq, adding 0 value
I0829 03:43:10.045955       1 node_metric.go:274] Unknown node feature: cgroupfs_memory_usage_bytes, adding 0 value
I0829 03:43:10.045977       1 node_metric.go:274] Unknown node feature: cgroupfs_kernel_memory_usage_bytes, adding 0 value
I0829 03:43:10.046002       1 node_metric.go:274] Unknown node feature: cgroupfs_tcp_memory_usage_bytes, adding 0 value
I0829 03:43:10.046027       1 node_metric.go:274] Unknown node feature: cgroupfs_cpu_usage_us, adding 0 value
I0829 03:43:10.046049       1 node_metric.go:274] Unknown node feature: cgroupfs_system_cpu_usage_us, adding 0 value
I0829 03:43:10.046072       1 node_metric.go:274] Unknown node feature: cgroupfs_user_cpu_usage_us, adding 0 value
I0829 03:43:10.046097       1 node_metric.go:274] Unknown node feature: cgroupfs_ioread_bytes, adding 0 value
I0829 03:43:10.046120       1 node_metric.go:274] Unknown node feature: cgroupfs_iowrite_bytes, adding 0 value
I0829 03:43:10.046141       1 node_metric.go:274] Unknown node feature: block_devices_used, adding 0 value
I0829 03:43:10.046162       1 node_metric.go:274] Unknown node feature: kubelet_cpu_usage, adding 0 value
I0829 03:43:10.046189       1 node_metric.go:274] Unknown node feature: kubelet_memory_bytes, adding 0 value
I0829 03:43:10.046212       1 node_metric.go:274] Unknown node feature: block_devices_used, adding 0 value
I0829 03:43:10.046247       1 node_metric.go:274] Unknown node feature: bpf_cpu_time_us, adding 0 value
I0829 03:43:10.046276       1 node_metric.go:274] Unknown node feature: bpf_net_tx_irq, adding 0 value
I0829 03:43:10.046302       1 node_metric.go:274] Unknown node feature: bpf_net_rx_irq, adding 0 value
I0829 03:43:10.046327       1 node_metric.go:274] Unknown node feature: bpf_block_irq, adding 0 value
I0829 03:43:10.046349       1 node_metric.go:274] Unknown node feature: cgroupfs_memory_usage_bytes, adding 0 value
I0829 03:43:10.046371       1 node_metric.go:274] Unknown node feature: cgroupfs_kernel_memory_usage_bytes, adding 0 value
I0829 03:43:10.046395       1 node_metric.go:274] Unknown node feature: cgroupfs_tcp_memory_usage_bytes, adding 0 value
I0829 03:43:10.046419       1 node_metric.go:274] Unknown node feature: cgroupfs_cpu_usage_us, adding 0 value
I0829 03:43:10.046443       1 node_metric.go:274] Unknown node feature: cgroupfs_system_cpu_usage_us, adding 0 value
I0829 03:43:10.046464       1 node_metric.go:274] Unknown node feature: cgroupfs_user_cpu_usage_us, adding 0 value
I0829 03:43:10.046487       1 node_metric.go:274] Unknown node feature: cgroupfs_ioread_bytes, adding 0 value
I0829 03:43:10.046539       1 node_metric.go:274] Unknown node feature: cgroupfs_iowrite_bytes, adding 0 value
I0829 03:43:10.046567       1 node_metric.go:274] Unknown node feature: block_devices_used, adding 0 value
I0829 03:43:10.046600       1 node_metric.go:274] Unknown node feature: kubelet_cpu_usage, adding 0 value
I0829 03:43:10.046622       1 node_metric.go:274] Unknown node feature: kubelet_memory_bytes, adding 0 value
I0829 03:43:10.046647       1 node_metric.go:274] Unknown node feature: block_devices_used, adding 0 value
I0829 03:43:10.050577       1 node_metric.go:274] Unknown node feature: bpf_cpu_time_us, adding 0 value
I0829 03:43:10.050601       1 node_metric.go:274] Unknown node feature: bpf_net_tx_irq, adding 0 value
I0829 03:43:10.050606       1 node_metric.go:274] Unknown node feature: bpf_net_rx_irq, adding 0 value
I0829 03:43:10.050619       1 node_metric.go:274] Unknown node feature: bpf_block_irq, adding 0 value
I0829 03:43:10.050623       1 node_metric.go:274] Unknown node feature: cgroupfs_memory_usage_bytes, adding 0 value
I0829 03:43:10.050627       1 node_metric.go:274] Unknown node feature: cgroupfs_kernel_memory_usage_bytes, adding 0 value
I0829 03:43:10.050631       1 node_metric.go:274] Unknown node feature: cgroupfs_tcp_memory_usage_bytes, adding 0 value
I0829 03:43:10.050634       1 node_metric.go:274] Unknown node feature: cgroupfs_cpu_usage_us, adding 0 value
I0829 03:43:10.050639       1 node_metric.go:274] Unknown node feature: cgroupfs_system_cpu_usage_us, adding 0 value
I0829 03:43:10.050643       1 node_metric.go:274] Unknown node feature: cgroupfs_user_cpu_usage_us, adding 0 value
I0829 03:43:10.050647       1 node_metric.go:274] Unknown node feature: cgroupfs_ioread_bytes, adding 0 value
I0829 03:43:10.050650       1 node_metric.go:274] Unknown node feature: cgroupfs_iowrite_bytes, adding 0 value
I0829 03:43:10.050654       1 node_metric.go:274] Unknown node feature: block_devices_used, adding 0 value
I0829 03:43:10.050659       1 node_metric.go:274] Unknown node feature: kubelet_cpu_usage, adding 0 value
I0829 03:43:10.050662       1 node_metric.go:274] Unknown node feature: kubelet_memory_bytes, adding 0 value
I0829 03:43:10.050666       1 node_metric.go:274] Unknown node feature: block_devices_used, adding 0 value
I0829 03:43:10.050681       1 node_metric.go:404] Energy stat: map[0:408082 (1632328)] (0)
I0829 03:43:10.050699       1 node_metric.go:404] Energy stat: map[0:408082 (4080820)] (0)
I0829 03:43:10.050704       1 node_metric.go:404] Energy stat: map[0:0 (0)] (0)
I0829 03:43:10.050707       1 node_metric.go:404] Energy stat: map[0:171123 (684492)] (0)
I0829 03:43:10.050712       1 node_metric.go:404] Energy stat: map[estimator0:3928 (15712)] (estimator0)
I0829 03:43:10.050920       1 exporter.go:276] Started Kepler in 7.703019732s
I0829 03:43:13.052060       1 libbpf_attacher.go:344] successfully get data with batch get and delete with 393 pids in 748.706µs
I0829 03:43:13.069477       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.070026       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.070244       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.070391       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.070586       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.070745       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.070891       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.071031       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.071179       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.071329       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.071516       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.071681       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.071821       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.071982       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.072125       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.072265       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.072271       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.072409       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.072559       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.072698       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.072865       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.072874       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.072876       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.073022       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.073039       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.073183       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.073367       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.073546       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.073697       1 container_cgroup_collector.go:34] PID 0 does not have cgroup metrics since there is no /proc/0/cgroup
I0829 03:43:13.077911       1 container_cgroup_collector.go:64] Kubelet Read: map[my pods] # Because the company stipulates
I0829 03:43:13.087728       1 node_metric.go:404] Energy stat: map[0:1224246 (2856574)] (0)
I0829 03:43:13.087885       1 node_metric.go:404] Energy stat: map[0:3672738 (7753558)] (0)
I0829 03:43:13.087936       1 node_metric.go:404] Energy stat: map[0:0 (0)] (0)
I0829 03:43:13.088011       1 node_metric.go:404] Energy stat: map[0:513369 (1197861)] (0)
I0829 03:43:13.088088       1 node_metric.go:404] Energy stat: map[estimator0:3928 (15712)] (estimator0)
I0829 03:43:13.092177       1 node_metric.go:404] Energy stat: map[0:408082 (3264656)] (0)
I0829 03:43:13.092293       1 node_metric.go:404] Energy stat: map[0:408082 (8161640)] (0)
I0829 03:43:13.092324       1 node_metric.go:404] Energy stat: map[0:0 (0)] (0)
I0829 03:43:13.092371       1 node_metric.go:404] Energy stat: map[0:171123 (1368984)] (0)
I0829 03:43:13.092432       1 node_metric.go:404] Energy stat: map[estimator0:3928 (31424)] (estimator0)
I0829 03:43:13.092500       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.092554       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.092593       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.092656       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.092701       1 container_metric.go:189] cannot extract:
I0829 03:43:13.092755       1 container_metric.go:189] cannot extract:
I0829 03:43:13.092812       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.092861       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.092947       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.093012       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.093056       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.093105       1 container_metric.go:189] cannot extract:
I0829 03:43:13.093159       1 container_metric.go:189] cannot extract:
I0829 03:43:13.093207       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.093276       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.093315       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.093369       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.093389       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.093450       1 container_metric.go:189] cannot extract:
I0829 03:43:13.093473       1 container_metric.go:189] cannot extract:
I0829 03:43:13.093533       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.093574       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.093623       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.093643       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.093702       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.093739       1 container_metric.go:189] cannot extract:
I0829 03:43:13.093781       1 container_metric.go:189] cannot extract:
I0829 03:43:13.093801       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.093854       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.093914       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.093938       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.093976       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.093995       1 container_metric.go:189] cannot extract:
I0829 03:43:13.094022       1 container_metric.go:189] cannot extract:
I0829 03:43:13.094043       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.094143       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094169       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094203       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094222       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.094242       1 container_metric.go:189] cannot extract:
I0829 03:43:13.094287       1 container_metric.go:189] cannot extract:
I0829 03:43:13.094306       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.094340       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094370       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094393       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094415       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.094450       1 container_metric.go:189] cannot extract:
I0829 03:43:13.094470       1 container_metric.go:189] cannot extract:
I0829 03:43:13.094492       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.094548       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094572       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094592       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094627       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.094647       1 container_metric.go:189] cannot extract:
I0829 03:43:13.094667       1 container_metric.go:189] cannot extract:
I0829 03:43:13.094686       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.094716       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094740       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094763       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094799       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.094818       1 container_metric.go:189] cannot extract:
I0829 03:43:13.094838       1 container_metric.go:189] cannot extract:
I0829 03:43:13.094857       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.094906       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094928       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094950       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.094982       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.094999       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095018       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095036       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095068       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095086       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095106       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095131       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095158       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095176       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095180       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095183       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095185       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095187       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095190       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095192       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095194       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095199       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095203       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095205       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095207       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095209       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095211       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095213       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095216       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095249       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095268       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095296       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095300       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095302       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095304       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095306       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095310       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095392       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095397       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095399       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095405       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095407       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095409       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095413       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095415       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095417       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095420       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095422       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095424       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095426       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095433       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095442       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095444       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095446       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095448       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095450       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095452       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095531       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095569       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095572       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095639       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095643       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095645       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095647       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095650       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095652       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095654       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095657       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095659       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095661       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095663       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095666       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095668       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095671       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095673       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095675       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095682       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095684       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095687       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095691       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095694       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095725       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095768       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095772       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095774       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095779       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095781       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095783       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095786       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095788       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095790       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095792       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095796       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095800       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095802       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095804       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095807       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095809       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095811       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095905       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095911       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095913       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095915       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095917       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095919       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095921       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095924       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095926       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095928       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095930       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095933       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095935       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095937       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095940       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095942       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095944       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095946       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.095949       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095954       1 container_metric.go:189] cannot extract:
I0829 03:43:13.095956       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.095959       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095962       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095964       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.095966       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.096000       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096039       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096043       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.096046       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096048       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096050       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096052       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.096055       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096057       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096059       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.096062       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096064       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096066       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096069       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.096073       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096075       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096078       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.096086       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096180       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096184       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096187       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.096189       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096191       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096193       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.096196       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096198       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096200       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096205       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.096207       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096209       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096211       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.096214       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096216       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096221       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096224       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.096226       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096228       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096230       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.096233       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096237       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096240       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096273       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.096312       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096315       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096317       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.096323       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096326       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096328       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096330       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.096332       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096334       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096336       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.096339       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096345       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096348       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096350       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.096352       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096354       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096356       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.096359       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096453       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096457       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 03:43:13.096459       1 container_metric.go:189] cannot extract: cache_miss
I0829 03:43:13.096461       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096463       1 container_metric.go:189] cannot extract:
I0829 03:43:13.096465       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 03:43:13.096471       1 node_metric.go:274] Unknown node feature: cpu_instructions, adding 0 value
I0829 03:43:13.096476       1 node_metric.go:274] Unknown node feature: cpu_instructions, adding 0 value
I0829 03:43:13.096479       1 node_metric.go:274] Unknown node feature: cpu_instructions, adding 0 value
I0829 03:43:13.096481       1 node_metric.go:274] Unknown node feature: cache_miss, adding 0 value

What did you expect to happen?
.
How can we reproduce it (as minimally and precisely as possible)?
.
Anything else we need to know?
.
Kepler image tag
.
Kubernetes version
.
Cloud provider or bare metal
.
OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Kepler deployment config

For on kubernetes:
$ KEPLER_NAMESPACE=kepler

# provide kepler configmap
$ kubectl get configmap kepler-cfm -n ${KEPLER_NAMESPACE}
# paste output here

# provide kepler deployment description
$ kubectl describe deployment kepler-exporter -n ${KEPLER_NAMESPACE}

For standalone:
put your Kepler command argument here

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

@Lai-Kenny Is this error occurring later in the log, or does it only appear in the initial moments when Kepler is initiating?
The initialization of the node resource utilization map happens after the container metrics have been updated within the AddNodeResUsageFromContainerResUsage function. During the initial few seconds, the container metrics might not have been collected yet, but they should become available in few more seconds. Could you please verify this?
By the way, we could prevent all these error messages by including a return statement while the node metrics map is still empty...

Hi, @marceloamaral . I found the following error continues to occur.
I0829 13:03:16.074472       1 container_metric.go:189] cannot extract:
I0829 13:03:16.074474       1 container_metric.go:189] cannot extract:
I0829 13:03:16.074476       1 container_metric.go:189] cannot extract: gpu_sm_util
I0829 13:03:16.074479       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 13:03:16.074481       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 13:03:16.074484       1 container_metric.go:189] cannot extract: cpu_instructions
I0829 13:03:16.074490       1 container_metric.go:189] cannot extract: cache_miss

@Lai-Kenny This is because you are running on a VM, which does not have hardware counter metrics (cpu_instructions, cache_miss) and does not seems to have GPU metrics (gpu_sm_util). But as expected, the other metrics were added to the node map and we do not see the warnings anymore.

@marceloamaral ok, I got it. But I have a question about it. That will affect energy estimate?

@Lai-Kenny this issue has been fixed in PR  https://github.com/sustainable-computing-io/kepler/pull/896 , you can try updating kepler code to lates or use latest image quay.io/sustainable_computing_io/kepler:latest

this issue has been fixed in PR https://github.com/sustainable-computing-io/kepler/pull/896 , you can try updating kepler code to lates or use latest image

I doubt it could per https://github.com/sustainable-computing-io/kepler/issues/898#issuecomment-1697412939
as this seems a VM env and #896 seems for other purpose..


refactor(batch): Use futures-async-stream to implement TopN executor

What's changed and what's your intention?
Implement TopN using Executor2 trait.
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
How does this PR work? Need a brief introduction for the changed logic (optional)
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)

Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)
close https://github.com/singularity-data/risingwave/issues/1945

There are unresolved conflicts, it's meaningless to trigger it now (

Why doesn't my local commit appear in the PR?

maybe because of this？

Hi, @D2Lark since bors failed, I just cloned your branch and push it to our repo to submit a PR. Sorry for the inconvenience, and we are working on it.

It's OK, thanks for your help~

Checkes all passed.


⚠ Bofrost.at has degraded performance

In 78004aa, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2047 ms

Resolved: Bofrost.at performance has improved in 3b4b72c.


Homepage statistics should display Total Mint and Burn amounts

Business/User Value: As an Explorer of Diem I want to see the total number of Diems that have been Minted and Burned so that I can preform research on the blockchain
Acceptance Criteria
GIVEN I am in the landing page
WHEN the page loads
THEN a card displaying the total amount of mints is displayed
AND a card displaying the total amount of burns is displayed
DEV NOTES

The data lives in the diem_in_circulation_realtime_aggregates  table
Display total mint, total burn, and total net
Only display XUS for now


Feat: Add Contributors Page to Display Project Contributors

Describe the feature
The contributors page will display the details of the contributors who have contributed to this project
Add ScreenShots

Will add it in the footer
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Satyam1923 Can I work on this?

@pani2004 fine.


run

What version of Go are you using (go version)?

$ go version
go version go1.23.0 darwin/arm64

Does this issue reproduce with the latest release?

What did you expect to see?
What did you see instead?

Related Issues and Documentation

Demo #66258 (closed)
sb #53220 (closed)
Bugs-Report #62338 (closed)
go #64466 (closed)
 #52089 (closed)
go #49423 (closed)
go build #52634 (closed)
? #43227 (closed)
Update #47124 (closed)
yaffaliu #56935 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)


run guide ?

you can tell me how to run in on ubuntu ?

i dont have a ftp for the payload
can i use it like that?
?scan http://thatsit.atwebpages.com/chhk
this is a free subdommain and chhk its the payload

Sorry I'm just wake up, Yeah sure you can do it as long as wget can download file from http.

ok nice
and some tips for you
make some owner access that can control about the bot in the IRC
like join part from channel
send messeges
change the bot nick
etc.
maybe even a shell for the server
like: ?shel : ?shell ls, cd, mkdir, etc.
thats can be nice

Thank you for The idea i'll think about it.
About to change bot nick name, You can change it manually in irc.go file in IRC_Login function.

Thank you for The tips, i'll think about it. But if i'm doing a full shell access The specific job of bot will not be an only DDoS.
About to change bot nick name, You can change it manually in IRC_Login function in irc.go file.

if you want a big project you can take ideas from here
https://pastebin.com/MAp9tWMj
this bot is crazy but its old
new bot like that can be very good project for you

Thank you for the resource and tip.

boz3r please tell me
there is a way to make your bot works only when i send the commands and not everyone ? like make it works on my nick only?

On The bot feature nope i didn't do it yet, But you can make your private IRC server to use it alone or you can make a channel password to make your channel have to require a password before joining.
But.... I have an idea about this feature, I think I'll add it in to v0.5 soon.

yes but i want the bot in my channel with my friends
hope you will do it

ok, I'll try to do it.

thanks mate

your welcome.

what is that problem can be?
[18:34:41] <@zizitripo> ?udp <IP_ADDRESS>
[18:34:41] <@[FATE][Z][51825> START UDP FLOOD TO: <IP_ADDRESS>
[18:34:41] * @[FATE][Z][51825 (~[FATE][Z]@bjv34b3v) Quit (EOF from client)
[18:34:41] <@[FATE][H][81595> START UDP FLOOD TO: <IP_ADDRESS>
[18:34:41] <@[FATE][A][24021> START UDP FLOOD TO: <IP_ADDRESS>
[18:34:41] * @[FATE][H][81595 (~[FATE][H]@kj3hb4jhb) Quit (EOF from client)
[18:34:41] <@[FATE][S][32221> START UDP FLOOD TO: <IP_ADDRESS>
[18:34:41] * @[FATE][A][24021 (~[FATE][A]@kh4bjh3b) Quit (EOF from client)
[18:34:41] * @[FATE][S][32221 (~[FATE][S]@jk3b4hjb) Quit (EOF from client)
[18:34:41] <@[FATE][V][1120]> START UDP FLOOD TO: <IP_ADDRESS>
[18:34:41] <@[FATE][W][90808> START UDP FLOOD TO: <IP_ADDRESS>
[18:34:41] <@[FATE][X][17319> START UDP FLOOD TO: <IP_ADDRESS>
[18:34:41] * @[FATE][V][1120] (~[FATE][V]@sdf3f4fd) Quit (EOF from client)
[18:34:42] * @[FATE][W][90808 (~[FATE][W]@kj34bnkm) Quit (EOF from client)
[18:34:42] <@[FATE][B][96721> START UDP FLOOD TO: <IP_ADDRESS>
[18:34:42] * @[FATE][X][17319 (~[FATE][X]@khj3b4jhb) Quit (EOF from client)
[18:34:42] * @[FATE][B][96721 (~[FATE][B]@kjb3h4jhb) Quit (EOF from client)
[18:34:42] <@[FATE][H][51960> START UDP FLOOD TO: <IP_ADDRESS>
[18:34:42] * @[FATE][H][51960 (~[FATE][H]@mkb34kb) Quit (EOF from client)
[18:34:42] <@[FATE][F][77814> START UDP FLOOD TO: <IP_ADDRESS>
[18:34:42] * @[FATE][F][77814 (~[FATE][F]@ljk3n4kjn) Quit (EOF from client)

aaaahhh shit... let's me seee.

oh oh oh you need to set the size of you udp packet

Ohh ok my bad 😅

it's ok. 😁

May i ask something?
Is my scanner are bad like it's take a long times to find a bot? Because i scan on my private network for a whole times.


Squirrel icon stays up after reading changelog

From @Stanzilla on May 2, 2015 12:51
Did I understand it correctly that the Squirrel icon in the status bar should go away after you read the changelog after updating?
If so, the icon stays up even through me reading the changelog a few times, closing it's tab and reopening it from the icon.
If not, maybe it should go away after you read it once.
Copied from original issue: atom/atom#6613

From @YuriSolovyov on May 2, 2015 16:43
Confirmed, pretty confusing

On a slightly related note, I'd prefer if the squirrel icon didn't go away until I read it.

@mehcode That might be worth opening a new issue about, if one doesn't exist.

I get this on OS X Yosemite too. Atom 0.198.0

:+1:

+1

+1 still happening. very annoying.

Where is the squirrel actually loaded? I cannot seem to locate it.

Bottom right of the window

I found my way to the atom/release-packages repo and it should be updated from there is it?

On 16 Nov 2015, at 10:52 AM, sbaker7<EMAIL_ADDRESS>wrote:
Bottom right of the window
—
Reply to this email directly or view it on GitHub https://github.com/atom/release-notes/issues/36#issuecomment-156896657.

From https://github.com/atom/release-notes/pull/38, I think Ian here already fixed this, but the team is waiting for #9164 to complete so they they can fix everything in one time?

Yeah, I'd love this. Squirrel is unneeded clutter after I've read the notes

+1 still happening OS X El Captain 10.11.1 (15B42) atom v. 1.2.3

It's still happening. Windows 7 atom v1.7.2

@trainto Release Notes is no longer packaged with Atom.  Please report this on atom/about instead.

But the icon is still present - is there possibility to hide it f.e. by modifying css ?

All repositories in the atom-archive organization are unmaintained and deprecated. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


be compatible with php-5.3

seems this was only place using php 5.4 short array syntax

Did you check it with static analysis? I know phpstorm can do this.

yes, that is what i used


please write mrubyc in Rust

nobody using python

We'll deal with Perl first :)

We'll deal with Perl first :)
5 or 6 version?

Both!

i found small runtime for mruby
https://github.com/mrubyc/mrubyc but not perfect, look nice.

Due to lack of time, I'm closing down this issue. Please check back later, if still not implemented.


secure_password  NOT FOUND

Hmm, this is regression. I'll tag it and get it fixed soon. Thanks for reporting.


Can I upload annotation masks as jpg? What should I do, otherwise, to convert my annotations into a proper format (e.g. segmentation-masks 1.1)?

My actions before raising this issue

[x] Read/searched the docs
[ ] Searched past issues

Expected Behaviour

Current Behaviour

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Git hash commit (git log -1):
Docker version docker version (e.g. Docker 17.0.05):
Are you using Docker Swarm or Kubernetes?
Operating System and version (e.g. Linux, Windows, MacOS):
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:
Logs from `cvat` container

@francescocister

Can I upload annotation masks as jpg?

I do not think so, because of .jpg compression specifics.

What should I do, otherwise, to convert my annotations into a proper format

To choose a format and write a conversion script, sorry for very common answer, but your format is not a CVAT issue. Try to ask community on gitter or Discord.
Thank you.


model::truncate()

no cache clear when using model::truncate() but ok when trying to delete one model result.

@meandus Thanks for alerting to this issue. Will look into this as soon as possible.

maybe not a bug but a feature request in this case ...


Update Triton inference server Docker deployment for Falcon 40B

https://github.com/h2oai/h2ogpt/blob/main/docs/TRITON.md
do same for Falcon 7B, then Falcon 40B

Is this possible yet?

waiting

If you are looking for a fast inference docker engine, I'd recommend hugging faces text generation inference server instead.  It's continuous batching makes it far superior to nvidia triton.

@pseudotensor Thanks, I'll try to test what you said

Hi @pseudotensor ,
i tried it but while conversion it is failing for below error:
File "/usr/local/lib/python3.8/dist-packages/torch/distributed/distributed_c10d.py", line 372, in _get_default_group
raise RuntimeError("Default process group has not been initialized, "
RuntimeError: Default process group has not been initialized, please make sure to call init_process_group.
have you faced the same issue?
Thanks
Raushan


Fix issue with recursion error caused by ParamSpec

Closes https://github.com/pydantic/pydantic/issues/6922

please review


psychlua.FunkinLua has no field runtimeShaders

Describe your bug here.
I've tried to compile the game on Linux and it doesn't compile because of this runtimeshaders thing
All dependencies are installed correctly and i haven't changed anything of source code
Command Prompt/Terminal logs (if existing)
ERROR  source/psychlua/ShaderFunctions.hx:28: characters 13-27

 28 |    if(!funk.runtimeShaders.exists(shader) && !funk.initLuaShader(shader))
    |             ^^^^^^^^^^^^^^
    | psychlua.FunkinLua has no field runtimeShaders

 ERROR  source/psychlua/ShaderFunctions.hx:41: characters 34-48

 41 |     var arr:Array<String> = funk.runtimeShaders.get(shader);
    |                                  ^^^^^^^^^^^^^^
    | psychlua.FunkinLua has no field runtimeShaders

Are you modding a build from source or with Lua?
Source
What is your build target?
Linux
Did you edit anything in this build? If so, mention or summarize your changes.
No, I haven't changed anything

Same issue here. hoping there's a solution to this soon enough

This worked for me


[Vue Router warn]: No match found for location with path "/dashboard"

vue-router.esm-bundler.js:72 [Vue Router warn]: No match found for location with path "/dashboard", 首次登陆 ，或者刷新 会出现这个路由警告，

https://github.com/vuejs/vue-router-next/issues/1053  打包之后就正常了


deployment: prompt if parameters are not provided

For now, it is by design, but if we have more user voices, we can reconsider.
Mark it as discussion.

I'd vote in favor of at least making it available as a flag... (--prompt)?
If you don't specify values it's going to fail anyway, is that really the desirable behavior?

I'm with @brendandburns on this. The current experience isn't particularly inspiring for the first impression/getting started experience, and I think it would go along way to have a prompt for parameters.
In fact, it would be even more awesome if the CLI allowed you to write out the parameters file with the values you specified to the prompt. That way it would work just like npm init and other similar experiences. Then you could take a template URI and combine it with the CLI to have a slightly more guided deployment experience.

@yugangw-msft what do you think? I'm happy to implement this...
Thanks
--brendan

@lostintangent, agreed on template file generation - it would be a very valuable command.
@brendandburns, if you can create a pull request for prompting on --prompt, we'd love to have it :).
A couple of notes: we want to (at a minimum) support keyvault references in the parameters file (and thus avoid issues like https://github.com/Azure/azure-xplat-cli/issues/3444). I don't believe that we'd have to support providing keyvault references in the prompting logic, but if someone comes up with a reasonable way to do so, it would be awesome.

Ok, I will start in on implementing this.


Regalloc assertion failure

test regalloc
set is_64bit=1
isa intel haswell

function %foo() native {
    sig0 = () -> i8 native
    sig1 = (i8) -> i8 native
    sig2 = (i8) native
    fn0 = sig0 %qux
    fn1 = sig1 %baz
    fn2 = sig2 %bar

  ebb0:
    v0 = call fn0()
    v1 = call fn1(v0)
    call fn2(v1)
    return
}

FAIL x.cton: panicked in worker #0: can't encode regmove.i8 v0, %rax -> %rdi

This test case looks a bit suspicious because I think the Intel legalizer would convert those i8 types in the signatures to i32. The Intel target ISA doesn't treat i8 and i16 as legal types at the moment.
Does this still fail with test compile where the legalizer also runs?

Yes, it fails in the same way with test compile.

Huh, thanks. That would suggest the the Intel backend is confused about which types are legal or not. I think the signature legalizer should treat i8 and i16 as illegal and promote to i32.
We don't yet have legalizer patterns for widening arithmetic, so you will probably run into this a lot if you generate code with small integer types.


not working in Firefox and IE

<UncontrolledDropdown>
               <DropdownToggle nav caret>
                       Availability
                </DropdownToggle>
                <DropdownMenu>
                       <DropdownItem>
                                 <NavLink href="url">Backup current</NavLink>
                       </DropdownItem>
                       <DropdownItem>
                                  <NavLink href="url">Restore</NavLink>
                       </DropdownItem>
                       <DropdownItem>
                                  <NavLink href="url">Share</NavLink>
                       </DropdownItem>
                </DropdownMenu>
 </UncontrolledDropdown>

This is working fine in chrome but in Firefox and IE the DropdownItem/NavLink doesn't respond to mouse click event. Dropdown menu just closes on click and doesn't navigate to the "url".

Works like charm. Thanks!

Along the same lines of thinking as TheSharpieOne, if you want this to work with the React Router Dom Link, rather than nesting them in a DropdownItem, you can simply do something like this:
<DropdownItem tag={Link} to='/Some-Example-Route' className='dropdown-option'>Some Example Route</DropdownItem>
Thanks to TheSharpieOne for simplifying the explanation.


Optimise BinaryConverter's reflection object creation.

Make the test for a type being S.D.L.Binary a single test as Binary is a sealed class and therefore there's no need to test bases.
Make the stored ReflectionObject static, reducing size and repeated allocations if BinaryConverter is explicitly created by the user.

LGTM


Renaming the config file breaks pushes

Description
I renamed my config file from /etc/gitea/gitea.ini to /etc/gitea/app.ini and when I tried to push to a pre-existing repo I get the following error:
$ git pushdev
Enter passphrase for key '/home/thomas/.ssh/id_ed25519':
Enumerating objects: 15, done.
Counting objects: 100% (15/15), done.
Delta compression using up to 16 threads
Compressing objects: 100% (7/7), done.
Writing objects: 100% (8/8), 1.59 KiB | 1.59 MiB/s, done.
Total 8 (delta 6), reused 0 (delta 0), pack-reused 0
remote: 2022/12/06 13:17:09 ...s/setting/setting.go:618:loadFromConf() [F] Unable to find configuration file: "/etc/gitea/gitea.ini".
remote:         Ensure you are running in the correct environment or set the correct configuration file with -c.
To 'ssh://git.HOST.TLD:PORT/USER/REPO.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'ssh://git.HOST.TLD:PORT/USER/REPO.git'

I am running gitea 1.17.3 on linux amd64
Going into the gitea homedir (in my case /var/lib/gitea) and issuing a
$ ln -s app.ini gitea.ini

worked to fix the issue.
This is strange that a repo depends on the filename of the config used to create it, hence reporting it :)
Cheers, and also thanks for all the hard work
Gitea Version
1.17.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
From the binary from GH release
Database
PostgreSQL

It's by designed.

It has been fixed by https://github.com/go-gitea/gitea/pull/21619

Please upgrade to v1.17.4 or v1.18.0, that will fix it.


[TINY] Fix to #10828 - Query: include doesn't work for queries with order byand group by

Problem was that when rewriting collection query for case with group result operator, we add order by key element, but we were not adding it as first orderby term. This would cause outer elements arrive in different order than inner, so include would not associate them together. Fix is to apply order by always as first element.

@anpete @smitpatel new version up (not so tiny now)


revert(charts): add rbac options to helm chart

Reverts #332

Hey @byashimov - out of curiosity why was this removed?

@ryaneorth hey!
We were just about to release the new version when this broke the operator. So it was reverted asap. I should have left this comment at least, but I was busy by the fix, sorry.
Our operator is designed to watch all namespaces, that's why it requires cluster wide role.
So to make this feature happen, we need to pass a list of namespaces to listen to helm values, and then to the operator as env variables.
Said that, it is not enough to change the role only.
If you still need this feature, I can create an issue on github. You can do it also if you have more to add. Then we can take this to the backlog :)

hey @byashimov ! My particular use-case was actually number 1 outlined in the original PR. Specifically to support:

The scenario where the engineer installing the chart has limited (i.e. namespace only) access and cannot install cluster-wide resources. This change allows the cluster-wide resources to be installed separately by cluster administrators while still allowing the engineers to manage the operator itself without having full cluster-wide access.

Given this, would it be possible to re-introduce the part of change that supports this use-case but not the second use-case (which I don't need) where you can optionally install non-cluster-wide roles/role bindings?

hey @ryaneorth!
Currently operator will request permissions to listen the whole cluster. So if you set limited role it won't work (well, it doesn't in our clusters, or probably we miss something?).
We have this in the backlog now. But I'm not sure I can say when this one is released :(


dbbackup successful command produces output in STDERR

When running dbbackup I get output in STDERR even when the command was successful:
python manage.py dbbackup --compress --clean > /dev/null

The command above will still print:
Backing Up Database: MyDatabase
Writing file to whatever-timestamp.mysql.gz

and it exits with code 0. I am redirecting the STDOUT to /dev/null so I would not expect to see anything apart from errors.
I have checked and if I redirect STDERR to /dev/null (2>) I do not get that output.
I am using:

Centos7
Django 1.11.16
django-dbbackup 3.2.0

P.S. I run dbbackup as a cron job and having STDERR causes the cron job to send an email. I got around the problem by setting --verbosity 0 but I believe that information message should be sent to
STDOUT.

We could probably be better with documentation here. Right now we are using logging and it seems like the logging module outputs things to stderr. With the right logging configuration on the user side this shouldn't be a problem.


Options for configuring 'LogSink.destination'.

When I drafted the logging usage doc, I assumed that users would want to pass in a string identifying the bucket, bigquery dataset, or pubsub topic, to which log entries would be exported, and I guessed at three properties, storage_bucket, bigquery_dataset, and pubsub_topic, which would consume and validate those strings.
Now, while working on the implementation, I believe that it might be better to have a destination property, whose setter would be willing to take any of:

a string (it would do no validation, but just store it).
a Bucket instance
a Dataset instance
a Topic instance.

In the case of the last three, the destination property setter would synthesize the appropriate destination string and store it.
We would then be able to accept a destination argument to Sink.__init__ and Client.sink, which would just rely on the destination property setter.
Thoughts?

I like it, but I am a bit worried about package inter-dependence. WDYT?

I guess we could weaken that by checking type(destination).__name__, but I'm not sure that would be a win.
We could just punt and require the user to pass in a propertly-formatted destination URI, pointing them to the exporting logs docs.

Yeah or we could do nested imports. But they make me sad.

As of #1596, we have punted, and require the user to pass in a correctly-formatted destination string.  I am leaving this issue open for reconsideration after merging the logging-api branch today or tomorrow.

@tseaver This has gone stale. Worth keeping open?

Superseded by #2127.


Auto fight doesn't work?

Hi,
I have a problem with auto fighter. When i activate it from 'main' all it does perform is upto 'fight_checker' after that it just goes back to home port even with undamaged fleet and normal morale.

Do you have any 間宮(mamiya)?
Mamiya is used to check fleet's morale, so it contains a bug if you don't have any one,
I opened the issue but not fix yet.

I do have both Mamiya and Irako.

Could you paste the log and screenshot (remeber remove your name) for me?

Is there some kind of limit you can set loop? Because it started working when i changed it from 1000 to 100.

Could you paste the modified file on gist?
https://gist.github.com/

I imagine you mean 'main.py' so here: https://drive.google.com/open?id=0B9dE2OuHvvSEcHZVYUhGa2lkTDQ&authuser=0

I can't open this file, please give permission to me.

Yeah, sorry. Pasted wrong link. https://drive.google.com/file/d/0B9dE2OuHvvSEcHZVYUhGa2lkTDQ/view?usp=sharing

In main.py,  "count" is just a variable about loop times. I think this modified variable should not change anything.
According to the following issue, I guess this problem comes from sikuli:
https://bugs.launchpad.net/sikuli/+bug/769924
https://answers.launchpad.net/sikuli/+question/262328


ABI dlopen example

Depends on https://github.com/pmix/pmix-abi/pull/9 (which is also shown in this PR).

Rebased now that PR #9 has been merged.

I just force pushed to this branch to update the example to reflect the stable/provisional split in the current proposal (https://github.com/pmix/pmix-standard/pull/397). The OpenPMIx implementation is here: https://github.com/openpmix/openpmix/pull/2617

Per IAWG meeting July 11, 2022:

We should add a lookup table in the base README.md to mark the version pairing on the PMIx Standard with the PMIx ABI.
Once PMIx Standard of v5.0 is released then we will mark the stable and provisional ABI to v1.0.
(Josh) Will add to this PR the README.md table

I just pushed the first draft of the version table to this PR. It looks like:

All PMIx Governance and PMIx Standard items have been merged for the ABI. We can merge this now and update the README.md with any notes necessary when we release the PMIx Standard v5.0.


Replaced poetry build system with hatch.

Removed test and lint workflows.
Add ci.yml (#7)
Create python-publish.yml (#8)
Updated code coverage uploads.
Fixed coverage collection.
Disabled pre-commit for Python 3.7.
Updated change log.
Refactored coverage reporting and added RTD preview.
Added upload of coverage data.
Added doc tests.
Moved docs tag to extras.
Fixed Sphinx build arguments.
Updated Sphinx build.
Removing explicit version.
Updated static paths.
Documentation changes.
Added docs to dev extras.
More Sphinx testing.
Updated sys.path.
More path fixes.
More Sphinx.
Switched to sphinx-apidoc.
Fixed sphinx-apidoc arguments.
Updated pyproject.toml.
Added doctest support.

Codecov Report

Merging #9 (e6fd0aa) into main (06456d4) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head e6fd0aa differs from pull request most recent head 8bc2eb3. Consider uploading reports for the commit 8bc2eb3 to get more accurate results

@@            Coverage Diff            @@
##              main        #9   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           13        16    +3
  Branches         1         2    +1
=========================================
+ Hits            13        16    +3

Impacted Files
Coverage Δ

src/pygopher/interfaces.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fixing broken styles

This fixes style regressions introduced in #44.

Really amazing. We will measure the success of this module as PRE-#45 and POST-#45 for years to come.


Dockerfile fix

Remove --depth when cloning the repo in the containers
Remove old file

Signed-off-by: Dimitris Karnikis<EMAIL_ADDRESS>

Hi Dimitris،
Whay is the reason for removing the depth argument?

Hi Dimitris، What is the reason for removing the depth argument?

In the current state, the user/developer is stuck at the main branch (due to depth) and cannot experiment with other branches (such as future)

Ah, t's because --depth fetches the latest (not the full repo). Good idea. Curious, what's the difference in terms of execution time?


Update the Repo URL after transfer to Astronomer org

depends on https://github.com/astronomer/astro-sdk/pull/374
We moved this repo from astro-projects to astronomer org. This commit updates the URL in the docs and code.

@kaxil, once the conflict with main is solved, please, feel free to merge this!


Any chance of a bugfix release?

I'm on 1.0.0 and am affected by https://github.com/Macchina-CLI/macchina/issues/131
It would be great to get a 1.0.1 release (also potentially a 0.9.4, although I'm not personally invested in the 0.9.x branch).
If the version's updated here, I'll be able to run an automated tool to update the version in nixpkgs :)

Sure, I'll have a look at what's causing the issue as soon as I can.

Thanks! I thought it was fixed in https://github.com/Macchina-CLI/macchina/pull/132?

Me too.
May I ask for a log? (It would help if you build from source) so I can try and inspect the source of the issue?

@uttarayan21 your commit feature saved my day :smile:

You're welcome, are the issues gone for good?


How is it possible to send a blob?

Hello, is it currently possible to send a blob over the websocket connection? (https://developer.mozilla.org/en-US/docs/Web/API/WebSocket)
The blob is filled with chunks from a webcam stream encoded in webm/v9.

Do you just want to send a single blob as a byte[] in a single invocation? I believe we don't support that now, only ArrayBuffer is supported. What error are you seeing when you try?

ArrayBuffer does not work either. The data object which gets transmitted is {}.

The message you're sending is 648KB in length. That's a very large message. SignalR is not designed to handle large single messages like that, it's designed for more frequent smaller messages. You'll have to break the message up into smaller chunks and send each chunk in a separate invocation (using some ID number and sequence numbers to keep track of which chunks are a part of which invocations and what order they come in).
If you're trying to send a video stream over SignalR, you're going to have to do a lot of manual work. It's simply not something SignalR is currently designed for. We've talked about ways to improve that, but the overhead is going to be quite large, compared to using something like WebRTC which is designed for exactly this purpose.

It is possible, but not recommended. You can bump the message size limit by increasing ApplicationMaxBufferSize (see #2266 for details).

To add to this conversation, I've also recently used SignalR to send ffmpeg compressed video frame packets with VP9 using SignalR and the solution was indeed to increase the ApplicationMessage size slightly, then send each packet as byte[] array.
A byte-streaming mode from client to server would be very welcome for such a scenario.

We've been looking at streaming from client-to-server. We're not yet sure how exactly it will land, but we've been working on prototype support for it. No guarantees it will land in 2.2, but it's something we're playing around with. It's definitely something you can build yourself though, since you can simply call separate Hub methods to initialize a stream and send smaller chunks of data.

@anurse That's what I did. However, the problem is that my wrapper is allocating a byte[] array for each message, I would preffer0 a non-allocating alternative and currently, SignalR does not expose extensibility points to do this (Unless I've missed something)

However, the problem is that my wrapper is allocating a byte[] array for each message

What do you mean by this? Where is the byte[] allocation that you want to remove? On the client or the server?

@anurse, I would like to eliminate the byte[] array allocation In both places ideally client code like this:
	var frame = new Frame
	{
		Data = new byte[length]
	}
	CopyUnmanagedPointerToBtyeArray(src, length, frame.Data);
	await SendPacket(frame);

Would be replaced with a non allocating version byte stream version. Same on the Server.

I see, so you have data in an unmanaged buffer you want to send without having to copy it to a managed buffer? This isn't really feasible right now. You could wrap it up in ReadOnlyMemory<byte> but I don't know for sure if that's possible or if JSON.NET/MessagePack-CSharp (our serializer libraries) will handle it properly.
If the only reason the buffer is unmanaged is because you need to call a native API to fill it, you could also try using a managed byte[] and pin it in order to get a native pointer you can pass into the native function to fill it up. Then you actually have a managed buffer, but the native code can fill it up:
var buffer = new byte[length];
fixed(byte* ptr = buffer)
{
    NativeAPIToFillTheBuffer(ptr, length);
}

Once you've filled the buffer, you can pass the byte[] array around without allocating new things. You can also pool the buffers (as long as you ensure you don't return the buffer to the pool until after awaiting the InvokeAsync/SendAsync call).

On the server, there's no way to pool the byte[] allocations we use when deserializing the message so that's not something that can be avoided at the moment.

@anurse there are a few shortcomings to using a byte array pool in my solution.
ffmpeg API does not allow you to pass a pointer to a buffer to use by compression API, it will always allocate a packet memory itself and refcount the packet, by design.
Using a buffer pool of byte[] arrays means they will have fixed sizes, compressed packets are not fixed sizes they can vary up to two orders of magnitude in size from around 1KB up to 200 - 300 KB with chosen settings, averaging at around 30 kb. I have chosen to send a packet in a single call and not bother with chunking at this stage (there was no observable benefit for my solution as the server is far from being maxed out).
In conclusion, the solution to increase application buffer size worked best for my use case.

We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.


Import from Notion fails

I have followed the documentation here but the import fails. After starting the import it quickly tallies up the remaining files to be imported and then the "Done" button shows up. No files are imported. In the developer tools console the following error message is shown:

Import dialog box:

Not sure if this is related to #61. The .zip I'm trying to import is only around 600 MB and the symptoms seem different.

Do you have a zip file within your zip file that is an attachment? I think that message seems to say that it ran into a broken zip file.

Do you have a zip file within your zip file that is an attachment? I think that message seems to say that it ran into a broken zip file.

Not sure if I understand correctly, but the zip I got from Notion has another zip file inside it. I've tried extracting it and importing the nested zip, but I get the same issue. Is this a botched export from Notion?

That seems to have been the issue. I had two zip files that were added as attachments to notes in Notion. I unzipped the whole export, removed the two zip files and zipped the export again. This time the import worked fine.
Maybe a check could be implemented in the importer so that if the importer finds any nested zip files you'll get a more descriptive actual error message in the UI?

Can you show me what those attachment file names look like?

These are the two files I removed from the export:

Ah ok, were they named like that in the package? Do you know what path they existed within the zip file? (I'm trying to figure out how we should detect if a zip is an attachment vs a zip that is a nested export zip)
Currently I think the most reasonable thing is to check if the zip is in the root of the parent zip - seems like Notion put the nested zips at the top level but attachments go into a subfolder.

Yes they were named the same.
This is an extract of the folder structure:
├── <guid>_Export-<guid-2>.zip <- this is the file I downloaded after exporting from Notion
│   ├── Export-<guid-2>-Part-1.zip
│   │   ├── Export-<guid-2>
│   │   │   ├── <some-notes>.html
│   │   │   ├── <some-databases>.csv
│   │   │   ├── <some-folder>
│   │   │   │   ├── <some-notes>.html
│   │   │   │   ├── <some-databases>.csv
│   │   │   │   ├── <some-folder>
│   │   │   │   │   ├── <some-notes>.html
│   │   │   │   │   ├── <some-databases>.csv
│   │   │   │   │   └── <some-file>.zip <- zip file causing problems

As far as I can understand, any zip file contained inside the folder named Export-<guid2> is an attachment and not a nested export zip. I think if you add an attachment to a note in the root folder, it would be exported as a folder containing the note in an html file and the attachment in whatever file format the attachment is in.

Thanks for the nice diagram! I understand now. I've added a check to only look into zips at the root of the export, which should solve this case, but it might also be a good idea to look for the word "export" in the name.

I did some testing. I created a new workspace. So it only contained the demo content that is generated by Notion. I added a small .zip file to an empty note in the root folder containing only the .zip file.
Again, it created the same two level nested zip file as before, but as you can see from the screenshot, the note containing the zip file becomes an html file in the root folder, while the zip file attached to that note ends up in a folder that is named the same as the html file. So there should be no risk of having any zip files (or any non html/csv files) in the root folder of the export.

And just tested importing that export into Obsidian. Importer worked perfectly. The empty note that only contained the attached zip now just contains the file name of the zip file and there's an emtpy attachments folder at the root level.

Is it possible to also implement an error message about the zip file being skipped?
Another thing is that I get this error message about index.html in the root folder. I got that in my first import as well. Is that normal?

index.html should be skipped. It's just something Notion includes, but isn't a real page.


Main class prevents all accesses through package name!

All package contents are not accessible through the package due to the name of the main class. For example, the class MungoError can still be accessed as long as no package name is defined; Accessing the class with package name MungoHealer.MungoError is always failed.

Thank for reporting the issue. Do you also have an idea how this can be fixed? Feel free to post a PR.

@Dschee  For a certain entity, we can just import it directly with swift default import declaration like
import protocol MungoHealer.BaseError
But in some cases, e.g. adding a new custom ErrorHandler, there is some efforts behind. A ton of related entities like BaseError, ... is required and has to be imported one-by-one.
For a long term solution, I prefer to rename the main class MungoHealer to Healer or something else that does not duplicate the package name. What do you think?

If that fixes the issue, I'm not against renaming MungoHealer (though I feel it's weird that we need to do this). I'd prefer Mungo over Healer though, since in the example code we also just name the global variable mungo – the type would fit then. Would you like to create a PR (and test if that actually solved the problem)?


How to port Rinforcement learning algorithm on smaug?

Hello, I'm trying to port RL maddpg algorithm on smaug. Is there any documentation you can provide to follow for integrating the new algorithm?
Thanks

See https://harvard-acc.github.io/smaug_docs/build_python_model.html for building a new python model. All the available operators are also listed on that site.

Hello, thanks for the document. I also wanted to know if this also works for pytorch reinforcement model maddpg with python version 3.6? And provides the acceleration capabilities?


Fix screening sorting on submission table

See https://github.com/OpenTechFund/hypha/pull/2148#issuecomment-737137459

Deploying to live now. Thanks for quick fix!


:tada: Add support for Challengermode demos

Added a DemoSource for Challengermode.
The FaceItParser seemed to work well both for CS:GO and CS:2.
I created a new analyzer for future differing behaviour (uneccessary?)
I can supply some more demos to test with if needed.
Regards,

Hi! Could you upload some CSGO/CS2 demos please?
Thanks

Made a PR
https://gitlab.com/akiver/cs-demos/-/merge_requests/1

Thanks!


RuntimeException: No EMS yet for host

Hello,
After onboarding CSAR file, runtime exception appeared for the message between generic VNFM and EMS. After throwing this exception, on boarding process is halted and VNFM sent ERROR message to VNFR .
Is there any way to handle this problem?
EMS_problem.txt
Thank you,
Onur

Any suggestion on that?

Hi, most of the time this is due to two main reasons:

EMS not properly installed/configured inside the VM where the VNF should be installed. For troubleshooting, I suggest you to ssh into the VM and check that the EMS configuration file is present (under /etc/openbaton/ems) and the conf.ini file is properly configured. Please paste if possible the content of that file. The installation/configuration of the EMS happens while the VM is booting using the cloud-init functionality.
in that file (conf.ini) you should see that there is a parameter orch_ip which is actually the IP of RabbitMQ. This IP must be reachable from the VM network, so that the EMS can register to the VNFM. If this IP is not set correctly (for instance is set to localhost), you should configure the NFVO/VNFM configuration files (rabbitmq related paramters) accordingly. http://openbaton.github.io/documentation/nfvo-configuration/

I have the same problem.
EMS is installed, I see the file (/etc/openbaton/ems/confi.ini):
[ems]
orch_ip = localhost
orch_port = 61613
type = generic
hostname = newName1
I did not understand well what should I do, can you explain please.

Please check my comment in issue #167


Could not run the client on linux

Hello,
The client would not sometimes. It seems to be stuck on something.
My log id is<PHONE_NUMBER>0c341d6e22651c
Don't hesitate to ask me questions if I can shed some lights on something.

This issue has been fixed in between. Thanks.