ZHA: Yale Real Living SYDL220: Battery drains in days, no battery info or lock state

I first posted this on the zha-device-handlers page, but was advised by @dmulcahey to post it here instead.
Operating environment

Home Assistant Docker container on Raspbian Buster, Raspberry Pi 3 Model B+
Dresden Elektronik RaspBee

Integration:
ZHA
Description of problem:
I have the Yale Real Living SYDL220 (Australian equivalent to YRL220) door lock with the ZBM-1 Zigbee module. It's connected to a Raspberry Pi with a RaspBee hat located about 1m away from the door handle, so signal strength is quite good.
When not using the Lock’s Zigbee module, the battery lasts for the expected 6-12 months. When connecting the lock to Home Assistant over ZHA, the battery drains within 3-4 days. I am new to Zigbee devices and don’t quite know where to start with regard to debugging this. My guess is that the lock never goes to sleep, though that’s really not based on much. There is a separate Zigbee setup in the apartment with Philips Hue lights and a Hue Bridge, though I have no idea if this might cause issues.
I have tried unpairing the lock and re-pairing it multiple times, seemingly to no effect. I have also flashed the RaspBee with the most recent firmware.
Additionally, the lock shows up in Home Assistant with two battery sensors, none of which are working. And the lock does not report its state in a manner that Home Assistant recognises.
I think I have found a cluster attribute that reflects the lock’s state, though none of the long list of battery attributes seem to return a value other than None.
Any help on this appreciated. I’m happy to provide any information that might be needed to figure this out. The battery drain especially is a bit painful.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
This Raspberry Pi is set up mostly to get the lock working. Below is the config in full. There are some automations to control the lock via MQTT from the main Home Assistant instance in the house in automations.yaml.
configuration.yaml
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

automations.yaml
- id: '1570870555842'
  alias: MQTT Front Door Lock
  description: ''
  trigger:
  - payload: lock
    platform: mqtt
    topic: home/frontdoor/set
  condition: []
  action:
  - alias: ''
    data:
      entity_id: lock.yale_cap_0c290c6d_1_257
    service: lock.lock
  - data:
      payload: lock
      topic: home/frontdoor/
    service: mqtt.publish
- id: '1570871822536'
  alias: MQTT Front Door Unlock
  description: ''
  trigger:
  - payload: unlock
    platform: mqtt
    topic: home/frontdoor/set
  condition: []
  action:
  - data:
      entity_id: lock.yale_cap_0c290c6d_1_257
    service: lock.unlock
  - data:
      payload: unlock
      topic: home/frontdoor/
    service: mqtt.publish
  - delay: 00:00:35
  - data:
      payload: lock
      topic: home/frontdoor/
    service: mqtt.publish
- id: '1570881385432'
  alias: Front Door Locked State
  description: ''
  trigger:
  - entity_id: lock.yale_cap_0c290c6d_1_257
    platform: state
    to: locked
  condition: []
  action:
  - data:
      payload: lock
      topic: home/frontdoor/
    service: mqtt.publish
- id: '1570881488679'
  alias: Front Door Unlock State
  description: ''
  trigger:
  - entity_id: lock.yale_cap_0c290c6d_1_257
    platform: state
    to: unlocked
  condition: []
  action:
  - data:
      payload: unlock
      topic: home/frontdoor/
    service: mqtt.publish
  - delay: 00:0:35
  - data:
      payload: lock
      topic: home/frontdoor/
    service: mqtt.publish
- id: '1570882480756'
  alias: MQTT Messages
  description: ''
  trigger:
  - platform: mqtt
    topic: home/frontdoor/#
  condition: []
  action:
  - data:
      '[object Object]':
    service: notify.notify

