text:
operator jaeger (1.59.0)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?
[x] Have you tested your Operator with all Custom Resource Definitions?
[x] Have you tested your Operator in all supported installation modes?
[x] Have you considered whether you want use semantic versioning order?
[x] Is your submission signed?
[x] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

The submitted files look weird, only files from the bundle dir should be submitted e.g. https://github.com/k8s-operatorhub/community-operators/commit/35590fc8ef7f4a7724169c42d9772abf24f93de6

/merge possible

/merge possible


text:
Add Direct Secret Reference extension

Direct Secret Reference extension allows Service Binding resource
with the service directly pointing to a secret resource.
This address the "Native Bindings" issue #92
Signed-off-by: Baiju Muthukadan baiju.m.mail@gmail.com

If anybody is interested in trying out this spec extension, I have a draft implementation over at https://github.com/vmware-labs/service-bindings/pull/64

thanks so much for doing this PR @baijum! I just added a very minor suggestion. LGTM

Thanks! I have committed your change.

source: gharchive/pull-request

authors: baijum scothis

license_type: permissive

license_source: github-api


text:
feat: supporting new schema refactor

Closes #
📑 Description

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

ℹ Additional Information

https://github.com/k8sgpt-ai/k8sgpt/pull/1219

You need to update your branch

authors: AlexsJones matthisholleville


text:
cni-log always creates the default log file in /var/log/cni-log.log

An application using it would most likely set its own path via SetLogFile before logging any messages.
currently we end up with the default log file always being created even if logs are not written to it.
proposal:
remove default log file, force user to set it
alternative:
if log file path was not set, use default (initialize on first write)

#9 fixes this.

source: gharchive/issue


text:
Fix wrong MAC address value in returned Result.

According to CNI Convention MAC address returned in the Result is the
one configured by the plugin, but plugin return initial VF's MAC addr
even if it was passed in cni config.
MAC address value, returned by SetupVF function, assigned from the
linkObj after mac address was setted. That's not correct, since linkObj
don't point directly to underlying kernel's netlink object, so mac
address still has initial value.
Fix that by doing correct assignments.
Fix: #143
Signed-off-by: Dmytro Linkin dlinkin@nvidia.com

from the code i can see the problem and the fix
so im LGTM.

authors: DmytroLinkin adrianchiris


text:
POD deployment failing with error "failed to find plugin "sriov" in path [/opt/cni/bin /opt/cni/bin]"

I have followed this git wiki to bring add SRIOV CNI plug into my k8s cluster v1.23.5
SRIOV VFs created on 3 worker nodes
root@worker1:~# lshw -c Network -businfo
Bus info          Device      Class          Description
========================================================
pci@0000:01:00.0  eno1        network        Ethernet Controller 10-Gigabit X540-AT2
pci@0000:01:00.1  eno2        network        Ethernet Controller 10-Gigabit X540-AT2
pci@0000:01:10.1  eno2v0      network        X540 Ethernet Controller Virtual Function
pci@0000:01:10.3  eno2v1      network        X540 Ethernet Controller Virtual Function
pci@0000:01:10.5  eno2v2      network        X540 Ethernet Controller Virtual Function
pci@0000:01:10.7  eno2v3      network        X540 Ethernet Controller Virtual Function
pci@0000:01:11.1  eno2v4      network        X540 Ethernet Controller Virtual Function
pci@0000:01:11.3  eno2v5      network        X540 Ethernet Controller Virtual Function
pci@0000:01:11.5  eno2v6      network        X540 Ethernet Controller Virtual Function
pci@0000:01:11.7  eno2v7      network        X540 Ethernet Controller Virtual Function
pci@0000:08:00.0  eno3        network        I350 Gigabit Network Connection
pci@0000:08:00.1  eno4        network        I350 Gigabit Network Connection
                  pkt0        network        Ethernet interface
                  vhost0      network        Ethernet interface
                  kube-ipvs0  network        Ethernet interface

lspci  -vmmkns 01:10.1
Slot:	01:10.1
Class:	0200
Vendor:	8086
Device:	1515
SVendor:	1028
SDevice:	1f61
Rev:	01
Driver:	ixgbevf
Module:	ixgbevf
NUMANode:	0

configMAP
apiVersion: v1
kind: ConfigMap
metadata:
  name: sriovdp-config
  namespace: kube-system
data:
  config.json: |
    {
        "resourceList": [{
                "resourceName": "intel_sriov_netdevice",
                "selectors": {
                    "vendors": ["8086"],
                    "devices": ["1515"],
                    "drivers": ["ixgbevf"]
                }
            }
        ]
    }

SRIOV Plugin Status
kubectl get pods -A -o wide | grep sriov
kube-system       kube-sriov-device-plugin-amd64-2b2k4        1/1     Running             0              3h20m   192.168.24.114   worker2       <none>           <none>
kube-system       kube-sriov-device-plugin-amd64-2k8ks        1/1     Running             0              3h20m   192.168.24.115   worker3       <none>           <none>
kube-system       kube-sriov-device-plugin-amd64-4vklh        1/1     Running             0              3h20m   192.168.24.112   controller1   <none>           <none>
kube-system       kube-sriov-device-plugin-amd64-vszsw        1/1     Running             0              3h20m   192.168.24.113   worker1       <none>           <none>

Worker1 SRIOV Plugin Logs
 kubectl logs kube-sriov-device-plugin-amd64-vszsw -n kube-ssytem
Error from server (NotFound): namespaces "kube-ssytem" not found
root@controller1:~/sriov-network-device-plugin/deployments# kubectl logs kube-sriov-device-plugin-amd64-vszsw -n kube-system
I1007 14:14:09.067263       1 manager.go:51] Using Kubelet Plugin Registry Mode
I1007 14:14:09.067668       1 main.go:44] resource manager reading configs
I1007 14:14:09.067716       1 manager.go:79] raw ResourceList: {
    "resourceList": [{
            "resourceName": "intel_sriov_netdevice",
            "selectors": {
                "vendors": ["8086"],
                "devices": ["1515"],
                "drivers": ["ixgbevf"]
            }
        }
    ]
}
I1007 14:14:09.067882       1 factory.go:166] net device selector for resource intel_sriov_netdevice is &{DeviceSelectors:{Vendors:[8086] Devices:[1515] Drivers:[ixgbevf] PciAddresses:[]} PfNames:[] RootDevices:[] LinkTypes:[] DDPProfiles:[] IsRdma:false NeedVhostNet:false}
I1007 14:14:09.067909       1 manager.go:99] unmarshalled ResourceList: [{ResourcePrefix: ResourceName:intel_sriov_netdevice DeviceType:netDevice Selectors:0xc00012ed20 SelectorObj:0xc0001eb1e0}]
I1007 14:14:09.067974       1 manager.go:200] validating resource name "intel.com/intel_sriov_netdevice"
I1007 14:14:09.067986       1 main.go:60] Discovering host devices
I1007 14:14:09.143094       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:00.0	02          	Intel Corporation   	Ethernet Controller 10-Gigabit X540-AT2
I1007 14:14:09.143593       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:00.1	02          	Intel Corporation   	Ethernet Controller 10-Gigabit X540-AT2
I1007 14:14:09.143912       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:10.1	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.144120       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:10.3	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.144298       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:10.5	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.144479       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:10.7	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.144658       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:11.1	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.144843       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:11.3	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.145018       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:11.5	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.145182       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:11.7	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.145361       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:08:00.0	02          	Intel Corporation   	I350 Gigabit Network Connection
I1007 14:14:09.145675       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:08:00.1	02          	Intel Corporation   	I350 Gigabit Network Connection
I1007 14:14:09.146062       1 netDeviceProvider.go:123] excluding interface eno4:  default route found: {Ifindex: 3 Dst: <nil> Src: <nil> Gw: 192.168.24.1 Flags: [] Table: 254 Realm: 0}
I1007 14:14:09.146165       1 main.go:66] Initializing resource servers
I1007 14:14:09.146177       1 manager.go:105] number of config: 1
I1007 14:14:09.146183       1 manager.go:109]
I1007 14:14:09.146201       1 manager.go:110] Creating new ResourcePool: intel_sriov_netdevice
I1007 14:14:09.146207       1 manager.go:111] DeviceType: netDevice
I1007 14:14:09.146468       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:00.0. error getting devlink device attributes for net device 0000:01:00.0 no such device
I1007 14:14:09.146981       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:10.1. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.147492       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:10.3. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.148057       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:10.5. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.148652       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:10.7. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.149327       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:11.1. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.150057       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:11.3. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.150795       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:11.5. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.151590       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:11.7. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.151982       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:08:00.0. error getting devlink device attributes for net device 0000:08:00.0 no such device
I1007 14:14:09.152226       1 factory.go:106] device added: [pciAddr: 0000:01:10.1, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.152237       1 factory.go:106] device added: [pciAddr: 0000:01:10.3, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.152244       1 factory.go:106] device added: [pciAddr: 0000:01:10.5, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.152249       1 factory.go:106] device added: [pciAddr: 0000:01:10.7, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.152255       1 factory.go:106] device added: [pciAddr: 0000:01:11.1, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.152260       1 factory.go:106] device added: [pciAddr: 0000:01:11.3, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.152266       1 factory.go:106] device added: [pciAddr: 0000:01:11.5, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.152272       1 factory.go:106] device added: [pciAddr: 0000:01:11.7, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.152291       1 manager.go:139] New resource server is created for intel_sriov_netdevice ResourcePool
I1007 14:14:09.152300       1 main.go:72] Starting all servers...
I1007 14:14:09.152966       1 server.go:199] starting intel_sriov_netdevice device plugin endpoint at: intel.com_intel_sriov_netdevice.sock
I1007 14:14:09.154007       1 server.go:226] intel_sriov_netdevice device plugin endpoint started serving
I1007 14:14:09.154081       1 main.go:77] All servers started.
I1007 14:14:09.154097       1 main.go:78] Listening for term signals
I1007 14:14:09.901179       1 server.go:110] Plugin: intel.com_intel_sriov_netdevice.sock gets registered successfully at Kubelet
I1007 14:14:09.901385       1 server.go:134] ListAndWatch(intel_sriov_netdevice) invoked
I1007 14:14:09.901431       1 server.go:142] ListAndWatch(intel_sriov_netdevice): send devices &ListAndWatchResponse{Devices:[]*Device{&Device{ID:0000:01:10.5,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:10.7,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:11.1,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:11.3,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:11.5,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:11.7,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:10.1,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:10.3,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},},}
I1007 17:05:18.522910       1 server.go:119] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:01:10.3],},},}
I1007 17:05:18.523176       1 netResourcePool.go:51] GetDeviceSpecs(): for devices: [0000:01:10.3]
I1007 17:05:18.523229       1 pool_stub.go:97] GetEnvs(): for devices: [0000:01:10.3]
I1007 17:05:18.523260       1 pool_stub.go:113] GetMounts(): for devices: [0000:01:10.3]
I1007 17:05:18.523294       1 server.go:128] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_NETDEVICE: 0000:01:10.3,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{},Annotations:map[string]string{},},},}
I1007 17:24:29.323445       1 server.go:119] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:01:10.7],},},}
I1007 17:24:29.323605       1 netResourcePool.go:51] GetDeviceSpecs(): for devices: [0000:01:10.7]
I1007 17:24:29.323648       1 pool_stub.go:97] GetEnvs(): for devices: [0000:01:10.7]
I1007 17:24:29.323675       1 pool_stub.go:113] GetMounts(): for devices: [0000:01:10.7]
I1007 17:24:29.323708       1 server.go:128] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_NETDEVICE: 0000:01:10.7,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{},Annotations:map[string]string{},},},}

