[Device Support Request] Aqara H1 Double Rocker No Neutral Switch (Xiaomi WS-EUK02/lumi.switch.l2aeu1)

Problem description
Hi all,
Since the merge of #2784 (Thanks for that @TheJulianJES) in release 0.0.107 (which has now been merged into Home Assistant version 2023.12.0), a new quirk has been added for the device with id lumi.switch.l2aeu1.
Unfortunately, it looks like not all functionality of the device is yet supported. Looking at the Zigbee2MQTT list of supported functionalities for this device it looks like some of the functionalities appear to not be available in this new quirk, like:

Power outage memory
Flip indicator light
LED disabled night
Operation mode (for each rocker separate)
Mode Switch
Some Actions (single_left, double_left, single_right and double_right appear to be working, single_both and double_both appear to not yet be working. Also the button_hold event appears to be the same for both the left and right rocker, shouldn't these be different for each rocker?)

Please add a comment or correct something if I am missing functionalities or have incorrectly labeled them here.
Solution description
I would like to see the quirk being updated to support the missing functionalities. I have tried looking into this myself, but unfortunately have not been successful yet.
Especially the Operation mode (Decoupled or Coupled/Control_relay) functionality is important to me currently.
It does look like (some of) the functionalities have already been implemented.
For example:
The quirk the device currently uses (zhaquirks.xiaomi.aqara.switch_h1_double.AqaraH1DoubleRockerSwitchNoNeutralAlt) has a base reference to XiaomiOpple2ButtonSwitchBase, which itself has an endpoint of 1 and 2 with the input_cluster OppleSwitchCluster. This input cluster contains a lot of the missing functionalities (like operation mode and switch type).
I am wondering why they aren't showing up in the device when using this quirk then. I have yet to be able to determine the cause for this, maybe someone could clarify it.
Screenshots/Video
Current functionality (since Home Assistant version 2023.12.0):

(Looks like the image is not showing using the <details> syntax, so pasted it outside so it at least shows)
Device signature
Device signature
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": "0x0104",
      "device_type": "0x0000",
      "input_clusters": [
        "0x0000",
        "0x0002",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0009",
        "0x0012",
        "0x0702",
        "0x0b04",
        "0xfcc0"
      ],
      "output_clusters": [
        "0x000a",
        "0x0019"
      ]
    },
    "2": {
      "profile_id": "0x0104",
      "device_type": "0x0000",
      "input_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0012",
        "0xfcc0"
      ],
      "output_clusters": []
    },
    "21": {
      "profile_id": "0x0104",
      "device_type": "0x0100",
      "input_clusters": [
        "0x000c"
      ],
      "output_clusters": []
    },
    "31": {
      "profile_id": "0x0104",
      "device_type": "0x0100",
      "input_clusters": [
        "0x000c"
      ],
      "output_clusters": []
    },
    "41": {
      "profile_id": "0x0104",
      "device_type": "0x0100",
      "input_clusters": [
        "0x0012"
      ],
      "output_clusters": []
    },
    "42": {
      "profile_id": "0x0104",
      "device_type": "0x0100",
      "input_clusters": [
        "0x0012"
      ],
      "output_clusters": []
    },
    "51": {
      "profile_id": "0x0104",
      "device_type": "0x0100",
      "input_clusters": [
        "0x0012"
      ],
      "output_clusters": []
    },
    "61": {
      "profile_id": "0x0104",
      "device_type": "0x0100",
      "input_clusters": [
        "0x0012"
      ],
      "output_clusters": []
    },
    "242": {
      "profile_id": "0xa1e0",
      "device_type": "0x0061",
      "input_clusters": [],
      "output_clusters": [
        "0x0021"
      ]
    }
  },
  "manufacturer": "LUMI",
  "model": "lumi.switch.l2aeu1",
  "class": "zhaquirks.xiaomi.aqara.switch_h1_double.AqaraH1DoubleRockerSwitchNoNeutralAlt"
}