Pairing information:
[0x0000:zdo] ZDO request 0x0036: [60, <Bool.false: 0>]
Device 0xc0b5 (00:0d:6f:00:0c:29:0c:6d) joined the network
[0xc0b5:zdo] ZDO request 0x0013: [0xc0b5, 00:0d:6f:00:0c:29:0c:6d, 128]
[0xc0b5] Requesting 'Node Descriptor'
[0xc0b5] Extending timeout for 0xab request
[0xc0b5] Node Descriptor: <Optional byte1=2 byte2=64 mac_capability_flags=128 manufacturer_code=43690 maximum_buffer_size=82 maximum_incoming_transfer_size=255 server_mask=0 maximum_outgoing_transfer_size=255 descriptor_capability_field=0>
Error calling listener.node_descriptor_updated: FOREIGN KEY constraint failed
[0xc0b5] Discovering endpoints
[0xc0b5] Extending timeout for 0xad request
[0xc0b5] Discovered endpoints: [1, 196]
[0xc0b5:1] Discovering endpoint information
[0xc0b5] Extending timeout for 0xaf request
[0xc0b5:1] Discovered endpoint information: <SimpleDescriptor endpoint=1 profile=260 device_type=10 device_version=0 input_clusters=[0, 9, 10, 257, 64512, 1] output_clusters=[]>
[0xc0b5] Extending timeout for 0xb1 request
[0xc0b5:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=177 command_id=Command.Read_Attributes_rsp>
[0xc0b5:1] Manufacturer: Yale
[0xc0b5:1] Model: Cap
[0xc0b5:196] Discovering endpoint information
[0xc0b5] Extending timeout for 0xb3 request
[0xc0b5:196] Discovered endpoint information: <SimpleDescriptor endpoint=196 profile=49757 device_type=1 device_version=0 input_clusters=[1] output_clusters=[]>
Checking quirks for Yale Cap (00:0d:6f:00:0c:29:0c:6d)
Considering <class 'zigpy.quirks.smartthings.SmartthingsMultiPurposeSensor'>
Fail because endpoint list mismatch: {1} {1, 196}
Considering <class 'zhaquirks.gledopto.soposhgu10.SoposhGU10'>
Fail because endpoint list mismatch: {11, 13} {1, 196}
Considering <class 'zhaquirks.lutron.lzl4bwhl01remote.LutronLZL4BWHL01Remote2'>
Fail because endpoint list mismatch: {1} {1, 196}
Considering <class 'zhaquirks.netvox.z308e3ed.Z308E3ED'>
Fail because endpoint list mismatch: {1} {1, 196}
Considering <class 'zhaquirks.osram.a19twhite.A19TunableWhite'>
Fail because endpoint list mismatch: {3} {1, 196}
Considering <class 'zhaquirks.philips.rwl021.PhilipsRWL021'>
Fail because endpoint list mismatch: {1, 2} {1, 196}
Considering <class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'>
Fail because endpoint list mismatch: {1} {1, 196}
Considering <class 'zhaquirks.xbee.xbee3_io.XBee3Sensor'>
Fail because endpoint list mismatch: {232, 230} {1, 196}
Considering <class 'zhaquirks.xbee.xbee_io.XbeeSensor'>
Fail because endpoint list mismatch: {232, 230} {1, 196}
Considering <class 'zhaquirks.xiaomi.mija.smoke.MijiaHoneywellSmokeDetectorSensor'>
Fail because endpoint list mismatch: {1} {1, 196}
device - 0xc0b5:00:0d:6f:00:0c:29:0c:6d entering async_device_initialized - is_new_join: True
device - 0xc0b5:00:0d:6f:00:0c:29:0c:6d has joined the ZHA zigbee network
[0xc0b5](Cap): started configuration
[0xc0b5:ZDO](Cap): channel: 'async_configure' stage succeeded
[0xc0b5] Extending timeout for 0xb5 request
[0xc0b5] Extending timeout for 0xb7 request
[0xc0b5] Extending timeout for 0xb9 request
[0xc0b5:1:0x0000]: bound 'basic' cluster: Status.SUCCESS
[0xc0b5:1:0x0000]: finished channel configuration
[0xc0b5] Extending timeout for 0xbb request
[0xc0b5:1:0x0101]: bound 'door_lock' cluster: Status.SUCCESS
[0xc0b5] Extending timeout for 0xbd request
[0xc0b5:1:0x0001]: bound 'power' cluster: Status.TABLE_FULL
[0xc0b5] Extending timeout for 0xbf request
[0xc0b5:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=187 command_id=Command.Read_Attributes_rsp>
[0xc0b5:1:0x0000]: initializing channel: from_cache: False
[0xc0b5:1:0x0000]: channel: 'async_configure' stage succeeded
[0xc0b5:1:0x0101] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=189 command_id=Command.Default_Response>
[0xc0b5:1:0x0101]: reporting 'lock_state' attr on 'door_lock' cluster: 0/900/1: Result: '[6, <Status.UNSUP_GENERAL_COMMAND: 130>]'
[0xc0b5:1:0x0001] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=191 command_id=Command.Default_Response>
[0xc0b5:1:0x0001]: reporting 'battery_voltage' attr on 'power' cluster: 3600/10800/1: Result: '[6, <Status.UNSUP_GENERAL_COMMAND: 130>]'
[0xc0b5:1:0x0101]: finished channel configuration
[0xc0b5:1:0x0101]: channel: 'async_configure' stage succeeded
[0xc0b5] Extending timeout for 0xc1 request
[0xc0b5:1:0x0001] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=193 command_id=Command.Default_Response>
[0xc0b5:1:0x0001]: reporting 'battery_percentage_remaining' attr on 'power' cluster: 3600/10800/1: Result: '[6, <Status.UNSUP_GENERAL_COMMAND: 130>]'
[0xc0b5:1:0x0001]: finished channel configuration
[0xc0b5:1:0x0001]: channel: 'async_configure' stage succeeded
[0xc0b5](Cap): completed configuration
[0xc0b5](Cap): stored in registry: ZhaDeviceEntry(name='Yale Cap', ieee='00:0d:6f:00:0c:29:0c:6d', last_seen=1572687760.500016)
[0xc0b5](Cap): started initialization
[0xc0b5:ZDO](Cap): entry loaded from storage: ZhaDeviceEntry(name='Yale Cap', ieee='00:0d:6f:00:0c:29:0c:6d', last_seen=1572687760.500016)
[0xc0b5:ZDO](Cap): channel: 'async_initialize' stage succeeded
[0xc0b5] Extending timeout for 0xc3 request
[0xc0b5] Extending timeout for 0xc5 request
[0xc0b5] Extending timeout for 0xc7 request
[0xc0b5:1:0x0000] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=195 command_id=Command.Read_Attributes_rsp>
[0xc0b5:1:0x0000]: initializing channel: from_cache: False
[0xc0b5:1:0x0000]: channel: 'async_initialize' stage succeeded
[0xc0b5:1:0x0101] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=197 command_id=Command.Read_Attributes_rsp>
[0xc0b5:1:0x0101]: Attribute report 'Door Lock'[lock_state] = 1
[0xc0b5:1:0x0101]: initializing channel: from_cache: False
[0xc0b5:1:0x0101]: channel: 'async_initialize' stage succeeded
[0xc0b5:1:0x0001] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=199 command_id=Command.Read_Attributes_rsp>
[0xc0b5] Extending timeout for 0xc9 request
[0xc0b5:1:0x0001] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=201 command_id=Command.Read_Attributes_rsp>
[0xc0b5] Extending timeout for 0xcb request
[0xc0b5:1:0x0001] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=203 command_id=Command.Read_Attributes_rsp>
[0xc0b5] Extending timeout for 0xcd request
[0xc0b5:1:0x0001] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=205 command_id=Command.Read_Attributes_rsp>
[0xc0b5:1:0x0001]: initializing channel: from_cache: False
[0xc0b5:1:0x0001]: channel: 'async_initialize' stage succeeded
[0xc0b5](Cap): power source: Battery or Unknown
[0xc0b5](Cap): completed initialization

Under "DoorLock"

Hrm, it does not support attribute reporting command. Leave it running for 3-4 hours  and then filter the log by 0xc0b5 and post it here. I'd like to see how much traffic it generates.

Hi @Adminiuga,
I don’t see any entries in home-assistant.log containing 0xc0b5. Am I looking at the right log? Or do you think I have to change the logging level?
These are the only messages in home-assistant.log since the pairing event above:
2019-11-02 22:42:36 WARNING (MainThread) [zigpy.util] Error calling listener.node_descriptor_updated: FOREIGN KEY constraint failed
2019-11-03 00:31:47 WARNING (MainThread) [zigpy_deconz.zigbee.application] Error while sending 208 req id frame: 0xd0
2019-11-03 00:32:48 WARNING (MainThread) [zigpy_deconz.zigbee.application] Error while sending 210 req id frame: 0xd0

Uh, the log book might offer a clue. Don’t know why I didn’t look there before.
This seemingly goes on like this forever.

Got the logging going. Here’s a snapshot after I restarted Home Assistant with new logging settings about 15 minutes ago:
2019-11-03 08:37:52 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [43, 34, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xfffd>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, 0, 0, 19, b'\x81\xb5\xc0m\x0c)\x0c\x00o\r\x00\x80', 0, 175, 255, 163, 0, 1, 2, -46]
2019-11-03 08:37:52 INFO (MainThread) [zigpy_deconz.zigbee.application] New device joined: 0xc0b5, 00:0d:6f:00:0c:29:0c:6d
2019-11-03 08:37:52 INFO (MainThread) [zigpy.application] Device 0xc0b5 (00:0d:6f:00:0c:29:0c:6d) joined the network
2019-11-03 08:37:52 DEBUG (MainThread) [zigpy.zdo] [0xc0b5:zdo] ZDO request 0x0013: [0xc0b5, 00:0d:6f:00:0c:29:0c:6d, 128]
2019-11-03 08:37:52 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, ep: 0, profile: 0x0000, cluster_id: 0x0013, data: b'81b5c06d0c290c006f0d0080'
2019-11-03 08:37:53 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xc0b5](Cap): started initialization
2019-11-03 08:37:53 DEBUG (MainThread) [homeassistant.components.zha.core.channels] [0xc0b5:ZDO](Cap): entry loaded from storage: ZhaDeviceEntry(name='Yale Cap', ieee='00:0d:6f:00:0c:29:0c:6d', last_seen=1572723323.7313643)
2019-11-03 08:37:53 DEBUG (MainThread) [homeassistant.components.zha.core.channels] [0xc0b5:ZDO](Cap): channel: 'async_initialize' stage succeeded
2019-11-03 08:37:53 DEBUG (MainThread) [homeassistant.components.zha.core.channels] [0xc0b5:1:0x0000]: initializing channel: from_cache: True
2019-11-03 08:37:53 DEBUG (MainThread) [homeassistant.components.zha.core.channels] [0xc0b5:1:0x0000]: channel: 'async_initialize' stage succeeded
2019-11-03 08:37:53 DEBUG (MainThread) [homeassistant.components.zha.core.channels] [0xc0b5:1:0x0101]: initializing channel: from_cache: True
2019-11-03 08:37:53 DEBUG (MainThread) [homeassistant.components.zha.core.channels] [0xc0b5:1:0x0101]: channel: 'async_initialize' stage succeeded
2019-11-03 08:37:53 DEBUG (MainThread) [homeassistant.components.zha.core.channels] [0xc0b5:1:0x0001]: initializing channel: from_cache: True
2019-11-03 08:37:53 DEBUG (MainThread) [homeassistant.components.zha.core.channels] [0xc0b5:1:0x0001]: channel: 'async_initialize' stage succeeded
2019-11-03 08:37:53 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xc0b5](Cap): power source: Battery or Unknown
2019-11-03 08:37:53 DEBUG (MainThread) [homeassistant.components.zha.core.device] [0xc0b5](Cap): completed initialization
2019-11-03 08:37:57 DEBUG (MainThread) [zigpy.device] [0xc0b5] Extending timeout for 0x01 request
2019-11-03 08:37:57 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (18, 2, 0, <DeconzAddressEndpoint address_mode=2 address=0xc0b5 endpoint=1>, 260, 257, 1, b'\x01\x01\x01', 2, 0)
2019-11-03 08:37:57 DEBUG (MainThread) [zigpy.device] [0xc0b5] Extending timeout for 0x03 request
2019-11-03 08:37:57 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (18, 4, 0, <DeconzAddressEndpoint address_mode=2 address=0xc0b5 endpoint=1>, 260, 257, 1, b'\x01\x03\x01', 2, 0)
2019-11-03 08:37:57 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x02 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0xc0b5 endpoint=1>, status: 0x00
2019-11-03 08:37:57 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x04 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0xc0b5 endpoint=1>, status: 0x00
2019-11-03 08:37:57 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [35, 34, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, 1, 260, 257, b'\t\x01\x01\x00', 0, 175, 255, 163, 0, 1, 4, -46]
2019-11-03 08:37:57 DEBUG (MainThread) [zigpy.zcl] [0xc0b5:1:0x0101] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=1 command_id=Command.Read_Attributes_rsp>
2019-11-03 08:37:57 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, ep: 1, profile: 0x0104, cluster_id: 0x0101, data: b'09010100'
2019-11-03 08:37:57 DEBUG (MainThread) [homeassistant.components.zha.core.channels] [0xc0b5:1:0x0101]: executed command: unlock_door with args: () with kwargs: {} and result: [<Status.SUCCESS: 0>]
2019-11-03 08:37:58 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [35, 34, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, 1, 260, 257, b'\t\x03\x01\x00', 0, 175, 255, 163, 0, 1, 2, -46]
2019-11-03 08:37:58 DEBUG (MainThread) [zigpy.zcl] [0xc0b5:1:0x0101] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=3 command_id=Command.Read_Attributes_rsp>
2019-11-03 08:37:58 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, ep: 1, profile: 0x0104, cluster_id: 0x0101, data: b'09030100'
2019-11-03 08:37:58 DEBUG (MainThread) [homeassistant.components.zha.core.channels] [0xc0b5:1:0x0101]: executed command: unlock_door with args: () with kwargs: {} and result: [<Status.SUCCESS: 0>]
2019-11-03 08:37:59 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [37, 34, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, 1, 260, 9, b'\t\t\x00\x19\x00\xfc', 0, 175, 255, 163, 0, 1, 4, -46]
2019-11-03 08:37:59 DEBUG (MainThread) [zigpy.zcl] [0xc0b5:1:0x0009] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=9 command_id=Command.Read_Attributes>
2019-11-03 08:37:59 DEBUG (MainThread) [zigpy.zcl] [0xc0b5:1:0x0009] ZCL request 0x0100: [25, 64512]
2019-11-03 08:37:59 DEBUG (MainThread) [zigpy.zcl] [0xc0b5:1:0x0009] No handler for cluster command 0
2019-11-03 08:37:59 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, ep: 1, profile: 0x0104, cluster_id: 0x0009, data: b'0909001900fc'
2019-11-03 08:38:33 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [37, 34, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, 1, 260, 9, b'\t\x0c\x00\x1b\x00\xfc', 0, 175, 255, 163, 0, 1, 2, -46]2019-11-03 08:38:33 DEBUG (MainThread) [zigpy.zcl] [0xc0b5:1:0x0009] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=12 command_id=Command.Read_Attributes>
2019-11-03 08:38:33 DEBUG (MainThread) [zigpy.zcl] [0xc0b5:1:0x0009] ZCL request 0x0100: [27, 64512]
2019-11-03 08:38:33 DEBUG (MainThread) [zigpy.zcl] [0xc0b5:1:0x0009] No handler for cluster command 0
2019-11-03 08:38:33 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, ep: 1, profile: 0x0104, cluster_id: 0x0009, data: b'090c001b00fc'
2019-11-03 08:40:01 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [43, 34, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xfffd>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, 0, 0, 19, b'\x81\xb5\xc0m\x0c)\x0c\x00o\r\x00\x80', 0, 175, 255, 163, 0, 1, 2, -46]
2019-11-03 08:40:01 INFO (MainThread) [zigpy_deconz.zigbee.application] New device joined: 0xc0b5, 00:0d:6f:00:0c:29:0c:6d
2019-11-03 08:40:01 INFO (MainThread) [zigpy.application] Device 0xc0b5 (00:0d:6f:00:0c:29:0c:6d) joined the network
2019-11-03 08:40:01 DEBUG (MainThread) [zigpy.zdo] [0xc0b5:zdo] ZDO request 0x0013: [0xc0b5, 00:0d:6f:00:0c:29:0c:6d, 128]
2019-11-03 08:40:01 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, ep: 0, profile: 0x0000, cluster_id: 0x0013, data: b'81b5c06d0c290c006f0d0080'
2019-11-03 08:42:27 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [43, 34, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xfffd>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, 0, 0, 19, b'\x81\xb5\xc0m\x0c)\x0c\x00o\r\x00\x80', 0, 175, 255, 163, 0, 1, 2, -46]
2019-11-03 08:42:27 INFO (MainThread) [zigpy_deconz.zigbee.application] New device joined: 0xc0b5, 00:0d:6f:00:0c:29:0c:6d
2019-11-03 08:42:27 INFO (MainThread) [zigpy.application] Device 0xc0b5 (00:0d:6f:00:0c:29:0c:6d) joined the network
2019-11-03 08:42:27 DEBUG (MainThread) [zigpy.zdo] [0xc0b5:zdo] ZDO request 0x0013: [0xc0b5, 00:0d:6f:00:0c:29:0c:6d, 128]
2019-11-03 08:42:27 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, ep: 0, profile: 0x0000, cluster_id: 0x0013, data: b'81b5c06d0c290c006f0d0080'
2019-11-03 08:43:16 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [43, 34, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xfffd>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, 0, 0, 19, b'\x81\xb5\xc0m\x0c)\x0c\x00o\r\x00\x80', 0, 175, 255, 163, 0, 1, 2, -46]
2019-11-03 08:43:16 INFO (MainThread) [zigpy_deconz.zigbee.application] New device joined: 0xc0b5, 00:0d:6f:00:0c:29:0c:6d
2019-11-03 08:43:16 INFO (MainThread) [zigpy.application] Device 0xc0b5 (00:0d:6f:00:0c:29:0c:6d) joined the network
2019-11-03 08:43:16 DEBUG (MainThread) [zigpy.zdo] [0xc0b5:zdo] ZDO request 0x0013: [0xc0b5, 00:0d:6f:00:0c:29:0c:6d, 128]
2019-11-03 08:43:16 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, ep: 0, profile: 0x0000, cluster_id: 0x0013, data: b'81b5c06d0c290c006f0d0080'
2019-11-03 08:47:57 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [43, 34, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xfffd>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, 0, 0, 19, b'\x81\xb5\xc0m\x0c)\x0c\x00o\r\x00\x80', 0, 175, 255, 163, 0, 1, 2, -46]
2019-11-03 08:47:57 INFO (MainThread) [zigpy_deconz.zigbee.application] New device joined: 0xc0b5, 00:0d:6f:00:0c:29:0c:6d
2019-11-03 08:47:57 INFO (MainThread) [zigpy.application] Device 0xc0b5 (00:0d:6f:00:0c:29:0c:6d) joined the network
2019-11-03 08:47:57 DEBUG (MainThread) [zigpy.zdo] [0xc0b5:zdo] ZDO request 0x0013: [0xc0b5, 00:0d:6f:00:0c:29:0c:6d, 128]
2019-11-03 08:47:57 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, ep: 0, profile: 0x0000, cluster_id: 0x0013, data: b'81b5c06d0c290c006f0d0080'
2019-11-03 08:49:06 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [43, 34, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0xfffd>, 0, <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, 0, 0, 19, b'\x81\xb5\xc0m\x0c)\x0c\x00o\r\x00\x80', 0, 175, 255, 163, 0, 1, 2, -46]
2019-11-03 08:49:06 INFO (MainThread) [zigpy_deconz.zigbee.application] New device joined: 0xc0b5, 00:0d:6f:00:0c:29:0c:6d
2019-11-03 08:49:06 INFO (MainThread) [zigpy.application] Device 0xc0b5 (00:0d:6f:00:0c:29:0c:6d) joined the network
2019-11-03 08:49:07 DEBUG (MainThread) [zigpy.zdo] [0xc0b5:zdo] ZDO request 0x0013: [0xc0b5, 00:0d:6f:00:0c:29:0c:6d, 128]
2019-11-03 08:49:07 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK_AND_IEEE address=0xc0b5>, ep: 0, profile: 0x0000, cluster_id: 0x0013, data: b'81b5c06d0c290c006f0d0080'