Worker2 SRIOV Plugin Logs
kubectl logs pod kube-sriov-device-plugin-amd64-2b2k4 -n kube-system
Error from server (NotFound): pods "pod" not found
root@controller1:~/sriov-network-device-plugin/deployments# kubectl logs kube-sriov-device-plugin-amd64-2b2k4 -n kube-system
I1007 14:14:09.079266       1 manager.go:51] Using Kubelet Plugin Registry Mode
I1007 14:14:09.079662       1 main.go:44] resource manager reading configs
I1007 14:14:09.079715       1 manager.go:79] raw ResourceList: {
    "resourceList": [{
            "resourceName": "intel_sriov_netdevice",
            "selectors": {
                "vendors": ["8086"],
                "devices": ["1515"],
                "drivers": ["ixgbevf"]
            }
        }
    ]
}
I1007 14:14:09.079850       1 factory.go:166] net device selector for resource intel_sriov_netdevice is &{DeviceSelectors:{Vendors:[8086] Devices:[1515] Drivers:[ixgbevf] PciAddresses:[]} PfNames:[] RootDevices:[] LinkTypes:[] DDPProfiles:[] IsRdma:false NeedVhostNet:false}
I1007 14:14:09.079881       1 manager.go:99] unmarshalled ResourceList: [{ResourcePrefix: ResourceName:intel_sriov_netdevice DeviceType:netDevice Selectors:0xc00000cd38 SelectorObj:0xc0002732b0}]
I1007 14:14:09.079937       1 manager.go:200] validating resource name "intel.com/intel_sriov_netdevice"
I1007 14:14:09.079948       1 main.go:60] Discovering host devices
I1007 14:14:09.160470       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:00.0	02          	Intel Corporation   	Ethernet Controller 10-Gigabit X540-AT2
I1007 14:14:09.160929       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:00.1	02          	Intel Corporation   	Ethernet Controller 10-Gigabit X540-AT2
I1007 14:14:09.161233       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:10.1	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.161423       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:10.3	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.161608       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:10.5	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.161790       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:10.7	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.161968       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:11.1	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.162148       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:11.3	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.162347       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:11.5	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.162517       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:01:11.7	02          	Intel Corporation   	X540 Ethernet Controller Virtual Func...
I1007 14:14:09.162696       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:07:00.0	02          	Intel Corporation   	I350 Gigabit Network Connection
I1007 14:14:09.163047       1 netDeviceProvider.go:84] netdevice AddTargetDevices(): device found: 0000:07:00.1	02          	Intel Corporation   	I350 Gigabit Network Connection
I1007 14:14:09.163359       1 netDeviceProvider.go:123] excluding interface eno4:  default route found: {Ifindex: 3 Dst: <nil> Src: <nil> Gw: 192.168.24.1 Flags: [] Table: 254 Realm: 0}
I1007 14:14:09.163464       1 main.go:66] Initializing resource servers
I1007 14:14:09.163474       1 manager.go:105] number of config: 1
I1007 14:14:09.163480       1 manager.go:109]
I1007 14:14:09.163484       1 manager.go:110] Creating new ResourcePool: intel_sriov_netdevice
I1007 14:14:09.163490       1 manager.go:111] DeviceType: netDevice
I1007 14:14:09.163757       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:00.0. error getting devlink device attributes for net device 0000:01:00.0 no such device
I1007 14:14:09.164263       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:10.1. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.164774       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:10.3. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.165335       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:10.5. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.165943       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:10.7. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.166623       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:11.1. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.223968       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:11.3. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.225272       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:11.5. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.226620       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:01:11.7. error getting devlink device attributes for net device 0000:01:00.1 no such device
I1007 14:14:09.227088       1 utils.go:71] Devlink query for eswitch mode is not supported for device 0000:07:00.0. error getting devlink device attributes for net device 0000:07:00.0 no such device
I1007 14:14:09.227365       1 factory.go:106] device added: [pciAddr: 0000:01:10.1, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.227383       1 factory.go:106] device added: [pciAddr: 0000:01:10.3, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.227391       1 factory.go:106] device added: [pciAddr: 0000:01:10.5, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.227399       1 factory.go:106] device added: [pciAddr: 0000:01:10.7, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.227406       1 factory.go:106] device added: [pciAddr: 0000:01:11.1, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.227413       1 factory.go:106] device added: [pciAddr: 0000:01:11.3, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.227420       1 factory.go:106] device added: [pciAddr: 0000:01:11.5, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.227427       1 factory.go:106] device added: [pciAddr: 0000:01:11.7, vendor: 8086, device: 1515, driver: ixgbevf]
I1007 14:14:09.227449       1 manager.go:139] New resource server is created for intel_sriov_netdevice ResourcePool
I1007 14:14:09.227463       1 main.go:72] Starting all servers...
I1007 14:14:09.228304       1 server.go:199] starting intel_sriov_netdevice device plugin endpoint at: intel.com_intel_sriov_netdevice.sock
I1007 14:14:09.229532       1 server.go:226] intel_sriov_netdevice device plugin endpoint started serving
I1007 14:14:09.229664       1 main.go:77] All servers started.
I1007 14:14:09.229703       1 main.go:78] Listening for term signals
I1007 14:14:09.723669       1 server.go:110] Plugin: intel.com_intel_sriov_netdevice.sock gets registered successfully at Kubelet
I1007 14:14:09.723803       1 server.go:134] ListAndWatch(intel_sriov_netdevice) invoked
I1007 14:14:09.723825       1 server.go:142] ListAndWatch(intel_sriov_netdevice): send devices &ListAndWatchResponse{Devices:[]*Device{&Device{ID:0000:01:11.3,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:11.5,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:11.7,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:10.1,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:10.3,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:10.5,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:10.7,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},&Device{ID:0000:01:11.1,Health:Healthy,Topology:&TopologyInfo{Nodes:[]*NUMANode{&NUMANode{ID:0,},},},},},}
I1007 16:40:58.109477       1 server.go:119] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:01:10.1],},},}
I1007 16:40:58.109645       1 netResourcePool.go:51] GetDeviceSpecs(): for devices: [0000:01:10.1]
I1007 16:40:58.109680       1 pool_stub.go:97] GetEnvs(): for devices: [0000:01:10.1]
I1007 16:40:58.109700       1 pool_stub.go:113] GetMounts(): for devices: [0000:01:10.1]
I1007 16:40:58.109714       1 server.go:128] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_NETDEVICE: 0000:01:10.1,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{},Annotations:map[string]string{},},},}
I1007 17:20:46.347960       1 server.go:119] Allocate() called with &AllocateRequest{ContainerRequests:[]*ContainerAllocateRequest{&ContainerAllocateRequest{DevicesIDs:[0000:01:10.7],},},}
I1007 17:20:46.348120       1 netResourcePool.go:51] GetDeviceSpecs(): for devices: [0000:01:10.7]
I1007 17:20:46.348153       1 pool_stub.go:97] GetEnvs(): for devices: [0000:01:10.7]
I1007 17:20:46.348171       1 pool_stub.go:113] GetMounts(): for devices: [0000:01:10.7]
I1007 17:20:46.348185       1 server.go:128] AllocateResponse send: &AllocateResponse{ContainerResponses:[]*ContainerAllocateResponse{&ContainerAllocateResponse{Envs:map[string]string{PCIDEVICE_INTEL_COM_INTEL_SRIOV_NETDEVICE: 0000:01:10.7,},Mounts:[]*Mount{},Devices:[]*DeviceSpec{},Annotations:map[string]string{},},},}
root@controller1:~/sriov-network-device-plugin/deployments#

NAD Defination:-
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: sriov-net1
  annotations:
    k8s.v1.cni.cncf.io/resourceName: intel.com/intel_sriov_netdevice
spec:
  config: '{
  "type": "sriov",
  "cniVersion": "0.3.1",
  "name": "sriov-network",
  "ipam": {
    "type": "host-local",
    "subnet": "192.168.200.0/24",
    "routes": [{
      "dst": "0.0.0.0/0"
    }],
    "gateway": "192.168.200.1"
  }
}'

POD Definition:-
apiVersion: v1
kind: Pod
metadata:
  name: testpod1
  annotations:
    k8s.v1.cni.cncf.io/networks: sriov-net1
spec:
  containers:
  - name: appcntr1
    image: centos/tools
    imagePullPolicy: IfNotPresent
    command: [ "/bin/bash", "-c", "--" ]
    args: [ "while true; do sleep 300000; done;" ]
    resources:
      requests:
        intel.com/intel_sriov_netdevice: '1'
      limits:
        intel.com/intel_sriov_netdevice: '1'

POD status
root@controller1:~/sriov-network-device-plugin/deployments# kubectl describe pod testpod1
Name:         testpod1
Namespace:    default
Priority:     0
Node:         worker1/192.168.24.113
Start Time:   Fri, 07 Oct 2022 17:24:29 +0000
Labels:       <none>
Annotations:  k8s.v1.cni.cncf.io/networks: sriov-net1
              kube-manager.juniper.net/vm-uuid: f575e0a7-6871-41a1-b9ca-03208085a060