Diagnostic information
Diagnostic information
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2023.12.0",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.11.6",
    "docker": true,
    "arch": "aarch64",
    "timezone": "Europe/Amsterdam",
    "os_name": "Linux",
    "os_version": "6.1.58-haos-raspi",
    "supervisor": "2023.11.6",
    "host_os": "Home Assistant OS 11.2",
    "docker_version": "24.0.7",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "grott": {
      "version": "1.1.0",
      "requirements": []
    },
    "volkswagen_we_connect_id": {
      "version": "1.0",
      "requirements": [
        "weconnect==0.58.0",
        "ascii_magic>=2.0.0"
      ]
    },
    "alarmo": {
      "version": "v1.9.13",
      "requirements": []
    },
    "hacs": {
      "version": "1.33.0",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
    "hass_agent_mediaplayer": {
      "version": "2022.5.6",
      "requirements": []
    },
    "afvalbeheer": {
      "version": "5.2.9",
      "requirements": [
        "rsa",
        "pycryptodome"
      ]
    },
    "multiscrape": {
      "version": "6.5.0",
      "requirements": [
        "lxml==4.9.1",
        "beautifulsoup4==4.11.1"
      ]
    },
    "dwains_dashboard": {
      "version": "3.6.0",
      "requirements": []
    },
    "hass_agent_notifier": {
      "version": "2<IP_ADDRESS>",
      "requirements": []
    },
    "webrtc": {
      "version": "v3.5.0",
      "requirements": []
    },
    "eufy_security": {
      "version": "7.7.4",
      "requirements": [
        "websocket-client==1.4.2",
        "aiortsp==1.3.7"
      ]
    },
    "watchman": {
      "version": "0.5.1",
      "requirements": [
        "prettytable==3.0.0"
      ]
    },
    "spotcast": {
      "version": "v3.6.30",
      "requirements": []
    }
  },
  "integration_manifest": {
    "domain": "zha",
    "name": "Zigbee Home Automation",
    "after_dependencies": [
      "onboarding",
      "usb"
    ],
    "codeowners": [
      "@dmulcahey",
      "@adminiuga",
      "@puddly",
      "@TheJulianJES"
    ],
    "config_flow": true,
    "dependencies": [
      "file_upload"
    ],
    "documentation": "https://www.home-assistant.io/integrations/zha",
    "iot_class": "local_polling",
    "loggers": [
      "aiosqlite",
      "bellows",
      "crccheck",
      "pure_pcapy3",
      "zhaquirks",
      "zigpy",
      "zigpy_deconz",
      "zigpy_xbee",
      "zigpy_zigate",
      "zigpy_znp",
      "universal_silabs_flasher"
    ],
    "requirements": [
      "bellows==0.37.1",
      "pyserial==3.5",
      "pyserial-asyncio==0.6",
      "zha-quirks==0.0.107",
      "zigpy-deconz==0.22.0",
      "zigpy==0.60.0",
      "zigpy-xbee==0.20.0",
      "zigpy-zigate==0.12.0",
      "zigpy-znp==0.12.0",
      "universal-silabs-flasher==0.0.15",
      "pyserial-asyncio-fast==0.11"
    ],
    "usb": [
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*2652*",
        "known_devices": [
          "slae.sh cc2652rb stick"
        ]
      },
      {
        "vid": "1A86",
        "pid": "55D4",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus v2"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*zigstar*",
        "known_devices": [
          "ZigStar Coordinators"
        ]
      },
      {
        "vid": "1CF1",
        "pid": "0030",
        "description": "*conbee*",
        "known_devices": [
          "Conbee II"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*conbee*",
        "known_devices": [
          "Conbee III"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*zigbee*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate+"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8B34",
        "description": "*bv 2010/10*",
        "known_devices": [
          "Bitron Video AV2010/10"
        ]
      }
    ],
    "zeroconf": [
      {
        "type": "_esphomelib._tcp.local.",
        "name": "tube*"
      },
      {
        "type": "_zigate-zigbee-gateway._tcp.local.",
        "name": "*zigate*"
      },
      {
        "type": "_zigstar_gw._tcp.local.",
        "name": "*zigstar*"
      },
      {
        "type": "_uzg-01._tcp.local.",
        "name": "uzg-01*"
      },
      {
        "type": "_slzb-06._tcp.local.",
        "name": "slzb-06*"
      }
    ],
    "is_built_in": true
  },
  "data": {
    "ieee": "**REDACTED**",
    "nwk": 11721,
    "manufacturer": "LUMI",
    "model": "lumi.switch.l2aeu1",
    "name": "LUMI lumi.switch.l2aeu1",
    "quirk_applied": true,
    "quirk_class": "zhaquirks.xiaomi.aqara.switch_h1_double.AqaraH1DoubleRockerSwitchNoNeutralAlt",
    "quirk_id": null,
    "manufacturer_code": 4447,
    "power_source": "Battery or Unknown",
    "lqi": 164,
    "rssi": -59,
    "last_seen": "2023-12-07T19:46:00",
    "available": true,
    "device_type": "EndDevice",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=11264, maximum_outgoing_transfer_size=100, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
      "endpoints": {
        "1": {
          "profile_id": "0x0104",
          "device_type": "0x0000",
          "input_clusters": [
            "0x0000",
            "0x0002",
            "0x0003",
            "0x0004",
            "0x0005",
            "0x0006",
            "0x0009",
            "0x0012",
            "0x0702",
            "0x0b04",
            "0xfcc0"
          ],
          "output_clusters": [
            "0x000a",
            "0x0019"
          ]
        },
        "2": {
          "profile_id": "0x0104",
          "device_type": "0x0000",
          "input_clusters": [
            "0x0000",
            "0x0003",
            "0x0004",
            "0x0005",
            "0x0006",
            "0x0012",
            "0xfcc0"
          ],
          "output_clusters": []
        },
        "21": {
          "profile_id": "0x0104",
          "device_type": "0x0100",
          "input_clusters": [
            "0x000c"
          ],
          "output_clusters": []
        },
        "31": {
          "profile_id": "0x0104",
          "device_type": "0x0100",
          "input_clusters": [
            "0x000c"
          ],
          "output_clusters": []
        },
        "41": {
          "profile_id": "0x0104",
          "device_type": "0x0100",
          "input_clusters": [
            "0x0012"
          ],
          "output_clusters": []
        },
        "42": {
          "profile_id": "0x0104",
          "device_type": "0x0100",
          "input_clusters": [
            "0x0012"
          ],
          "output_clusters": []
        },
        "51": {
          "profile_id": "0x0104",
          "device_type": "0x0100",
          "input_clusters": [
            "0x0012"
          ],
          "output_clusters": []
        },
        "61": {
          "profile_id": "0x0104",
          "device_type": "0x0100",
          "input_clusters": [
            "0x0012"
          ],
          "output_clusters": []
        },
        "242": {
          "profile_id": "0xa1e0",
          "device_type": "0x0061",
          "input_clusters": [],
          "output_clusters": [
            "0x0021"
          ]
        }
      },
      "manufacturer": "LUMI",
      "model": "lumi.switch.l2aeu1"
    },
    "active_coordinator": false,
    "entities": [
      {
        "entity_id": "button.lumi_lumi_switch_l2aeu1_identify",
        "name": "LUMI lumi.switch.l2aeu1"
      },
      {
        "entity_id": "sensor.lumi_lumi_switch_l2aeu1_voltage",
        "name": "LUMI lumi.switch.l2aeu1"
      },
      {
        "entity_id": "sensor.lumi_lumi_switch_l2aeu1_device_temperature",
        "name": "LUMI lumi.switch.l2aeu1"
      },
      {
        "entity_id": "sensor.lumi_lumi_switch_l2aeu1_power",
        "name": "LUMI lumi.switch.l2aeu1"
      },
      {
        "entity_id": "sensor.lumi_lumi_switch_l2aeu1_summation_delivered",
        "name": "LUMI lumi.switch.l2aeu1"
      },
      {
        "entity_id": "switch.lumi_lumi_switch_l2aeu1_switch",
        "name": "LUMI lumi.switch.l2aeu1"
      },
      {
        "entity_id": "switch.lumi_lumi_switch_l2aeu1_switch_2",
        "name": "LUMI lumi.switch.l2aeu1"
      }
    ],
    "neighbors": [],
    "routes": [],
    "endpoint_names": [
      {
        "name": "ON_OFF_SWITCH"
      },
      {
        "name": "ON_OFF_SWITCH"
      },
      {
        "name": "ON_OFF_LIGHT"
      },
      {
        "name": "ON_OFF_LIGHT"
      },
      {
        "name": "ON_OFF_LIGHT"
      },
      {
        "name": "ON_OFF_LIGHT"
      },
      {
        "name": "ON_OFF_LIGHT"
      },
      {
        "name": "ON_OFF_LIGHT"
      },
      {
        "name": "PROXY_BASIC"
      }
    ],
    "user_given_name": null,
    "device_reg_id": "c12643c3720da74abf21c3615a143757",
    "area_id": null,
    "cluster_details": {
      "1": {
        "device_type": {
          "name": "ON_OFF_SWITCH",
          "id": 0
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {
              "0x0005": {
                "attribute_name": "model",
                "value": "lumi.switch.l2aeu1"
              }
            },
            "unsupported_attributes": {}
          },
          "0x0002": {
            "endpoint_attribute": "device_temperature",
            "attributes": {
              "0x0000": {
                "attribute_name": "current_temperature",
                "value": 2000
              }
            },
            "unsupported_attributes": {}
          },
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0004": {
            "endpoint_attribute": "groups",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0005": {
            "endpoint_attribute": "scenes",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0006": {
            "endpoint_attribute": "on_off",
            "attributes": {
              "0x0000": {
                "attribute_name": "on_off",
                "value": 0
              }
            },
            "unsupported_attributes": {
              "0x4003": {
                "attribute_name": "start_up_on_off"
              }
            }
          },
          "0x0009": {
            "endpoint_attribute": "alarms",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0012": {
            "endpoint_attribute": "multistate_input",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0702": {
            "endpoint_attribute": "smartenergy_metering",
            "attributes": {
              "0x0000": {
                "attribute_name": "current_summ_delivered",
                "value": 0
              },
              "0x0302": {
                "attribute_name": "divisor",
                "value": 1000
              },
              "0x0306": {
                "attribute_name": "metering_device_type",
                "value": 0
              },
              "0x0301": {
                "attribute_name": "multiplier",
                "value": 1
              },
              "0x0303": {
                "attribute_name": "summation_formatting",
                "value": 35
              },
              "0x0300": {
                "attribute_name": "unit_of_measure",
                "value": 0
              }
            },
            "unsupported_attributes": {
              "0x0400": {
                "attribute_name": "instantaneous_demand"
              },
              "0x0100": {
                "attribute_name": "current_tier1_summ_delivered"
              },
              "0x0102": {
                "attribute_name": "current_tier2_summ_delivered"
              },
              "0x0106": {
                "attribute_name": "current_tier4_summ_delivered"
              },
              "0x0304": {
                "attribute_name": "demand_formatting"
              },
              "0x0104": {
                "attribute_name": "current_tier3_summ_delivered"
              },
              "0x0108": {
                "attribute_name": "current_tier5_summ_delivered"
              },
              "0x010a": {
                "attribute_name": "current_tier6_summ_delivered"
              },
              "0x0200": {
                "attribute_name": "status"
              }
            }
          },
          "0x0b04": {
            "endpoint_attribute": "electrical_measurement",
            "attributes": {
              "0x0605": {
                "attribute_name": "ac_power_divisor",
                "value": 10
              },
              "0x0604": {
                "attribute_name": "ac_power_multiplier",
                "value": 1
              },
              "0x050b": {
                "attribute_name": "active_power",
                "value": 0
              },
              "0x0403": {
                "attribute_name": "power_divisor",
                "value": 1
              },
              "0x0402": {
                "attribute_name": "power_multiplier",
                "value": 1
              },
              "0x0505": {
                "attribute_name": "rms_voltage",
                "value": 0
              },
              "0x0304": {
                "attribute_name": "total_active_power",
                "value": 0
              }
            },
            "unsupported_attributes": {
              "0x0600": {
                "attribute_name": "ac_voltage_multiplier"
              },
              "0x0601": {
                "attribute_name": "ac_voltage_divisor"
              },
              "0x0602": {
                "attribute_name": "ac_current_multiplier"
              },
              "0x0603": {
                "attribute_name": "ac_current_divisor"
              },
              "0x0401": {
                "attribute_name": "ac_frequency_divisor"
              },
              "0x0400": {
                "attribute_name": "ac_frequency_multiplier"
              },
              "0x0000": {
                "attribute_name": "measurement_type"
              },
              "0x0507": {
                "attribute_name": "rms_voltage_max"
              },
              "0x0508": {
                "attribute_name": "rms_current"
              },
              "0x0300": {
                "attribute_name": "ac_frequency"
              },
              "0x050a": {
                "attribute_name": "rms_current_max"
              },
              "0x0302": {
                "attribute_name": "ac_frequency_max"
              },
              "0x050d": {
                "attribute_name": "active_power_max"
              },
              "0x050f": {
                "attribute_name": "apparent_power"
              },
              "0x0510": {
                "attribute_name": "power_factor"
              }
            }
          },
          "0xfcc0": {
            "endpoint_attribute": "opple_cluster",
            "attributes": {},
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {
          "0x000a": {
            "endpoint_attribute": "time",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0019": {
            "endpoint_attribute": "ota",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      },
      "2": {
        "device_type": {
          "name": "ON_OFF_SWITCH",
          "id": 0
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0004": {
            "endpoint_attribute": "groups",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0005": {
            "endpoint_attribute": "scenes",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0006": {
            "endpoint_attribute": "on_off",
            "attributes": {
              "0x0000": {
                "attribute_name": "on_off",
                "value": 0
              }
            },
            "unsupported_attributes": {
              "0x4003": {
                "attribute_name": "start_up_on_off"
              }
            }
          },
          "0x0012": {
            "endpoint_attribute": "multistate_input",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0xfcc0": {
            "endpoint_attribute": "opple_cluster",
            "attributes": {},
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {}
      },
      "21": {
        "device_type": {
          "name": "ON_OFF_LIGHT",
          "id": 256
        },
        "profile_id": 260,
        "in_clusters": {
          "0x000c": {
            "endpoint_attribute": "analog_input",
            "attributes": {},
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {}
      },
      "31": {
        "device_type": {
          "name": "ON_OFF_LIGHT",
          "id": 256
        },
        "profile_id": 260,
        "in_clusters": {
          "0x000c": {
            "endpoint_attribute": "analog_input",
            "attributes": {},
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {}
      },
      "41": {
        "device_type": {
          "name": "ON_OFF_LIGHT",
          "id": 256
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0012": {
            "endpoint_attribute": "multistate_input",
            "attributes": {
              "0x0055": {
                "attribute_name": "present_value",
                "value": 1.0
              }
            },
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {}
      },
      "42": {
        "device_type": {
          "name": "ON_OFF_LIGHT",
          "id": 256
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0012": {
            "endpoint_attribute": "multistate_input",
            "attributes": {
              "0x0055": {
                "attribute_name": "present_value",
                "value": 1.0
              }
            },
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {}
      },
      "51": {
        "device_type": {
          "name": "ON_OFF_LIGHT",
          "id": 256
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0012": {
            "endpoint_attribute": "multistate_input",
            "attributes": {
              "0x0055": {
                "attribute_name": "present_value",
                "value": 1.0
              }
            },
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {}
      },
      "61": {
        "device_type": {
          "name": "ON_OFF_LIGHT",
          "id": 256
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0012": {
            "endpoint_attribute": "multistate_input",
            "attributes": {},
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {}
      },
      "242": {
        "device_type": {
          "name": "PROXY_BASIC",
          "id": 97
        },
        "profile_id": 41440,
        "in_clusters": {},
        "out_clusters": {
          "0x0021": {
            "endpoint_attribute": "green_power",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      }
    }
  }
}

Logs
Logs
I don't know if this is the correct piece of the debug logging, but here it is:
```python
2023-12-07 19:52:16.624 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'8160597e'
2023-12-07 19:52:16.627 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received incomingMessageHandler: [, EmberApsFrame(profileId=260, clusterId=0, sourceEndpoint=1, destinationEndpoint=1, options=, groupId=0, sequence=26), 156, -61, 0x0f3a, 255, 255, b'\x18t\x01\x04\x00\x00B\x04LUMI\x05\x00\x00B\x12lumi.switch.l2aeu1']
2023-12-07 19:52:16.627 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [, EmberApsFrame(profileId=260, clusterId=0, sourceEndpoint=1, destinationEndpoint=1, options=, groupId=0, sequence=26), 156, -61, 0x0f3a, 255, 255, b'\x18t\x01\x04\x00\x00B\x04LUMI\x05\x00\x00B\x12lumi.switch.l2aeu1']
2023-12-07 19:52:16.628 DEBUG (MainThread) [zigpy.application] Received a packet: ZigbeePacket(timestamp=datetime.datetime(2023, 12, 7, 18, 52, 16, 628382, tzinfo=datetime.timezone.utc), src=AddrModeAddress(addr_mode=, address=0x0F3A), src_ep=1, dst=AddrModeAddress(addr_mode=, address=0x0000), dst_ep=1, source_route=None, extended_timeout=False, tsn=26, profile_id=260, cluster_id=0, data=Serialized[b'\x18t\x01\x04\x00\x00B\x04LUMI\x05\x00\x00B\x12lumi.switch.l2aeu1'], tx_options=, radius=0, non_member_radius=0, lqi=156, rssi=-61)
2023-12-07 19:52:16.629 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:1:0x0000] Received ZCL frame: b'\x18t\x01\x04\x00\x00B\x04LUMI\x05\x00\x00B\x12lumi.switch.l2aeu1'
2023-12-07 19:52:16.630 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:1:0x0000] Decoded ZCL frame header: ZCLHeader(frame_control=FrameControl(frame_type=, is_manufacturer_specific=0, direction=, disable_default_response=1, reserved=0, *is_cluster=False, *is_general=True), tsn=116, command_id=1, *direction=)
2023-12-07 19:52:16.637 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:1:0x0000] Decoded ZCL frame: Basic:Read_Attributes_rsp(status_records=[ReadAttributeRecord(attrid=0x0004, status=, value=TypeValue(type=CharacterString, value='LUMI')), ReadAttributeRecord(attrid=0x0005, status=, value=TypeValue(type=CharacterString, value='lumi.switch.l2aeu1'))])
2023-12-07 19:52:16.640 INFO (MainThread) [zigpy.device] [0x0f3a] Read model 'lumi.switch.l2aeu1' and manufacturer 'LUMI' from >
2023-12-07 19:52:16.640 INFO (MainThread) [zigpy.device] [0x0f3a] Discovered basic device information for
2023-12-07 19:52:16.640 DEBUG (MainThread) [zigpy.application] Device is initialized
2023-12-07 19:52:16.641 DEBUG (MainThread) [zigpy.quirks.registry] Checking quirks for LUMI lumi.switch.l2aeu1 (54:ef:44:10:00:90:56:5c)
2023-12-07 19:52:16.641 DEBUG (MainThread) [zigpy.quirks.registry] Considering
2023-12-07 19:52:16.641 DEBUG (MainThread) [zigpy.quirks.registry] Found custom device replacement for 54:ef:44:10:00:90:56:5c:
2023-12-07 19:52:16.644 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 0 class:
2023-12-07 19:52:16.644 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 2 class:
2023-12-07 19:52:16.644 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 3 class:
2023-12-07 19:52:16.644 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 4 class:
2023-12-07 19:52:16.644 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 5 class:
2023-12-07 19:52:16.645 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 6 class:
2023-12-07 19:52:16.645 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 9 class:
2023-12-07 19:52:16.645 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 18 class:
2023-12-07 19:52:16.645 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 1794 class:
2023-12-07 19:52:16.645 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 2820 class:
2023-12-07 19:52:16.645 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 64704 class:
2023-12-07 19:52:16.646 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] Discovering entities for endpoint: 54:ef:44:10:00:90:56:5c-1
2023-12-07 19:52:16.648 DEBUG (Thread-6) [aiosqlite] executing functools.partial(, '\n            INSERT INTO attributes_cache_v12\n            VALUES (:ieee, :endpoint_id, :cluster_id, :attrid, :value, :timestamp)\n                ON CONFLICT (ieee, endpoint_id, cluster, attrid) DO UPDATE\n                SET value=excluded.value, last_updated=excluded.last_updated\n                WHERE\n                    value != excluded.value\n                    OR :timestamp - last_updated > :min_update_delta\n            ', {'ieee': 54:ef:44:10:00:90:56:5c, 'endpoint_id': 1, 'cluster_id': 0, 'attrid': 4, 'value': 'LUMI', 'timestamp':<PHONE_NUMBER>.639729, 'min_update_delta': 30.0})
2023-12-07 19:52:16.652 DEBUG (Thread-6) [aiosqlite] returning exception FOREIGN KEY constraint failed
2023-12-07 19:52:16.655 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'button' component -> 'ZHAIdentifyButton' using ['identify']
2023-12-07 19:52:16.656 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'ElectricalMeasurementApparentPower' using ['electrical_measurement']
2023-12-07 19:52:16.656 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'ElectricalMeasurementRMSCurrent' using ['electrical_measurement']
2023-12-07 19:52:16.656 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'ElectricalMeasurementRMSVoltage' using ['electrical_measurement']
2023-12-07 19:52:16.656 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'ElectricalMeasurementFrequency' using ['electrical_measurement']
2023-12-07 19:52:16.656 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'ElectricalMeasurementPowerFactor' using ['electrical_measurement']
2023-12-07 19:52:16.656 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'DeviceTemperature' using ['device_temperature']
2023-12-07 19:52:16.656 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'RSSISensor' using ['basic']
2023-12-07 19:52:16.657 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'LQISensor' using ['basic']
2023-12-07 19:52:16.657 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'PolledElectricalMeasurement' using ['electrical_measurement']
2023-12-07 19:52:16.657 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'SmartEnergyMetering' using ['smartenergy_metering']
2023-12-07 19:52:16.657 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'SmartEnergySummation' using ['smartenergy_metering']
2023-12-07 19:52:16.665 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'select' component -> 'TuyaPowerOnStateSelectEntity' using ['on_off']
2023-12-07 19:52:16.665 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'select' component -> 'TuyaBacklightModeSelectEntity' using ['on_off']
2023-12-07 19:52:16.666 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'select' component -> 'ZHAStartupOnOffSelectEntity' using ['on_off']
2023-12-07 19:52:16.666 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'switch' component -> 'TuyaChildLockSwitch' using ['on_off']
2023-12-07 19:52:16.666 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 0 class:
2023-12-07 19:52:16.666 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 3 class:
2023-12-07 19:52:16.666 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 4 class:
2023-12-07 19:52:16.666 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 5 class:
2023-12-07 19:52:16.667 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 6 class:
2023-12-07 19:52:16.667 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 18 class:
2023-12-07 19:52:16.667 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 64704 class:
2023-12-07 19:52:16.667 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] Discovering entities for endpoint: 54:ef:44:10:00:90:56:5c-2
2023-12-07 19:52:16.674 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'button' component -> 'ZHAIdentifyButton' using ['identify']
2023-12-07 19:52:16.674 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'RSSISensor' using ['basic']
2023-12-07 19:52:16.674 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'sensor' component -> 'LQISensor' using ['basic']
2023-12-07 19:52:16.682 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'select' component -> 'TuyaPowerOnStateSelectEntity' using ['on_off']
2023-12-07 19:52:16.682 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'select' component -> 'TuyaBacklightModeSelectEntity' using ['on_off']
2023-12-07 19:52:16.683 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'select' component -> 'ZHAStartupOnOffSelectEntity' using ['on_off']
2023-12-07 19:52:16.683 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] 'switch' component -> 'TuyaChildLockSwitch' using ['on_off']
2023-12-07 19:52:16.683 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 12 class:
2023-12-07 19:52:16.683 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] Discovering entities for endpoint: 54:ef:44:10:00:90:56:5c-21
2023-12-07 19:52:16.695 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 12 class:
2023-12-07 19:52:16.696 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] Discovering entities for endpoint: 54:ef:44:10:00:90:56:5c-31
2023-12-07 19:52:16.704 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 18 class:
2023-12-07 19:52:16.705 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] Discovering entities for endpoint: 54:ef:44:10:00:90:56:5c-41
2023-12-07 19:52:16.714 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 18 class:
2023-12-07 19:52:16.714 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] Discovering entities for endpoint: 54:ef:44:10:00:90:56:5c-42
2023-12-07 19:52:16.727 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 18 class:
2023-12-07 19:52:16.728 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] Discovering entities for endpoint: 54:ef:44:10:00:90:56:5c-51
2023-12-07 19:52:16.733 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 18 class:
2023-12-07 19:52:16.734 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] Discovering entities for endpoint: 54:ef:44:10:00:90:56:5c-61
2023-12-07 19:52:16.750 DEBUG (MainThread) [homeassistant.components.zha.core.discovery] Discovering entities for endpoint: 54:ef:44:10:00:90:56:5c-242
2023-12-07 19:52:16.763 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x0F3A:54:ef:44:10:00:90:56:5c entering async_device_initialized - is_new_join: True
2023-12-07 19:52:16.764 DEBUG (MainThread) [homeassistant.components.zha.core.gateway] device - 0x0F3A:54:ef:44:10:00:90:56:5c has joined the ZHA zigbee network
2023-12-07 19:52:16.768 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0x0F3A](lumi.switch.l2aeu1): started configuration
2023-12-07 19:52:16.768 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:ZDO](lumi.switch.l2aeu1): 'async_configure' stage succeeded
2023-12-07 19:52:16.781 DEBUG (MainThread) [zigpy.appdb] Error handling '_save_attribute' event with (54:ef:44:10:00:90:56:5c, 1, 0, 4, 'LUMI', datetime.datetime(2023, 12, 7, 18, 52, 16, 639729, tzinfo=datetime.timezone.utc)) params: FOREIGN KEY constraint failed
2023-12-07 19:52:16.782 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0b04]: Performing cluster binding
2023-12-07 19:52:16.783 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0b04]: bound 'electrical_measurement' cluster: Status.SUCCESS
2023-12-07 19:52:16.783 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0b04]: Configuring cluster attribute reporting
2023-12-07 19:52:16.784 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0b04]: Successfully configured reporting for '{'active_power': (5, 900, 1), 'active_power_max': (30, 900, 1), 'apparent_power': (5, 900, 1)}' on 'electrical_measurement' cluster: [ConfigureReportingResponseRecord(status=)]
2023-12-07 19:52:16.786 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0b04]: Successfully configured reporting for '{'rms_current': (5, 900, 1), 'rms_current_max': (30, 900, 1), 'rms_voltage': (5, 900, 1)}' on 'electrical_measurement' cluster: [ConfigureReportingResponseRecord(status=)]
2023-12-07 19:52:16.787 DEBUG (Thread-6) [aiosqlite] executing functools.partial(, '\n            INSERT INTO attributes_cache_v12\n            VALUES (:ieee, :endpoint_id, :cluster_id, :attrid, :value, :timestamp)\n                ON CONFLICT (ieee, endpoint_id, cluster, attrid) DO UPDATE\n                SET value=excluded.value, last_updated=excluded.last_updated\n                WHERE\n                    value != excluded.value\n                    OR :timestamp - last_updated > :min_update_delta\n            ', {'ieee': 54:ef:44:10:00:90:56:5c, 'endpoint_id': 1, 'cluster_id': 0, 'attrid': 5, 'value': 'lumi.switch.l2aeu1', 'timestamp':<PHONE_NUMBER>.639847, 'min_update_delta': 30.0})
2023-12-07 19:52:16.788 DEBUG (Thread-6) [aiosqlite] returning exception FOREIGN KEY constraint failed
2023-12-07 19:52:16.790 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0b04]: Successfully configured reporting for '{'rms_voltage_max': (30, 900, 1), 'ac_frequency': (5, 900, 1), 'ac_frequency_max': (30, 900, 1)}' on 'electrical_measurement' cluster: [ConfigureReportingResponseRecord(status=)]
2023-12-07 19:52:16.791 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0b04]: finished cluster handler configuration
2023-12-07 19:52:16.792 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0003]: Configuring cluster attribute reporting
2023-12-07 19:52:16.792 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0003]: finished cluster handler configuration
2023-12-07 19:52:16.793 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0002]: Performing cluster binding
2023-12-07 19:52:16.793 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0002]: bound 'device_temperature' cluster: Status.SUCCESS
2023-12-07 19:52:16.793 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0002]: Configuring cluster attribute reporting
2023-12-07 19:52:16.794 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0002]: Successfully configured reporting for '{'current_temperature': (30, 900, 50)}' on 'device_temperature' cluster: [ConfigureReportingResponseRecord(status=)]
2023-12-07 19:52:16.794 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0002]: finished cluster handler configuration
2023-12-07 19:52:16.794 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0000]: Configuring cluster attribute reporting
2023-12-07 19:52:16.794 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0000]: finished cluster handler configuration
2023-12-07 19:52:16.795 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0702]: Performing cluster binding
2023-12-07 19:52:16.795 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0702]: bound 'smartenergy_metering' cluster: Status.SUCCESS
2023-12-07 19:52:16.798 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0702]: Configuring cluster attribute reporting
2023-12-07 19:52:16.799 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0702]: Successfully configured reporting for '{'instantaneous_demand': (5, 900, 1), 'current_summ_delivered': (30, 900, 1), 'current_tier1_summ_delivered': (30, 900, 1)}' on 'smartenergy_metering' cluster: [ConfigureReportingResponseRecord(status=)]
2023-12-07 19:52:18.043 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'16feb1a90d2a2fbd05c2da25ba117d1d14f026bc3f6e9f7e'
2023-12-07 19:52:18.043 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'82503a7e'
2023-12-07 19:52:18.096 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'26feb1a9112a15b658924a27ab5593499c555b10d7c19874f3de9083fc7e2fa71ecdfd6f7000c5df98fc7e'
2023-12-07 19:52:18.096 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'83401b7e'
2023-12-07 19:52:18.098 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0702]: Successfully configured reporting for '{'current_tier2_summ_delivered': (30, 900, 1), 'current_tier3_summ_delivered': (30, 900, 1), 'current_tier4_summ_delivered': (30, 900, 1)}' on 'smartenergy_metering' cluster: [ConfigureReportingResponseRecord(status=)]
2023-12-07 19:52:18.099 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0702]: Successfully configured reporting for '{'current_tier5_summ_delivered': (30, 900, 1), 'current_tier6_summ_delivered': (30, 900, 1), 'status': (1, 900, 1)}' on 'smartenergy_metering' cluster: [ConfigureReportingResponseRecord(status=)]
2023-12-07 19:52:18.100 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0702]: finished cluster handler configuration
2023-12-07 19:52:18.101 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0xfcc0]: Performing cluster binding
2023-12-07 19:52:18.102 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'1efeb1a90d2a2fbd05c2da25ba117d1d14f026bc3fa1e97e'
2023-12-07 19:52:18.102 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'82503a7e'
2023-12-07 19:52:18.105 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'2efeb1a9112a15b658924a27ab5593499c555b10d7c19874f3de9083fc7e2fa71ecdfd6f7000c5df9d3b7e'
2023-12-07 19:52:18.105 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'83401b7e'
2023-12-07 19:52:18.102 DEBUG (MainThread) [zigpy.device] [0x0f3a] Extending timeout for 0x7d request
2023-12-07 19:52:18.106 DEBUG (MainThread) [bellows.zigbee.application] Sending packet ZigbeePacket(timestamp=datetime.datetime(2023, 12, 7, 18, 52, 18, 106302, tzinfo=datetime.timezone.utc), src=AddrModeAddress(addr_mode=, address=0x0000), src_ep=0, dst=AddrModeAddress(addr_mode=, address=0x0F3A), dst_ep=0, source_route=None, extended_timeout=True, tsn=125, profile_id=0, cluster_id=, data=Serialized[b'}\\V\x90\x00\x10D\xefT\x01\xc0\xfc\x03\xb1\xc9"\xfe\xffn\x02\xbc\x01'], tx_options=, radius=0, non_member_radius=0, lqi=None, rssi=None)
2023-12-07 19:52:18.107 DEBUG (MainThread) [bellows.ezsp.protocol] Send command setExtendedTimeout: (54:ef:44:10:00:90:56:5c, True)
2023-12-07 19:52:18.108 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0006]: Performing cluster binding
2023-12-07 19:52:18.110 DEBUG (MainThread) [zigpy.device] [0x0f3a] Extending timeout for 0x7f request
2023-12-07 19:52:18.110 DEBUG (MainThread) [bellows.zigbee.application] Sending packet ZigbeePacket(timestamp=datetime.datetime(2023, 12, 7, 18, 52, 18, 110545, tzinfo=datetime.timezone.utc), src=AddrModeAddress(addr_mode=, address=0x0000), src_ep=0, dst=AddrModeAddress(addr_mode=, address=0x0F3A), dst_ep=0, source_route=None, extended_timeout=True, tsn=127, profile_id=0, cluster_id=, data=Serialized[b'\x7f\\V\x90\x00\x10D\xefT\x01\x06\x00\x03\xb1\xc9"\xfe\xffn\x02\xbc\x01'], tx_options=, radius=0, non_member_radius=0, lqi=None, rssi=None)
2023-12-07 19:52:18.111 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:1:0x0019]: finished cluster handler configuration
2023-12-07 19:52:18.111 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:2:0x0000]: Configuring cluster attribute reporting
2023-12-07 19:52:18.112 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:2:0x0000]: finished cluster handler configuration
2023-12-07 19:52:18.112 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:2:0x0003]: Configuring cluster attribute reporting
2023-12-07 19:52:18.112 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:2:0x0003]: finished cluster handler configuration
2023-12-07 19:52:18.112 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:2:0xfcc0]: Performing cluster binding
2023-12-07 19:52:18.113 DEBUG (MainThread) [zigpy.device] [0x0f3a] Extending timeout for 0x81 request
2023-12-07 19:52:18.115 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'63ff21a92a2a49e4c9945a614501936af27e'
2023-12-07 19:52:18.113 DEBUG (MainThread) [bellows.zigbee.application] Sending packet ZigbeePacket(timestamp=datetime.datetime(2023, 12, 7, 18, 52, 18, 113556, tzinfo=datetime.timezone.utc), src=AddrModeAddress(addr_mode=, address=0x0000), src_ep=0, dst=AddrModeAddress(addr_mode=, address=0x0F3A), dst_ep=0, source_route=None, extended_timeout=True, tsn=129, profile_id=0, cluster_id=, data=Serialized[b'\x81\\V\x90\x00\x10D\xefT\x02\xc0\xfc\x03\xb1\xc9"\xfe\xffn\x02\xbc\x01'], tx_options=, radius=0, non_member_radius=0, lqi=None, rssi=None)
2023-12-07 19:52:18.116 DEBUG (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x0F3A:2:0x0006]: Performing cluster binding
2023-12-07 19:52:18.117 DEBUG (MainThread) [zigpy.device] [0x0f3a] Extending timeout for 0x83 request
2023-12-07 19:52:18.117 DEBUG (MainThread) [bellows.zigbee.application] Sending packet ZigbeePacket(timestamp=datetime.datetime(2023, 12, 7, 18, 52, 18, 117850, tzinfo=datetime.timezone.utc), src=AddrModeAddress(addr_mode=, address=0x0000), src_ep=0, dst=AddrModeAddress(addr_mode=, address=0x0F3A), dst_ep=0, source_route=None, extended_timeout=True, tsn=131, profile_id=0, cluster_id=, data=Serialized[b'\x83\\V\x90\x00\x10D\xefT\x02\x06\x00\x03\xb1\xc9"\xfe\xffn\x02\xbc\x01'], tx_options=, radius=0, non_member_radius=0, lqi=None, rssi=None)
2023-12-07 19:52:18.119 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received incomingRouteRecordHandler: [0x0f3a, 54:ef:44:10:00:90:56:5c, 136, -66, [0xd217]]
2023-12-07 19:52:18.119 DEBUG (MainThread) [bellows.zigbee.application] Received incomingRouteRecordHandler frame with [0x0f3a, 54:ef:44:10:00:90:56:5c, 136, -66, [0xd217]]
2023-12-07 19:52:18.119 DEBUG (MainThread) [bellows.zigbee.application] Processing route record request: (0x0f3a, 54:ef:44:10:00:90:56:5c, 136, -66, [0xd217])
2023-12-07 19:52:18.120 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received incomingMessageHandler: [, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=2, destinationEndpoint=1, options=, groupId=0, sequence=27), 124, -69, 0x0f3a, 255, 255, b'\x18\xf3\n\x00\x00\x10\x00\xf5\x00#\x00\xff\xff\x02']
2023-12-07 19:52:18.120 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=2, destinationEndpoint=1, options=, groupId=0, sequence=27), 124, -69, 0x0f3a, 255, 255, b'\x18\xf3\n\x00\x00\x10\x00\xf5\x00#\x00\xff\xff\x02']
2023-12-07 19:52:18.120 DEBUG (MainThread) [zigpy.application] Received a packet: ZigbeePacket(timestamp=datetime.datetime(2023, 12, 7, 18, 52, 18, 120847, tzinfo=datetime.timezone.utc), src=AddrModeAddress(addr_mode=, address=0x0F3A), src_ep=2, dst=AddrModeAddress(addr_mode=, address=0x0000), dst_ep=1, source_route=None, extended_timeout=False, tsn=27, profile_id=260, cluster_id=6, data=Serialized[b'\x18\xf3\n\x00\x00\x10\x00\xf5\x00#\x00\xff\xff\x02'], tx_options=, radius=0, non_member_radius=0, lqi=124, rssi=-69)
2023-12-07 19:52:18.121 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:2:0x0006] Received ZCL frame: b'\x18\xf3\n\x00\x00\x10\x00\xf5\x00#\x00\xff\xff\x02'
2023-12-07 19:52:18.122 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:2:0x0006] Decoded ZCL frame header: ZCLHeader(frame_control=FrameControl(frame_type=, is_manufacturer_specific=0, direction=, disable_default_response=1, reserved=0, *is_cluster=False, *is_general=True), tsn=243, command_id=10, *direction=)
2023-12-07 19:52:18.124 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:2:0x0006] Decoded ZCL frame: OnOffCluster:Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=)), Attribute(attrid=0x00F5, value=TypeValue(type=uint32_t, value=50331392))])
2023-12-07 19:52:18.125 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:2:0x0006] Received command 0x0A (TSN 243): Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=)), Attribute(attrid=0x00F5, value=TypeValue(type=uint32_t, value=50331392))])
2023-12-07 19:52:18.125 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:2:0x0006] Attribute report received: on_off=, 0x00F5=50331392
2023-12-07 19:52:18.126 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received incomingRouteRecordHandler: [0x0f3a, 54:ef:44:10:00:90:56:5c, 136, -66, [0xd217]]
2023-12-07 19:52:18.126 DEBUG (MainThread) [bellows.zigbee.application] Received incomingRouteRecordHandler frame with [0x0f3a, 54:ef:44:10:00:90:56:5c, 136, -66, [0xd217]]
2023-12-07 19:52:18.126 DEBUG (MainThread) [bellows.zigbee.application] Processing route record request: (0x0f3a, 54:ef:44:10:00:90:56:5c, 136, -66, [0xd217])
2023-12-07 19:52:18.127 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received incomingMessageHandler: [, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=2, destinationEndpoint=1, options=, groupId=0, sequence=27), 124, -69, 0x0f3a, 255, 255, b'\x18\xf3\n\x00\x00\x10\x00\xf5\x00#\x00\xff\xff\x02']
2023-12-07 19:52:18.127 DEBUG (MainThread) [bellows.zigbee.application] Received incomingMessageHandler frame with [, EmberApsFrame(profileId=260, clusterId=6, sourceEndpoint=2, destinationEndpoint=1, options=, groupId=0, sequence=27), 124, -69, 0x0f3a, 255, 255, b'\x18\xf3\n\x00\x00\x10\x00\xf5\x00#\x00\xff\xff\x02']
2023-12-07 19:52:18.128 DEBUG (MainThread) [zigpy.application] Received a packet: ZigbeePacket(timestamp=datetime.datetime(2023, 12, 7, 18, 52, 18, 128427, tzinfo=datetime.timezone.utc), src=AddrModeAddress(addr_mode=, address=0x0F3A), src_ep=2, dst=AddrModeAddress(addr_mode=, address=0x0000), dst_ep=1, source_route=None, extended_timeout=False, tsn=27, profile_id=260, cluster_id=6, data=Serialized[b'\x18\xf3\n\x00\x00\x10\x00\xf5\x00#\x00\xff\xff\x02'], tx_options=, radius=0, non_member_radius=0, lqi=124, rssi=-69)
2023-12-07 19:52:18.129 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:2:0x0006] Received ZCL frame: b'\x18\xf3\n\x00\x00\x10\x00\xf5\x00#\x00\xff\xff\x02'
2023-12-07 19:52:18.130 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:2:0x0006] Decoded ZCL frame header: ZCLHeader(frame_control=FrameControl(frame_type=, is_manufacturer_specific=0, direction=, disable_default_response=1, reserved=0, *is_cluster=False, *is_general=True), tsn=243, command_id=10, *direction=)
2023-12-07 19:52:18.131 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:2:0x0006] Decoded ZCL frame: OnOffCluster:Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=)), Attribute(attrid=0x00F5, value=TypeValue(type=uint32_t, value=50331392))])
2023-12-07 19:52:18.132 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:2:0x0006] Received command 0x0A (TSN 243): Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=Bool, value=)), Attribute(attrid=0x00F5, value=TypeValue(type=uint32_t, value=50331392))])
2023-12-07 19:52:18.133 DEBUG (MainThread) [zigpy.zcl] [0x0F3A:2:0x0006] Attribute report received: on_off=, 0x00F5=50331392
2023-12-07 19:52:18.134 DEBUG (bellows.thread_0) [bellows.uart] Data frame: b'37ffa1a92a2a60b87e'
2023-12-07 19:52:18.134 DEBUG (bellows.thread_0) [bellows.uart] Sending: b'8430fc7e'
2023-12-07 19:52:18.146 DEBUG (MainThread) [zigpy.appdb] Error handling '_save_attribute' event with (54:ef:44:10:00:90:56:5c, 1, 0, 5, 'lumi.switch.l2aeu1', datetime.datetime(2023, 12, 7, 18, 52, 16, 639847, tzinfo=datetime.timezone.utc)) params: FOREIGN KEY constraint failed
2023-12-07 19:52:18.146 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received setExtendedTimeout: []
```
If you need any more (or different) logs, please let me know. Happy to provide them.

Custom quirk
Not yet available
Additional information
I hope you can help me out figuring out how we can add these functionalities. I am willing to help create/improve the quirk, although I have been unsuccessful thus far.
Thank you very much in advance for your help.

Did you check the "Manage Zigbee device" -> "clusters" dialog? (Three dots on the device page)

Unfortunately you are not able at the moment to change this through the UI

You can change it on that page. Change the upper "value" field to 0 or 1 for example. Leave the lower text field empty. Then, press "write attribute". Afterwards, you can press "read attribute" to see if it correctly wrote that value.
But yes, ZHA config entities should be added for these custom attributes.

Change the upper "value" field to 0 or 1 for example.
Thank you very much for this tip. I tried entering OppleOperationMode.Coupled or OppleOperationMode.Decoupled and then pressing "write attribute", but that didn't work. Using 0 and 1 did the trick!

But yes, ZHA config entities should be added for these custom attributes. (just not implemented yet)
If that's something I could help with, please let me know. Happy to help and contribute to this, just not sure where to start to achieve this at the moment.

Just a quick related question, is the l1aeu1 also supposed to support the same features as the l2aeu1? In HA I only see the changes for my l2aeu1 device, and my l1aeu1 devices have not changed.

FYI, there is an indirectly inconsistency issue where the Aqara Wall Switch single and double rocker have different device type:
https://github.com/zigpy/zha-device-handlers/discussions/1957
There also seems to be a related bug that prevents users modifying the device type in ZHA without using a custom quirk:
https://github.com/home-assistant/core/issues/101093

This is not solved just yet, still looking for now to see "on power on, use last state" anyone done this?

This is not solved just yet, still looking for now to see "on power on, use last state" anyone done this?

I'm having the same issue. Which cluster can I use to toggle power off memory status?

Change the upper "value" field to 0 or 1 for example.

Thank you very much for this tip. I tried entering OppleOperationMode.Coupled or OppleOperationMode.Decoupled and then pressing "write attribute", but that didn't work. Using 0 and 1 did the trick!

But yes, ZHA config entities should be added for these custom attributes. (just not implemented yet)

If that's something I could help with, please let me know. Happy to help and contribute to this, just not sure where to start to achieve this at the moment.

I have been testing the double rocker no neutral version about the decoupled mode as that was a deal breaker for my use case
Did you find any way to set the switch to be on (rather than off) by default?

Hi @joker11940,
Didn't see your reply in my notifications. The way I temporarily 'fixed' it for now is to check on a button press (which throws an event in Home Assistant) if the switch is set to off. If that's the case, it will turn on the switch. This way it makes sure that even after a power outage, the switch gets turned on even though the switch is in decoupled mode.
Hope this helps you out temporarily at least.

I have been testing the double rocker no neutral version about the decoupled mode as that was a deal breaker for my use case
Did you find any way to set the switch to be on (rather than off) by default?

Hi @joker11940,
Didn't see your reply in my notifications. The way I temporarily 'fixed' it for now is to check on a button press (which throws an event in Home Assistant) if the switch is set to off. If that's the case, it will turn on the switch. This way it makes sure that even after a power outage, the switch gets turned on even though the switch is in decoupled mode. Hope this helps you out temporarily at least.

Oh that's not a bad work around, I may use that for some other switches. My main issue going this route is its powering smart bulbs that are Zigbee routers, when they go off the longer they are off the worse my network gets 😅
I do think I have found something that kind of does what I need and that is changing the following option to True.
My understanding is it will remember that it was on and turn turn back on. Any ideas if I am right? Not had a power cut yet 😅


conform to XDG base dir spec on linux

Proposed Changes
Conform to the XDG base dir spec on linux to not spam the users home directory.
This change is backwards compatible and still uses the old directory if it exists.
It also asks the user on startup if they want to migrate to the new directory.
Testing
Ran tests and the advanced flow on an Android AVD.

Hi @NyCodeGHG, I'll take a look at this next week

@NyCodeGHG could you provide some more context on what "spamming the users home directory" means?

@axelniklasson
If i look in my home directory, there are a lot of directories starting with a dot. (currently 56)
That's really annoying and a lot of clutter.
Thats why the XDG Basedir Spec exists.
It's comparable to the similar guidelines which exist for macOS and Windows as well.
This spec gives guidelines where applications should store their data.

@axelniklasson If i look in my home directory, there are a lot of directories starting with a dot. (currently 56) That's really annoying and a lot of clutter. Thats why the XDG Basedir Spec exists. It's comparable to the similar guidelines which exist for macOS and Windows as well. This spec gives guidelines where applications should store their data.

@NyCodeGHG  Are there multiple .maestro directories created by accident or are there one .maestro and 55 other directories that start with a dot?

@axelniklasson one .maestro and 55 other directories created by other applications. It wouldn't really be a problem for me if only maestro would do that, but way too many applications just dump their data in the home directory where it doesn't really belong.
If the migration thing is too complicated I would also suggest that we could leave the migration thing out and only use the new directory if the old one doesn't exist, which would probably be much simpler to maintain.

@NyCodeGHG Thanks for the context. While I see that this is a bit annoying for you and I appreciate that you took the time to create a PR, we won't be merging this PR. Thanks for your time and willingness to contribute to maestro!


Questions about Channel-wise Separable Convolutions

Hi! Thanks for the great work!
I have a question related to the Channel-wise Separable Convolutions part in the RNL module.
In your paper, you mention that Fθ should not fuse together information across channels.
But in your code, the parameter of groups in DepthwiseConv3d is not equal to the in_channels, it is "groups = max(in_channels // 32, 1)".
Are there any specific reasons for you to choose this group?
Thank you!

Hi,
Thank you for interesting my work.
For the implementation of Fθ, I did use channel-wise(depth-wise) convolution, which mean the numbe of groups is equal to the channel number. However, in Pytorch,  setting the groups parameter as  the channel number for a Conv would cuase low efficency. I guess  Pytorch1.3 implemented it with a loop operation. So I code the DepthwiseConv3d myself by setting masks for some channels.
I have tested that in Pytorch-1.6 or higher versions, they have make the Convolution with multiple goups more efficient.  But considering that the trained models still use  Pytorch1.3, so I did not change it.

Hi,
Thanks for the reply!
It solved all my problems.

Hi,
Thanks for the reply!
It solved all my problems.


Build on ARM64 for Bashupport Pro

I'm sorry, this PR should've been opened on my fork. This is wip to make a arm64 build, but I'm not sure if I'll succeed.


Decorator for nonblocking sample methods

This decorator is intended to make it easier to construct non-blocking composites, (e.g. would have simplified #555,  #677).
This approach might be convenient for expert users, but I am worried that it obfuscates the implementation in a confusing way.

Codecov Report

Merging #684 into master will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #684      +/-   ##
==========================================
+ Coverage   91.70%   91.72%   +0.01%
==========================================
  Files          60       60
  Lines        4146     4156      +10
==========================================
+ Hits         3802     3812      +10
  Misses        344      344

Impacted Files
Coverage Δ

dimod/decorators.py
64.93% <100.00%> (+1.92%)
:arrow_up:

dimod/reference/composites/scalecomposite.py
97.14% <100.00%> (+0.17%)
:arrow_up:

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 d697266...5331e4d. Read the comment docs.


[Bug report] Problem when shrinking the image with gestures and rotate

Version
7.0.2
Platforms
iOS
Device Model
iPhone 13
flutter info
[✓] Flutter (Channel stable, 3.7.10, on macOS 13.2 22D49 darwin-arm64, locale it-IT)
    • Flutter version 3.7.10 on channel stable at /Users/carlosacchetti/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4b12645012 (7 days ago), 2023-04-03 17:46:48 -0700
    • Engine revision ec975089ac
    • Dart version 2.19.6
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/carlosacchetti/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] VS Code (version 1.77.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.62.0

[✓] Connected device (5 available)
    • SM G780G (mobile)     • RF8T30H0K2Y               • android-arm64  • Android 13 (API 33)
    • iPhone CS (mobile)    • 00008110-000A5CD42682801E • ios            • iOS 16.4 20E247
    • iPhone di CS (mobile) • 00008101-0015458A3488001E • ios            • iOS 14.7.1 18G82
    • macOS (desktop)       • macos                     • darwin-arm64   • macOS 13.2 22D49 darwin-arm64
    • Chrome (web)          • chrome                    • web-javascript • Google Chrome 112.0.5615.49

[✓] HTTP Host Availability
    • All required HTTP hosts are available

How to reproduce?
If I try to shrink the image with gestures (it does not matter if I put a minimum size of 1.0 or less) if I then rotate the phone the position is wrong.
Logs
There are no log errors. Simply the position of the image is wrong

Example code (optional)
No response
Contact
<EMAIL_ADDRESS>

the same issue with me

not support this case 'rotate the phone'


Artist Series Rail QA Fixes + Center Collection Header Titles

Visual QA Fixes from Artist Series:

Renders a default image in the artwork grids on Artist Series rails when collections have only 1-2 artworks
Centers collection header title text

Before:

After:

Before:

After:

Before:

After:

Before:

After:

https://artsyproduct.atlassian.net/browse/FX-1929
https://artsyproduct.atlassian.net/browse/FX-1928

After resolving the merge conflict this should be good to go!


[devops:bot] update deps in nix/sources.json (from: rhino-core@96a887a

update nix refernces for rhino-core and|or nixpkgs to match https://github.com/rhinofi/rhino-core/blob/96a887a994883a5582e36baebbf18c726f261eb3/nix/sources.json (branch: dev)

superseded by #86


Unable to load example grammar file

Trying to parse the example test/resources/ipv4.abnf provided with the repository, I get this result.
iex(1)> grammar = ABNF.load_file "ipv4.abnf"
** (throw) {:incomplete_parsing, 'IPv4address =\n  dec-octet "."\n  dec-octet "."\n  dec-octet "."\n  dec-octet !!!\n    state = Map.put state, :ipv4address, rule\n    {:ok, state, "Your ip address is: \#{rule}"}\n  !!!\n\ndec-octet = DIGIT         ; 0-9\n  / %x31-39 DIGIT         ; 10-99\n  / "1" 2DIGIT            ; 100-199\n  / "2" %x30-34 DIGIT     ; 200-249\n  / "25" %x30-35          ; 250-255\n\nDIGIT = %x30-39\n'}
    lib/ex_abnf.ex:41: ABNF.load/1

Unit tests run successfully.
Version info (running on OS X Mavericks 10.11.2):
> elixir -v
Erlang/OTP 18 [erts-7.2.1] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false] [dtrace]

Elixir 1.2.0

It seems as though the examples all use DOS line endings (CLRF). If you use unix line endings, the parser fails.

Hello!
It is correct that DOS line endings are required in the abnf files since 0.2 (as the README states). The change was made to make it compatible with how the RFC defines the rules:

A rule is defined by the following sequence:
name =  elements crlf
where  is the name of the rule,  is one or more rule
names or terminal specifications, and

However, this does work for me:
$ iex -S mix
Erlang/OTP 18 [erts-7.0] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false]

Interactive Elixir (1.1.1) - press Ctrl+C to exit (type h() ENTER for help)
iex(1)> grammar = ABNF.load_file "test/resources/ipv4.abnf"

I'm using elixir 1.1.1 currently. Will try 1.2.0 and let you know.

Interactive Elixir (1.2.0) - press Ctrl+C to exit (type h() ENTER for help)

iex(1)> grammar = ABNF.load_file "test/resources/ipv4.abnf"

iex(2)> ABNF.apply grammar, "ipv4address", '<IP_ADDRESS>', %{}
%ABNF.CaptureResult{input: '<IP_ADDRESS>', rest: [],
 state: %{ipv4address: '<IP_ADDRESS>'}, string_text: '<IP_ADDRESS>',
 string_tokens: ['192', '.', '168', '.', '0', '.', '10'],
 values: ["Your ip address is: <IP_ADDRESS>"]}

So I confirm it works with 1.2.0 too.
Could you try specifying the complete path to the ipv4.abnf file? Perhaps it's taking an outdated ipv4 file as input?


Mention --default-label-scoping-rules CLI option

Mention the --default-label-scoping-rules=false CLI option, add a FAQ section about kapp's labels, and cross-link the docs in the apply section with the configuration.
I found kapp's use of labels rather than annotations quite confusing and frustrating when I hit this bug that breaks kube-prometheus's service label selector.
May require merge with https://github.com/carvel-dev/carvel/pull/773

Thank you for making the docs better @ringerc!
Do you also want to make the change in older versions of kapp? Or at least the latest version along with develop.

Yes, I can backport to latest stable. Will update.


Kapacitor alert passing through message with Go structs when no value for template

@desa Can you take a look at this one?

yup

Looks like it's coming from here alert.go#L1075-L1100
What should the expected behavior be? To some degree I think the current behavior is acceptable.


NoSuchMethod Error

Getting this when running the jar through console to get it to run. For some reason running the .exe has no effect. It just makes a log file and does nothing else.

C:\Users\doomm\Downloads>java -jar mppatch-0.1.3.jar
================================================================================
MPPatch version 0.1.3
Revision 8adb8b73, built on May 8, 2021 by jenkins@himawari
Build ID   : 3e5748f5-a000-46d0-87d3-cd86ca811320
Build Date : 2021-05-08T12:40:07Z
Revision   : 8adb8b735e884f26ae8e750339bbf213f8b556a4
Tree Status:
[2022-11-10T02:55:11Z/ INFO] Changing patch package...
Exception in thread "main" java.lang.NoSuchMethodError: Non-existent method WindowsRegOpenKey in java.util.prefs.WindowsPreferences was accessed.
at moe.lymia.mppatch.util.win32.DynamicReflectiveProxy.applyDynamic(DynamicReflectiveProxy.scala:100)
at moe.lymia.mppatch.util.win32.WindowsRegistry$.moe$lymia$mppatch$util$win32$WindowsRegistry$$withKey(WindowsRegistry.scala:37)
at moe.lymia.mppatch.util.win32.WindowsRegistry$RegistryStringKey$.readKey(WindowsRegistry.scala:53)
at moe.lymia.mppatch.util.win32.WindowsRegistry$Hive.readKey(WindowsRegistry.scala:72)
at moe.lymia.mppatch.util.win32.WindowsRegistry$Hive.apply(WindowsRegistry.scala:73)
at moe.lymia.mppatch.core.Win32Platform$.defaultSystemPaths(platform.scala:75)
at moe.lymia.mppatch.ui.MainFrame.pathFromRegistry(MainFrame.scala:91)
at moe.lymia.mppatch.ui.MainFrame.(MainFrame.scala:102)
at moe.lymia.mppatch.ui.InstallerMain.main(Installer.scala:77)
at moe.lymia.mppatch.ui.Installer$.main(Installer.scala:89)
at moe.lymia.mppatch.ui.Installer.main(Installer.scala)

Erk... This is definitely a case of my poor past design choices coming back to bite me. I don't currently have the time to work on this, but I'll try to get a new version out sometime within a week or two. For now, try using Java 8.

Erk... This is definitely a case of my poor past design choices coming back to bite me. I don't currently have the time to work on this, but I'll try to get a new version out sometime within a week or two. For now, try using Java 8.

Running it via the Java 8 JRE worked good and patch installed, I was previously using 17.0.4
.exe version still never worked for me though. Currently running Windows 10 Pro version 21H2

It appears that these issues stem from the same problem:
https://github.com/Lymia/MPPatch/issues/66
https://github.com/Lymia/MPPatch/issues/69
Should the system have a Java SDK installed (as well as JRE 8) then app would run under newer SDK java by default and encounter these issues, silently crashing.
The WindowsRegOpenKey method no longer accepts the parameters (int, byte[], int), but (long, byte[], int), amongst other issues.
The fix is to modify project/launch4j.xml and add "1.8.1" (This will have EXE run at 1.8.0 rather than 17.0 or what not).
When running the Jar directly just mandate JRE 8 I suppose, otherwise have to fix several other bugs.

Er, unfortunately the MPPatch that I build makes Civ5 crash on launch, even though the only local change has been to fix the EXE failing to launch due to conflicting java. (Compiling with no changes, same issue).


[CSM-320] Regenerate genesis

Why is it needed btw?

@gromakovsky AFAIK, current master fails to start in prod mode

cardano-node: Failed to read genesis: Attempted to read too many bytes for StaticSize 28 Data.ByteString.ByteString. Needed 28, but only 22 remain.
GenesisCoreData
CallStack (from HasCallStack):
  error, called at src/Debug.hs:43:11 in universum-0.4.3-CkMiNAiq0KBB5vO0r3nIZM:Debug

Okay, indeed.

It works!


backport 1.0.x - Update to security role in response to openssl

http://www.ubuntu.com/usn/usn-2537-1/
Conflicts:
roles/security_errata/handlers/main.yml

:+1:

This apparently needs a rebase?

dead branch.


README.md: provide link for References

If suitable, provide a link pointing to URL of sources mentioned in References.

Good idea, I've added the remaining ones in 205f7d3d5e7d77977b42b0e82cd8cd9c7af8b5cd.
Best, Alex


Add support for zone-level Access routes

Description
Provides support for zone-level Access endpoints. The Access team reverted its decision to deprecate zone based routes because of users needing zone-scoped access tokens. Zone based routes have also been added back to the documentation: https://api.cloudflare.com/.
Related issue: https://github.com/cloudflare/terraform-provider-cloudflare/issues/812.
Has your change been tested?
Tests were included for every added request.
Types of changes
What sort of change does your code introduce/modify?

[X] New feature (non-breaking change which adds functionality)

Cheers @Justin-Holmes; thinking about this some more (for here and upstream), do we want to keep both account and zone ones around? Is there is a use case where you'd use one over the other?

🙇♂ appreciate the info! I'll be sure to keep it in mind for the Terraform work.


Can't load Notification attachment picture after adding a second Frigate Integration

Version of the custom_component

Frigate custom component version 2.2.2
Configuration
Frigate Server 1 Configuration:
frigateCL1 configuration.txt
Frigate Server 2 Configuration:
frigateCL2 configuration.txt
Frigate Integration Card:

Current automation YAML to send notification and image to my phone:
alias: Notify me Person in Camera
description: ''
trigger:
  - platform: mqtt
    topic: frigateCL2/events
condition:
  - condition: state
    entity_id: timer.notification_timer
    state: idle
  - condition: template
    value_template: '{{ trigger.payload_json[''after''][''label''] == ''person'' }}'
  - condition: template
    value_template: '{{ ''frontyard'' in trigger.payload_json[''after''][''entered_zones''] }}'
action:
  - service: notify.mobile_app_mine
    data_template:
      message: A {{trigger.payload_json["after"]["label"]}} was detected.
      data:
        image: >-
          https://***********.com/api/frigate/notifications/{{trigger.payload_json["after"]["id"]}}/thumbnail.jpg
        tag: '{{trigger.payload_json["after"]["id"]}}'
        when: '{{trigger.payload_json["after"]["start_time"]|int}}'
  - service: timer.start
    data:
      duration: '0'
    target:
      entity_id: timer.notification_timer
mode: single

Describe the bug
When I add a second integration to Home Assistant for the second Frigate server (doing nothing else), the notification that are send to my phone stop working correctly. I still get the notification but not the image any longer. The images, notifications, and automation are from the original integration. Instead of an image, I get:
Failed to load Attachment
Response Status code was unacceptable:
400.
See screenshot below from my phone.

Any suggestions on what else to try?
Debug log

2022-03-26 13:45:51 INFO (MainThread) [custom_components.frigate]
-------------------------------------------------------------------
Frigate
Integration Version: 2.2.2
This is a custom integration!
 Try this:
  image: >-
          https://***********.com/api/frigate/frigateCL2/notifications/{{trigger.payload_json["after"]["id"]}}/thumbnail.jpg

Note the new '/frigateCL2/in the URL (this is the MQTTclient_id` from your 2nd configuration file).

Thank you Sir, you are amazing. That solved my issue.


Feature/add eum

The only strange thing to me is that it receives the utility = np.dot as a parameter. I can not think of a use case where someone will pass a weight list, but not use np.dot.

The only strange thing to me is that it receives the utility = np.dot as a parameter. I can not think of a use case where someone will pass a weight list, but not use np.dot.

In the case the user's utility follows a non linear setting.


Implement default quotas

Author Name: Carlos Martín (Carlos Martín)
Original Redmine Issue: 1870, https://dev.opennebula.org/issues/1870
Original Date: 2013-04-08

Default quotas for users or groups cannot be viewed or edited

Already done


update purescript release version

Updates PureScript to the latest release
@shinnn @garyb

Coverage remained the same at 100.0% when pulling a1298de192729c0755fe61f0da560ff7ed288066 on seanstrom:support/update-purescript-version into dffa6b1c9c8673b0b8d332acc30264fae44a12a4 on purescript-contrib:master.

I'm always -1 on semver-invalid versioning of purescript.
@paf31 Why not 0.6.10?

Once we release the next version (0.7) we're going to try to do something more principled with the versions as it's pretty arbitrary right now.

Released as 0.6.10. Thanks, @seanstrom.


Added social media icons

Fixes #782
Note that if we obtain a different Facebook username, the URL will have to be changed
Describe the changes you have made in this pr -
Added Facebook and Twitter icons
Screenshots of the changes (If any) -

Coverage remained the same at 83.264% when pulling ee5c3b6088407aa9d08a7f72d3a0323f73ed6fb8 on JoshHeng:add-social-media-icons into f46375d11e0ce81e8543127338053180c48298c2 on CircuitVerse:master.

Could you post screenshot of a mobile screen as well. Thanks.

A little padding on both sides vertically would make it better.

@nitin10s Vertical padding would make the top bar bigger vertically on a wider screen or shrink the social icons.
Media queries would be possible but would get messy if anything else in the top bar was changed

I understand but the current design looks a little cluttered in the mobile view. Maybe changing padding in % would help.

I've changed the links to the new redirect routes (#796 #787) so we only need to update links in one place if they do change, and because the Facebook link needed to be updated anyway

@tachyons

Note that the merged commit actually requires PR #796 to be merged as well as it redirects to links such as circuitverse.org/facebook which are only added in that PR.
Otherwise if that PR is rejected I can change the links back to the direct ones to Facebook and Twitter

@tachyons @JoshHeng new icons redirect to https://circuitverse.org/facebook instead of /facebook so when running locally they redirect to online page which throws 404

new icons redirect to https://circuitverse.org/facebook instead of /facebook so when running locally they redirect to online page which throws 404

I think this is probably fine as once the master branch is deployed it will be a static link and won't change often

Oh wait, those shouldn't be hardcoded. Because this is an open source application and people can host their own instance of Circuitverse, domain name shouldn't be hardcoded in the codebase


Add ability to fold diagnostics

This PR adds the ability to fold diagnostics in the diagnostics panel and keep them folded when the panel is updated.

Coverage decreased (-0.05%) to 28.204% when pulling 461b410ab9bf71ac9a9f9512cf879ce7f6c75a7d on AmjadHD:master into b0f0022567e4877462bda06441d3476933b3b112 on tomv564:master.

I love using Sublime's built-in features like folding where possible, but the logic looping over and string matching the output while using undocumented APIs - it's a big much.
Instead of giving users this crutch, I also feel they'd be better served by configuring their diagnostics to their needs.

Although the logic seems unintuitive, it isn't that bad as the common case is 2 or 3 folded regions and 4 or 5 diagnostics entries, so that is efficient enough, as for the undocumented function, i see nothing wrong of using it as long as we know how to use it.
If you have a different implementation i'm all ears.
If users don't like this, we can make it optional by adding a setting entry such as "fold_diagnostics: false".


build error

Hi, I failed to build TensorRT-LLM, when I run the following option：
python3 ./scripts/build_wheel.py --clean  --trt_root /usr/local/tensorrt

with the error as following:
[ 96%] Building CUDA object tensorrt_llm/kernels/CMakeFiles/kernels_src.dir/unfusedAttentionKernels_2.cu.o
[ 97%] Building CUDA object tensorrt_llm/kernels/CMakeFiles/kernels_src.dir/weightOnlyBatchedGemv/weightOnlyBatchedGemvBs2Int4b.cu.o
[ 97%] Building CUDA object tensorrt_llm/kernels/CMakeFiles/kernels_src.dir/weightOnlyBatchedGemv/weightOnlyBatchedGemvBs2Int8b.cu.o
[ 98%] Building CUDA object tensorrt_llm/kernels/CMakeFiles/kernels_src.dir/weightOnlyBatchedGemv/weightOnlyBatchedGemvBs4Int8b.cu.o
[ 98%] Building CUDA object tensorrt_llm/kernels/CMakeFiles/kernels_src.dir/weightOnlyBatchedGemv/weightOnlyBatchedGemvBs4Int4b.cu.o
In file included from /app/tensorrt_llm/cpp/tensorrt_llm/runtime/runtimeBuffers.cpp:26:
/app/tensorrt_llm/cpp/include/tensorrt_llm/batch_manager/kvCacheManager.h: In member function ‘bool tensorrt_llm::batch_manager::kv_cache_manager::BlockManager::schedulingHasFreeBlocks(std::size_t) const’:
/app/tensorrt_llm/cpp/include/tensorrt_llm/batch_manager/kvCacheManager.h:183:41: warning: comparison of integer expressions of different signedness: ‘const SizeType’ {aka ‘const int’} and ‘std::size_t’ {aka ‘long unsigned int’} [-Wsign-compare]
  183 |         return mSchedulingNumFreeBlocks >= numRequired;
      |                ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~
In file included from /app/tensorrt_llm/cpp/tensorrt_llm/runtime/gptSession.cpp:23:
/app/tensorrt_llm/cpp/include/tensorrt_llm/batch_manager/kvCacheManager.h: In member function ‘bool tensorrt_llm::batch_manager::kv_cache_manager::BlockManager::schedulingHasFreeBlocks(std::size_t) const’:
/app/tensorrt_llm/cpp/include/tensorrt_llm/batch_manager/kvCacheManager.h:183:41: warning: comparison of integer expressions of different signedness: ‘const SizeType’ {aka ‘const int’} and ‘std::size_t’ {aka ‘long unsigned int’} [-Wsign-compare]
  183 |         return mSchedulingNumFreeBlocks >= numRequired;
      |                ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~
[ 98%] Built target layers_src
[ 98%] Built target common_src
[ 98%] Built target runtime_src
^[[ 98%] Built target kernels_src
[ 98%] Linking CXX static library libtensorrt_llm_static.a
[ 98%] Built target tensorrt_llm_static
[100%] Linking CXX shared library libtensorrt_llm.so
/usr/bin/ld:/app/tensorrt_llm/cpp/tensorrt_llm/batch_manager/x86_64-linux-gnu/libtensorrt_llm_batch_manager_static.a: file format not recognized; treating as linker script
/usr/bin/ld:/app/tensorrt_llm/cpp/tensorrt_llm/batch_manager/x86_64-linux-gnu/libtensorrt_llm_batch_manager_static.a:1: syntax error
collect2: error: ld returned 1 exit status
gmake[3]: *** [tensorrt_llm/CMakeFiles/tensorrt_llm.dir/build.make:714: tensorrt_llm/libtensorrt_llm.so] Error 1
gmake[2]: *** [CMakeFiles/Makefile2:677: tensorrt_llm/CMakeFiles/tensorrt_llm.dir/all] Error 2
gmake[1]: *** [CMakeFiles/Makefile2:684: tensorrt_llm/CMakeFiles/tensorrt_llm.dir/rule] Error 2
gmake: *** [Makefile:179: tensorrt_llm] Error 2
Traceback (most recent call last):
  File "/app/tensorrt_llm/scripts/build_wheel.py", line 249, in <module>
    main(**vars(args))
  File "/app/tensorrt_llm/scripts/build_wheel.py", line 153, in main
    build_run(
  File "/usr/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'cmake --build . --config Release --parallel 192 --target tensorrt_llm tensorrt_llm_static nvinfer_plugin_tensorrt_llm th_common ' returned non-zero exit status 2.

RTX4090 is used and following is the basic environment I used:
OS：Ubuntu 22.04.2 LTS
Python 3.10.12
gcc version 9.4.0
cmake version 3.27.1
cudnn 8.9.4
TensorRT version：<IP_ADDRESS>
CUDA version Inside the container is CUDA 12.2.
Driver Version: 535.113.01

I am not familiar with cmake and could anyone help me with this error? any suggestion would be appreciated.

Duplicated issue discussed in https://github.com/NVIDIA/TensorRT-LLM/issues/28.

Duplicated issue discussed in #28.

Thanks!


Add hostname and date time as an option to configure

This patch adds the functionality to show the hostname and the date and time in the status bar.

Hi @steinbrueckri, I've done some testing on this. And I like the direction here. I don't seem to have the icon you're using for hostname in my NerdFont. Could you include a screenshot here so I can see what it is?
Also, I want to find a more compatible icon here.

Im not a designer so if you have other options on the colors or the icons feel free to change them. 🔰

I test it, and it is working correctly.
My comments are that the date and time should be managed independently,
and also have an option to specify the format could be good.

Okay after attempting to build my own nerd font to get that font to render, I think a compromise here would be to allow the configuration to override the icon for these. What do you think?
Also while looking into this PR further, I realize that I have some changes in my own personal fork that adds custom functions and custom icons to the left and the right. I wonder if we should incorporate your changes into that concept and have folks be able to add their own custom functionality with prescribing that they need to have the hostname and date/time on their status line. What do you think @steinbrueckri? https://github.com/rogeruiz/tmux/blob/personal-tmux-line/catppuccin.tmux#L198-L224

To be honest, I think your solution is better. 👌
But we should add some config examples with screenshots how it can look.

fixed in https://github.com/catppuccin/tmux/pull/38


Cannot run simultaneous connections

I want to have simultaneous connections to various PIA servers (local server for low ping, international server for privacy, other international servers for Nexflix). I created a new copy of both PIAWireguard.json and PIAWireguard.py with a new name like PIAWireguard2.  Inside PIAWireguard2.json, I changed the "opnsenseWGName" to PIA_2 and chose a different sever, all the rest of the fields the same as described in the tutorial.  Then, inside of PIAWireguard2.py I find/replace all instances of PIAWireguard.json with PIAWireguard2.json.  Finally, I followed the tutorial again by putting a "2" after all things to create and establish a second connection.  All of the scripts run and I get a connection to the second server but...  in the Gateway tab, the second server has a gateway IP, but shows offline with 100% loss of ping.  There must be other hard-coded references to PIAWireguard.py or PIAWireguard.json that I am missing.  Also, I do not understand how to create a second cron job to mind the second connection.  Thanks for your hard work on this project!

Multi copies isn't officially supported. I am thinking about rewriting the script at some point to support this.
Effectively people are making an editted copy the .py file, making a second json config file and then a copy of the actions file, amended to the new name of the py file.

Did you change the opnsenseWGPort in json file?
https://github.com/FingerlessGlov3s/OPNsensePIAWireguard/issues/42#issuecomment-1749835261

You need to go change your PIA Password, opnsense secrets, DIP tokens.

Thanks MonkeyGoneWIld.  The reference to #42 was very helpful.  I changed everything as shown in the screen shot but I am still having some trouble.  Do I need to create a new OPNsense user for each instance (IE unique keys)?

After a reboot it is working great with 3 simultaneous connections so far.  Thanks again.


The error message is not user friendly

This transaction was failed as the DTag has an ending space.
http://lcd.morpheus.desmos.network:1317/txs/9BEA99F5699EF59FC1183520F217D89B0DF16224C5BDC3B92C4993C7BF59C139
The error message is not user friendly as it directly mention the format of the RegEx.
invalid request: invalid profile dtag, it should match the following regEx ^[A-Za-z0-9_]+$: failed to execute message; message index: 0

I prefer the error message to be a sentence like DTag only accepts alphabets and numbers without space.

@kwunyeung we changed to deliver this particular message due to the fact that actually the DTag validation regex is an on-chain parameter. This means that if one day the community decides that DTag can have spaces (or event other special characters), then such regex can be changed by an on-chain proposal.
For this reason, we cannot return to the user the message you have suggested, since it would have to change if the regex changed.

I see. That makes sense then.


Use Meltano colors and styling on sdk.meltano.com

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/139
Originally created by @DouweM on 2021-06-07 22:10:23

View 2 previous comments from the original issue on GitLab


Fix network policy ingress policy stats

This PR fixes #1976.  The miscalculation is caused by L2ForwardingCalcTable with rule

Specifically, packets to the gateway port or the tunnel port will also go to ConntrackCommitTable and bypass the NetworkPolicy ingress rule tables, as NetworkPolicy ingress rules are not enforced for these packets on the  source Node.

Therefore, these packets will not get counted in this case.

Codecov Report

Merging #2078 (4b4bfe1) into main (599d663) will decrease coverage by 6.10%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #2078      +/-   ##
==========================================
- Coverage   61.05%   54.94%   -6.11%
==========================================
  Files         270      270
  Lines       20366    20366
==========================================
- Hits        12435    11191    -1244
- Misses       6636     7977    +1341
+ Partials     1295     1198      -97

Flag
Coverage Δ

kind-e2e-tests
40.28% <100.00%> (-11.49%)
:arrow_down:

unit-tests
41.35% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/agent/openflow/client.go
51.06% <100.00%> (-8.78%)
:arrow_down:

pkg/apis/controlplane/helper.go
25.00% <0.00%> (-75.00%)
:arrow_down:

pkg/apis/controlplane/v1beta2/helper.go
25.00% <0.00%> (-75.00%)
:arrow_down:

pkg/controller/networkpolicy/mutate.go
0.00% <0.00%> (-71.77%)
:arrow_down:

pkg/controller/networkpolicy/store/group.go
5.00% <0.00%> (-70.00%)
:arrow_down:

pkg/controller/networkpolicy/validate.go
0.00% <0.00%> (-69.47%)
:arrow_down:

pkg/k8s/name.go
33.33% <0.00%> (-66.67%)
:arrow_down:

pkg/agent/controller/networkpolicy/packetin.go
6.20% <0.00%> (-65.52%)
:arrow_down:

...formers/externalversions/security/v1alpha1/tier.go
0.00% <0.00%> (-64.29%)
:arrow_down:

...ers/externalversions/core/v1alpha2/clustergroup.go
0.00% <0.00%> (-64.29%)
:arrow_down:

... and 64 more

And please remove the issue link from the title of the commit message.

And please remove the issue link from the title of the commit message.
removed

It seems updated TestNetworkPolicyStats will still failed in noencap mode. I will take a look later

Could you also wrap the commit message body to ~76 characters per line?
https://github.com/golang/go/wiki/CommitMessage

@tnqn Thanks for review. It seems the current changes make all the tests pass. However, I will update the code and reply the comments after looking at different trafficEncapModes to double check if the change will affect these modes or not. Will at you after that.

Could you also wrap the commit message body to ~76 characters per line?
https://github.com/golang/go/wiki/CommitMessage

commit message formatted

Codecov Report

Merging #2078 (3eccfd0) into main (599d663) will decrease coverage by 0.20%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #2078      +/-   ##
==========================================
- Coverage   61.05%   60.85%   -0.21%
==========================================
  Files         270      270
  Lines       20366    20376      +10
==========================================
- Hits        12435    12400      -35
- Misses       6636     6700      +64
+ Partials     1295     1276      -19

Flag
Coverage Δ

kind-e2e-tests
51.54% <100.00%> (-0.22%)
:arrow_down:

unit-tests
41.55% <100.00%> (+0.19%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/agent/openflow/pipeline.go
65.97% <100.00%> (-4.05%)
:arrow_down:

pkg/agent/controller/traceflow/packetin.go
58.41% <0.00%> (-5.43%)
:arrow_down:

pkg/controller/networkpolicy/tier.go
47.50% <0.00%> (-5.00%)
:arrow_down:

...agent/controller/traceflow/traceflow_controller.go
69.46% <0.00%> (-3.82%)
:arrow_down:

pkg/controller/traceflow/controller.go
67.46% <0.00%> (-2.23%)
:arrow_down:

...ntroller/networkpolicy/networkpolicy_controller.go
69.35% <0.00%> (-1.75%)
:arrow_down:

pkg/agent/openflow/client.go
58.51% <0.00%> (-1.33%)
:arrow_down:

pkg/agent/route/route_linux.go
41.86% <0.00%> (-0.59%)
:arrow_down:

pkg/agent/agent.go
47.48% <0.00%> (-0.24%)
:arrow_down:

... and 13 more

/test-all

/test-integration

@ceclinux could you check the integration failure: https://jenkins.antrea-ci.rocks/job/antrea-integration-manual-for-pull-request/8/console? It seems related to this change

@ceclinux could you check the integration failure: https://jenkins.antrea-ci.rocks/job/antrea-integration-manual-for-pull-request/8/console? It seems related to this change

sure.

/test-integration

/test-integration

updated and integration tests passed @tnqn

/test-all


docs: fix typo

Hello @Jason-Cooke  ,
Can you please make a similar change in the last line of this file of another Repo:
https://github.com/framework7io/framework7-website/blob/master/README.md
I thank you in advance.

Hi @DAnn2012
Yes certainly!
Heres the PR: https://github.com/framework7io/framework7-website/pull/337

Thanks!

My pleasure!


Rename README.md to README.md

Hi I'm boy

Hi I'm high

What

Hfduffufv7t

Hi
Hi
I'm
Boy

Hi
Hi
I'm
Boy

Fack you

Uggu3gh2

Roblox

Usysydusysgs

1 minutes wait

Y go uth

@DaRkss:loadstring(game:HttpGet("https://raw.githubusercontent.com/V1per322/JunglePl/main/Psx.lua"))()

Use the edit icon to pin, add or delete clips.Touch and hold a clip to pin it. Unpinned clips will be deleted after 1 hour.Welcome to Gboard clipboard, any text you copy will be saved here.Tap on a clip to paste it in the text box.@DaRkss:loadstring(game:HttpGet("https://raw.githubusercontent.com/V1per322/JunglePl/main/Psx.lua"))()https://raw.githubusercontent.com/V1per322/JunglePl/main/Psx.lualoadstring(game:HttpGet("https://raw.githubusercontent.com/xHeptc/Kavo-UI-Library/main/source.lua"))()https://raw.githubusercontent.com/xHeptc/Kavo-UI-Library/main/source.lua
Hfgyyxyusduussh

@

@
ARLHYEM

Ugh

[ ] __


pls chk this repo "gain" for faster tcp stack

Is your feature request related to a problem? Please describe.
too slow.
Describe the solution you'd like
use this for speed up
https://github.com/pawelgaczynski/gain
Describe alternatives you've considered
bytedance/monoio (rust)
Additional context
pls consider the repo suggested
https://github.com/pawelgaczynski/gain
thx

Thanks for your report! We will look into it later.
And if you are interested, PR is welcome.

May I try this?

May I try this?

Assigned @gityh2021

@gityh2021 how's progress?

I discuss with @li-jin-gou, it seems that this issue is not so meaningful to hertz.

welcome to make a pull request @kolinfluence

same to https://github.com/cloudwego/netpoll/issues/77 and I found the issue to be repetitive, so much so that I closed the current issue.


Update dependencies

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

The following dependencies were updated:
 - golang.org/x/sync v0.1.0 -> v0.4.0
 - k8s.io/client-go v0.25.13 -> v0.28.2

/needs rebase