It sends a ZDO broadcast device announcement every few minutes. Those are supposed to be sent when device joins or re-joins the network. I can see how this would drain the battery, but it is not something we control. Do you have any mains powered Zigbee device near the lock? Maybe it just needs a stronger signal? Could be it needs a special initialization or configuration, hard to say. Is there a ST device handler specific to this lock?

The Raspberry Pi with the RaspBee sits about a meter away from the door, so I think the signal should be decent. It's reporting an LQI of 255 and RSSI of -46. Does that sound reasonable? There are a few Philips Hue bulbs in the ceiling overhead, though they are connected to a Hue Hub and not the Raspberry Pi. Any chance the Hue Zigbee network could interfere with the signal?
As for ST device handlers, I haven't been able to find one for SYDL220 specifically, though there are a few for the YRL220. Home Assistant also supports YRL220 I think.
To me, SYDL220 and YRL220 look like the same lock with a different model number for different regions, though I'm not sure if there are other differences under the hood. I would think the Zigbee module in the lock would be the same as in the rest of the world, though I don't know that for sure. I'll take it out of the lock and have a look.

This is the Zigbee module in the lock:

Could that be a Control4 module?  Here is what my module looks like.

Could that be a Control4 module?

That's a good catch. ZB C4 does look like Control4 module.
@presslab-us what endpoints do you have on your lock? I see this one reporting two endpoints:
<SimpleDescriptor endpoint=1 profile=260 device_type=10 device_version=0 input_clusters=[0, 9, 10, 257, 64512, 1] output_clusters=[]>
<SimpleDescriptor endpoint=196 profile=49757 device_type=1 device_version=0 input_clusters=[1] output_clusters=[]>

Mine only has one endpoint.  I didn't feel like joining it again, but here's what in my database.
INSERT INTO devices VALUES('00:0d:6f:00:02:4c:56:a3',7702,2);
INSERT INTO endpoints VALUES('00:0d:6f:00:02:4c:56:a3',1,260,10,1);
INSERT INTO clusters VALUES('00:0d:6f:00:02:4c:56:a3',1,0);
INSERT INTO clusters VALUES('00:0d:6f:00:02:4c:56:a3',1,1);
INSERT INTO clusters VALUES('00:0d:6f:00:02:4c:56:a3',1,3);
INSERT INTO clusters VALUES('00:0d:6f:00:02:4c:56:a3',1,9);
INSERT INTO clusters VALUES('00:0d:6f:00:02:4c:56:a3',1,10);
INSERT INTO clusters VALUES('00:0d:6f:00:02:4c:56:a3',1,257);
INSERT INTO clusters VALUES('00:0d:6f:00:02:4c:56:a3',1,32);
INSERT INTO output_clusters VALUES('00:0d:6f:00:02:4c:56:a3',1,10);
INSERT INTO output_clusters VALUES('00:0d:6f:00:02:4c:56:a3',1,25);
INSERT INTO attributes VALUES('00:0d:6f:00:02:4c:56:a3',1,0,5,'YRD210 PB DB');
INSERT INTO attributes VALUES('00:0d:6f:00:02:4c:56:a3',1,0,7,3);
INSERT INTO attributes VALUES('00:0d:6f:00:02:4c:56:a3',1,0,4,'Yale');
INSERT INTO attributes VALUES('00:0d:6f:00:02:4c:56:a3',1,257,0,1);
INSERT INTO attributes VALUES('00:0d:6f:00:02:4c:56:a3',1,1,33,200);
INSERT INTO node_descriptors VALUES('00:0d:6f:00:02:4c:56:a3',X'024080aaaa52ff000000ff0000');

Oh, here's my simple descriptor from when I did this PR.  https://github.com/dmulcahey/zha-device-handlers/pull/131
        #  <SimpleDescriptor endpoint=1 profile=260 device_type=10
        #  device_version=0
        #  input_clusters=[0, 1, 3, 9, 10, 257, 32]
        #  output_clusters=[10, 25]>

Yeah, it is different indeed.
There are different modules which look the same https://fcc.report/FCC-ID/U4A-YRHCPZB0LM/2242120.pdf and @thimic it does look like your's a Control4 variation which is not going to work with Zigbee HA profile as far as I know.

@presslab-us, @Adminiuga, thanks so much for figuring this out! I must confess I didn't know there were different varieties of the Zigbee module out there.
So are you saying that due to being Control4 and not HA, this module cannot work properly with Home Assistant's ZHA component? Or might it be possible to create a working profile?
What would you recommend? Go back to the vendor and see if they have the right module, or is there a chance I can get the current module to work with some fiddling?

I recommend going back to vendor and asking the HA1.2 one. It's unlikely we'll have C4 support any time soon.

Thanks @Adminiuga, I really appreciate the help and advice. I took it back to the store today and they gave me a refund. They’ll check with their supplier to see if they can order in the HA 1.2 version on Monday. If that’s not the case, I’ve been looking at the newer Yale YRM256 with this HA module: https://www.amazon.com/YALE-AYR202-NETWORK-MOD-Yale/dp/B07VWYNR6D
What do you think chances are that that module works with ZHA, if you don’t mind me asking?

This guy has a Yale YRD 226 Assure Lock and he said it's working fine (after changing the batteries), for whatever that's worth.  I'm not sure if he has the same module or not.
https://community.home-assistant.io/t/zha-lock-setup/124185/7

Thanks @presslab-us, I’ll ask about what module he’s using.
Closing this as we seem to have the answer: I unwittingly bought the Control4 version of the ZigBee module, which is not compatible with ZHA.
Thank you so much for all your help and insight @Adminiuga, @presslab-us and @dmulcahey.

FYI BendedArror seems to have the HA version of the module https://community.home-assistant.io/t/zha-lock-setup/124185/11?u=quatuor
Vendor's link  specifically calls out it being incompatible with Control4.
Good luck!

Monday. If that’s not the case, I’ve been looking at the newer Yale YRM256 with this HA module: https://www.amazon.com/YALE-AYR202-NETWORK-MOD-Yale/dp/B07VWYNR6D
What do you think chances are that that module works with ZHA, if you don’t mind me asking?

Well, I hate to speculate and frankly i'm not familiar with any of those. The item description does say the part number is AYR202-ZB-HA and google says it is indeed HA version of it and not compatible with Control4. I guess there's only one way to find out :D

@Adminiuga, Thanks, I’ll see what the vendor says on Monday and decide if I’ll switch to the YRL256 or stay with the SYDL220. Will report back here when I have the new setup in place. Fingers crossed it works!

Thanks @Adminiuga, I really appreciate the help and advice. I took it back to the store today and they gave me a refund. They’ll check with their supplier to see if they can order in the HA 1.2 version on Monday. If that’s not the case, I’ve been looking at the newer Yale YRM256 with this HA module: https://www.amazon.com/YALE-AYR202-NETWORK-MOD-Yale/dp/B07VWYNR6D
What do you think chances are that that module works with ZHA, if you don’t mind me asking?

Just a final update. I ended up getting the lock and module above and they work great! It pairs easily with Home Assistant, control and sensors work and the battery percentage has gone down about 1% in the space of a week.
The newer lock’s mechanism is much faster as well.
Thanks again for your help!


Elementum 0.1.77 seasons will not download properly anymore

Since the last update to 0.1.77 torrents with seasons will not start with downloading the first episode like before. In fact it downloads everything except the first episode and then times out since it reaches the timelimit for the first episode, which never got downloaded. Single episodes torrents are no problem.
If I then exit kodi and restart it elmentum/burst will then resume the download and fetch the missing episode and I can then watch from the first episode.
Edit: scratch that. Season downloading is broken. It keeps downloading every episode except the one I am trying to watch.

Log file?
(Link how to make it was in issue template)

Also what is you settings regarding download season packs? (E.g. single file/season files/all files).

I usually download whole seasons. So I guess "files/all files ". I actually found a crash log from yesterday that contains all what I described in my previous post. It was quite infuriating since the episodes I wanted to see was the ones that refused being downloaded.
The torrent section said 100% but if I manually play/resume it jumped down to 45% which seemed more true. But did it ever download the whole thing? Nope.
Just tried with the TV/computer in the living room which is still waiting for the last upgrades and no issues there. Works as intended.
kodi_crashlog-20210521_034242.log
I guess from line 426 and onwards.
Hope it helps! I only use elementum and it has beeen the best. Hands down.