Status:       Pending
IP:
IPs:          <none>
Containers:
  appcntr1:
    Container ID:
    Image:         centos/tools
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/bash
      -c
      --
    Args:
      while true; do sleep 300000; done;
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Limits:
      intel.com/intel_sriov_netdevice:  1
    Requests:
      intel.com/intel_sriov_netdevice:  1
    Environment:                        <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hz5c2 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  kube-api-access-hz5c2:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason                  Age   From               Message
  ----     ------                  ----  ----               -------
  Normal   Scheduled               26s   default-scheduler  Successfully assigned default/testpod1 to worker1
  Normal   AddedInterface          11s   multus             Add eth0 [10.233.65.2/18] from default-podnetwork
  Warning  FailedCreatePodSandBox  11s   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "5e61b2bf0b849ef8d39f2b0268284d02710d4d1dad222ecd902ed565ed826fc7": plugin type="multus" name="multus-cni-network" failed (add): [default/testpod1:sriov-network]: error adding container to network "sriov-network": failed to find plugin "sriov" in path [/opt/cni/bin /opt/cni/bin]

SRIOV CNI was not available in the worker nodes

SRIOV CNI was not available in the worker nodes

You have to install sriov cni in advance, refer to https://github.com/k8snetworkplumbingwg/sriov-cni

authors: kashif-nawaz runzhliu


text:
config-daemon: Improve logging of draining state

Executions of nodeUpdateHandler are not tracked by logs,
that make debugging problems harder.
Also, adding a log line to write the node name the config-daemon is working on.
Note: part of this work will be superseded by

https://github.com/k8snetworkplumbingwg/sriov-network-operator/pull/488

but it's still useful to deal with draining issue while waiting for that PR.

Pull Request Test Coverage Report for Build 5950522014

9 of 13 (69.23%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.09%) to 24.769%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/daemon/daemon.go
9
13
69.23%

Files with Coverage Reduction
New Missed Lines
%

controllers/sriovibnetwork_controller.go
2
64.15%

controllers/sriovnetwork_controller.go
2
67.62%

Totals

Change from base Build 5949253686:
0.09%

Covered Lines:
2122

Relevant Lines:
8567

💛  - Coveralls

authors: coveralls zeeke


text:
Touch of Corruption not applying cruelty

Describe the bug
They fail the save and gain no status effect from any cruelty
To Reproduce
Steps to reproduce the behavior:

Attack with cruelty
Check to see if they failed the save
Check status of enemy
See that there is no status effect applied

Expected behavior
Feared, sickened or other status effect applied

As an example I tried using sicken on this and it doesn't have immunity to sicken. Ive tried all my cruelties out including fear which nothing should be immune to.

Example of me trying it with fear in another playthrough without the conquerer archtype.

Not even working on a basic cultist

The silly thing is that I have fixed this before, I don't know what changed and won't be able to get time for a look for a day or two.
Any chance it worked in the past and broke suddenly, or has it never worked in your game?

No I tried it again a few more times today and tried turning off other mods with no luck. Thanks for looking into it. Will just put these play throughs on hold till you get a chance to find the issue. Love your mod btw and am excited to play with it more.

Fixed! One of the last updates broke every single one, so I won't be able to update until I have more the the 20 or so min today to sort them all out.
Thanks for your testing it was a big help, if there is anything you want from the tabletop that I might be able to add let me know.
I'll leave this ticket open until the update is out.

Happy to help! Content mods like yours make this game way more replayable and its always a pleasure to see new ones coming up.
" if there is anything you want from the tabletop that I might be able to add let me know."
I know it would be a big ask, but I've been desperate for some psychic class/ archtypes from pnp. I loved playing it with "Call of the Wild" in kingmaker, and was sad to see no one adopt the class/ psychic archtypes yet for Wotr. Other than that more gish archtypes are always fun like the Blade Adept Archanist :)

Updates out, one day I might be brave enough to try the psychic stuff but not yet.
I believe another modder is doing the blade adept archetype so I'll hold off on that for now.
Once again, thanks for the help!

authors: bittercranberry mccabefliam

repo: ka-dyn/ExpandedContent

license: MIT


text:
APP-476: [C] Segmentation fault in Notification demo

(cherry picked from commit 8cfd807454f539c3f8e772029df3f416a7f52318)
Merge of #484 to 'master'

@kaa-leeroy test this please

@kaa-leeroy test this fully please

@kaa-leeroy test this fully please

repo: kaaproject/sample-apps


text:
KAA-947 Update configuration and gpio demos

Added specific dependencies for TI SDK v1.2.0.
Added license headers.

LGTM

authors: forGGe rasendubi


text:
StringTemplate4 does not handle embedded open and close curly braces.

I want to do something like this:
const fs = require('fs');

// Read package.json
const packageJson = JSON.parse(fs.readFileSync('./package.json', 'utf8'));

// Extract the antlr4 version
const antlrVersion = packageJson.dependencies.antlr4.replace('^', '');

// Run the command with the antlr4 version
const { exec } = require('child_process');
<tool_grammar_tuples:{x |

exec("antlr4 -v antlrVersion -encoding <antlr_encoding> -Dlanguage=JavaScript <x.AntlrArgs> <antlr_tool_args:{y | <y> } > <x.GrammarFileName>", (err, stdout, stderr) => \{
    if (err) \{
        // node couldn't execute the command
        return;
    \}

    console.log("stdout: $\{stdout\}");
    console.log("stderr: $\{stderr\}");
} >
});

In this template file, I want to instantiate some Javascript code that expands the call to "antlr4" for all .g4 files. But, StringTemplate won't allow open and close curlies in the template expansion for Anonymous subtemplates. If I escape the curlies using \{ and \} as I done above, the code is expanded, but StringTemplate does not remove the backslash of \{ or \} after expansion.

Looks like the template grammar is Antlr3, and it's only for the parser side. The lexer for the grammar is hand-written code.


text:
Steps to remove Microsoft IME

https://atmarkit.itmedia.co.jp/ait/articles/1902/04/news027.html
Needs to add Google Input first, and Microsoft IME can be removal

Hmmm... appeared again, and cannot remove IME in thesedays. I guess, since Windows 11 Version 24H2 (KB5043178) ref: https://github.com/kachick/dotfiles/issues/818

repo: kachick/dotfiles


text:
Fast Render Not Working in Meteor 1.4.2

I recently update to meteor 1.4.2, and fast-render is not injecting data into html.
Is it right? or am I missing something?

OH holy crap, I wasted a whole afternoon just because I updated Meteor? .......

Same here... at least I know what the problem is now.

Meteor. 1.4.2
meteor-react-router-ssr (it's used for the de/rehydration methods)

Haven't tried downgrading yet.

Update: I've tried installing older meteor versions back to 1.3.5.1 to no avail. Still doesn't work. What versions have others used that are known to work?

Update 2: (partial success) I created a fresh test project with meteor 1.3.5.1 w/ the bare minimum for meteor package: reactrouter:react-router-ssr  which uses fastrender and it works now. The rehydrateHook() receives the data and it's present in the js inject code in the client-side source.
meteor create frtest --release 1.3.5.1
Will try updating and adding packages to pinpoint further.

I'm currently using 1.4.2, It seems all versions after 1.4 don't work, anyone succeeded~?

Update 3: Ok, gets weirder... I upgraded my test installation that was at 1.3.5.1 to 1.4
meteor create frtest --release 1.4
and it continued to work.
Then I tried adding some packages, removing insecure and autopublish to rule those out and it still worked.
Then I tried updating to the newest meteor version 1.4.2 and it stopped working, as expected.
But when I tried to revert back to 1.4 with meteor create frtest --release 1.4, now fast render no longer works when it worked at that version before.
So updating to >1.4 somehow changes your installation so that even if you revert back to a known working version of meteor, fastrender still wont work.
Maybe it's node or the node version? FastRender injects data into the server response in webapp middleware (var res). Maybe meteor upgrading to 4 from 0.xx.x has something to do with it?
Next, I'm going to try creating a fresh project with the latest meteor version and see if that works.

Update 4: I'm pretty sure it's the webapp package >1.3.10. I think that's the reason why fastrender continued to work when I upgraded from 1.3.5.1 to 1.4.0.
When you upgrade to 1.4 from 1.3 there are a number of packages that don't get updated automatically. You need to explicitly run meteor update --packages-only to update them. I hadn't done that before I tested it again, so webapp wasn't updated.
And when I did update the packages and webapp updated from 1.3.10 to 1.3.12 that's when fastrender stoped working.
I'll continue investigating and submit a bug report @ meteor/meteor when I have more.

What I found until now:
I think the main problem of this issue is InjectData package. This package tries to override res.write method.
In that method, there is conditional statement below.
var condition =
      res._injectPayload && !res._injected &&
      encoding === undefined &&
      /<!DOCTYPE html>/.test(chunk);

These conditions are true except last one.  /<!DOCTYPE html>/.test(chunk) this condition always fail, because chuck parameter is not string but object(buffer) always.
So, I downgraded webapp package to 1.3.10(@rigconfig advised), and conditional statement return true. After that final string is what i expect like this, but weird thing is that in the browser, result html is same as before.

@simsim0709 I've got an update here at Meteor's issue tracker that addresses data-inject package. I just commented out a few lines above that to get it working again.
I've forked the inject-data repo w/ the fix
cd packages/
git clone https://github.com/rigconfig/inject-data
meteor run

@rigconfig Thanks. It's working fine! You did good job!! :)

Hey @rigconfig, trying to use your fix but still not receiving a FastRender payload.
I cloned your repo to /packages/ and ran meteor add meteorhacks:inject-data. Do I need to downgrade webapp to 1.3.10 as well or should it be working now?

@abecks Actually, you don't need to manually add meteorhacks:inject-data. It's a dependency of the fast-render package. I'm thinking that maybe because you manually added inject-data package it's not using the local package.
Try removing or commenting out the meteorhacks:inject-data line in your ./meteor/packages file,  restart and let me know if that changes anything.

Hey @rigconfig,
Unfortunately that didn't work either. Are you running the fix with webapp@1.3.12 or 1.3.10? I've been trying to downgrade to 1.3.10, but its a bit of a rabbit hole dependency wise (mongo, accounts-base, and service-configuration all have to be downgraded too). Maybe you know of an easier way to downgrade?

@abecks Oh, you don't need to downgrade webapp... I'm using it with the latest webapp@1.3.12 and the latest Meteor version 1.4.2.
Can you give me a list of your packages and meteor version? Maybe I can reproduce it.

Appreciate the help.
Ok, project starts out as 1.4.1.1.
I run meteor update to get to 1.4.2.
I run:
cd packages/
git clone https://github.com/rigconfig/inject-data

and launch the app. I log in, then refresh the page, expecting FastRender to do its magic. FastRender.debugger.getPayload returns undefined.
I added a console log to the condition check in inject-data/lib/server.js:
  res.write = function(chunk, encoding) {
    var condition =
      res._injectPayload && !res._injected &&
      encoding === undefined &&
      /<!DOCTYPE html>/.test(chunk);

    console.log('condition', condition);

condition is always false. It looks like what @simsim0709 was referring to where the chunk is now a buffer and no longer a string. If its working for you on webapp@1.3.12, how is your condition evaluating to true?
Here is my full package list:
# Meteor packages used by this project, one per line.
# Check this file (and the other files in this directory) into your repository.
#
# 'meteor add' and 'meteor remove' will edit this file for you,
# but you can also edit it by hand.

meteor-base@1.0.4             # Packages every Meteor app needs to have
mobile-experience@1.0.4       # Packages for a great mobile UX
mongo@1.1.14                   # The database Meteor supports right now
blaze-html-templates@1.0.4    # Compile .html files into Meteor Blaze views
reactive-var@1.0.11            # Reactive variable for tracker
jquery@1.11.10                  # Helpful client-side library
tracker@1.1.1                 # Meteor's client-side reactive programming library

standard-minifier-js@1.2.1    # JS minifier run for production mode
es5-shim@4.6.15                # ECMAScript 5 compatibility for older browsers.
ecmascript@0.5.9              # Enable ECMAScript2015+ syntax in app code
aldeed:simple-schema
kadira:flow-router
kadira:blaze-layout
accounts-base@1.2.14
accounts-password@1.3.1
less@2.7.6
aldeed:collection2
aldeed:autoform
staringatlights:autoform-generic-error
arillo:flow-router-helpers
jwo1f:parent-template
meteorhacks:fast-render
random@1.0.10
alanning:roles
tmeasday:acceptance-test-driver
xolvio:cleaner
reactive-dict@1.1.8
juliancwirko:s-alert
juliancwirko:s-alert-flip
session@1.1.7
dispatch:phoneformat.js
copleykj:livestamp
meteorhacks:subs-manager
aldeed:template-extension
tinymce
agnito:autogrow
email@1.1.18
http@1.2.10
meteortypescript:typescript-libs
fortawesome:fontawesome
perak:codemirror
seba:minifiers-autoprefixer
meteorhacks:aggregate
okgrow:router-autoscroll
meteorhacks:picker
matb33:collection-hooks
meteorhacks:kadira
tomwasd:history-polyfill
meteorhacks:zones
shell-server@0.2.1
reywood:publish-composite
muqube:autoform-nouislider
facts@1.0.9

If its working for you on webapp@1.3.12, how is your condition evaluating to true?

I haven't checked the condition that @simsim0709 was referring to. I just commented out the if statement at the beginning of the function to fix it.
I'll check the condition in my working version and then will try with your packages to see if there's a conflict there. Will post back. I'm on the road at the moment.

@abecks Ok, quick question... How are you achieving server-side rendering? I was looking through your packages and didn't see anything that does ssr? I'm probably missing something obvious, because I don't use blaze or flow-router anymore (switched to react and meteor-react-router-ssr a while ago).
From what I remember, to do ssr you need to install the package kadira:flow-router-ssr. Also, it says in the docs that it only works w/ react.
But again, I haven't been using flow router or blaze for a while, so I may be missing something simple?
If you could check your .meteor/versions file to see if inject-data is there or just post the list here.

Hey @rigconfig, I'm not server side rendering actually. But I prefer to have FastRender delivering the user's authentication status with the initial payload (which it should do on its own). I'm currently using FlowRouter.

@abecks Ok, thanks for the clarification. I'll see what I can do with creating a collection and subscription w/ your package list and see if I can duplicate the problem.
It might be easier though if you could create a reproduction recipe:

Create a new Meteor app that displays the bug with as little code as possible.
Create a new GitHub repository with a name like meteor-reactivity-bug [...] and push your code to it.
Reproduce the bug from scratch, starting with a git clone command.

Yeah, I'm not familiar enough with the technique you're employing, so I would need to see a minimal reproduction of the issue as mentioned above. I'l certainly take a look, though, if you want to do that.

Heres what I am talking about: https://meteorhacks.com/instant-login-for-meteor-with-fast-render/
Fast-Render looks for all the null publications and sends all their documents to the client with the initial HTML.
Because Fast Render is not sending any payload for me on 1.4.2, I am not receiving the "instant login" functionality that Fast Render provides. My FlowRouter routes trigger before the user is logged in, so every page refresh the user gets redirected to the login page, even though they are logged in.
I'll try to piece together a reproduction repo for you. Thanks for your time on this.

Having exactly the same thing as @abecks, since updating to 1.4.2 fast render stopped working completely. I also use it for "instant login".
Seems that chunk is always a buffer indeed.

I remember reading a comment by @arunoda somewhere that they needed to switch FastRender to use a new Meteor API for injecting data (instead of his inject-data package). I can't remember off the top of my head where I saw that comment though.
I know @arunoda/kadira have abandoned these Meteor repositories, so someone will have to fork FastRender to update it to the new injection API.

Hey @anschutz, just wondering if you found a solution yet. If not, I'll try to take a stab at forking Fast Render.

Hi @abecks, looks like the reason Fast Render can't inject the data is described in meteor/meteor#7753.
I just had to roll back to Meteor 1.4.1.3 for now.
There's an update in meteor/meteor#7992 where they suggest to use dynamicBody or dynamicHead instead of intercepting server messages.

@abecks if you only need it for instant login, you could simply "fake" the InjectData approach with dynamicHead
with this code you can still get your instant login:
WebApp.connectHandlers.use((req, res, next)->
    if not IsAppUrl(req)
        next()
        return

    loginToken = req.cookies['meteor_login_token']

    if loginToken
        loginToken = Accounts._hashLoginToken loginToken

        user = [Meteor.users.find({'services.resume.loginTokens.hashedToken': loginToken}).fetch()]

    payload = {
        subscriptions: {users: true},
        collectionData: {
            users: user
        }
    }

    data = {
        'fast-render-data': payload
    }

    req.dynamicHead = "<script type='text/inject-data'>#{encodeURIComponent (EJSON.stringify data)}</script>"
    next()
)

@adrianhunter That is wicked. Thanks for the example. I still need FastRender's subscriptions as well, so I'm going to attempt a PR fix for this.

I have added support for Meteor 1.4.2+ via the new dynamicHead feature in this PR to meteorhacks:inject-data.

authors: CharlesOy abecks adrianhunter anschutz rigconfig simsim0709

repo: kadirahq/fast-render

license: mit

license_source: bigquery


text:
Bugfix: CORS config on error handling

[ ] Breaking change?

What changes did you make? (Give an overview)

If you run frontend in development mode (i.e. port 3000), you will see CORS error, despite the old fix by @Haarolean (https://github.com/provectus/kafka-ui/pull/3957). Therefore, it seems that the following changes are neede:

diff --cc api/src/main/java/io/kafbat/ui/config/CorsGlobalConfiguration.java
--- a/api/src/main/java/io/kafbat/ui/config/CorsGlobalConfiguration.java
+++ b/api/src/main/java/io/kafbat/ui/config/CorsGlobalConfiguration.java
@@@ -22,7 -22,7 +22,8 @@@ public class CorsGlobalConfiguration

        final ServerHttpResponse response = ctx.getResponse();
        final HttpHeaders headers = response.getHeaders();
--      headers.add("Access-Control-Allow-Origin", "*");
++      headers.add("Access-Control-Allow-Origin", request.getHeaders().getOrigin());
++      headers.add("Access-Control-Allow-Credentials", "true");
        headers.add("Access-Control-Allow-Methods", "GET, PUT, POST, DELETE, OPTIONS");
        headers.add("Access-Control-Max-Age", "3600");
        headers.add("Access-Control-Allow-Headers", "Content-Type");

Furthermore, if you call an API which causes any Error (happy path example: calling writable APIs on readonly mode clusters), the error handler (GlobalErrorWebExceptionHandler) baypasses CORS configs in CorsGlobalConfiguration, causing "Something went wrong: An error occurred" instead of "405 Method Not Allowed: This cluster is in read-only mode." in frontend. It seems that we should manually fill response headers in error handler, too.

I splitted changes into multiple commits to make tracking chnages easier.
Is there anything you'd like reviewers to focus on?
Spring web CORS configurations
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

No need to
[X] Manually (please, describe, if necessary)
Unit checks
Integration checks
Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[X] My changes generate no new warnings (e.g. Sonar is happy)
I have added tests that prove my fix is effective or that my feature works -> automatic testing spring configurations is too hard!
[X] New and existing unit tests pass locally with my changes
[X] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal

Hi, which issues are you experiencing besides seeing an error in your dev console? What are we trying to fix here exactly?

Hi, which issues are you experiencing besides seeing an error in your dev console? What are we trying to fix here exactly?

Hi!
Without the first change I described (Access-Control-Allow-Credentials header and explicitly filling Access-Control-Allow-Origin) only a white screen was visible in react dev mode (port 3000), providing features like hot auto-reload triggered by save. Because spring server takes the port 8080, I could not run react dev mode on the same port (without using perhaps something like nginx).
After fixing that, the second change (in GlobalErrorWebExceptionHandler) was needed to show the right messages in the red warning box at the bottom-right part of the page, not just in dev console. I can provide some screenshots tomorrow if needed.
By the way, all the changes in this PR aim to facilitate running the product in dev mode and will not provide any improvement in the production mode.

only a white screen

That's weird, as this works for me and the other folks, given you're not running the backend with SSL enabled.
I don't mind these changes for dev purposes, but I previously considered allowing the end user to configure cors for production via properties rather than just disabling it completely.

That's weird, as this works for me and the other folks, given you're not running the backend with SSL enabled.
I don't mind these changes for dev purposes, but I previously considered allowing the end user to configure cors for production via properties rather than just disabling it completely.

This is my procedure which causes the problem on main branch:
I run the front-end in dev mode via npm run dev after the following change:
diff --git a/frontend/src/lib/constants.ts b/frontend/src/lib/constants.ts
index 3e3925ec..33f49c7a 100644
--- a/frontend/src/lib/constants.ts
+++ b/frontend/src/lib/constants.ts
@@ -7,7 +7,7 @@ declare global {
 }

 export const BASE_PARAMS: ConfigurationParameters = {
-  basePath: window.basePath || '',
+  basePath: window.basePath || 'http://localhost:8080',
   credentials: 'include',
   headers: {
     'Content-Type': 'application/json',

I see only a white screen in my Firefox 130.0.1 on Ubuntu 20.04.6 LTS. I get the same result using Chrome. The network inspector claims CORS problems:

Maybe I should run the React dev mode via another way or something? Or maybe I should do something else other than modifying constants.ts?
P.S. I rebased the branch with main.

authors: Haarolean hadisfr

repo: kafbat/kafka-ui


text:
Cannot see mount in df -h if I use cache

Hi All,
When I mount goofys without cache like this (same via fstab so that is not the problem)
./goofys -f --debug_fuse --debug_s3 -o allow_other --gid "999" --uid "999" --endpoint https://x bucket /opt/x/x
I can see the mount with df -h no problem however... if I add the cache option I can see it twice and only in df -a... but I can still use the mount as if it was mounted properly...
./goofys -f --debug_fuse --debug_s3 --cache "-oallow_other:-ononempty:--free:10%:/opt/zimbra/backup_old/cache" -o allow_other --gid "999" --uid "999" --endpoint https://x bucket /opt/x/x
Sample of df -a:
"bucket                                  -          -          -    - /opt/x/x
/dev/fuse                               0          0          0    - /opt/x/x
"
Any idea why cache is mounting it "twice"? Also if I do it with the -f as I am showing and then cancel it... by doing Ctr + C it will stop the cache and mount it properly and it can be seen via df -h at this point.
I cannot understand why it does it...

cache is implemented as another fuse filesystem that's mounted on top of goofys. df -h should include the mountpoint, could you paste its output here?

There is nothing to paste... df -h just shows all the normal mounts whilst df -a will show the bucket mount and /dev/fuse additional mounts. Without cache the bucket mount will show in df -h as normal.

I am not sure why it works fine for me. Either way, is there actually an issue here? You can just use df -ah?

@kahing It is not an issue per se but it just looks weird that I have two mounts instead of one... and I also cannot see how much space is taken as it shows everything as 0.

S3 doesn't have an API to tell how much space is used. The two mountpoint thing is not something that can be fixed.

Thanks for clarifying, if it is the way it should be then all good.

authors: cblackuk kahing

repo: kahing/goofys


text:
Using standard bearer token auth in Restivus

Hi there!
Thanks for taking the time to put Restivus together!  This is fantastic!
So, hey...  we're working on a package that implements the HL7 Argonaut FHIR spec, and the first implementation sprint has a requirement that involves implementing an auth token using the following HTTP Authorization header:
Authorization: Bearer {server-specific-token-here}
Any chance you could recommend how to implement this using Restivus?  I got the rest of the spec worked out; but I'm a little unsure of how one would implement a custom HTTP Authorization header with Restivus.
The Clinical/Healthcare Working Group has a bunch of members who are requesting this HL7 functionality, and it's going to get used in all sorts of neat applications:   teleradiology viewers, genetic analysis of pediatric cancer patients, personalized medicine dispensaries, health information exchanges, healthcare marketplaces, etc.
Any help you might be able to give will be going to a good cause!
Thanks,
Abigail

Hi Abigail!
First and foremost, I just want to say a huge THANK YOU to you for all your awesome contributions to Meteor and its community. The cookbook was a great resource when I was first getting started with Meteor and had no idea which way to turn, and you've even answered random emails from a friend of mine that really helped steer us in the right direction on a few issues in the past. So thanks for all of that, and everything else you do to help make the Meteor community one of the best out there!
Okay, that being said, I certainly want to do anything I can to return the favor. I'm sorry that the documentation on custom authentication is insufficient. This is probably as good a time as ever to clean that up.
Do you need an OAuth provider (to generate and persist a token), or are you just looking to use the bearer token standard to authorize a user/account that has already authenticated by some other means? I, shamefully, have very limited experience with OAuth, so I would need to do some further research to see what solutions are out there for implementing a custom OAuth provider in Meteor.
If you're using an existing OAuth provider (or not using OAuth at all) and you'll already have the token stored on the server, then there is a way to do this with Restivus' custom auth. There are three steps to implementing this in Restivus, all of which must take place in the custom auth function:

Parse the bearer token
Validate the bearer token (find the user/account with that token)
Return the authorized user/account

1. Parsing the bearer token
Restivus does not provide an out-of-the-box solution for parsing a bearer token. If you already have code to do this, then you can skip ahead to the next step. If you don't, there's a (currently unpublished) Connect middleware package for parsing a standard bearer token. Any route that it is added to will have this.request.authToken set to the parsed token.
Since Restivus is built on top of simple:json-routes, you can add middleware using JsonRoutes.addMiddleWare(). Since the middleware package exposes its middleware function as JsonRoutes.Middleware.parseBearerToken, you can use
JsonRoutes.addMiddleWare('api/path', JsonRoutes.Middleware.parseBearerToken);

where 'api/path' is the route path where the middleware will be added. To add the middleware to all routes, just exclude the path (you probably already know this from working with Connect in the past).
2. Validating the bearer token
This is pretty straightforward. Grab the bearer token you parsed in the previous step and handle any validation steps you deem necessary. For most folks this will probably amount to simply querying the user/account collection where the bearer token is stored (probably the Meteor.users collection, but nothing is stopping you from using a different collection). If the token exists, it's considered validated. Of course, you can provide additional validation steps, such as hashing a token, or maybe validating a time stamp to check for its expiration. That's all up to your specific requirements.
If validating against a hashed bearer token stored in the default location in a Meteor.user document, you can use this (also currently unpublished) middleware package.
3. Return the authorized user/account
Once you consider the token validated, you just need to return the user/account document that it belongs to as {user: <user_document>}. That document will be available in any authenticated endpoints as this.user, with its Mongo ID available as this.userId.
Putting that all together should look something like:
CoffeeScript (I'll convert this to JS at your request)
JsonRoutes.addMiddleWare 'api/path', JsonRoutes.Middleware.parseBearerToken
Api = new Restivus
  useDefaultAuth: false
  auth:
    user: ->
      authToken = this.request.authToken
      user = Meteor.users.findOne {'path.to.token': authToken}
      user: user

Not as bad as it sounded up above, I think :)
Hopefully, that's a good start. Of course, there are some planned features for Restivus that will make this even better. Namely, improved support for middleware integration, allowing middleware to be added directly to Restivus routes/endpoints, for hassle-free, finer-grained control over middleware behaviors. My goal for v0.9 is to separate Restivus "core" and move all the extra functionality into add-on packages (e.g., collections support) and middleware (e.g., auth, error handling, before/on/after hooks, etc).
Additionally, I'll see if we can go ahead and get those middleware packages published, along with the other updates that have been lingering on simple:rest. It's been a while, so I'm not quite sure what was preventing us from publishing everything. I'll have to coordinate with @stubailo and @aldeed on that. I'll try my very best to take care of it by this weekend, or at the very least get the ball rolling on it.
Please let me know if you need me to clarify anything, or if you need any additional information at all. Hopefully, this can be a start to my effort to repay you for all your great contributions to the community. Thanks so much, and keep up the awesome work!

Yeah I've been lagging on publishing that stuff. But I have published the new version of simple:json-routes with all of the new stuff. I guess we should publish the middleware packages as well.

Thanks for the speedy response, Sashko!
Sounds great. Let me know if there's anything I can do to help.

Hi Kahmali  :)
I really appreciate that.  Thank you.  They say no good deed goes unpunished; and you might be surprised at the amount of crap I deal with on a regular basis for being so active in the community.  (Or maybe you wouldn't be surprised at all, and would understand exactly what I'm talking about.)  Regardless, it always means a lot to hear those stories, and know that other people are finding the Cookbook and other projects I'm working on to be helpful.
Anyhow.  Awesome response.  Thank you!  Thank you!  I think this should get me up and running with something.  I'm very excited to give this a try with the middleware components.
My apologies for the delay in response... I've had a client emergency this past week regarding a HIPAA audit.  Also, I'm getting ready to drive out to Santa Cruz, and It will be another couple of weeks before I can implement.  I'm looking at the week of Sept 15th before I can do another HL7/Rest sprint.  But this is very much on my roadmap, and I'll get a response on how it integrates, and some documentation in a few weeks.
Regarding your question of OAuth... it's in the HL7 Argonaut spec.  So, yes.  We would very much like to eventually get an OAuth2 server incorporated.
The good news is that we've got financial resources from UC Santa Cruz, four or five Meteor startups willing to help with it; and the resources of some big players like Epic and Cerner willing to help with externalized testing.   We're planning development sprints over the next few months; and want to put together an entire OAuth2 server reference implementation as part of the HL7 spec.
So, I may very well ping you with occasional questions over the next few months, if it's okay.  And any thoughts you have on OAuth2 server integration...  I'd be more than happy to have a conversation here, on the meteor forums, a hackpad, or elsewhere.
Thank you again for your wonderful reply!  :)

Hi Kahmali,
Good day.
I'm new to developing an API and I found out your art work ~ "Restivus". Currently, I'm using it to my API development with Meteor. It's pretty dope man! Thanks!! Right now, I'm creating a custom login authentication as per my company requires, that all request are in http body request which is now giving me a headache on how to implement because its not following the standard that is already built in with meteor accounts.
My main goal is to reuse/override the authentication that is already on meteor.
Can you please convert this coffeescript to javascript?
JsonRoutes.addMiddleWare 'api/path', JsonRoutes.Middleware.parseBearerToken
Api = new Restivus
useDefaultAuth: false
auth:
user: ->
authToken = this.request.authToken
user = Meteor.users.findOne {'path.to.token': authToken}
user: user
Once again, thank you!
Best Regards,
Christian

Use http://js2.coffee/ for translating it
Andreas

Hi, thanks for the quick response. Anyway, I've already converted it when I Googled it.
The next question is how to do about it after converting, when running it gives me these error:
TypeError: Cannot read property 'handle' of undefined
W20150924-21:52:12.096(8)? (STDERR)     at Function.app.use (/Users/user/.meteor/packages/simple_json-routes/.1.0.4.8tkp64++os+web.browser+web.cordova/npm/node_modules/connect/lib/proto.js:69:30)

Thanks for the tip @a4xrbj1!
Hi @LshanuNearKheel. Thanks so much for the kind words!! Can you do me a favor and open a new issue if you're experiencing problems. It appears Abigail (the author of the original issue) was able to successfully implement bearer token auth with the steps provided here. There's no need to bug her with our messages since this is an unrelated issue. I'm actually going to close this issue, since it's intended purpose has been fulfilled.
Also, please read the extremely short section from my Contributing Guidelines on reporting bugs (I can almost assure you this isn't a bug, but rather just something off about your code, no disrespect). If you need help debugging your code, that may be a better question for Stack Overflow, or the Meteor forums. I'm so insanely busy trying to launch an MVP right now that writing this message is pretty much all the time I have to spend on Restivus today. Only about 20 people see these Issues, but 100s will see your SO question, so you just have a better chance of getting a quick response, possibly from a few different people. Same for the Meteor forums.
I wish I could be more help. If you run into a wall on SO and the Meteor forums, just come back here (well, not exactly here, but in a new issue) and let me know, and we'll definitely get this figured out for you.

repo: kahmali/meteor-restivus


text:
fix: search pane appearance (fix #170)

I added appearance: none to buttons and inputs to override
platform native styling on these form elements. Earlier, to
fix issue #1, I had added --webkit-appearance: none only to
the search inputs. It didn't fix the issue completely, because
some browsers still apply a default border-radius to inputs.
I now add border-radius: none and appearance: none
to all inputs and buttons.

I tested this with the device simulator in Xcode and it seems to have fixed this issue.


text:
上传组件在build-pro的页面里在选择上传文件后会报错TypeError: t.upload.addEventListener is not a function

element-plus-Ix-kQ1m3.js:48 Uncaught (in promise) TypeError: t.upload.addEventListener is not a function
at fR (element-plus-Ix-kQ1m3.js:48:182695)
at element-plus-Ix-kQ1m3.js:48:190299
at Generator.next ()
at l (element-plus-Ix-kQ1m3.js:1:681)

楼上解决了吗？

ElUpload 组件如果使用的action绑定上传接口URL，把本地viteMockServe插件注释后打包即可解决，原因是mock组件和Elupload冲突

@b7wch


text:
:robot: Reset test is very flaky

Kairos version:
master
CPU architecture, OS, and Version:
all
Describe the bug
Reset test is failing a lot lately, we should check to see if we can improve it somehow to be less flaky or identify if there is a corner case where it makes it fail due to some specific issue.
To Reproduce
check reset jobs on build PRs pipeline
Expected behavior
doesnt fail all the time
Logs

Additional context

Let's wait until master CI is green ( to avoid debugging irrelevant issues ), then let's create a PR that only runs this test (disabling the rest) and finally let's keep triggering this until it fails, because this was not reproducible locally and we no longer have a link to a failed job.
We want the make sure there isn't something wrong with our reset workflow, that's why we are insisting on this one.

The test has been consistently green in the past 10 runs ... will try to run multiple times locally to validate

still green on every master run and for many local runs ... we've been merging changes on peg, upgrading packages so hard to tell if one of this changes fixed it, we also have the faster runners which might have made the test more reliable. Closing for now but feel free to re-open

authors: Itxaka jimmykarily mauromorales

repo: kairos-io/kairos


text:
saved_entry grub options not getting applied on boot in kairos 2.4.0

Kairos version:
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
KAIROS_NAME="kairos-core-ubuntu"
KAIROS_VERSION="v2.4.0"
KAIROS_ID="ubuntu"
KAIROS_ID_LIKE="kairos-core-ubuntu"
KAIROS_VERSION_ID="v2.4.0"
KAIROS_PRETTY_NAME="kairos-core-ubuntu v2.4.0"
KAIROS_BUG_REPORT_URL="https://github.com/spectrocloud/CanvOS/issues"
KAIROS_HOME_URL="https://github.com/spectrocloud/CanvOS"
KAIROS_IMAGE_REPO="spectrocloud/CanvOS"
KAIROS_IMAGE_LABEL="latest"
KAIROS_GITHUB_REPO=""
KAIROS_VARIANT="ubuntu"
KAIROS_FLAVOR="ubuntu"root@localhost:/var/log#

CPU architecture, OS, and Version:
Linux localhost 6.2.0-33-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep  7 10:33:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Describe the bug
We are adding saved_entry grub_options as part of the elemental install config through kairos pkg github.com/kairos-io/kairos/pkg/config. These options get passed to the install config through a handler which gets executed by agent.install plugin event.
cloudInit.Install.Auto = true
cloudInit.Install.Reboot = !cloudInit.Install.Poweroff
cloudInit.Install.GrubOptions["saved_entry"] = "registration"

/oem/90_custom.yaml using 2.3.2
kairos@Master-one:/var/log$ cat /oem/90_custom.yaml
#cloud-config
install:
  auto: true
  grub_options:
    saved_entry: registration
  reboot: true
stages:
  after-upgrade:
  - commands:
    - mkdir -p /usr/local/bin
    - '[ -L /usr/local/bin/agent-provider-stylus ] || ln -s /opt/spectrocloud/bin/agent-provider-stylus
      /usr/local/bin/agent-provider-stylus'
    - bash /opt/spectrocloud/scripts/content.sh
  - commands:
    - grub2-editenv /oem/grubenv unset saved_entry
    if: '[ -f /oem/grubenv ]'
  initramfs:
  - if: '[ ! -f /oem/80_stylus.yaml ]'
    name: set_inotify_max_values
    sysctl:
      fs.inotify.max_user_instances: "8192"
      fs.inotify.max_user_watches: "524288"

With v2.4.0, the after-upgrade stage seems to be missing altogether.
#cloud-config

install:
    grub-entry-name: Palette eXtended Kubernetes Edge
    poweroff: true
    recovery-system:
        size: 5000
    system:
        size: 5000
reset:
    grub-entry-name: Palette eXtended Kubernetes Edge
    system:
        size: 5000
stages:
    initramfs:
        - users:
            kairos:
                groups:
                    - sudo
                passwd: kairos
        - users:
            kairos:
                groups:
                    - sudo
                passwd: kairos

Here, setting the saved_entry flag to the registration grub. However, after upgrading to 2.4.0, we found
/oem/grubenv missing and after installation next boot is not going to this grub instead it is going to the first entry in the grub menu.
Output of grubmenu.cfg
root@localhost:/var/log# cat /etc/kairos/branding/grubmenu.cfg
menuentry "Palette eXtended Kubernetes Edge Reset" --id statereset {
    set img=/cOS/recovery.img
    search.fs_label COS_RECOVERY root
    set label=COS_SYSTEM
    loopback loop0 /$img
    set root=($root)
    source (loop0)/etc/cos/bootargs.cfg
    linux (loop0)$kernel $kernelcmd ${extra_cmdline} ${extra_recovery_cmdline} kairos.reset
    initrd (loop0)$initramfs
}

menuentry "Palette eXtended Kubernetes Edge Registration" --id registration {
    search --no-floppy --label --set=root COS_STATE
    set img=/cOS/active.img
    set label=COS_ACTIVE
    loopback loop0 /$img
    set root=($root)
    source (loop0)/etc/cos/bootargs.cfg
    linux (loop0)$kernel $kernelcmd ${extra_cmdline} ${extra_active_cmdline} stylus.registration
    initrd (loop0)$initramfs
}

Expected behavior
Expected to boot into proper grub menu entry. Here, in this case, it should boot into menuentry "Palette eXtended Kubernetes Edge Registration" --id registration. It was working fine till v2.3.2.
This issue is similar to the one https://github.com/kairos-io/kairos/issues/1460

This works as expected via config file so the problem may lie passing the arguments via the bus?
hint: Its an object so it may not have the proper header for the collector to understand if if the collecter is reading it somehow...


text:
Alphabet --- First attempt

This is the first attempt on the alphabet implementation.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@2ab4ca9). Click here to learn what that means.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##             master      #4   +/-   ##
========================================
  Coverage          ?   2.43%
========================================
  Files             ?       2
  Lines             ?      41
  Branches          ?       0
========================================
  Hits              ?       1
  Misses            ?      40
  Partials          ?       0

Flag
Coverage Δ

#unittests
2.43% <0.00%> (?)

Impacted Files
Coverage Δ

src/Alphabet.jl
0.00% <0.00%> (ø)

src/KnuthBendix.jl
100.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2ab4ca9...46a122b. Read the comment docs.

authors: bprzybylski codecov-commenter


text:
Error with rostopic echo /line_segments

Hello!
I managed to run the package and visualize the lines from /marker topic through rviz. But when I am trying to access the topic /line_segments to get the list of lines I get the following error:
ERROR: Cannot load message class for [laser_line_extraction/LineSegmentList]. Are your messages built?
The topic appears in the list of active topics with rostopic lists, but rqt_graph does not include it. When I try to see the published messages with rostopic echo I get the error above. I tried to clean the workspace with catkin_make clean and rebuild it with catkin_make, then source again the environment but still, I get the same error. I think I am missing something here. Can you please provide any hint?
Thanks in advance!

Update: I managed to get the content of the topic with rostopic echo. I was not sourcing the environment in my current terminal (not proud for that). But rqt_graph still does not show the topic /line_segments. Any hint for that???

Update: I managed to get the content of the topic with rostopic echo. I was not sourcing the environment in my current terminal (not proud for that). But rqt_graph still does not show the topic /line_segments. Any hint for that???

Note that rqt_graph only shows topics that are being subscribed to? Is something subscribed to /line_segments? Note that rviz subscribes to /line_markers, not /line_segments.

Update: I managed to get the content of the topic with rostopic echo. I was not sourcing the environment in my current terminal (not proud for that). But rqt_graph still does not show the topic /line_segments. Any hint for that???

Note that rqt_graph only shows topics that are being subscribed to? Is something subscribed to /line_segments? Note that rviz subscribes to /line_markers, not /line_segments.

I wasn't aware that rqt_graph shows only subscribed topics. I don't have any subscriber there yet, so it makes sense. My bad. Thanks a lot!


text:
Maximum Target temperature limited to 25 degree

Hello, first one thank you for this nice integration.
at the moment my panasonic is working on fixed target temperature.
when i would like to set the target temperature from Homeassistant, the maximum of climate.panasonic_heat_pump_main_z1_temp is 25
i can´t set the target temperature over dashboard to higher of 25. is possible to change this?

and the same for the target senor

thank you

For now there is some issues with direct temperature settings.. so please wait for solution :)  duplicate issue in #57

It should be fixed in 0.9.6

authors: Striker2102 geduxas kamaradclimber

repo: kamaradclimber/heishamon-homeassistant


text:
Drop V2: Organization Overview page

Background

Drop and stop using V2 components
This pull request display changes only for overview page for org

View
Before:
https://github.com/kamilkisiela/graphql-hive/assets/37614975/fb0b96d9-a50a-4d2f-96ef-b93a374abbb9
After:
https://github.com/kamilkisiela/graphql-hive/assets/37614975/f78db9aa-f23e-44ee-8c95-b0f08ce16f5b

These margin are huge :D I think I prefer the "before" margins better

authors: TuvalSimha kamilkisiela

repo: kamilkisiela/graphql-hive


text:
Relax "os" gem version to minor level

The "os" gem compatibility means that 1.1 is fine to use with this gem.
Closes: https://github.com/kapoorlakshya/screen-recorder/issues/96

@hlascelles Thanks for your contribution! Will try to get a release out this weekend.

Fantastic, thank you :rocket:!

authors: hlascelles kapoorlakshya

repo: kapoorlakshya/screen-recorder


text:
this addon on windows 10 opens too many terminals at once

with added path to e.g. git-bash.exe (64bit) 8 terminals are opened and it looks weird why it's like that, maybe it has 8 runs as I have 8 CPU active threads (core-i7)???

I'm guessing you have 8 projects and this is due to the lack of multiple project support. Try atom-terminus: https://github.com/drelyn86/atom-terminus

repo: karan/atom-terminal


text:
Fails to run when segment_size is set to anything except 256 in mdx_params of Separator

Trying to run the library similarly to how I use UVR5; I wanted to run a model with a larger segment size, but I can't seem to get anything other than the default 256 to work at all on either of the two MDX models I've tried (Voc FT and Inst HQ 4).
Running the below code works normally:
from audio_separator.separator import Separator

sep = Separator(model_file_dir="./models", invert_using_spec=True)

# sep.load_model("UVR-MDX-NET-Inst_HQ_4.onnx")

# prim, _ = sep.separate("test.wav")

sep.load_model("UVR-MDX-NET-Voc_FT.onnx")

voc, _ = sep.separate("test.wav")

...outputs two stems as wav files in the parent directory, as expected.
But changing this line:
...
sep = Separator(model_file_dir="models", invert_using_spec=True, mdx_params={"segment_size": 1024})
...

gives the following output:
2024-03-14 15:57:19,547 - INFO - separator - Separator version 0.15.3 instantiating with output_dir: None, output_format: WAV
2024-03-14 15:57:19,547 - DEBUG - separator - Secondary step will be inverted using spectogram rather than waveform. This may improve quality, but is slightly slower.
2024-03-14 15:57:19,548 - INFO - separator - Operating System: Windows 10.0.19045
2024-03-14 15:57:19,548 - INFO - separator - System: Windows Node: realbox Release: 10 Machine: AMD64 Proc: AMD64 Family 25 Model 33 Stepping 2, AuthenticAMD
2024-03-14 15:57:19,548 - INFO - separator - Python Version: 3.11.7
2024-03-14 15:57:19,548 - INFO - separator - PyTorch Version: 2.1.2+cu121
2024-03-14 15:57:19,566 - INFO - separator - FFmpeg installed: ffmpeg version 2024-02-04-git-7375a6ca7b-essentials_build-www.gyan.dev Copyright (c) 2000-2024 the FFmpeg developers
2024-03-14 15:57:19,568 - DEBUG - separator - Python package: onnxruntime-silicon not installed
2024-03-14 15:57:19,570 - INFO - separator - ONNX Runtime GPU package installed with version: 1.17.1
2024-03-14 15:57:19,570 - INFO - separator - ONNX Runtime CPU package installed with version: 1.16.3
2024-03-14 15:57:19,589 - INFO - separator - CUDA is available in Torch, setting Torch device to CUDA
2024-03-14 15:57:19,589 - INFO - separator - ONNXruntime has CUDAExecutionProvider available, enabling acceleration
2024-03-14 15:57:19,589 - INFO - separator - Loading model UVR-MDX-NET-Voc_FT.onnx...
2024-03-14 15:57:19,589 - DEBUG - separator - File already exists at ./models\download_checks.json, skipping download
2024-03-14 15:57:19,590 - DEBUG - separator - Model download list loaded
2024-03-14 15:57:19,590 - DEBUG - separator - Searching for model_filename UVR-MDX-NET-Voc_FT.onnx in supported_model_files_grouped
2024-03-14 15:57:19,590 - DEBUG - separator - Single file model identified: MDX-Net Model: UVR-MDX-NET Voc FT
2024-03-14 15:57:19,590 - DEBUG - separator - File already exists at ./models\UVR-MDX-NET-Voc_FT.onnx, skipping download
2024-03-14 15:57:19,591 - DEBUG - separator - Returning path for single model file: ./models\UVR-MDX-NET-Voc_FT.onnx
2024-03-14 15:57:19,591 - DEBUG - separator - Model downloaded, friendly name: MDX-Net Model: UVR-MDX-NET Voc FT
2024-03-14 15:57:19,591 - DEBUG - separator - Calculating MD5 hash for model file to identify model parameters from UVR data...
2024-03-14 15:57:19,591 - DEBUG - separator - Calculating hash of model file ./models\UVR-MDX-NET-Voc_FT.onnx
2024-03-14 15:57:19,605 - DEBUG - separator - Model ./models\UVR-MDX-NET-Voc_FT.onnx has hash 77d07b2667ddf05b9e3175941b4454a0
2024-03-14 15:57:19,606 - DEBUG - separator - VR model data path set to ./models\vr_model_data.json
2024-03-14 15:57:19,606 - DEBUG - separator - File already exists at ./models\vr_model_data.json, skipping download
2024-03-14 15:57:19,606 - DEBUG - separator - MDX model data path set to ./models\mdx_model_data.json
2024-03-14 15:57:19,606 - DEBUG - separator - File already exists at ./models\mdx_model_data.json, skipping download
2024-03-14 15:57:19,607 - DEBUG - separator - Loading MDX and VR model parameters from UVR model data files...
2024-03-14 15:57:19,607 - DEBUG - separator - Model data loaded from UVR JSON using hash 77d07b2667ddf05b9e3175941b4454a0: {'compensate': 1.021, 'mdx_dim_f_set': 3072, 'mdx_dim_t_set': 8, 'mdx_n_fft_scale_set': 7680, 'primary_stem': 'Vocals'}
2024-03-14 15:57:20,238 - DEBUG - common_separator - Common params: model_name=UVR-MDX-NET-Voc_FT, model_path=./models\UVR-MDX-NET-Voc_FT.onnx
2024-03-14 15:57:20,238 - DEBUG - common_separator - Common params: primary_stem_output_path=None, secondary_stem_output_path=None
2024-03-14 15:57:20,238 - DEBUG - common_separator - Common params: output_dir=None, output_format=WAV
2024-03-14 15:57:20,239 - DEBUG - common_separator - Common params: normalization_threshold=0.9
2024-03-14 15:57:20,239 - DEBUG - common_separator - Common params: enable_denoise=None, output_single_stem=None
2024-03-14 15:57:20,239 - DEBUG - common_separator - Common params: invert_using_spec=True, sample_rate=44100
2024-03-14 15:57:20,239 - DEBUG - common_separator - Common params: primary_stem_name=Vocals, secondary_stem_name=Instrumental
2024-03-14 15:57:20,239 - DEBUG - common_separator - Common params: is_karaoke=False, is_bv_model=False, bv_model_rebalance=0
2024-03-14 15:57:20,239 - DEBUG - mdx_separator - MDX arch params: batch_size=1, segment_size=1024
2024-03-14 15:57:20,240 - DEBUG - mdx_separator - MDX arch params: overlap=None, hop_length=None, enable_denoise=None
2024-03-14 15:57:20,240 - DEBUG - mdx_separator - MDX arch params: compensate=1.021, dim_f=3072, dim_t=256, n_fft=7680
2024-03-14 15:57:20,240 - DEBUG - mdx_separator - MDX arch params: config_yaml=None
2024-03-14 15:57:20,240 - DEBUG - mdx_separator - Loading ONNX model for inference...
Traceback (most recent call last):
  File "t:\python-audio-separator-test\Untitled-1.py", line 10, in <module>
    sep.load_model("UVR-MDX-NET-Voc_FT.onnx")
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\audio_separator\separator\separator.py", line 605, in load_model
    self.model_instance = separator_class(common_config=common_params, arch_config=self.arch_specific_params[model_type])
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\audio_separator\separator\architectures\mdx_separator.py", line 106, in __init__
    self.model_run = onnx2torch.convert(self.model_path)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\onnx2torch\converter.py", line 72, in convert
    onnx_model = safe_shape_inference(onnx_model_or_path)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\onnx2torch\utils\safe_shape_inference.py", line 46, in safe_shape_inference
    return _shape_inference_by_model_path(onnx_model_or_path, output_path=tmp_model_file.name, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\onnx2torch\utils\safe_shape_inference.py", line 24, in _shape_inference_by_model_path
    return onnx.load(output_path)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\onnx\__init__.py", line 208, in load_model
    model = _get_serializer(format, f).deserialize_proto(_load_bytes(f), ModelProto())
                                                         ^^^^^^^^^^^^^^
  File "C:\ProgramData\Anaconda3\envs\uvrcli\Lib\site-packages\onnx\__init__.py", line 145, in _load_bytes
    with open(f, "rb") as readable:
         ^^^^^^^^^^^^^
PermissionError: [Errno 13] Permission denied: 'T:\\python-audio-separator-test\\models\\tmptftn7wrq'

Tried the same code on M1 Mac, but the issue doesn't reproduce.

That's really strange, since the error message you saw in your first debug log output seems to be a permissions issue with a temporary folder, which I wouldn't expect to have anything to do with that parameter...
However, honestly I haven't tested on Windows at all, I don't have a Windows machine to hand and don't really know how to use that operating system these days so I'm not very well equipped to help.
I develop on a Mac and test on Linux (in a docker container).
Are you able to run Docker on your Windows machine? If so, that's probably the easiest way to get things to "just work", as the docker container will run within a Linux VM which will likely resolve any file path and/or permission issues.
I do note that there is a (subtle, but relevant) difference between your two example code lines though - in one you're setting model_file_dir to "./models" and the other, "models".
Technically those should both be relative paths to the same directory you're in, but windows file paths are weird (backslash instead of forward slash) so you might want to try experimenting with that!
If you want to try and debug it more thoroughly with support from me I'm happy to jump on a screen share call some time to investigate properly, just let me know a good date/time/timezone for you! I just don't have a Windows machine to do that myself :)

Ah, sorry, that's just from me testing to make sure the paths weren't a problem. I removed all the spaces from the path, and I put the dot slash to make sure that it was getting the correct models folder, but the result was the same.
I'm sure it would work in the docker container, now seeing that it worked fine on my own Mac. I'll experiment more later and come back with any updates, if I find anything else or if I get something working. I'll close the issue for now.

Thanks for the pointer @helloimmatt !
I don't have a Windows machine to test on but I've opened this PR with what I think you're suggesting the fix is?
If you're able to reproduce the error, please could you test that branch (name: attempt-to-test-windows-mdx-fix) on your machine to see if it fixes it? 🙇
Cheers,
Andrew

Thanks for testing and confirming @helloimmatt !
FYI @CarpetBook and anyone else who sees this - this issue on Windows should be fixed from v0.16.5 onwards 🙏

authors: CarpetBook beveradb

repo: karaokenerds/python-audio-separator


text:
ERROR com.intuit.karate - java.net.SocketException: Connection reset, http call failed after xxxxx secs

I have been trying to run a service which was working fine before. the only change happened is the conversion from http to https. Ususally in my other Karate projects , this was handled by
[ * configure ssl = true  ] in the feature file.
But for current project I am receiving the below error :
ERROR com.intuit.karate - java.net.SocketException: Connection reset, http call failed after xxxxx secs
I tried the below workarounds found in the stackoverflow but could not succeed.

usage of Karate-jersey instead of Karate-apache in the pom.xml
usage of below dependency

org.apache.httpcomponents
httpclient
${apache.version}

Below are the versions I used in pom file.
<karate.version>0.9.5</karate.version>
<apache.version>4.5.12</apache.version>
Strange this is my colleague was able to execute the same feature file in his system by changing the true to false for ssl validation as below:

configure ssl = false

But when I try this I get the SSL handshake exception. Can anyone help here ?

you are not going to get better help here instead of stack overflow unless you follow this process: https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue
maybe you have a proxy involved: https://stackoverflow.com/a/60641599/143475

you are not going to get better help here instead of stack overflow unless you follow this process: https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue
maybe you have a proxy involved: https://stackoverflow.com/a/60641599/143475

authors: Diyaneswar ptrthomas user198930

repo: karatelabs/karate


text:
MacOS sources of ART

On MacOS system, MacOS sources for ART should be downloaded.

Solved

repo: karel-brinda/smbl


text:
NSConcreteTask launchWithDictionary: crash

Crashed Thread:        1  Dispatch queue: com.find.timesync
Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [0]
Application Specific Backtrace 1:
0   CoreFoundation                      0x00007fff84a482cb __exceptionPreprocess + 171
1   libobjc.A.dylib                     0x00007fff9985348d objc_exception_throw + 48
2   CoreFoundation                      0x00007fff84ac6c3d +[NSException raise:format:] + 205
3   Foundation                          0x00007fff864712e6 -[NSConcreteTask launchWithDictionary:] + 2518
4   SwiftShell                          0x0000000105ade1f9 TToFE10SwiftShellCSo7Process15launchThrowablyfzT_T + 41
5   SwiftShell                          0x0000000105adea43 TFC10SwiftShell9RunOutputcfT6launchCS_12AsyncCommand_S0 + 147
6   SwiftShell                          0x0000000105ae2874 _TTSf4gs_g_n_n___TTSg5C10SwiftShell11MainContextS0_S_14CommandRunningS____TFE10SwiftShellPS_14CommandRunning3runfTSSGSaP__13combineOutputSb_CS_9RunOutput + 820
7   SwiftShell                          0x0000000105adbaf8 _TTSf4gs_n___TF10SwiftShell3runFT4bashSS13combineOutputSb_CS_9RunOutput + 264
8   SwiftShell                          0x0000000105adb93f _TF10SwiftShell3runFT4bashSS13combineOutputSb_CS_9RunOutput + 15
9   find                                0x0000000103587568 TTSf4d___TZFC4find10AppManager7syncNTPfT_GSqSd + 296
10  find                                0x000000010348b79d TFC4find18FindTimeSyncServer11loopProcessfT_T + 301
11  find                                0x000000010348bacb TFFFC4find18FindTimeSyncServer11loopProcessFT_T_U_FT_T_U_FT_T + 43
12  libdispatch.dylib                   0x00007fff9a10b524 _dispatch_call_block_and_release + 12
13  libdispatch.dylib                   0x00007fff9a1028fc _dispatch_client_callout + 8
14  libdispatch.dylib                   0x00007fff9a1189a0 _dispatch_queue_serial_drain + 896
15  libdispatch.dylib                   0x00007fff9a10b306 _dispatch_queue_invoke + 1046
16  libdispatch.dylib                   0x00007fff9a111020 _dispatch_queue_override_invoke + 369
17  libdispatch.dylib                   0x00007fff9a1046b5 _dispatch_root_queue_drain + 476
18  libdispatch.dylib                   0x00007fff9a10448c _dispatch_worker_thread3 + 99
19  libsystem_pthread.dylib             0x00007fff9a3515a2 _pthread_wqthread + 1299
20  libsystem_pthread.dylib             0x00007fff9a35107d start_wqthread + 13

Ok... so what is the code that is crashing?

Since there is no information to work with here I’m closing this issue. Feel free to reopen it if you want to add the code that is causing this crash.

authors: kareman xinlehou

repo: kareman/SwiftShell


text:
chore: move sources to root

Can we move everything from the KIDS directory to the root?
This results in a more uniform project structure overall, as well as the simplification of other "auto-tools" like CPM.

Im happy to take a PR to do this, otherwise I'm not sure I will be able to find the time.

I'll create a PR 🥳


text:
Revert "website images improvement"

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR reverted #157, as we found the docs link changed a lot by this PR and that maybe lead to links in blogs becoming invalid.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
I'm sorry that I didn't realize it before.

/assign @Poor12

/lgtm

repo: karmada-io/website


text:
拡張編集フィルタの上限

読み込まれた数：exedit92 + 0x146248
読み込まれたフィルタ情報（LoadedFilterTable）：exedit92 + 0x187c98
上限数：512（LoadedFilterTableの配列数が512のため）
現状としてこの上限がそこまで重要になることは無いはずですが、今後のpatch.aulで拡張編集用フィルタプラグインを読み込むような仕組みを作ることで増える可能性があるため情報として書きました

情報提供ありがとうございます。
読み込まれた拡張編集フィルタの数を表に追加で表示するようにしてみました。
Release v0.5.0 · karoterra/aviutl_ShowLimit
aufなどと同様に拡張編集フィルタについても一覧を出力する機能を実装してみようかと思いましたが、その一覧をどうやって取得すればよいかすぐには分からなかったため、一旦見送りとしました。
ちなみにこちらについては、 aviutl_exedit_sdk の ExEdit::Filter[512] という理解であってますでしょうか。

読み込まれたフィルタ情報（LoadedFilterTable）：exedit92 + 0x187c98

ExEdit::Filter LoadedFilterTable[512]   // こちらではなく
ExEdit::Filter *LoadedFilterTable[512]  // こっち

もしかしてこうですかね

https://github.com/nazonoSAUNA/patch.aul/blob/r43_58/patch/patch_exfilter.hpp
このあたりの使い方が参考になりますか？
後者で、厳密にはflagにExEdit::Filter::Flag::ExEditFilterがあればExEdit::Filterで、なければAviUtl::Filterだったと思いますが、今回は特に区別しなくても使えそうな気はします

もう少し通常な使い方をしている方も貼っておきます
https://github.com/nazonoSAUNA/SortEffect/blob/main/src.cpp#L200

ありがとうございます。
拡張編集フィルタの一覧も出力できるようになったので v0.5.1 としてリリースしました。
Release v0.5.1 · karoterra/aviutl_ShowLimit

authors: karoterra nazonoSAUNA


text:
make llama2.go ref llama2.c

hello everyone:
First of all, I would like to thank Karpathy for his contributions.
I have successfully implemented a golang version of the code. If you're interested, I would be more than happy to share it with you.
https://github.com/haormj/llama2.go

cool!

authors: haormj karpathy


text:
Fix copy and casting from spawning excessive threads

Due to Amdahl's law this optimization won't really matter (we only call this on the first call to gpt2_update), but for reference:
for a 124M model:

shard_num_parameters (in zero stage 0, and single GPU setups) is 124M
shard.size can be as small as 764 (layernorm shards)

So we're spawning 124M threads more than we need. :')

shouldn't shard size be 764/num_gpus, so even smaller?

true! our code fails if we run on a 764+ GPU cluster? :P


text:
Machine

合并

这是啥

repo: karsonzhang/fastadmin


text:
[Feature Request]: Adding preview in links shared to chat with click property

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The main problem is to make the links shared in the chat clickable and also preview it in the chat like discord or LinkedIn, twitter, Instagram platform does.
Record

[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

@yashksaini-coder are u working

@yashksaini-coder are u working

yes already done just checking the response

authors: Sibam-Paul yashksaini-coder

repo: kartikayasijaa/talk-trove


text:
Use kartotherian fork of tilelive-tmsource

For consistency with kartotherian (see
https://github.com/kartotherian/kartotherian/commit/3449c065c5a49ea6e6647dab2a1db5923e76a4d2).

LGTM. Tested and passed.

repo: kartotherian/tilerator