@ThurahT
i meant value of setting called "Which files to download" in elementum.
if i am not mistaken, in log i see that you use "Season files" - please confirm this by opening elementum settings in kodi.
"Season files" should download selected file (e.g. s02e01) and all other files belonging to season (e.g. s02eXX).
and you have "Use files" as storage, that is suitable for "Season files".
also would be easier if you would stick to issue template and provided steps to reproduce your issue.
specifically also how exactly you start download of season pack?
in log i can see that you run search for episode s02e04 from trakt show progress and then choose season pack.
so i test the torrent you used with the settings like yours - it works fine.
of course it takes much more time to start playback since you said to elementum to download all files of the season.
but with my connection speed elementum is still able to finish buffering before the timeout.
so, to solve your particular issue, you can:

set "Which files to download" to "Only playback file"
increase "Initial buffering timeout (seconds)" (60s by default)
increase your internet speed

@ThurahT
i meant value of setting called "Which files to download" in elementum.

I had it to playback then I changed that setting around hoping it would fix stuff.

if i am not mistaken, in log i see that you use "Season files" - please confirm this by opening elementum settings in kodi.

Possible. It doesn't matter which I choose. See below.

"Season files" should download selected file (e.g. s02e01) and all other files belonging to season (e.g. s02eXX).
and you have "Use files" as storage, that is suitable for "Season files".
also would be easier if you would stick to issue template and provided steps to reproduce your issue.
Steps:
1: Choose a show.
2: Select a full season
3: Realize 0.0.77 misbehaves.
specifically also how exactly you start download of season pack?
Well, I choose a torrent that is a full season of course. As I have done numerous times before. Then it starts with the first episode and I can usually watch it within 10 seconds of buffering. By the time I've done watching the rest of the season is waiting for me.
in log i can see that you run search for episode s02e04 from trakt show progress and then choose season pack.
so i test the torrent you used with the settings like yours - it works fine.
of course it takes much more time to start playback since you said to elementum to download all files of the season.
but with my connection speed elementum is still able to finish buffering before the timeout.
so, to solve your particular issue, you can either:
1. set "Which files to download" to "Only playback file"

It was set to playback file. Not all files. But it doesn't matter if I choose all files or season or playback. It doesn't start with first/next episode as it used to do before 0.0.77. It just sits there and downloads half of every other file and then tells me 100%. Which is not even true.

2. increase "Initial buffering timeout (seconds)" (60s by default)

I have it set to 60 seconds. I have never even come close to that because before the download started with first episode and I could start watching after ten seconds.

3. increase your internet speed

I think 100/100 is fine.

then i dunno.
i do not see anything that could lead to this issue in 0.1.77 https://github.com/elgatito/elementum/commits/master
also it does work for me with the same torrent that you used.
maybe author will be able to help.

@ThurahT There is nothing to discuss without a proper log file, with enabled debug log level in Elementum (last settings tab).

@elgatito I'll do better next time I file a bug report. I didn't now there were an additional level to the logging. Or, I guess I did, but I forgot a long the way.
Anyway, I pretty sure I managed to fix it. I guess I should have collected the proper logs before hand and then after, but I was just testing things out, and what I did was just clearing all caches and old torrents and restart kodi.
Now seasons work as usual again. I have files set to "playback" and that works as intended. So does "all files" and "seasons" as well. So, I guess I just need to clean out caches and old torrents from time to time. Or between releaeses at least.
I consider Elementum to be the best kodi addon I ever used since I started using it back in I don't know. 2016-17? And I am very happy with its continued existence with patching and bug fixes.
I'm sorry for the noise with this issue I made. I consider it solved and closed.

@ThurahT No problem. If you encounter the issue - you can use Elementum's log uploaded to get log url without need to do something manually.


How can I make same Hero as Buefy website has?

Overview of the problem
Buefy version: [0.5.0]
Vuejs version: [2.1.10]
OS/Browser:Ubuntu 17.04/Chrome
Description
This is not an actual issue but I would like to know if someone can guide me through the same hero as the Buefy website has. Hero-foot is the actual part which I am looking for.
Your ideas are well appreciated. Thanks in advance.

Just check the source files :eyes:
https://github.com/rafaelpimpa/buefy/blob/fc71ace1e17890e1aeb39dfed63ebda3fa106453/docs/pages/documentation/Documentation.vue#L13

I am really new to Vue actually so I need to learn that lil bit . THanks @iwan-wijaya


Using Vite config inside of nuxt.config causes error

Environment
Not sure if this should be a vite or nuxt issue, but posting here for now as it only happens when using nuxt.config.ts
After seeing:
 WARN  Using vite.config.ts is not supported together with Nuxt. Use options.vite instead. You can read more in https://nuxt.com/docs/api/nuxt-config#vite.
I moved my config into my nuxt.config file, however I am getting an error with vite-plugin-vue-inspector which doesn't occur when my vite config is in a separate file:
ERROR:
[오전 9:46:08]  ERROR  Pre-transform error: At least one <template> or <script> is required in a single file component. ~/node_modules/.pnpm/vite-plugin-vue-inspector@5.1.3_vite@5.4.9_@types+node@22.7.6_sass<EMAIL_ADDRESS>
Am I setting this up incorrectly?
Reproduction
https://stackblitz.com/edit/github-dy5mxd?file=nuxt.config.ts
Describe the bug
When using vite: config within nuxt.config.ts, a pre-transform error on Overlay.vue template is seen
Additional context
No response
Logs
No response

Why do you need to specify the Vue plugin? It should come bundled with Nuxt as default.

Why do you need to specify the Vue plugin? It should come bundled with Nuxt as default.

Because I am compiling vue SFC files and Vite doesn't know (by default) how to handle them. If I remove it, I cannot use autoprefixer, and all my templates will be without style.


Have METexpress handle situations where data loading was incomplete

Describe the Enhancement
The database loader (met_db_load.py) on Jet occasionally fails in the middle of loading MODE stat files into the database. I'm working on getting to the bottom of this (Randy suspects the rocoto workflow is not allocating it enough memory), but METexpress needs to gracefully handle situations when this happens. Currently. METexpress throws an error if an object exists in the pairs table but not the single object table (which is impossible if the data is loaded correctly). Instead of an error, it should just return missing data in that case.
Time Estimate
1-2 days

I reloaded all of the GSL MODE data, so the error is at least no longer being thrown (and the data trace is more complete!), but this fix still needs to be included in the next METexpress update.

Have not done this yet but it should only take ~30 minutes to complete and test.

This was resolved by adding the following check:
            # in case loading wend wrong and we don't have all our rows
            if object_row_idx >= len(object_data):
                continue

as long as the index on the mode_obj_single data is not out of bounds (original assumption was that it never would be), METexpress is smart enough to figure out where data is missing, and no error will be thrown.


Networking: Tests: Reduce cyclomatic complexity

Reduce the cyclomatic complexity of the test tools used to
manually setup networking interfaces.
Signed-off-by: Manohar Castelino<EMAIL_ADDRESS>

Coverage increased (+0.02%) to 54.367% when pulling 671aa4f9698c55b163a4844342c5489391608365 on mcastelino:master into 4da2d17b8c55334618cc69d4b5065e9905172f47 on 01org:master.


merge callback args into EventCtx struct

Before
fn wl_output_cb(
    conn: &mut Connection<State>,
    state: &mut State,
    output: WlOutput,
    event: wl_output::Event,
) {
    todo!();
}

After
fn wl_output_cb(ctx: EventCtx<'_, State, WlOutput>) {
    todo!();
}

This is obviously a breaking change and migrating is a bit annoying, but there are several advantages:

Shorter code.
No need to specify the event type (it is derived from proxy type).
EventCtx is #[non_exhaustive] - supplying more information to callbacks will not be a breaking change in the future.

I have no idea why the CI is suddenly failing


fixing anneal rate

Seems like there was a typo in the tau adjustment -- in the current implementation, it goes from 5.0 to 0.5 immediately and stays there.  Compare that to line 25 of Jang's implementation:
https://gist.githubusercontent.com/ericjang/d30ed6e2528594a6b4421f45459abe74/raw/c516f2b767492441eb1b3e7ac83c47334e1094e4/gs-train.py
The current change is closer (though the actual rates might be somewhat different).

cool, thanks!


Optimise ROB

As for now ROB is implemented using array of registers. It would be good to use memory, to reduce ROB cost.

Done in https://github.com/kuznia-rdzeni/coreblocks/pull/655.


Weight/percentage-based events routing

A group function (https://github.com/serverless/event-gateway/issues/295) that has multiple backing functions, each with a "weight" value that determines the proportional amount of traffic each should receive. If all are the same, they all receive requests equally. If one is 99 and another is 1, 99% of traffic will be sent to the one with a weight of 99.

This feature could help support A/B or canary deployments of individual functions. Functions (AWS) could be registered with EG using function alias's in the ARN (...:my-func:live). So there could be an alias for the 'A' deployment and an alias for the 'B' or canary deployment. Your CD pipeline could update the EG config for the group function to set or alter the weighting between 'A' and 'B'.
Having weighted routing in the EG would be MUCH easier than doing seperate API-Gateway deployments and some funcky route 53 routing.

I believe weighted alias routing was a feature announced at reinvent. Any chance and interface for this in serverless may come soon?

http://docs.aws.amazon.com/lambda/latest/dg/lambda-traffic-shifting-using-aliases.html


Simplify the Annotations session

There are too many steps now.. Need to think of a way of making it easier.

Done with the above commits.


Merges Master to Live. See commits for details.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsAuthConfig.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsAuthConfig.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Kubernetes tooling umbrella issue

This lists the improvements we want to do around tooling to improve workflows that involve Kubernetes. Add entries with checkboxes in the list below, and when implementing them, check the box and add a link to the PR that implements that entry.

[ ] Ability to determine Run and Resolution based on pod.

This didn't catch on.


Add info on how to get master and worker IAM accounts.

[#160412476]
Signed-off-by: Carlo Colombo<EMAIL_ADDRESS>

Thank you @leeloodub !


Unwanted caption in picture on Telegram

Using botbuilder 3.6.0.
When sending a simple image (message with no text and one single attachment), on Telegram the message is displayed with an unwanted caption (the picture's filename). The same message is shown correctly (without any text) on Facebook Messenger however.
Code used to send the image:
session.send(new builder.Message(session).addAttachment({
    contentType: "image/png",
    contentUrl: "http://botify.it/codyquiz/riddles/1.png"
}));

Shown on Telegram as:

(Unwanted caption underlined in red.)
Is there a way to prevent the caption from showing up?

Also, on Skype the same image is shown with a bold “Picture” title:

Adding eric who can confirm but that is most likely the default behavior of Telegram & Skype if you don't provide a title.  May not be anything we can do about that.

This is the default behavior of Telegram for images. You can work around it by sending the image as a hero card:
    var card = new builder.HeroCard(session)
        .images([builder.CardImage.create(session, 'http://botify.it/codyquiz/riddles/1.png')]);
    var msg = new builder.Message(session)
        .attachments([card]);
    session.send(msg);

Closing this for now. Please feel free to add further comments.


Support Twitch API v5

Twitch API v5 was just supported,. A key change will be moving from username to user ID. This impacts a good amount of TwitchApi class in TwitchLib.

As a side note, documentation will arrive for v5 in mid-December, so a majority of work for this issue will need to wait a few weeks.

Nice! Keep up your good work. 👍

Initial support: 3fce04c2e8e8777239b1920494744be07c3823c6

Supported.


⚠ Bofrost.be has degraded performance

In 310dcdd, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1411 ms

Resolved: Bofrost.be performance has improved in 8551ab1 after 6 minutes.


Implement/fix JSON to XML converter

Description:
Json to xml conversion is temporarily disabled while implementing new xml proposal, we need to rewrite this convertor for new node structure.
Note: this does not affect main development branches
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

org.ballerinalang.jvm.JSONToXMLConverter is a unused class and will be removed.
org.ballerinalang.stdlib.xmlutils.JSONToXMLConverter is also unused and will not be deleted (the syntax issues in this class is already fixed in https://github.com/ballerina-platform/ballerina-lang/pull/20915)


update readme because instructions don't work

So here is what I did:
git clone git@github.com:euske/pdfminer.git
10378  cd pdfminer
10379  ls
10380  sudo python setup.py install

//Then
python main.py ~/Desktop/MyFile.pdf

➜  pdfminer git:(master) ✗ ls
MANIFEST.in Makefile    README.md   build       cmaprsrc    docs        pdfminer    samples     setup.py    tools

python: can't open file 'main.py': [Errno 2] No such file or directory
Am I missing a step here? Is this the correct repo to clone?

main.py is not in pdfminer, it's in pdf-to-markdown. I've made README.md clearer in 48548046f93.


No information on deleting datasets

I created a dataset with the wrong type. I want to recreate it with the same name but the correct type. However, I can't find any information on how to delete a dataset. The linked docs page mentions archiving but not how to delete datasets. I feel this should be documented somewhere.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: cf5a19a0-c37e-4567-0c30-7efe1c433dfb
Version Independent ID: 8c4e79d0-0f84-3a28-bfb4-9f972e02a37f
Content: az ml data
Content Source: latest/docs-ref-autogen/ml/data.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Thank you for opening this issue, we will look into it.

@davystrong You can unregister data assets and archive jobs, but these operations don't delete the data. To entirely remove the data, data assets and job data require deletion at the storage level. Storage level deletion happens in the portal.
As an initial step, traverse to ML Studio -> Select Data under Assets -> Select the Assets you wish to delete -> Click on the Assest
The asset contains information as shown below. Click on View in Azure portal browse as highlighted in the image.

View in Azure portal redirects to the path where the data asset is located in storage account. Click on Delete. This deletes the asset.
As per this document, its mentioned that you can export or delete your workspace data using either the portal graphical interface or the Python SDK.
If you want to do via Azure CLI, its bit of complicated process.

First, you need to identify the datastore using the path where the data asset is located. You can use az ml data show  command.
Using datastore , identify the account name and container name where data assets is stored. You can use az ml datastore show command.
Traverse to the storage account and identify the container where data assets are stored. The exact path can be identified from the first step. You can use az storage blob delete command to delete the data asset.

The above information is shared based on the assumption that you are using version 1 API to create the data asset. I assume that its same process for version 2 as well. Do let me know if that does not work for you or if you have further questions.

@davystrong I am bit confused about your request. The Archive button does what you are asking for, it removes the link between the data asset and underlying storage.

Hi, I'm also experiencing the same issue where I have a v2 data asset that was named incorrectly, but I want to rename it without having to delete the underlying data.

@ccaitlien this isn't the same issue. Archiving a v2 asset doesn't delete the underlying data.

@davystrong I'm aware, let me clarify my issue- I've created a v2 data asset when I meant to create a v1 dataset. I want to delete the v2 data asset and create a new v1 dataset with the same name. However, archiving a v2 asset doesn't delete the underlying data, so I'm unable to create a v1 dataset with the same name since ML studio doesn't allow for duplicate names. There should be the ability to rename data assets or change their type.


Minor typo ZWESI00 instead of ZWESIS01

This section refers to ZWESI00 instead of ZWESIS01
https://docs.zowe.org/stable/user-guide/configure-xmem-server/#summary-of-cross-memory-server-installation
For example,
PPT PGMNAME(ZWESI00) KEY(4) NOSWAP
should be
PPT PGMNAME(ZWESIS01) KEY(4) NOSWAP

Thank you for reporting this issue to us! Would you please review this PR#2637 and let me know if it is good to go? Thanks


Create  Footer 6(White, Blue, Dark)

@Rajdip019 Please assign this to me, I've already made it just need to raise PR

Done
#879  (White)
#881  (Blue)
#882   (Dark)


[Bug] 在折线图中。当线条数大于或等于3时，重新setOption隐藏其中一条线条并放大和缩小图表。会有重影。

Version
5.4.2
Link to Minimal Reproduction
https://codesandbox.io/s/focused-bouman-lqvlpy?file=/src/index.js
Steps to Reproduce
1:示例设置了setTimeout;你需要在5秒内放大和缩小图表。
2:5秒后setOption图上会有重影。
Current Behavior
有重影
Expected Behavior
没有重影
Environment
- OS:Windows
- Browser:Chrome 114.0.5735.199
- Framework:Vue@2

Any additional comments?
No response

set axisPointer: {show: false}

Also cant reproduce on a minimal example: link

@MatthiasMert I need axisPointer is true.

I agree with @MatthiasMert, there is no ghosting problem.
Please set lineStyle: { color: 'red',...} on the third series in your code to see better.

Just to be clear. In the given codesandbox if you use the zoom before the timer runs out, I experience the mentioned ghosting issue.
I just couldnt reproduce it on a minimal example. So if @shArpyYAo would supply a more concise example it would be easier to find out whats causing it.

ok, I see the problem now, it's chart.clear(); - remove it and the chart will update with only two lines instead of three.

@MatthiasMert Hi, I've changed my example to remove the extra data and instead use a for loop to generate the data.Please take a look.thank.

@helgasoft Great. I saw the problem disappear.but i needchart.clear() to clear something. why is chart.clear() problematic


We need alert suppression for X minutes to reduce but not completely turn off noise from multiple alerts in a single day

The shortest suppression duration is 1 day, this is not going to work for most suppression scenarios. If I have an alert that is triggering multiple times a day, it will be silenced for the entire day. We should have a configurable suppression duration to allow us to quiet multiple alerts from the same sourced event or incident, but not for an entire day.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f826c77e-a9c8-5baa-af70-690e8383372b
Version Independent ID: df6cea2c-8b90-706a-2dfd-041026e7396d
Content: Action rules for Azure Monitor alerts
Content Source: articles/azure-monitor/platform/alerts-action-rules.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @anantr
Microsoft Alias: robb

Thanks for your comment. We are actively investigating and will get back to you shortly. Thanks for your patience.

@the-blesss Thanks for reaching out! Perhaps I am missing out in something you have commented. Here are my comments about the request.

you can suppress the alert for duration which you want. I tried suppression of alerts for a duration of 15 min.Here is screenshot for the same.

You can suppress alerts from same source using filter option. The snapshot below shows the list of filter conditions that are available.

We will close the issue now. If you have further questions , please respond, we will be very glad to assist you.In case, you would like to provide feedback or request on additional features, i would recommend you to provide here.

My issue is that for a reoccurring alert, we have been getting multiple alerts triggered with a single action/change or similar action. I don't know the "schedule" of when those actions will occur, so I cannot use the schedule option with the granular time. If I could suppress the same alerts for 15 minutes, from whenever it is triggered, I would only get one alert notification, verses the 3-5 I'm getting now.

@the-blesss The option "Suppress Alerts" is only available for Log alert rules. For metric alerts , to suppress you have the only option to use "Suppression Config" as mentioned in previous comment.
For your reference, here is a snapshot.


[RFE] alert user when posting as3 to 'common' tenant

It was suggested to provide a pop up or log message the remind users to not deploy as3 to the common tenant.   We understand that sometimes this may be necessary, so a warning message but continue processing, is probably a good middle ground.

Got details from the originator of this idea that things are good the way they are and we can revisit this in the future.  closing for now


Control flow analysis for array construction

This PR introduces control flow analysis for array construction patterns that originate in an empty array literal (x = []) followed by some number of x.push(value) or x[n] = value operations.
A let, const, or var variable declared with no type annotation and an initial value of [] is considered an implicit any[] variable. When an implicit any variable (see #11263) or implicit any[] variable is assigned an empty array literal [], each following x.push(value) or x[n] = value operation evolves the type of the variable in accordance with what elements are added to it.
function f1() {
    let x = [];
    x[0] = 5;
    x[1] = "hello";
    x[2] = true;
    return x;  // (string | number | boolean)[]
}

function f2() {
    let x = [];
    x.push(5);
    x.push("hello");
    x.push(true);
    return x;  // (string | number | boolean)[]
}

function f3() {
    let x = null;
    if (cond()) {
        x = [];
        while (cond()) {
            x.push("hello");
        }
    }
    return x;  // string[] | null
}

An array type is evolved only by operations on the variable in which the evolving array type originated. When an evolving array type variable is referenced in an expression, its type is "fixed" and cannot be further evolved.
function f4() {
    let x = [];       // x has evolving array type
    x.push(5);
    let y = x;        // y has fixed array type
    x.push("hello");  // Ok
    y.push("hello");  // Error
}

Similar to implicit any variables, control flow analysis is unable to determine the actual types of implicit any[] variables when they are referenced in nested functions. In such cases, the variables will appear to have type any[] in the nested functions and errors will be reported for the references if --noImplicitAny is enabled.
function f3() {
    let x = [];  // Error: Variable 'x' implicitly has type 'any[]' in some locations where its type cannot be determined.
    x.push(5);
    function g() {
        x;    // Error: Variable 'x' implicitly has an 'any[]' type.
    }
}

Will this affect a problem (#11082) I submitted earlier? This sounds like its different enough from my problem but wanted to check if there is any overlap, thanks!

@zenmumbler No, this PR doesn't affect the issue in #11082.

@mhegazy Want to take a look before I merge this?

With the latest commits, when an evolving array has no x.push(value), x.unshift(value) or x[n] = value operations in any control flow path leading to the current location, its type is implicitly any[]. Thus, any reference to such an empty evolving array will produce an error with --noImplicitAny:
function f1() {
    let a = [];
    if (cond()) {
        a.push("hello");
    }
    a;  // string[]
}

function f2() {
    let a = [];
    a;  // any[], error with --noImplicitAny
}

Note that references to the length property are always allowed since they don't depend on the element type of the array:
function f3() {
    let a = [];
    while (a.length < 10) {
        a.push("test");
    }
    return a;  // string[]
}

@mhegazy Latest commits should solve the issue we discussed yesterday.


Unified inputs for grayscale ops and transforms

Related to #2292
Description:

Unified inputs for grayscale op and transforms: GrayScale, RandomGrayscale, F.rgb_to_grayscale.
Modified F_t.rgb_to_grayscale implemention to match better PIL implementation

Side effect: this breaks test_adjustments => we need to update this test according to how we test results in test_adjust_gamma.

Deprecated F.to_grayscale in favor of F.rgb_to_grayscale

EDIT:

uint8 type is transformed as L = (19595 * r + 38470 * g + 7471 * b + 2 ** 15) / 2 ** 16
How to transform floating point ? -> (0.299 * r + 0.587 * g + 0.114 * b)

Unlocks #2566 #2595

@pytorchbot retest this please

@fmassa I updated the PR. Changes:

F.to_grayscale works on PIL Image and goes directly to F_pil.to_grayscale.
F.rgb_to_grayscale works on both: PIL images and Tensors and dispatch to F_pil.to_grayscale or F_t.rgb_to_grayscale
no more deprecations
reverted to unique manner to compute F_t.rgb_to_grayscale on float/uint8 tensors and added other review comments
kept num_output_channels in F.to_grayscale, F.rgb_to_grayscale. We can iterate on that.

Let me know if it corresponds to your ideas.


Ant convert gradle feasure

convert ant to gradle

Curious. Why a new PR?

i'm sorry to new PR.I found old pr has some information i won't commit.
except azkaban-common.jar,azkaban-web-server.jar,azkaban-exec-server.jar is not in public repository,i find  teradata-connector-1.4.2.jar etc also are not in.how are we manager those jar?

i agree with you break existing code.
The idea is  project azkaban-plugins should contain only the plugin.Common module hadoopsecuritymanager hadoopsecuritymanager - common, hadoopsecuritymanager - yarn should be placed in azkaban-common.

about breaking existing code,can you talk about yout ideas?

We cannot commit something that will break existing stuff. You can put all of these old jars in a single directory like rootproject/lib. The switch to gradle should build the same artifacts but probably with minor changes like adding version numbers, etc.

@suvodeep-pyne ok


wrong behavior when linking libraries on android

🐛 Bug Report
when linking libraries  it uses backslash not the division slash in settings.gradle
so that i have to change it every time i link new library

To Reproduce

react-native link any library
go to android/settings.gradle

Expected Behavior
uses division slash
Environment
System:
OS: Windows 10
CPU: (4) x64 Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz
Memory: 1.25 GB / 7.95 GB
Binaries:
Yarn: 1.13.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-182.5<IP_ADDRESS>64788

it was solved in version 0.59


Could not get models from the server

My actions before raising this issue

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

Hello. I followed the steps to deploy nuclio dashboard
However. I got the error messages Error: Request failed with status code 502. "502 Server Error: Bad Gateway for url: http://nuclio:8070/api/functions".  when I entered into localhost:8080
Besides, When I entered into localhost:8070, I also got two error messages as the pictures below.
How should I do to deal with the problems ?
Thank you for your help in advance.

I'm experiencing the same problem.

I see an error:

Error - Get "https://github.com/nuclio/nuclio-templates.git/info/refs?service=git-upload-pack": dial tcp: lookup github.com on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:49724-><IP_ADDRESS>:53: i/o timeout

Try to wait for some time and run dashboad again, maybe it is a temorary network issue
Address the issue to nuclio community

Excuse me @bsekachev
Is it possible that I'm in the branch v2.4.1 instead of master so I could not get "https://github.com/nuclio/nuclio-templates.git/info/refs?service=git-upload-pack" ?

@ShangWeiKuo
I hardly think it depends on your branch.

I got the same issue on CVAT version v2.5.2. Any pointer?


this repository for easy downloading videos from pornhub

this repository for easy downloading videos from pornhub

it is written in python and is designed to work through a console application


Upgrade to use APIv2

Upgrade to use APIv2 in order to ensure proper compatibility with newer releases of Defect Dojo.

Hey @adracea
I was wondering if you had the chance to take a look at this?
Cheers,
fred

Hey @adracea
I was wondering if you had the chance to take a look at this?
Cheers,
fred

Hey @madchap  I was looking into this at some point but I do believe I may have lost the progress I had back then, I'll try to find some free time for it but if someone else can accomplish this sooner, I'd say it's up for taking .

It's not yet a PR but an issue. The Burp plugin does not work with apiv2 and apiv1 is now deprecated.

@madchap  @adracea I have upgraded the plugin to support API v2, Could you please test it in your end https://github.com/ihebski/Burp-Plugin
I have submitted a pull request for this issue.
Thanks

I'll give it a shot soon :+1: Thanks for that contribution!


Domain names and IP ranges relationship

What's the relationship between the DNS domain names and the subnets specified near them? Do they complement one another? Or this means that the DNS names resolve to IP addresses in these subnets?
For instance:
*.protection.outlook.com
<IP_ADDRESS>/15, <IP_ADDRESS>/16, <IP_ADDRESS>/14, <IP_ADDRESS>/32, <IP_ADDRESS>/17, 2a01:111:f403::/48
Does this mean that any hosts under *.protection.outlook.com will always resolve to these 6 ranges? Or this means that I must open access on my firewall/proxy BOTH to the hosts under *.protection.outlook.com AND to all these ranges?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 077406d8-bff1-496e-3ea2-b38558fd9355
Version Independent ID: 57db3dec-2250-2dee-fd1a-ec6656911798
Content: Office 365 URLs and IP address ranges
Content Source: Enterprise/urls-and-ip-address-ranges.md
Service: o365-administration
GitHub Login: @LauraWi
Microsoft Alias: laurawi

Hi @cat-mucius Does this FAQ entry address your question: https://docs.microsoft.com/en-us/office365/enterprise/managing-office-365-endpoints#some-office-365-urls-point-to-cname-records-instead-of-a-records-in-the-dns-what-do-i-have-to-do-with-the-cname-records

Thanks, but not really - I wasn't asking about CNAMEs. But this one maybe does:

"When using a PAC file for direct egress of vital Office 365 network traffic, you also need to allow connectivity to the IP addresses behind these URLs on your network perimeter firewall. This is done by fetching the IP addresses for the same Office 365 endpoint categories as specified in the PAC file and creating firewall ACLs based on those addresses."

So as I understand:

If I don't use direct access (all requests pass through proxy), it's enough to configure the proxy to allow traffic to *.protection.outlook.com. Hosts under this domain will always resolve to IP addresses in these ranges, so there's NO NEED to allow explicitly access to these ranges on the proxy.
However, if I route traffic there directly via a firewall (which cannot be set with wildcard domain such as *.protection.outlook.com as destination), then I need to configure the firewall to allow traffic to these subnets:
<IP_ADDRESS>/15, <IP_ADDRESS>/16, <IP_ADDRESS>/14, <IP_ADDRESS>/32, <IP_ADDRESS>/17, 2a01:111:f403::/48

Is my understanding correct?

Since I'm monitoring this topic for a direct who's on leave (I am not a networking SME), I posed this one to my engineering contacts for this space. His answer: "Yes, that’s the right idea. The underlying assumption here, which is pretty common in enterprises who use proxy servers, is that the client is blocked from direct Internet access by an IP firewall and the proxy server is not blocked. This means that by forwarding the traffic to the proxy server and if the proxy server allows the connection, there’s no additional IP firewall ACL’s required."

Ok, Laura, thank you!

We've run in to this same issue just yesterday.
We added all of the IPs listed on our firewall for Exchange Online, however when running a connector validation, it was connecting from xxxxxxxxxx.eop-gbr01.prod.protection.outlook.com (<IP_ADDRESS>) which was coming from a completely different IP address than what is listed on this page.

@nitvit610, that's strange, because according to https://bgp.he.net/ip/<IP_ADDRESS>, the IP address belongs to some telecommunications company "ITS Technology Group Limited". They don't offer CDN, so it doesn't seem likely that Microsoft service would be frontend by their IP.
Maybe it's your some local DNS issue?

@cat-mucius potentially. I'm not a network engineer myself so this is only what they told me (and what I could see from the error message).
I'd been told that we'd added all the IPs under the Exchange Online section, yet still weren't able to connect.
We ended up fixing it by opening ports 25 & 443 to all IP ranges but obviously this is not ideal.

So what's the conclusion?  Do we need to allow both the wildcard domain names and the IP addresses or is it enough to allow the wildcard FQDNs?

If I understood @LauraWi 's response correctly, FQDNs are enough (accessed via proxy).
My experience so far supports that, Office sites worked pretty well, but I didn't test their functionality in depth, just "touched the surface".


C++ nested try/catch: Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled. ESP-IDF v4.4 / v5.0 (IDFGH-6907)

Environment

Development Kit:      none
Module or chip used:  ESP32-WROOM-32 (tested with different modules)
IDF version: v5.0-dev-1318-g34c21cb693
Build System:         idf.py
Compiler version: (crosstool-NG esp-2021r2) 8.4.0
Operating System:     Linux
Using an IDE?: No
Power Supply:  USB

Problem Description
Nested exceptions + rethrow don't work if the outer try/catch has more than 2 catch blocks, so if } catch(exceptiontype1) { is removed the test code doesn't throw an excption/abort
try {
   try {
     throw some_exception();
   } catch(...) {
     throw;
   }
} catch(exceptiontype1) {
} catch(exceptiontype1) {
} catch(...) {
}
printf("try/catch test done");

Expected Behavior
Normal C++ exception handling; Example code seems to work with only 2 catch() blocks!
Actual Behavior
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
Steps to reproduce
slightly modified hello-world example, hello_world_main.c renamed to hello_world_main.cpp; as well as in CMakeLists.txt; idf.py menuconfig -> Compiler options -> Enable C++ exceptions
see C++ code
Code to reproduce this issue
#include <stdio.h>
#include "sdkconfig.h"
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "esp_system.h"
#include "esp_spi_flash.h"

#include <stdexcept>

extern "C" void app_main(void)
{
printf("Hello world!\n");
printf("ESP_IDF Version: %s\n", esp_get_idf_version());
try {
    try {
        printf("try / try\n");
        throw std::runtime_error("test runtime error");
    } catch(...) {
        printf("catch1\n");
        throw;
    }
} catch(const char *e) {
    printf("~~~~~ cought outer exception char * %s ~~~~\n", e);
} catch(const std::exception &e ) {
    printf("~~~~~ cought outer exception %s ~~~~\n", e.what());
} catch(...) {
    printf("~~~~~ all caught ~~~~\n");
}
printf("try/catch test done\n");

sleep(10);
abort();
// rest of hello_world.c

hello_world_main.cpp.txt
Debug Logs
Hello world!
ESP_IDF Version: v5.0-dev-1318-g34c21cb693-dirty
try / try
catch1
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.

Core  0 register dump:
PC      : 0x4000127a  PS      : 0x00060030  A0      : 0x800d7270  A1      : 0x3ffb5840
A2      : 0x3f406b74  A3      : 0x00000000  A4      : 0x00060c20  A5      : 0x00060c23
A6      : 0x00000031  A7      : 0x3ffb59f0  A8      : 0x00000063  A9      : 0x3ffb5820
A10     : 0x3ffb2728  A11     : 0x3ffb2728  A12     : 0x00060c20  A13     : 0x00060023
A14     : 0x432b2b00  A15     : 0x3ffb5a00  SAR     : 0x00000019  EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000000  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xffffffff

Backtrace:0x40001277:0x3ffb58400x400d726d:0x3ffb5850 0x400e6e37:0x3ffb5870 0x400d7f51:0x3ffb5890 0x400e6e03:0x3ffb58b0 0x400d7629:0x3ffb58e0 0x400d8589:0x3ffb5950 0x400d8747:0x3ffb5a00 0x400d6f3d:0x3ffb5aa0 0x400d4ecc:0x3ffb5ac0 0x400e72dc:0x3ffb5ae0 0x40087ac9:0x3ffb5b00
0x400d726d: std::type_info::operator==(std::type_info const&) const at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/typeinfo:124
 (inlined by) std::type_info::__do_catch(std::type_info const*, void**, unsigned int) const at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/tinfo.cc:72

0x400e6e37: __cxxabiv1::__pbase_type_info::__pointer_catch(__cxxabiv1::__pbase_type_info const*, void**, unsigned int) const at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/cxxabi.h:307
 (inlined by) __cxxabiv1::__pointer_type_info::__pointer_catch(__cxxabiv1::__pbase_type_info const*, void**, unsigned int) const at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/pointer_type_info.cc:51

0x400d7f51: __cxxabiv1::__pbase_type_info::__do_catch(std::type_info const*, void**, unsigned int) const at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/pbase_type_info.cc:100
 (inlined by) __cxxabiv1::__pbase_type_info::__do_catch(std::type_info const*, void**, unsigned int) const at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/pbase_type_info.cc:32

0x400e6e03: get_adjusted_ptr(std::type_info const*, std::type_info const*, void**) at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/eh_personality.cc:228

0x400d7629: __gxx_personality_v0 at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/eh_personality.cc:595

0x400d8589: _Unwind_RaiseException at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/libgcc/unwind.inc:118

0x400d8747: _Unwind_Resume_or_Rethrow at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/libgcc/unwind.inc:264

0x400d6f3d: __cxa_rethrow at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:126

0x400d4ecc: app_main at /home/chris/bin/esp/esp-idf/examples/get-started/hello_world/build/../main/hello_world_main.cpp:30

0x400e72dc: main_task at /home/chris/bin/esp/esp-idf/components/freertos/FreeRTOS-Kernel/portable/port_common.c:127 (discriminator 2)

0x40087ac9: vPortTaskWrapper at /home/chris/bin/esp/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:134

Other items if possible

[x] sdkconfig file (attach the sdkconfig file from your project folder) sdkconfig.txt
[ ] elf file in the build folder (note this may contain all the code details and symbols of your project.) - can be provided if necessary
[ ] coredump (This provides stacks of tasks.)

Related to #5360 possible regression caused in fixes there.

Hi @ferbar, given that the backtrace points to std::type_info, could you please try enabling CONFIG_COMPILER_CXX_RTTI as well?

@igrr, you are right, this doesn't crash:
Hello world!
ESP_IDF Version: v5.0-dev-1318-g34c21cb693-dirty
try / try
catch1
~~~~~ cought outer exception test runtime error ~~~~
try/catch test done

However the arduino libraries are compiled without RTTI, so changing the CONFIG_COMPILER_CXX_RTTI isn't that easy.

@ferbar log an issue and/or submit a PR to https://github.com/espressif/esp32-arduino-lib-builder so that RTTI can be evaluated for enabling in Arduino.

(off topic) @atanisoft it's for this: https://github.com/ferbar/btcontrol/tree/master/control-esp32
I think RTTI is disabled intentionally in the arduino libs, I would not change it :-) Since this bug can be easily reproduced I would prefer a bugfix in unwind.inc os somewhere around.

@ferbar @atanisoft C++ exception handling should generally work without RTTI enabled. Hence, enabling RTTI is more a workaround. I'll take a look at this by the end of this week or the beginning of next week.
In GCC, C++ exceptions and RTTI both use the same system to recognize C++ types, hence there might be some bug with correctly excluding the RTTI-based parts while still retaining the parts used by C++ exceptions.

@ferbar I've taken a look last week but couldn't find out the root cause so far. We are suspecting some kind of compiler bug or a bug in our linker scripts or the linker itself. In particular, if you remove the second printf line printf("ESP_IDF Version: %s\n", esp_get_idf_version());, then the program runs fine again, even if you just print a simple string.
We need further investigation for this.

The issue does occur on all Xtensa architectures. On ESP32-C3 (RISC-V architecture), this problem does not occur with aforementioned code.

@0xjakob I didn't see the printf thing when I was testing. Looks as if there is something with the stack, maybe I found an easier way to reproduce the issue:
printf("string");
printf("string");
nested_try_catch_block

=> works
void *n=NULL
printf("string");
printf("string");
nested_try_catch_block
printf("test done");
printf("string %p", n);  // <- some usage of n that it doesn't get optimized out.

=> does NOT work

@ferbar Sorry for the long turnaround, but this issue took a while to investigate. I opened a bug on GCC for this since it looks like an issue in libsupc++ which is part of libstdc++.
BTW, a minimal reproducer would be:
#include <cstdio>
#include <stdexcept>

int main(int argc, char** argv) {
    try {
        throw std::runtime_error("test runtime error");
    } catch (const char *e) {
        printf("~~~~~ cought outer exception char * %s ~~~~\n", e);
    } catch (const std::exception &e) {
        printf("~~~~~ cought outer exception %s ~~~~\n", e.what());
    }
}

and then shuffle some printf()s around until you get the error. I.e., you don't need a nested try-catch, the important bit is that you have a catch statement with a pointer type as argument (const char* in the example) and a non-pointer type exception passing by (std::runtime_error in the example).

OMG thanks a lot!
If you still need to analyze SEGVs on x86 maybe valgrind can help you.

@ferbar We merged the new toolchain with the fix for this bug (among other things) into master. You shouldn't be able to observe this particular bug anymore with the newest toolchain (2022r1). There's a slight caveat, though: catching an exception of pointer-to-member type will not work anymore if the standard library without RTTI is used. It's a consequence or rather tradeoff of the (trlsyibrly easy) fix. If catching this type of exception is unavoidable, then a standard library with RTTI has to be used. However, I don't think pointer-to-member types are used that often. Please let us know if there are any further problems related to this issue, otherwise we'd like to close it.

@ferbar I'm closing this issue for now. We'll backport the fix to the older toolchains in the near future. If you still observe the bug on current master, please let us know!

Thanks, my test code is working as expected


Allow replay without exiting the program after a game over

I think it would be useful to be able to replay without exiting the program after a game over. This allows you to skip the display time of copyright.
I create an Issue as you might want to implement this. I will contact you before I start the implementation.

Yes. Thank you very much!

I'm trying to check the guideline and imitating the game followed by this guideline.
The games I often refer to are as follows (you know)

Tetris 99
tetris.com

Do you think it is needed to implement?
The current version starts up so fast that the players don't have to wait.

#41 needs to measure the sleep runtime, so I think it might take longer on startup. (I was thinking of measuring the sleep runtime when the logo is displayed.)
However, I still don't know how #41 will turn out, and I might be able to measure it during "ready", so I think it's enough to think about it later.
Let's close it.


added marketing email api modules

Added these marketing email api modules:
List
Category
Recipients

I believe this is out of date against master and latest api, but please comment/reopen if I've got that wrong!


Proposal: Add registry login command to ofc-bootstrap

It would be great to be able to provide a command to create the config.json registry secret file using ofc-bootstrap. Some users have the secrets helper installed by default with docker and the login command stores the secrets outside of the file.
Expected Behaviour

A user should be able to run ofc-bootstrap --registry-login with --username --password-stdin (or --password) and optionally --url to generate the registry config file in ./tmp/config.json (create if not exists)
Current Behaviour

No checks (pending #125 where there is a check being added) on the file at the moment, so if a user has incorrectly setup the file then the deployment happens, creates a bad secret, and then cant pull any functions.
Possible Solution

implement a --registry-login command that creates a valid file in ./tmp/config.json for the supplied url (or docker's default https://index.docker.io/v1/  if no url provided)

I think it would be a sub-command docker-login or registry-login or generate registry-login
Then the server ARG would be needed and like you say --username. I think only having --password-stdin is fine.
Output file should perhaps be in the same folder by default? Not sure.

Please go ahead with this. It doesn't actually have to validate the user's password, just generate a base64-encoded Docker config json file.
Another thought is what we can do for AWS ECR users, we could just take different flags for them perhaps and generate the equivalent file.

This is a good idea, this part definitely slowed me down when I was trying the bootstrap.  I think it might actually be ok to have a dedicated subfolder for credentials and other custom fields.  We can easily ignore the whole folder and be certain it is never committed to a repo

@csakshaug has some ideas about secret management too

derek assign: me

Derek assign: me

Also / can take the place of the text Derek


CliRunner doesn't call group callback

It seems that a group's main callback isn't called when a subcommand is invoked using CliRunner. Given
import click
from click.testing import CliRunner

@click.group()
def main():
    click.echo('Hello')

@main.command()
def hello():
    click.echo('World!')

runner = CliRunner()
result = runner.invoke(hello, [])
print result.output

I would expect the output to be
Hello
World!

However, I get
World!

instead.
Replacing the last 3 lines of the script with main() and calling the script with a single hello argument yields the expected result.
This is on Python 2.7 using click 4.0.

It seems that result = runner.invoke(main, ['hello']) works as expected.


Update README.md

Updated the outdated link to the ESMF code

This updated link cannot access. Maybe it more stable replaced by the main port: https://github.com/esmf-org/esmf?
Yes @Jipingnersc that is better, I changed the link.


Inverted hexagrams

I thought it was worth noting that the ‘binary’ sequence that is followed here is vertically inverted from the way it is represented in traditional sources.
See, for example, the diagram sent from Bouvet to Leibniz, running ䷁, ䷖, …

It would also be fun to have the ‘King Wen’ sequence available 😉

Noted...


Issue with Svelte Sonner

Describe the bug
Installing and then running my project displays the following error after installing svelte-sonner.
I'm doing the below in my +layout.svelte file :
import { Toaster } from '$lib/components/ui/sonner';
<Toaster />

It does seem to be the import that is causing the problem. I'm using svelte-5 and had to use --force to install it via NPM. Any advice ?

Reproduction
<script>
	import { Toaster } from 'svelte-sonner';
</script>

<Toaster />

<div class="max-w-6xl mx-auto h-[100vh]" class:hidden={hidden}>
	<slot />
</div>

Logs
No response
System Info
System:
    OS: macOS 14.2.1
    CPU: (12) arm64 Apple M2 Max
    Memory: 53.70 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.6.1 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 10.2.4 - /usr/local/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 124.0.6367.92
    Safari: 17.2.1
  npmPackages:
    @sveltejs/kit: 2.5.5 => 2.5.5
    bits-ui: ^0.16.0 => 0.16.0
    cmdk-sv: ^0.0.13 => 0.0.13
    formsnap: ^0.4.3 => 0.4.3
    lucide-svelte: ^0.368.0 => 0.368.0
    mode-watcher: ^0.2.2 => 0.2.2
    svelte: ^5.0.0-next.55 => 5.0.0-next.55
    svelte-sonner: ^0.3.22 => 0.3.22
    sveltekit-superforms: ^1.13.4 => 1.13.4

Severity
blocking an upgrade

This issue isn't related to shadcn-svelte based on the stack trace. https://github.com/wobsoriano/svelte-sonner instead.

Hey, @vexkiddy
IIRC, when this happened to me, killing the dev server and restarting it solved the issue for me. 🤷♂
Wdyt?

@shyakadavis thanks for the tip! that worked :D


More interface fixes

Put proper types in the exported create function instead of anys.
Properly export the Cache type.
Export PostgresBackendOptions.
Temporarely make CoreBackend.connection public because the queue requires access to it.

Change-type: major
Signed-off-by: Carol Schulze<EMAIL_ADDRESS>

@balena-ci I self-certify!


feat(authorize): provide meaningful error when room is missing

Solves part of https://github.com/liveblocks/liveblocks/issues/331
Next step: throw a meaningful error when result of auth in createClient is missing {token: "xxx"}

Additionally, a check could be added in @liveblocks-client for a missing actor in the token


Details pane loads slowly on mobile firefox

https://files.catbox.moe/m2jttu.mp4

Chrome is fine, this only happens on Firefox Nightly.
URL fragment is changing instantly but the details pane /  preview card highlight isn't.

Suspicious timing, details pane / preview card highlight seem to wait for Button ripple animation

Maybe a mui bug
https://github.com/mui/material-ui/issues/12667


Server-specific commands always visible

Steps to reproduce:

Open kak;
Type :ccls;
Observe the autocompletion containing commands that are only relevant for C/C++/etc. projects, and only with CCLS installed.

Same with clangd, ejdtls etc.

All kakoune commands are always visible. Ideally they would hide themselves depending on the context but they don't.

Not true. Try launching kak in tmux and outside of it, for example.

@rouanth You are correct about tmux -- thanks for the counterexample.
Let me modify my statement then: people could write define-commands to be context sensitive i.e. only be visible in appropriate situations but generally I don't see it happen very much.

@rouanth You are correct about tmux -- thanks for the counterexample.
Also one more thing occurred to me. In the case of tmux being present or not, that is not a dynamic property. My guess is that when kakoune starts up, it checks for the presence of tmux and then define-command tmux specific commands (or not).
Knowing when to show a specify command like clangd-switch-source-header is a more dynamic property. You should display this command only when the filetype of a buffer is C/C++ source/header perhaps.
In other words, we just could have define-command -override -hidden clangd-switch-source-header ... when you want to hide it and -override without the -hidden to unhide it. I wonder how practical that is or if there is a smarter way to do this. This is an interesting Kakoune problem to me!

My guess is that when kakoune starts up, it checks for the presence of tmux and then define-command tmux specific commands (or not).

This is more or less the case. More accurately, the commands are defined in a module (in rc/windowing/tmux.kak), and the module is imported only if tmux is detected (in rc/windowing/detection.kak). The same is performed for command available for specific filetypes (see rc/tools/python/jedi.kak for an example; you're interested in require-module and provide-module at the top).

I wonder how practical that is or if there is a smarter way to do this.

Looks like the idiomatic way to do this is to define a module (say, lsp-ccls) with the commands that should be unavailable sometimes and only import it if the file is in the C family.

Looks like the idiomatic way to do this is to define a module (say, lsp-ccls) with the commands that should be unavailable sometimes and only import it if the file is in the C family.

I'm not sure this approach would work in the way you we want. Because once imported, if you open another file which is not a part of the C-family the command will still be available in the menu!
We would need to do the define-command -override -hidden ... trick to hide the command. And override again, without -hidden when we want to show it...

Looks like the idiomatic way to do this is to define a module (say, lsp-ccls) with the commands that should be unavailable sometimes and only import it if the file is in the C family.

I'm not sure this approach would work in the way you we want. Because once imported, if you open another file which is not a part of the C-family the command will still be available in the menu!

It's still good enough for many cases: it gets rid of most unnecessarily eager script evaluation, which I think is the main point of modules.
I have considered using a module for all of kak-lsp but it probably won't improve much, because we don't have heavy-weight initialization anyway, and users already load us explicitly, unlike some standard scripts.
A lsp-ccls module sounds promising, but we'd need a hook that loads the module when we first open a C/C++ file and ccls is installed.
I guess we could just not load the commands if ccls is not in $PATH.
So far we don't have shell calls at startup but one or two won't hurt.
Of course we could make everything a subcommand of a new lsp-ccls command that loads everything, but that command is still ugly.
Not really happy with any of the solutions.
For now a workaround could be
evaluate-commands %sh{
    kak-lsp --kakoune -s $kak_session |
        sed '/define-command.*ccls\|clangd\|ejdtls/s/^/nop /'
}


Add WebComponent polyfills

Right now we pretty much only run in recent versions of Blink, this should fix this issue.

Partial support in #9, polyfills are bundled with Yoru but seem not to do anything at least on Firefox


Verify server signature

I think you need unit test for that.

Look for the TODO comments in the code, many of them have TODO signature verification
address these places in the code where you find these.
I think also there needs to be a testcase on every context type (data, user, admin, config, json-query, provenance, etc) that tests signature verification, i.e. it fails if the signature is wrong.


Missing info: at what time "today's" image is created?

As per title, when the change in what day is "today" happens?
Looking at the code, it seems that datetime.today().date() returns the local datetime, so what local is that?

I believe this code is run local to Eastern US time, however its been years since I checked this.
=brian
From: Emmanuele Villa<EMAIL_ADDRESS>Reply-To: nasa/apod-api<EMAIL_ADDRESS>Date: Tuesday, July 30, 2019 at 4:54 AM
To: nasa/apod-api<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [EXTERNAL] [nasa/apod-api] Missing info: at what time "today's" image is created? (#26)
As per title, when the change in what day is "today" happens?
Looking at the code, it seems that datetime.today().date() returns the local datetime, so what local is that?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_nasa_apod-2Dapi_issues_26-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAA6NHGOSONVL4PVIW4T3E7LQB76U5A5CNFSM4IHZ7RMKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HCHVBJA&d=DwMCaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=BZpo7Ra1k7-CMa5_b1wFxVw3bMQgOLcmuYgw3r1v4sI&m=8SEl0xAjFlJ-HzpB8SJQ_zke6O7V9e_VyF3UVMvfcz8&s=dW7CWiFtWpPrfssLskFr_VZ5zO-olMaH1rOtr0CLLTo&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AA6NHGJQ6CKLQVBE5ZGE2VDQB76U5ANCNFSM4IHZ7RMA&d=DwMCaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=BZpo7Ra1k7-CMa5_b1wFxVw3bMQgOLcmuYgw3r1v4sI&m=8SEl0xAjFlJ-HzpB8SJQ_zke6O7V9e_VyF3UVMvfcz8&s=7GTFi7q31BAwZeGzcFPH_kOBJ4nkXKprjqWL3Nm_ul8&e=.


[google_maps_fltutter] - Maps can run in debug mode but its not work in --release mode

I using google_maps_flutter and added minimal map with initial camera  when I run with "flutter run" its workly. after that I try to run with "flutter run --release" command app can be lanch and show but the map not shown its only google logo
I'm allready create api key and key.jks
and I allready create appbunble.aap
I find many solution but its not working
please help me
How i can resolve this problem
this my code
`return MaterialApp(
title: 'Thepha CoHort Ward',
theme: ThemeData(
primarySwatch: Colors.green,
//colorScheme: const ColorScheme(primary: Color.fromARGB(a, r, g, b)),
),
  home: GoogleMap(
  initialCameraPosition: cameraPosition,
  mapType: MapType.satellite,
),

  // routes: routes,
  // initialRoute: firstRoutePage,

);`

Thank you.
regard..

Hi @salampos
Can you please provide your flutter doctor -v,  and a minimal complete reproducible code sample?
Thank you

Thank you for you replied
Now resolved this problem by recreate the credential
Thank you ..
On Wed, Nov 17, 2021 at 5:49 PM Mamus Eferha @.***>
wrote:

Hi @salampos https://github.com/salampos
Can you please provide your flutter doctor -v, and a minimal complete
reproducible code sample
https://stackoverflow.com/help/minimal-reproducible-example?
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/93777#issuecomment-971457261,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APV7AA3XMDD7XGALMARQQN3UMOCCTANCNFSM5IGOYQDA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
ภูริพัฒน์ กะมิง
โปรแกรมเมอร์
งานสารสนเทศทางการแพทย์
โรงพยาบาลเทพา จังหวัดสงขลา
โทร: 074376359 ต่อ 105 มือถือ :<PHONE_NUMBER>
อีเมลล์ : @., @.

Hi @salampos
Given your last message I feel safe to close this issue, if you disagree please write in the comments and I will reopen it.
Thank you


feat: add label style property to axis

I don't see how this PR fixes https://github.com/zakodium/react-plot/issues/11. The default font is not changed here.

@targos Sorry, I missed the title, I solved what was inside (the issue name wasn't the best one)


DLLs (and dylib) missing for 0.8.0 on PyPI

I just found out that the DLLs are missing in the wheel packages for 0.8.0, and judging by the file sizes on https://pypi.python.org/pypi/PySoundFile/0.8.0#downloads, the dylib is missing, too.

Oh! Thank you for the hint. Should be fixed now. (Also, should be available as pip install soundfile as well)

Great, thanks!
I already saw the "soundfile" project on PyPI, that's very nice!


Restrict a recent XFAILing long_test to assert configurations, rdar://38631299

This recent XFAIL only actually fails when asserts are on. More-recently the construction of a builder that does long_tests in non-assert mode XPASSes here. Fixing the test accordingly, cc @jrose-apple
rdar://38631299

@swift-ci please test and merge