Received unsolicited notification

System Health details
System Information

version
core-2024.6.4

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.2

os_name
Linux

os_version
6.6.33-haos

arch
x86_64

timezone
Europe/Vienna

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
5000

Installed Version
1.34.0

Stage
running

Available Repositories
1391

Downloaded Repositories
11

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 12.4

update_channel
stable

supervisor_version
supervisor-2024.06.2

agent_version
1.6.0

docker_version
26.1.4

disk_total
468.7 GB

disk_used
17.1 GB

healthy
true

supported
true

host_connectivity
true

supervisor_connectivity
true

ntp_synchronized
true

virtualization

board
generic-x86-64

supervisor_api
ok

version_api
ok

installed_addons
Samba share (12.3.1), File editor (5.8.0), RaspberryMatic CCU (<IP_ADDRESS>40601), Advanced SSH & Web Terminal (18.0.0), Mosquitto broker (6.4.1), VNC Viewer (1.6.0), ESPHome (2024.6.4), HomeConnect2MQTT (v0.1.1)

Dashboards

dashboards
3

resources
0

views
14

mode
storage

Recorder

oldest_recorder_run
June 21, 2024 at 11:19

current_recorder_run
June 28, 2024 at 14:47

estimated_db_size
297.54 MiB

database_engine
sqlite

database_version
3.44.2

Solcast PV Forecast

can_reach_server
ok

used_requests
2

rooftop_site_count
1

Spotify

api_endpoint_reachable
ok

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Nuki Device type
Nuki Smart Lock 3
hass_nuki_bt version
v0.0.14
Describe the issue
I have also integrated the lock into HomeKit. In HomeKit I have an automation that locks the lock at 10 p.m.
Whenever this automation is carried out I get errors.
`Logger: pyNukiBT.nuki
Source: runner.py:190
First occurred: June 28, 2024 at 22:00:12 (4 occurrences)
Last logged: June 29, 2024 at 22:00:10
HomeAssistant: Received unsolicited notification: Container: auth_id = b'\x04\x00\xf0\t' (total 4) command = (enum) CHALLENGE 4 payload = Container: nonce = b'\xa5\x07\xe4\xd4\xb0}\xbcw\xb9\xc3\xf5\xc5\x97\xfbR\x0e'... (truncated, total 32) unknown = b'' (total 0) crc = 31944
was expecting CHALLENGE
HomeAssistant: Received unsolicited notification: Container: auth_id = b'\x04\x00\xf0\t' (total 4) command = (enum) CHALLENGE 4 payload = Container: nonce = b'\xb3J\xd3"s\xf3\x7fl\x107\x861\x03\x83\x97\x0e'... (truncated, total 32) unknown = b'' (total 0) crc = 38749`
Reproduction steps

Add lock to HomeKit.
Add automation to close in HomeKit.
When this automation is executed the error occurs.

Debug logs
2024-06-28 22:00:02.211 INFO (MainThread) [pyNukiBT.nuki] Lock action LOCK
2024-06-28 22:00:02.211 INFO (MainThread) [pyNukiBT.nuki] sending encrypted command REQUEST_DATA
2024-06-28 22:00:02.212 INFO (MainThread) [pyNukiBT.nuki] Trying to send data. Attempt 1
2024-06-28 22:00:04.147 DEBUG (MainThread) [pyNukiBT.nuki] Services ['00001801-0000-1000-8000-00805f9b34fb (Handle: 1): Generic Attribute Profile', '00001800-0000-1000-8000-00805f9b34fb (Handle: 9): Generic Access Profile', '0000180a-0000-1000-8000-00805f9b34fb (Handle: 14): Gardena DeviceInformation', 'a92ee100-5501-11e4-916c-0800200c9a66 (Handle: 23): Unknown', 'a92ee200-5501-11e4-916c-0800200c9a66 (Handle: 27): Unknown', '00000045-0000-1000-8000-0026bb765291 (Handle: 36): Unknown', '00000096-0000-1000-8000-0026bb765291 (Handle: 53): Unknown', '0000003e-0000-1000-8000-0026bb765291 (Handle: 71): Unknown', '000000a2-0000-1000-8000-0026bb765291 (Handle: 105): Unknown', '00000055-0000-1000-8000-0026bb765291 (Handle: 114): Unknown']
2024-06-28 22:00:04.148 DEBUG (MainThread) [pyNukiBT.nuki] Characteristics ['00002a05-0000-1000-8000-00805f9b34fb (Handle: 3): Service Changed', '00002b2a-0000-1000-8000-00805f9b34fb (Handle: 6): Database Hash', '00002b29-0000-1000-8000-00805f9b34fb (Handle: 8): Client Supported Features', '00002a00-0000-1000-8000-00805f9b34fb (Handle: 11): Device Name', '00002a01-0000-1000-8000-00805f9b34fb (Handle: 13): Appearance', '00002a25-0000-1000-8000-00805f9b34fb (Handle: 16): Serial Number String', '00002a27-0000-1000-8000-00805f9b34fb (Handle: 18): Hardware Revision String', '00002a26-0000-1000-8000-00805f9b34fb (Handle: 20): Gardena DeviceInformation Firmware Version', '00002a24-0000-1000-8000-00805f9b34fb (Handle: 22): Gardena DeviceInformation Model Number', 'a92ee101-5501-11e4-916c-0800200c9a66 (Handle: 25): Unknown', 'a92ee201-5501-11e4-916c-0800200c9a66 (Handle: 29): Unknown', 'a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown', 'a92ee203-5501-11e4-916c-0800200c9a66 (Handle: 35): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 38): Unknown', '000000a5-0000-1000-8000-0026bb765291 (Handle: 40): Unknown', '0000001d-0000-1000-8000-0026bb765291 (Handle: 43): Unknown', '0000001e-0000-1000-8000-0026bb765291 (Handle: 47): MCAP Control Channel', '00000023-0000-1000-8000-0026bb765291 (Handle: 51): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 55): Unknown', '00000079-0000-1000-8000-0026bb765291 (Handle: 57): Unknown', '00000068-0000-1000-8000-0026bb765291 (Handle: 61): Unknown', '0000008f-0000-1000-8000-0026bb765291 (Handle: 65): Unknown', '00000023-0000-1000-8000-0026bb765291 (Handle: 69): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 73): Unknown', '00000014-0000-1000-8000-0026bb765291 (Handle: 75): Hardcopy Data Channel', '00000020-0000-1000-8000-0026bb765291 (Handle: 78): Unknown', '00000021-0000-1000-8000-0026bb765291 (Handle: 81): Unknown', '00000023-0000-1000-8000-0026bb765291 (Handle: 84): Unknown', '00000030-0000-1000-8000-0026bb765291 (Handle: 87): Unknown', '00000052-0000-1000-8000-0026bb765291 (Handle: 90): Unknown', '00000053-0000-1000-8000-0026bb765291 (Handle: 93): Unknown', '00000037-0000-1000-8000-0026bb765291 (Handle: 96): Unknown', '00000220-0000-1000-8000-0026bb765291 (Handle: 99): Unknown', '000000a6-0000-1000-8000-0026bb765291 (Handle: 102): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 107): Unknown', '000000a5-0000-1000-8000-0026bb765291 (Handle: 109): Unknown', '00000037-0000-1000-8000-0026bb765291 (Handle: 112): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 116): Unknown', '0000004c-0000-1000-8000-0026bb765291 (Handle: 118): Unknown', '0000004e-0000-1000-8000-0026bb765291 (Handle: 121): Unknown', '0000004f-0000-1000-8000-0026bb765291 (Handle: 124): Unknown', '00000050-0000-1000-8000-0026bb765291 (Handle: 127): Unknown']
2024-06-28 22:00:04.196 INFO (MainThread) [pyNukiBT.nuki] Connected
2024-06-28 22:00:04.196 INFO (MainThread) [pyNukiBT.nuki] Sending data to Nuki
2024-06-28 22:00:04.269 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'B\x06\xa1\xcc\xe49T\xe3)7\xe5N\x8e]\xf4\x83\x0c\xed\x13ly:\xae\x07\x04\x00\xf0\t8\x00\xc0n\x11~\xe5M\xcf\xf7\xe9\x84*K\x19\x1d\x97\xe4\xec0&,\xbf\xa4\xa9G\xe3\xaf\xe1\x9d\x9d\x9ano\xe5\t\xb0\x0b\x04[\xd78kzUN-B\xeb\xe3D\x15f\x0e\xd3\xb9)\x0c')
2024-06-28 22:00:04.275 INFO (MainThread) [pyNukiBT.nuki] Data sent on attempt 1
2024-06-28 22:00:04.276 INFO (MainThread) [pyNukiBT.nuki] sending encrypted command LOCK_ACTION
2024-06-28 22:00:04.276 INFO (MainThread) [pyNukiBT.nuki] Trying to send data. Attempt 1
2024-06-28 22:00:04.276 INFO (MainThread) [pyNukiBT.nuki] Connected
2024-06-28 22:00:04.276 INFO (MainThread) [pyNukiBT.nuki] Sending data to Nuki
2024-06-28 22:00:04.313 INFO (MainThread) [pyNukiBT.nuki] Data sent on attempt 1
2024-06-28 22:00:04.337 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'\xdd[\xa9_\xf2\xd6\xa6\xfb8\x18\x00_!\xa6Cx\xed\xeb*V"\xcc\x92\xfc\x04\x00\xf0\t\x19\x00\x1b\xcfQ?S\xac\x86\xc6$\x19k\xe9`Z\xf05\x1a\xc9\xab\xf6oM^Uf')
2024-06-28 22:00:04.338 DEBUG (MainThread) [pyNukiBT.nuki] Last action: ACCEPTED
2024-06-28 22:00:04.339 INFO (MainThread) [pyNukiBT.nuki] ACCEPTED
2024-06-28 22:00:04.360 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'\x1c]Qy\x04\xd4W\xed\xf9x\xe4\xcf\x84\xed\xde\nO\x03\xac=\xba\n\x0f\xc7\x04\x00\xf0\t2\x00\x1e\x7f)\x1e\xb0\xe8#o\xc3\xacW]\x90\x87\xfa\xf8U\xbb\x8e\xba\x94^\x04Yn\x81\xf9\xb9;\x99m\xed35\x04\xe1\xfbz\xe7\xbc3wv\xeb\xbf\xb8a\xd19(')
2024-06-28 22:00:04.362 DEBUG (MainThread) [pyNukiBT.nuki] State: Container:
nuki_state = (enum) DOOR_MODE 2
lock_state = (enum) LOCKING 4
trigger = (enum) SYSTEM 0
current_time = Container:
year = 2024
month = 6
day = 28
hour = 19
minute = 59
second = 50
timezone_offset = 0
critical_battery_state = 124
config_update_count = 16
lock_n_go_timer = 0
last_lock_action = (enum) LOCK 2
last_lock_action_trigger = (enum) SYSTEM 0
last_lock_action_completion_status = (enum) MOTOR_BLOCKED 1
door_sensor_state = (enum) UNAVAILABLE 0
nightmode_active = 0
accessory_battery_state = 0
2024-06-28 22:00:04.362 DEBUG (MainThread) [pyNukiBT.nuki] HomeAssistant: Fire callbacks
2024-06-28 22:00:12.347 DEBUG (MainThread) [pyNukiBT.nuki] Nuki: 54:D2:72:75:B2:FC, RSSI: -56
2024-06-28 22:00:12.348 INFO (MainThread) [pyNukiBT.nuki] Querying Nuki state
2024-06-28 22:00:12.349 INFO (MainThread) [pyNukiBT.nuki] sending encrypted command REQUEST_DATA
2024-06-28 22:00:12.349 INFO (MainThread) [pyNukiBT.nuki] Trying to send data. Attempt 1
2024-06-28 22:00:12.369 DEBUG (MainThread) [pyNukiBT.nuki] Services ['00001801-0000-1000-8000-00805f9b34fb (Handle: 1): Generic Attribute Profile', '00001800-0000-1000-8000-00805f9b34fb (Handle: 9): Generic Access Profile', '0000180a-0000-1000-8000-00805f9b34fb (Handle: 14): Gardena DeviceInformation', 'a92ee100-5501-11e4-916c-0800200c9a66 (Handle: 23): Unknown', 'a92ee200-5501-11e4-916c-0800200c9a66 (Handle: 27): Unknown', '00000045-0000-1000-8000-0026bb765291 (Handle: 36): Unknown', '00000096-0000-1000-8000-0026bb765291 (Handle: 53): Unknown', '0000003e-0000-1000-8000-0026bb765291 (Handle: 71): Unknown', '000000a2-0000-1000-8000-0026bb765291 (Handle: 105): Unknown', '00000055-0000-1000-8000-0026bb765291 (Handle: 114): Unknown']
2024-06-28 22:00:12.370 DEBUG (MainThread) [pyNukiBT.nuki] Characteristics ['00002a05-0000-1000-8000-00805f9b34fb (Handle: 3): Service Changed', '00002b2a-0000-1000-8000-00805f9b34fb (Handle: 6): Database Hash', '00002b29-0000-1000-8000-00805f9b34fb (Handle: 8): Client Supported Features', '00002a00-0000-1000-8000-00805f9b34fb (Handle: 11): Device Name', '00002a01-0000-1000-8000-00805f9b34fb (Handle: 13): Appearance', '00002a25-0000-1000-8000-00805f9b34fb (Handle: 16): Serial Number String', '00002a27-0000-1000-8000-00805f9b34fb (Handle: 18): Hardware Revision String', '00002a26-0000-1000-8000-00805f9b34fb (Handle: 20): Gardena DeviceInformation Firmware Version', '00002a24-0000-1000-8000-00805f9b34fb (Handle: 22): Gardena DeviceInformation Model Number', 'a92ee101-5501-11e4-916c-0800200c9a66 (Handle: 25): Unknown', 'a92ee201-5501-11e4-916c-0800200c9a66 (Handle: 29): Unknown', 'a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown', 'a92ee203-5501-11e4-916c-0800200c9a66 (Handle: 35): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 38): Unknown', '000000a5-0000-1000-8000-0026bb765291 (Handle: 40): Unknown', '0000001d-0000-1000-8000-0026bb765291 (Handle: 43): Unknown', '0000001e-0000-1000-8000-0026bb765291 (Handle: 47): MCAP Control Channel', '00000023-0000-1000-8000-0026bb765291 (Handle: 51): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 55): Unknown', '00000079-0000-1000-8000-0026bb765291 (Handle: 57): Unknown', '00000068-0000-1000-8000-0026bb765291 (Handle: 61): Unknown', '0000008f-0000-1000-8000-0026bb765291 (Handle: 65): Unknown', '00000023-0000-1000-8000-0026bb765291 (Handle: 69): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 73): Unknown', '00000014-0000-1000-8000-0026bb765291 (Handle: 75): Hardcopy Data Channel', '00000020-0000-1000-8000-0026bb765291 (Handle: 78): Unknown', '00000021-0000-1000-8000-0026bb765291 (Handle: 81): Unknown', '00000023-0000-1000-8000-0026bb765291 (Handle: 84): Unknown', '00000030-0000-1000-8000-0026bb765291 (Handle: 87): Unknown', '00000052-0000-1000-8000-0026bb765291 (Handle: 90): Unknown', '00000053-0000-1000-8000-0026bb765291 (Handle: 93): Unknown', '00000037-0000-1000-8000-0026bb765291 (Handle: 96): Unknown', '00000220-0000-1000-8000-0026bb765291 (Handle: 99): Unknown', '000000a6-0000-1000-8000-0026bb765291 (Handle: 102): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 107): Unknown', '000000a5-0000-1000-8000-0026bb765291 (Handle: 109): Unknown', '00000037-0000-1000-8000-0026bb765291 (Handle: 112): Unknown', 'e604e95d-a759-4817-87d3-aa005083a0d1 (Handle: 116): Unknown', '0000004c-0000-1000-8000-0026bb765291 (Handle: 118): Unknown', '0000004e-0000-1000-8000-0026bb765291 (Handle: 121): Unknown', '0000004f-0000-1000-8000-0026bb765291 (Handle: 124): Unknown', '00000050-0000-1000-8000-0026bb765291 (Handle: 127): Unknown']
2024-06-28 22:00:12.372 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'\xce\xea\xe2\x1c\xe0\xf7$\xd5\x96\xea\xf2\x1f\x8d7S\x1b\xa8QnC\x8a\x18\x9b\xde\x04\x00\xf0\t2\x00\xb8\x14\xc3\n\x12\\\xff\xcd3v\xa4\x8d\xa5\x10P\xcc\x978\xf78I\xf5)mP\x8b\x1fy\xdb\xb6D[\xb0\x930\x03q.\xcd\xe2##\x86\xda\xc6\xe3Ss7\x1d')
2024-06-28 22:00:12.397 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'\xe7\x8d\x96\x988/$\xe66\xf3\x98\x10\xac\x0b\xde\x0f\x04 \x8f\xc7\xa0\xd2\x1fK\x04\x00\xf0\t\x19\x001\xb1\xdc\x062\xcfd\xa0\xcb\x92F\xc4\xa1r\xc9-\xcb\x00\x88\xacA\xf7O\xecB')
2024-06-28 22:00:12.398 DEBUG (MainThread) [pyNukiBT.nuki] Last action: COMPLETED
2024-06-28 22:00:12.398 INFO (MainThread) [pyNukiBT.nuki] Last action: COMPLETED
2024-06-28 22:00:12.398 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'\xe7\x8d\x96\x988/$\xe66\xf3\x98\x10\xac\x0b\xde\x0f\x04 \x8f\xc7\xa0\xd2\x1fK\x04\x00\xf0\t\x19\x001\xb1\xdc\x062\xcfd\xa0\xcb\x92F\xc4\xa1r\xc9-\xcb\x00\x88\xacA\xf7O\xecB')
2024-06-28 22:00:12.399 DEBUG (MainThread) [pyNukiBT.nuki] Last action: COMPLETED
2024-06-28 22:00:12.399 INFO (MainThread) [pyNukiBT.nuki] Last action: COMPLETED
2024-06-28 22:00:12.424 INFO (MainThread) [pyNukiBT.nuki] Connected
2024-06-28 22:00:12.424 INFO (MainThread) [pyNukiBT.nuki] Sending data to Nuki
2024-06-28 22:00:12.478 DEBUG (MainThread) [pyNukiBT.nuki] Nuki: 54:D2:72:75:B2:FC, RSSI: -56
2024-06-28 22:00:12.478 INFO (MainThread) [pyNukiBT.nuki] Ignoring duplicate beacon from Nuki 54:D2:72:75:B2:FC
2024-06-28 22:00:12.497 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'\xf5\xd15.\xa1\x00u\xe9*t3M\x979%~\xc3d3\x84\xe663\xd9\x04\x00\xf0\t2\x00\x07BeA\x0c\x0eF\x1a\x9c%E>rq\xd5\xd0p=Q\x9f5\xbb\xa5\xba\x8c,\xd2J\x84@\xaa{\xf2\x1e\x12\x8b|\xa6\x9b5\xd0U\t\xfcC-e\x8aie')
2024-06-28 22:00:12.499 DEBUG (MainThread) [pyNukiBT.nuki] State: Container:
nuki_state = (enum) DOOR_MODE 2
lock_state = (enum) LOCKED 1
trigger = (enum) SYSTEM 0
current_time = Container:
year = 2024
month = 6
day = 28
hour = 19
minute = 59
second = 58
timezone_offset = 0
critical_battery_state = 124
config_update_count = 16
lock_n_go_timer = 0
last_lock_action = (enum) LOCK 2
last_lock_action_trigger = (enum) SYSTEM 0
last_lock_action_completion_status = (enum) SUCCESS 0
door_sensor_state = (enum) UNAVAILABLE 0
nightmode_active = 0
accessory_battery_state = 0
2024-06-28 22:00:12.499 DEBUG (MainThread) [pyNukiBT.nuki] HomeAssistant: Fire callbacks
2024-06-28 22:00:12.502 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'\xf5\xd15.\xa1\x00u\xe9*t3M\x979%~\xc3d3\x84\xe663\xd9\x04\x00\xf0\t2\x00\x07BeA\x0c\x0eF\x1a\x9c%E>rq\xd5\xd0p=Q\x9f5\xbb\xa5\xba\x8c,\xd2J\x84@\xaa{\xf2\x1e\x12\x8b|\xa6\x9b5\xd0U\t\xfcC-e\x8aie')
2024-06-28 22:00:12.503 DEBUG (MainThread) [pyNukiBT.nuki] State: Container:
nuki_state = (enum) DOOR_MODE 2
lock_state = (enum) LOCKED 1
trigger = (enum) SYSTEM 0
current_time = Container:
year = 2024
month = 6
day = 28
hour = 19
minute = 59
second = 58
timezone_offset = 0
critical_battery_state = 124
config_update_count = 16
lock_n_go_timer = 0
last_lock_action = (enum) LOCK 2
last_lock_action_trigger = (enum) SYSTEM 0
last_lock_action_completion_status = (enum) SUCCESS 0
door_sensor_state = (enum) UNAVAILABLE 0
nightmode_active = 0
accessory_battery_state = 0
2024-06-28 22:00:12.503 DEBUG (MainThread) [pyNukiBT.nuki] HomeAssistant: Fire callbacks
2024-06-28 22:00:12.505 INFO (MainThread) [pyNukiBT.nuki] Data sent on attempt 1
2024-06-28 22:00:12.505 DEBUG (MainThread) [pyNukiBT.nuki] State: Container:
nuki_state = (enum) DOOR_MODE 2
lock_state = (enum) LOCKED 1
trigger = (enum) SYSTEM 0
current_time = Container:
year = 2024
month = 6
day = 28
hour = 19
minute = 59
second = 58
timezone_offset = 0
critical_battery_state = 124
config_update_count = 16
lock_n_go_timer = 0
last_lock_action = (enum) LOCK 2
last_lock_action_trigger = (enum) SYSTEM 0
last_lock_action_completion_status = (enum) SUCCESS 0
door_sensor_state = (enum) UNAVAILABLE 0
nightmode_active = 0
accessory_battery_state = 0
2024-06-28 22:00:12.505 INFO (MainThread) [pyNukiBT.nuki] request 1 log entries, start=0
2024-06-28 22:00:12.505 INFO (MainThread) [pyNukiBT.nuki] sending encrypted command REQUEST_DATA
2024-06-28 22:00:12.506 INFO (MainThread) [pyNukiBT.nuki] Trying to send data. Attempt 1
2024-06-28 22:00:12.506 INFO (MainThread) [pyNukiBT.nuki] Connected
2024-06-28 22:00:12.506 INFO (MainThread) [pyNukiBT.nuki] Sending data to Nuki
2024-06-28 22:00:12.558 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'\x8f\x12(\xfcE\xc2z\x8f4j\xe2\xa8\xa9$\xdfI\x92\xfb}\xe0\xa3z\x90\xdd\x04\x00\xf0\t8\x00\xe1\xd8\x18\x7f\x99\xdbM\xb9\x93\xba|\xe6-\x8bjw\xdc\x1ek\xf3\x01\t\x86\xaf\xe5\xf0\xa8VY\xa0\x96\xdf6Z\xcaQ\x98\x10\xf1\xc7P\xaa\xe7Y\xae\xd3t\xad\xf5\x91" ?k\xa2\xd5')
2024-06-28 22:00:12.560 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'\x8f\x12(\xfcE\xc2z\x8f4j\xe2\xa8\xa9$\xdfI\x92\xfb}\xe0\xa3z\x90\xdd\x04\x00\xf0\t8\x00\xe1\xd8\x18\x7f\x99\xdbM\xb9\x93\xba|\xe6-\x8bjw\xdc\x1ek\xf3\x01\t\x86\xaf\xe5\xf0\xa8VY\xa0\x96\xdf6Z\xcaQ\x98\x10\xf1\xc7P\xaa\xe7Y\xae\xd3t\xad\xf5\x91" ?k\xa2\xd5')
2024-06-28 22:00:12.561 ERROR (MainThread) [pyNukiBT.nuki] HomeAssistant: Received unsolicited notification: Container:
auth_id = b'\x04\x00\xf0\t' (total 4)
command = (enum) CHALLENGE 4
payload = Container:
nonce = b'\xa5\x07\xe4\xd4\xb0}\xbcw\xb9\xc3\xf5\xc5\x97\xfbR\x0e'... (truncated, total 32)
unknown = b'' (total 0)
crc = 31944
2024-06-28 22:00:12.562 ERROR (MainThread) [pyNukiBT.nuki] was expecting CHALLENGE
2024-06-28 22:00:12.565 INFO (MainThread) [pyNukiBT.nuki] Data sent on attempt 1
2024-06-28 22:00:12.565 INFO (MainThread) [pyNukiBT.nuki] sending encrypted command REQUEST_LOG_ENTRIES
2024-06-28 22:00:12.566 INFO (MainThread) [pyNukiBT.nuki] Trying to send data. Attempt 1
2024-06-28 22:00:12.566 INFO (MainThread) [pyNukiBT.nuki] Connected
2024-06-28 22:00:12.566 INFO (MainThread) [pyNukiBT.nuki] Sending data to Nuki
2024-06-28 22:00:12.623 INFO (MainThread) [pyNukiBT.nuki] Data sent on attempt 1
2024-06-28 22:00:12.643 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b"\xe0)\xa1a\xa1\xc2YiL\x18}\xb0\xfd<\xf7\xe5t\xaf5\xe6\x1aT\x1c\xba\x04\x00\xf0\tM\x00\x8b\xe4\x91\xb7\x9f\x11\xa6Sn\xbfj\x06\xa8\xa9\xd7l\xf4k\x8e\x94r7\x1dOd\xb6\xcf\xc4\x05\xa2f\xa8\x00\x8f\x89HtX9\r\xb1\xa8\xf6B\xe8`\x0c\xe2\x0e\xa7b\x1e\x94O}\xbat\xc0\xdd2\xbc\xd9&\'[\xa2\x04\x10\xedStlUt\xa5\xb7=")
2024-06-28 22:00:12.645 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b"\xe0)\xa1a\xa1\xc2YiL\x18}\xb0\xfd<\xf7\xe5t\xaf5\xe6\x1aT\x1c\xba\x04\x00\xf0\tM\x00\x8b\xe4\x91\xb7\x9f\x11\xa6Sn\xbfj\x06\xa8\xa9\xd7l\xf4k\x8e\x94r7\x1dOd\xb6\xcf\xc4\x05\xa2f\xa8\x00\x8f\x89HtX9\r\xb1\xa8\xf6B\xe8`\x0c\xe2\x0e\xa7b\x1e\x94O}\xbat\xc0\xdd2\xbc\xd9&\'[\xa2\x04\x10\xedStlUt\xa5\xb7=")
2024-06-28 22:00:12.666 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'\xeep\xa5R\xe2d\xd4=\xfa\x05D\xb0\xa5\x8e\x84\xf9\x87\xe7\xad\xe8\x04\x19he\x04\x00\xf0\t\x19\x00\xef\x8c\x14\x05rr\xed\x1f\xb8d\xe2\xd9\x19\x01\\\\\xef\xd2\xa2\xed\xb3$x2\x87')
2024-06-28 22:00:12.667 DEBUG (MainThread) [pyNukiBT.nuki] Last action: COMPLETED
2024-06-28 22:00:12.667 DEBUG (MainThread) [pyNukiBT.nuki] Notification handler: a92ee202-5501-11e4-916c-0800200c9a66 (Handle: 32): Unknown, data: bytearray(b'\xeep\xa5R\xe2d\xd4=\xfa\x05D\xb0\xa5\x8e\x84\xf9\x87\xe7\xad\xe8\x04\x19he\x04\x00\xf0\t\x19\x00\xef\x8c\x14\x05rr\xed\x1f\xb8d\xe2\xd9\x19\x01\\\\\xef\xd2\xa2\xed\xb3$x2\x87')
2024-06-28 22:00:12.668 DEBUG (MainThread) [pyNukiBT.nuki] Last action: COMPLETED
2024-06-28 22:00:12.668 INFO (MainThread) [pyNukiBT.nuki] Last action: COMPLETED
2024-06-28 22:00:12.668 DEBUG (MainThread) [pyNukiBT.nuki] Container:
status = (enum) COMPLETED 0
2024-06-28 22:00:12.668 DEBUG (MainThread) [pyNukiBT.nuki] [Container(index=2619, timestamp=Container(year=2024, month=6, day=28, hour=19, minute=59, second=58), auth_id=166723588, name=u'HomeAssistant', type=uEnumIntegerString.new(2, 'LOCK_ACTION'), data=Container(lock_action=uEnumIntegerString.new(2, 'LOCK'), trigger=uEnumIntegerString.new(0, 'SYSTEM'), flags=0, completion_status=uEnumIntegerString.new(0, 'SUCCESS'), padding=None)), Container(index=2619, timestamp=Container(year=2024, month=6, day=28, hour=19, minute=59, second=58), auth_id=166723588, name=u'HomeAssistant', type=uEnumIntegerString.new(2, 'LOCK_ACTION'), data=Container(lock_action=uEnumIntegerString.new(2, 'LOCK'), trigger=uEnumIntegerString.new(0, 'SYSTEM'), flags=0, completion_status=uEnumIntegerString.new(0, 'SUCCESS'), padding=None))]

Diagnostics dump
No response

@011V32
Other then the log, is there any issue?
I did had some issues with logging in this area, I hope to fix them in the next version.
But as i dont have homekit, I have no way to test/reproduce this issue.

@ronengr
I don't think so. I have to admit that I only use it sometimes through automations and I haven't noticed anything so far.
I can observe it again when your changes are there. 👍
But I have another behavior:
If an action is carried out that has actually already been completed, then the status is toggled 2 times.
So if the status is already open and an automation "open" is triggert again, then it is briefly shown as closed, even though only opening is requested.
The same applies the other way around.
This means I always get two notifications even though the status doesn't actually change.

@011V32 the version i released yesterday (0.0.15 and up) already has the fix I was talking about.
Regarding the status change you described - I didn't encounter such issue, even though i have several automatons that open the door without checking it's status (so sending "open" when it is already open).
Can you send me logs so i can see what exactly is happening?
Could it be that it changes from locked->locking->locked and not from locked->unlocked->locked? if this is the case, it makes more sense.

@ronengr
It didn't show up for me until I initiate the update information manually.
I'm now on 0.0.16 and will report back. 👍

@ronengr

Regarding the status change you described - I didn't encounter such issue, even though i have several automatons that open the door without checking it's status (so sending "open" when it is already open).
Can you send me logs so i can see what exactly is happening?
Could it be that it changes from locked->locking->locked and not from locked->unlocked->locked? if this is the case, it makes more sense.

I think with version 0.0.16, the system no longer switches back and forth twice when the same state is triggered again.
With version 0.0.14 the Logbook was as follow wenn opening with open lock (from bottom to up like in HA):

Nuki_3575B2FC Last action user name changed to HomeAssistant
14:05:04 - 24 minutes ago
Nuki_3575B2FC Lock state changed to UNLOCKED
14:05:04 - 24 minutes ago
Nuki_3575B2FC Lock was unlocked triggered by HomeKit send command unlock for Lock (Nuki_3575B2FC Lock)
14:05:04 - 24 minutes ago
Nuki_3575B2FC Last Action Trigger changed to SYSTEM
14:05:03 - 24 minutes ago
Nuki_3575B2FC Last lock action changed to UNLOCK
14:05:03 - 24 minutes ago
Nuki_3575B2FC Lock state changed to UNLOCKING
14:05:03 - 24 minutes ago
Nuki_3575B2FC Lock is unlocking triggered by HomeKit send command unlock for Lock (Nuki_3575B2FC Lock)
14:05:03 - 24 minutes ago

With version 0.0.16 it ist now:

Nuki_3575B2FC Last Nuki command status changed to COMPLETED
14:27:03 - 4 minutes ago
Nuki_3575B2FC Last Nuki command status changed to ACCEPTED
14:27:03 - 4 minutes ago

I will test a little bit 👍

@ronengr
I think that the state only needs to change if it can change. I can only press Unlock in the UI when it is locked and not when it is already unlocked.
So if you execute Unlock and it is already open, then you will get instant the status succesful back.
But I have to admit that I don't know the exact topic behind HA and the other systems. I can only express my opinion from a user perspective.

I an ideal world you are probably correct. But as there are communication issues, the "real" state of the lock is not always updated correctly in HA. (Sometimes a status change update is missed, for several reasons i cannot control).
This is why I don't want to block commands at the integration level, but rather prefer to send every command to the lock itself, regardless of the state i think the lock is in at the moment.
The question is mostly from user perspective - what do you (or the average user) prefer:

Get an immediate indication when you execute a lock/unlock command (change to locking/unlocking), and than getting the real state from the lock after HA was able to communicate with the Nuki lock.
Don't get an immediate indication, only get an indication after HA was able to communicate with Nuki lock.

Personally I'm not sure which is better. Should we indicate locking/unlocking only when the lock is actually turning (this is the state now), or should we indicate locking/unlocking from the moment we start sending the relevant command for the lock.

For me it looks like this:

I'm not familiar with HomeKit, so i wouldn't know why it acts this way.
Anyway, I will probably keep the current state (updating locking status only after reading from the lock)

@011V32
I'm not sure i fully understand the issue in the screenshot you provided.
It seems locking was triggered by HomeKit once (at 22:00:03) and was finished only once.
What am I missing?
Anyway, I think you are correct and it is better to open a new issue for this.


Add note about Google’s terms of service to README.md

I think it's important to mention this as it wasn't immediately obvious to me until I stumbled across it in the documentation.

thanks, and apology for the very late reply


External links

Users will be able to include external links (= internet URLs with an optional caption) in entries. Lexonomy will make sure they are clickable when the entry is formatted for display.

Related to commit 806c7cd which, in my opinion, needs to be re-implemented differently, so that the hiding, abbreviation and clickability of URLs in Xonomy is optional and configurable.
Then we need some additions to Lexonomy's styling configuration for URLs: let the user configure certain elemens or attributes as clickable links and tell us where the URL (and optionally, the display text) is coming from.

I'm closing this for now -- there is a solution in place, any https and https URL is clickable and as discussed, this doesn't harm anything.


Scheduled Test Notification

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
Other
🔖 Feature description
I love this piece of software! However, overtime I get paranoid that Uptime Kuma itself has malfunctioned OR my notif system OR my network has broken and I am unable to receive notifications to my phone. I want a feature where I can enable and schedule test notifications to be sent regularly so I know that uptime kuma is working.
✔ Solution
I go to to the notification settings and find a setting that says " Enable SVNA (Scheduled Verification of Notification Arrival)" with a check box next to it that I need to click to enable....no just  the uptime kuma switch thing.
For example, I will enable the SVNA feature and set it to test my Telegram Notification every single Friday at 12:00PM +10UCT time. From then on, I should get a test notification sent to my Telegram every single Friday at 12:00PM +10UCT and if i get that notification then I have peace of mind. If i do not receive that integrity test notification, than I know that something is wrong/broken and I need to diagnose and fix the issue.
I am naming it SVNA in this example. I should be able to setup multiple SVNA services that can each test different notification methods such as one testing Telegram every month and one testing Email every week.
❓ Alternatives
No response
📝 Additional Context
My name ideas for the feature: "Self-Integrity Test", "Self-Integrity Check", "Scheduled Test Notifications", or the best name:
SVNA (Scheduled Verification of Notification Arrival)

A lightweight implementation of this would be to allow to configure checks to also send "Up" notifications, then you could just test your kuma install itself with a weekly heartbeat interval.

A lightweight implementation of this would be to allow to configure checks to also send "Up" notifications, then you could just test your kuma install itself with a weekly heartbeat interval.

I'm not sure why I would configure to recieve "Up" notifications. I don't want my phone to recieve a notification and distract just to tell me that nothing is wrong and nothing has changed. Am I missing something?? Please please tell me if I am missing something and there are applications where Up notifications are useful. I hope I am not coming off as rude, I am genuinely curious.
But yes, a weekly heartbeat by Uptime Kuma to validate that it is working is exactly what I want. I love that term actually.
"Configure Uptime Kuma Heartbeat" Love it.

Haven't tested this but I think for now you can do this yourself:
Add a monitor to monitor Uptime Kuma itself:

HTTP to localhost
Upside down mode
Resend notification: 0
Heartbeat Interval: however long you want to receive a test notification

Then you should receive a notification on every heartbeat.

Thanks ! Only additional thing I did is do a custom notification to hard-code the subject line to [Kuma healthcheck] up and running ✅, so that I don't get the default red icon.
Personally happy with this slightly hacky workaround.
But definitely an ad-hoc setting (probably in the notification config so you can configure it per notification) would be more elegant.

Haven't tested this but I think for now you can do this yourself:
Add a monitor to monitor Uptime Kuma itself:
* HTTP monitor to localhost

* Upside down mode

* Resend notification: 0

* Heartbeat Interval: however long you want to receive a test notification

Then you should receive a notification on every heartbeat.

That is a great temporary workaround but has downsides. One such downside is that I want a test notif ever 24 hours at 12PM, I need to physically wait until 12PM to create the monitor and set it to 24 hours (86400 seconds)

@anonfather4359 what you are referring to is a different issue: https://github.com/louislam/uptime-kuma/pull/3447
@anonfather4359
Is this issue resolved or can/should I mark it as resolved once we switch to https://github.com/louislam/uptime-kuma/pull/3414?
If it is resolved, could you close this issue?


Fixed responseXML for correct responseType

According to https://xhr.spec.whatwg.org/#the-responsexml-attribute the responseXML attribute is only available when responseType is an empty string or "document". Here's a fix for that.

Related to #111 - a solution similar to #117

Honestly given the XMLHttpRequest specs I'd prefer a combination of all three pull requests - only return responseXML if (responseType === '' || responseType === 'document') and the Firefox bug is not taking effect (ala #118).
If library backwards compatibility is more important than spec compliance, we can roll with #118.

Thanks @ciscoheat - we'll include this in our current rework of responseXML handling.
I'll merge your PR before our rework if you add a test for your exact case. If not, there's no point, because the lines you changed will have to be different anyway, as you can see in @TehShrike's comments

It's fine, I'm sure you have full knowledge of this problem, so if you have your own upcoming fix, you can close this PR. Thanks for your great work!

This inspired the final solution. Thanks!
Closing.


[DatePicker] orientation="landscape" doesn't work on DatePicker

Hey. Prop orientation="landscape" does not have effect on DatePicker component and works only on StaticDatePicker. I couldn't find anything related to this in documentation so I believe this is a bug.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
orientation="landscape" doesn't force DatePicker component to render landscape-oriented calendar.
Expected Behavior 🤔
Behavior of orientation="landscape" should be documented properly or in case this is a bug it should render landscape-oriented calendar.
Steps to Reproduce 🕹

Create a component as described in https://codesandbox.io/s/staticdatepickerlandscape-material-demo-forked-e1xd4?file=/demo.tsx

Your Environment 🌎

Chrome 92

`npx @material-ui/envinfo`
  System:
    OS: Linux 5.4 Ubuntu 20.04.2 LTS (Focal Fossa)
  Binaries:
    Node: 12.22.1 - ~/.nvm/versions/node/v12.22.1/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 7.17.0 - ~/.nvm/versions/node/v12.22.1/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    @emotion/react: ^11.4.0 => 11.4.0
    @emotion/styled: ^11.3.0 => 11.3.0
    @material-ui/core: ^5.0.0-beta.1 => 5.0.0-beta.1
    @material-ui/icons: ^5.0.0-beta.0 => 5.0.0-beta.0
    @material-ui/lab: ^5.0.0-alpha.40 => 5.0.0-alpha.40
    @material-ui/private-theming:  5.0.0-beta.1
    @material-ui/styled-engine:  5.0.0-beta.1
    @material-ui/system:  5.0.0-beta.1
    @material-ui/types:  6.0.1
    @material-ui/unstyled:  5.0.0-alpha.40
    @material-ui/utils:  5.0.0-beta.0
    @types/react: ^17.0.11 => 17.0.11
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    typescript: ^4.3.2 => 4.3.2

Thanks for the feedback.
There's just no landscape specific layout for DesktopDatePicker as far as I know.
We need to update the API docs for the desktop variants.


Default retention time is being overwritten

Is your feature request related to a problem? Please describe.
Variables stored on friday will expire by monday since the retention period is set to 1.
https://github.com/UnlyEd/github-action-store-variable/blob/main/src/manageArtifacts.ts#L49
Describe the solution you'd like
If the value was set to 0 then it looks like the default retention setting would be taken.

Hi, I wasn't aware of that configuration.
I'm not sure what would be the "default" value. See https://github.com/actions/toolkit/blob/c861dd8859fe5294289fcada363ce9bc71e9d260/packages/artifact/src/internal/upload-options.ts#L1
What value would you need for your use case? I believe this could become a new option, with 1 by default, to keep the current behavior by default.

Thinking of storing a slack_thread_id so that when a PR is updated the correct slack message is updated too. That said; it's looking like i could just use actions/cache@v3 to store them and pull it from that.

I wonder if this project is still useful to anyone, I believe the core "setstate" function makes it useless now.
https://github.com/UnlyEd/github-action-store-variable/issues/46


When a Grid in a StackPanel, the <Grid.RowDefininations> work abnormally

Describe the bug
My Microsoft.WindowsAppSDK version: 1.5.240404000
Here is my code.

It seems like that it will be a gray Grid here, but it does not!

What it will happen when I changed the code RowDefinition Height="4*" to RowDefinition Height="400" on line 26 ? It will draw successfully, but its position is not correct.

When I put the Grid and StackPanel in another Grid together, the code will run successfully again!

(Wow amazing! You did a good job winui3👍)
In order to justify that the Grid.RowDefininations work abnormally only if the Grid in a StackPanel, I did some experiments.

╰（‵□′）╯
Steps to reproduce the bug
Here's the code in the experiment.
<StackPanel>
    <Grid>
        <Grid.RowDefinitions>
            <RowDefinition Height="1*"></RowDefinition>
            <RowDefinition Height="1*"></RowDefinition>
            <RowDefinition Height="1*"></RowDefinition>
        </Grid.RowDefinitions>
        <Grid.ColumnDefinitions>
            <ColumnDefinition Width="1*"></ColumnDefinition>
            <ColumnDefinition Width="1*"></ColumnDefinition>
            <ColumnDefinition Width="1*"></ColumnDefinition>
        </Grid.ColumnDefinitions>

        <Grid Grid.Column="1" Grid.Row="1" Background="White"/>
    </Grid>
</StackPanel>

Expected behavior
No response
Screenshots
My windows version (post here because there is not my version in your Windows version selections)

NuGet package version
WinUI 3 - Windows App SDK 1.5.2: 1.5.240404000
Windows version
No response
Additional context
No response

Per the Star sizing documentation:
https://learn.microsoft.com/en-us/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.gridlength?view=windows-app-sdk-1.5#star-sizing

Star sizing is a convention whereby a GridLength has a number value that specifies a weighted factor versus other GridLength values. Any GridLength values that use star sizing divide the available space, accounting for the weighting factors, and evaluating after any fixed widths are applied.

Per documentation on StackPanel usage:
https://learn.microsoft.com/en-us/windows/apps/design/layout/layouts-with-xaml#layout-panels

Stretch values for HorizontalAlignment/VerticalAlignment are respected in the direction opposite the Orientation property. If an element's size is not set explicitly, it stretches to fill the available width (or height if the Orientation is Horizontal). In the direction specified by the Orientation property, an element sizes to its content.

StackPanel.Orientation default value is Vertical. So your Grid is being vertically sized to its content in the StackPanel, which is nothing, so the Grid is asks for and receives no available space from the StackPanel during layout, so the star sizing has no space to divide up, hence the rows have no height.
If you give the Grid some amount of height or provide content that asks for some amount of height, then the StackPanel will provide said height and star sizing will have something to work with. Note that content in a single row requesting Height of 400 means the grid asks its parent for 400 height, gets it, uses it for that row, and the stars are left with nothing to work with.

Ok I got it


.setav not working?

Whenever I use .setav , .setavatar, with an image URL Nadeko does not respond alongside the bots profile image not updating. I have used an imgur link, a .jpg, and even a .gift.

What, if anything do you see in the console? And you are the botowner, correct?

It does work, you must be bot owner though. It won't work on the public bot.
SERVER OWNERS ARE NOT BOT OWNERS. All owner-only commands require you host the bot. Hosting means you are running a nadekobot on your own computer. If you want to learn how to host the bot yourself, type -guide


[New game]: 4 player ludo game

🎮 Game Request
This is a ludo game of maximum 4 player.
Point down the features

Multiple players can play ludo (maximum 4 player).
Interactive user interface.

Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @BidisaChowdhury !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @BidisaChowdhury 👋!
@kunjgit here,
We have this annoucement to make 📢!!
💥 Special Announcement:
It's the Call to all the designers 🔥 🎨
As you all know that GameZone has crossed 100 games 💗 , it's time that we all come up together and make the UI even better!!
We are redesigning the thumbnails, make sure you come up with the aesthetic and cool ideas 🚀 !
You are supposed to share the 4 different templates that can be used. Make sure that the size is: 1280 px X 720 px.
The frame should be such that there is only a single image of the game that's taking up the major portion of the frame. Any kind of text should not be there.
The design should be catchy and aesthetic! 🔥
Note: You are not supposed to create any issue right now for the same.
You have to share different designs right now in Discord  and Project Admin would be selecting one design and would be assigning the issue. After that only, you have to start working on it.

Hey @BidisaChowdhury ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


HikariCP 5 - Connection is not available, request timed out after 300001ms.

Hi,
I still see the issue with HikariCP V5 + OpenJDK 11. Could you please help with a resolution at the earliest possible? Thank you.
===
minimumIdle: 5
maximumPoolSize: 5
maxLifetime: 1800000
leakDetectionThreshold: 45000
keepaliveTime: 120000
connectionTimeout: 300000
===
When total becomes less than maximumPoolSize, why are nt new connections added to the pool to retain minimumIdle (which is = maximumPoolSize = 5)?
===
...
2021-07-26 13:15:13.321 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : Driver class org.postgresql.Driver found in Thread context class loader org.springframework.boot.loader.LaunchedURLClassLoader@68be2bc2
2021-07-26 13:15:13.442 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : prod-postingestion-pool - configuration:
2021-07-26 13:15:13.453 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : allowPoolSuspension.............false
2021-07-26 13:15:13.454 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : autoCommit......................true
2021-07-26 13:15:13.454 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : catalog.........................none
2021-07-26 13:15:13.454 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : connectionInitSql...............none
2021-07-26 13:15:13.454 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : connectionTestQuery.............none
2021-07-26 13:15:13.454 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : connectionTimeout...............300000
2021-07-26 13:15:13.454 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : dataSource......................none
2021-07-26 13:15:13.454 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : dataSourceClassName.............none
2021-07-26 13:15:13.454 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : dataSourceJNDI..................none
2021-07-26 13:15:13.455 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : dataSourceProperties............{password=}
2021-07-26 13:15:13.457 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : driverClassName................."org.postgresql.Driver"
2021-07-26 13:15:13.457 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : exceptionOverrideClassName......none
2021-07-26 13:15:13.457 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : healthCheckProperties...........{}
2021-07-26 13:15:13.457 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : healthCheckRegistry.............none
2021-07-26 13:15:13.457 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : idleTimeout.....................600000
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : initializationFailTimeout.......1
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : isolateInternalQueries..........false
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : jdbcUrl.........................jdbc:postgresql://:5432/?currentSchema=&stringtype=unspecified&sslmode=allow
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : keepaliveTime...................120000
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : leakDetectionThreshold..........45000
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : maxLifetime.....................1800000
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : maximumPoolSize.................5
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : metricRegistry..................none
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : metricsTrackerFactory...........none
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : minimumIdle.....................5
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : password........................
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : poolName........................"prod-postingestion-pool"
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : readOnly........................false
2021-07-26 13:15:13.458 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : registerMbeans..................false
2021-07-26 13:15:13.459 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : scheduledExecutor...............none
2021-07-26 13:15:13.459 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : schema..........................none
2021-07-26 13:15:13.459 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : threadFactory...................internal
2021-07-26 13:15:13.459 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : transactionIsolation............default
2021-07-26 13:15:13.459 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : username........................""
2021-07-26 13:15:13.459 DEBUG 97145 --- [           main] com.zaxxer.hikari.HikariConfig           : validationTimeout...............5000
2021-07-26 13:15:13.459  INFO 97145 --- [           main] com.zaxxer.hikari.HikariDataSource       : prod-postingestion-pool - Starting...
2021-07-26 13:15:14.289  INFO 97145 --- [           main] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Added connection org.postgresql.jdbc.PgConnection@733037
2021-07-26 13:15:14.291  INFO 97145 --- [           main] com.zaxxer.hikari.HikariDataSource       : prod-postingestion-pool - Start completed.
2021-07-26 13:15:14.348  INFO 97145 --- [           main] o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [name: default]
2021-07-26 13:15:14.391 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=1, active=0, idle=1, waiting=0)
...
2021-07-26 21:41:47.679 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=5, active=0, idle=5, waiting=0)
2021-07-26 21:41:47.679 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Fill pool skipped, pool has sufficient level or currently being filled (queueDepth=0.
...
2021-07-26 21:42:06.578 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@2b18cf39 is alive
2021-07-26 21:42:17.679 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=5, active=0, idle=5, waiting=0)
2021-07-26 21:42:17.680 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Fill pool skipped, pool has sufficient level or currently being filled (queueDepth=0.
...
2021-07-26 21:42:40.350  WARN 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.PoolBase          : prod-postingestion-pool - Failed to validate connection org.postgresql.jdbc.PgConnection@5f05f5ef (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2021-07-26 21:42:40.351 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Add connection elided, waiting=0, adders pending/running=1
2021-07-26 21:42:40.351 DEBUG 97145 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase          : prod-postingestion-pool - Closing connection org.postgresql.jdbc.PgConnection@5f05f5ef: (connection is dead)
2021-07-26 21:42:40.351 DEBUG 97145 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase          : prod-postingestion-pool - Closing connection org.postgresql.jdbc.PgConnection@2b18cf39: (connection has passed maxLifetime)
2021-07-27 14:33:18.262 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=5, active=0, idle=5, waiting=0)
2021-07-27 14:33:18.262 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Fill pool skipped, pool has sufficient level or currently being filled (queueDepth=0.
...
2021-07-27 14:33:34.807 DEBUG 97145 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase          : prod-postingestion-pool - Closing connection org.postgresql.jdbc.PgConnection@3b2a1c76: (connection has passed maxLifetime)
2021-07-27 14:33:48.263 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=4, active=0, idle=4, waiting=0)
2021-07-27 14:34:12.700 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@6d16cbcd is alive
2021-07-27 14:34:18.263 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=4, active=0, idle=4, waiting=0)
...
2021-07-27 14:34:48.263 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=4, active=0, idle=4, waiting=0)
...
2021-07-27 14:34:54.699 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@6b4ef4a7 is alive
2021-07-27 14:35:04.665 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@763217ad is alive
2021-07-27 14:35:10.616 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@52857c47 is alive
2021-07-27 14:35:18.263 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=4, active=0, idle=4, waiting=0)
...
2021-07-27 14:35:48.263 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=4, active=0, idle=4, waiting=0)
2021-07-27 14:36:09.980 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@6d16cbcd is alive
2021-07-27 14:36:18.264 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=4, active=0, idle=4, waiting=0)
2021-07-27 14:36:44.154 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Add connection elided, waiting=0, adders pending/running=8
2021-07-27 14:36:44.154 DEBUG 97145 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase          : prod-postingestion-pool - Closing connection org.postgresql.jdbc.PgConnection@763217ad: (connection has passed maxLifetime)
2021-07-27 14:36:46.545 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@6b4ef4a7 is alive
2021-07-27 14:36:48.264 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=3, active=0, idle=3, waiting=0)
...
2021-07-27 14:37:08.340 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@52857c47 is alive
2021-07-27 14:37:18.264 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=3, active=0, idle=3, waiting=0)
...
2021-07-27 14:37:48.264 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=3, active=0, idle=3, waiting=0)
2021-07-27 14:38:07.259 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@6d16cbcd is alive
2021-07-27 14:38:18.265 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=3, active=0, idle=3, waiting=0)
...
2021-07-27 14:38:38.391 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@6b4ef4a7 is alive
2021-07-27 14:38:48.265 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=3, active=0, idle=3, waiting=0)
...
2021-07-27 14:39:06.063 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@52857c47 is alive
2021-07-27 14:39:18.265 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=3, active=0, idle=3, waiting=0)
...
2021-07-27 14:39:48.266 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=3, active=0, idle=3, waiting=0)
...
2021-07-27 14:58:43.303 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@52857c47 is alive
2021-07-27 14:58:48.275 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=3, active=0, idle=3, waiting=0)
...
2021-07-27 14:59:08.699 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - keepalive: connection org.postgresql.jdbc.PgConnection@6b4ef4a7 is alive
2021-07-27 14:59:18.276 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=3, active=0, idle=3, waiting=0)
...
2021-07-27 14:59:35.641 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Add connection elided, waiting=0, adders pending/running=17
2021-07-27 14:59:35.641 DEBUG 97145 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase          : prod-postingestion-pool - Closing connection org.postgresql.jdbc.PgConnection@6d16cbcd: (connection has passed maxLifetime)
2021-07-27 14:59:48.276 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=2, active=0, idle=2, waiting=0)
...
2021-07-27 15:02:48.277 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=2, active=0, idle=2, waiting=0)
...
2021-07-27 15:02:51.934 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Add connection elided, waiting=0, adders pending/running=17
2021-07-27 15:02:51.935 DEBUG 97145 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase          : prod-postingestion-pool - Closing connection org.postgresql.jdbc.PgConnection@6b4ef4a7: (connection has passed maxLifetime)
2021-07-27 15:03:12.268 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Add connection elided, waiting=0, adders pending/running=17
2021-07-27 15:03:12.268 DEBUG 97145 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase          : prod-postingestion-pool - Closing connection org.postgresql.jdbc.PgConnection@52857c47: (connection has passed maxLifetime)
2021-07-27 15:03:18.279 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=0, active=0, idle=0, waiting=0)
...
2021-07-27 15:03:48.279 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=0, active=0, idle=0, waiting=0)
2021-07-27 15:04:18.279 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=0, active=0, idle=0, waiting=0)
...
2021-07-27 15:04:48.279 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=0, active=0, idle=0, waiting=0)
...
2021-07-27 15:04:51.612 DEBUG 97145 --- [   scheduling-1] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Add connection elided, waiting=1, adders pending/running=17
2021-07-27 15:05:18.280 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=0, active=0, idle=0, waiting=1)
2021-07-27 15:05:48.280 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=0, active=0, idle=0, waiting=1)
...
2021-07-27 15:09:18.282 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=0, active=0, idle=0, waiting=1)
2021-07-27 15:09:48.282 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Pool stats (total=0, active=0, idle=0, waiting=1)
2021-07-27 15:09:51.612 DEBUG 97145 --- [   scheduling-1] com.zaxxer.hikari.pool.HikariPool        : prod-postingestion-pool - Timeout failure stats (total=0, active=0, idle=0, waiting=0)
2021-07-27 15:09:51.622  WARN 97145 --- [   scheduling-1] o.h.engine.jdbc.spi.SqlExceptionHelper   : SQL Error: 0, SQLState: null
2021-07-27 15:09:51.622 ERROR 97145 --- [   scheduling-1] o.h.engine.jdbc.spi.SqlExceptionHelper   : prod-postingestion-pool - Connection is not available, request timed out after 300001ms.
2021-07-27 15:09:51.631 ERROR 97145 --- [   scheduling-1] o.s.s.s.TaskUtils$LoggingErrorHandler    : Unexpected error occurred in scheduled task
org.springframework.dao.DataAccessResourceFailureException: Unable to acquire JDBC Connection; nested exception is org.hibernate.exception.JDBCConnectionException: Unable to acquire JDBC Connection
at org.springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:277) ~[spring-orm-5.2.6.RELEASE.jar!/:5.2.6.RELEASE]
at org.springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:255) ~[spring-orm-5.2.6.RELEASE.jar!/:5.2.6.RELEASE]
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.translateExceptionIfPossible(AbstractEntityManagerFactoryBean.java:528) ~[
===

This log...
2021-07-27 14:59:35.641 DEBUG 97145 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool : prod-postingestion-pool - Add connection elided, waiting=0, adders pending/running=17

indicates that the connection adder thread is running ... and there are 17 other "adder tasks" piled up behind that one, waiting to add.
This means that the "adder" thread is simply "stuck" trying to add a connection. It is calling "getConnection()" on the underlying driver, and then timing out or failing, and then retrying.
The "adder talk" loops infinitely until it can fill the pool upto at least minimumIdle connections.
I recommend forcing a full stacktrace dump to check where the adder task thread is waiting.  My guess is either getConnection() on the underlying DataSource, or in the sleep before retry. If the getConnection() call is failing instantly on the underlying DataSource, you will see the adder task spending most of its time in the sleep between retries.

This issue is related to recently added new issue "Not removing a dead connection from the queue #1819".

"I recommend forcing a full stacktrace dump" -> I use PostGres driver. Is there anything I need to do to enable this? I have done all in my powers to extract maximum logs.

@KarthikeyanB007 Here are several ways to get stacktrace dumps:
https://access.redhat.com/solutions/18178

We are experiencing similar problems. We did not have the logging enabled, instead we read out the pool stats using Spring Actuator. However, we did create a thread dump at the time, which might be helpful:
"HikariPool-1 connection adder" #193102 daemon prio=5 os_prio=0 cpu=7.29ms elapsed=3499.00s tid=0x000055b81eebd800 nid=0x7892 runnable  [0x00007fa3a3f89000]
   java.lang.Thread.State: RUNNABLE
	at<EMAIL_ADDRESS>Method)
	at java.net.SocketInputStream.socketRead(java.base@11.0.5/SocketInputStream.java:115)
	at java.net.SocketInputStream.read(java.base@11.0.5/SocketInputStream.java:168)
	at java.net.SocketInputStream.read(java.base@11.0.5/SocketInputStream.java:140)
	at sun.security.ssl.SSLSocketInputRecord.read(java.base@11.0.5/SSLSocketInputRecord.java:448)
	at sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(java.base@11.0.5/SSLSocketInputRecord.java:68)
	at sun.security.ssl.SSLSocketImpl.readApplicationRecord(java.base@11.0.5/SSLSocketImpl.java:1104)
	at sun.security.ssl.SSLSocketImpl$AppInputStream.read(java.base@11.0.5/SSLSocketImpl.java:823)
	- locked <0x00000000f6c22358> (a sun.security.ssl.SSLSocketImpl$AppInputStream)
	at org.postgresql.core.VisibleBufferedInputStream.readMore(VisibleBufferedInputStream.java:161)
	at org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:128)
	at org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:113)
	at org.postgresql.core.VisibleBufferedInputStream.read(VisibleBufferedInputStream.java:73)
	at org.postgresql.core.PGStream.receiveChar(PGStream.java:370)
	at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:510)
	at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:146)
	at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:197)
	at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
	at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:211)
	at org.postgresql.Driver.makeConnection(Driver.java:459)
	at org.postgresql.Driver.connect(Driver.java:261)
	at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138)
	at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:358)
	at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:206)
	at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:477)
	at com.zaxxer.hikari.pool.HikariPool.access$100(HikariPool.java:71)
	at com.zaxxer.hikari.pool.HikariPool$PoolEntryCreator.call(HikariPool.java:725)
	at com.zaxxer.hikari.pool.HikariPool$PoolEntryCreator.call(HikariPool.java:711)
	at java.util.concurrent.FutureTask.run(java.base@11.0.5/FutureTask.java:264)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@11.0.5/ThreadPoolExecutor.java:1128)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@11.0.5/ThreadPoolExecutor.java:628)
	at java.lang.Thread.run(java.base@11.0.5/Thread.java:834)

So in our case there were also no connections available anymore and no connections were added either.
Looking at this part of the thread dump, it looks like PostgreSQL JDBC driver was able to setup a connection, but got stuck while authenticating.
We did not configured socket timeouts for the data source, so I assume the connection became stale and this process was waiting infinitely for the read to end. So setting a data source socket timeout might solve this, but, not sure I am correct, this will limit the execution time of your queries as well.
Just like mentioned here https://github.com/brettwooldridge/HikariCP/issues/1819#issuecomment-909875464 both the client and the PostgreSQL server are hosted on Azure.

I've also been experiencing this issue, and I was wondering, should I be using autoReconnect=true on jdbc url?

I've also been experiencing this issue.
I've already changed the properties autoReconnect=true to false and setMaximumPoolSize to higher and lower numbers
Here is my stacktrace:
[31merror[0m] from application in application-akka.actor.default-dispatcher-3 -
java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30001ms.
	at com.zaxxer.hikari.pool.HikariPool.createTimeoutException(HikariPool.java:696)
	at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:181)
	at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:146)
	at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:100)

from com.zaxxer.hikari.pool.PoolBase in xx - 5 connection closer - xx - 5 - Closing connection com.mysql.jdbc.JDBC4Connection@399823e1: (connection has passed maxLifetime)
from com.zaxxer.hikari.pool.HikariPool in xx - 5 connection adder - xx - 5 - Added connection com.mysql.jdbc.JDBC4Connection@29681660
from com.zaxxer.hikari.pool.PoolBase in xx - 3 connection closer - xx - 3 - Closing connection com.mysql.jdbc.JDBC4Connection@292be283: (connection has passed maxLifetime)
from com.zaxxer.hikari.pool.HikariPool in xx - 3 connection adder - xx - 3 - Added connection com.mysql.jdbc.JDBC4Connection@1d785115
from com.zaxxer.hikari.pool.PoolBase in xx - 5 connection closer - xx - 5 - Closing connection com.mysql.jdbc.JDBC4Connection@646e1c68: (connection has passed maxLifetime)
from com.zaxxer.hikari.pool.HikariPool in xx - 5 connection adder - xx - 5 - Added connection com.mysql.jdbc.JDBC4Connection@361f2f1
from com.zaxxer.hikari.pool.HikariPool in application-akka.actor.default-dispatcher-5 - HikariPool-1 - Timeout failure stats (total=64, active=64, idle=0, waiting=10)
from com.zaxxer.hikari.pool.HikariPool in application-akka.actor.default-dispatcher-6 - HikariPool-1 - Timeout failure stats (total=64, active=64, idle=0, waiting=9)
from com.zaxxer.hikari.pool.HikariPool in application-akka.actor.default-dispatcher-3 - HikariPool-1 - Timeout failure stats (total=64, active=64, idle=0, waiting=8)

It's seems to freeze when calling getConnection().

Yesterday I deployed the version 5.0.1, today I'm already getting this error.
Is there something I can do here to make this stop?

@toniclecb, Your situation sounds different, and much simpler. The log says you have 64 "active" connections. This means that there have been 64 connections borrowed from the pool that were never returned. You need to make sure that you close connections after you use them in order to return them to the pool.

Thanks @lfbayer
I've already define setLeakDetectionThreshold().
Today I got this:
3 housekeeper - Connection leak detection triggered for com.mysql.jdbc.JDBC4Connection@753bed27 on thread pool-6-thread-4, stack trace follows
3 housekeeper - Connection leak detection triggered for com.mysql.jdbc.JDBC4Connection@554264a5 on thread pool-6-thread-4, stack trace follows

thread-7 - Previously reported leaked connection com.mysql.jdbc.JDBC4Connection@1b4967c3 on thread pool-6-thread-4 was returned to the pool (unleaked)
thread-9 - Previously reported leaked connection com.mysql.jdbc.JDBC4Connection@5569decd on thread pool-6-thread-4 was returned to the pool (unleaked)

This means the two connections passed the time defined in setLeakDetectionThreshold, but were closed after that?
The stats now are similar to this:
1 housekeeper - AMTI - 1 - Pool stats (total=24, active=2, idle=22, waiting=0)
2 housekeeper - INATIVOS - Pool stats (total=24, active=0, idle=24, waiting=0)
4 housekeeper - AMTI - 4 - Pool stats (total=24, active=3, idle=21, waiting=0)
2 housekeeper - AMTI - 2 - Pool stats (total=24, active=0, idle=24, waiting=0)

Toni, there might be an easy solution for you which is use the DataSourceUtil class, I was having the same exceptions until I just ended up using it,
 return DataSourceUtils.getConnection(databasePool.getDataSource());
        <dependency>             <groupId>org.springframework</groupId>             <artifactId>spring-jdbc</artifactId>             <version>5.3.15</version>             <scope>compile</scope>         </dependency>

@PedroMPagani This is good advice. The doc for DataSourceUtils.getConnection() says:

Is aware of a corresponding Connection bound to the current thread, for example when using DataSourceTransactionManager. Will bind a Connection to the thread if transaction synchronization is active, e.g. when running within a JTA transaction).

My company's application implements a similar class to DataSourceUtils that returns the same Connection that a thread already holds if it requests another Connection, instead of consuming another one from the pool.

That's right @brettwooldridge, I didn't mention the doc trusting that fellow users would research the reason why, thank you!


refactor(tools): migrate scripts to Dart

Description

Migrated all scripts in the tools/ directory to Dart.
Updated any relevant references and documentation to reflect the new script locations and usage instructions.
Ensured that all migrated scripts are functional and tested within their new Dart implementation.

Related Issue

Type of Change

[ ] 🚀 feat – New feature (non-breaking change that adds functionality)
[ ] 🛠 fix – Bug fix (non-breaking change that fixes an issue)
[ ] ❌ ! – Breaking change (fix or feature that causes existing functionality to change)
[ ] ⚡ perf – Performance improvement
[x] 🧹 refactor – Code refactor (no functionality change)
[ ] 📝 docs – Documentation update
[ ] 🎨 style – Code style changes (formatting, renaming, etc.)
[ ] 🧪 test – Test update or addition
[ ] 🔧 build – Build related changes
[ ] ✅ ci – CI related changes
[ ] 🗑 chore – Chore (maintenance, non-production code change)
[ ] ◀  revert – Revert a previous commit

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 62.18%. Comparing base (c6c2c5c) to head (aa57eee).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #931   +/-   ##
=======================================
  Coverage   62.18%   62.18%
=======================================
  Files          34       34
  Lines        1145     1145
=======================================
  Hits          712      712
  Misses        433      433

Flag
Coverage Δ

generator
63.13% <ø> (ø)

win32
60.84% <ø> (ø)

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

----
🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles


PostgreSQL Vapor Packages won't compile after install

I installed PostgreSQL on my Mac and installed the PostgreSQL provider to my project but after I run my project it says how libpq-fe.h isn't found and also I've noticed the whole CPostgreSQL folder is empty under Dependencies. It also saysCould not build Objective-C module CPostgreSQL I'm guessing that's because the folder is empty. I have no clue how to fix this any any help would be greatly appreciated.

The fact that CPostgreSQL is empty is normal, it's a system module so it has no visible sources in Xcode.
But how did you install Postgres? If you install it with Homebrew, and Homebrew is installed in the default location, things should just work. But only then.

@vzsg I used the PostgreSQL app from their website for MacOS. I'm guessing this has to do with the problem

Alright after an hour of looking I figured out the solution. Under Dependencies I installed the line .Package(url: "https://github.com/vapor/postgresql.git", majorVersion: 2) .
Full Code

dependencies: [
.Package(url: "https://github.com/vapor/vapor.git", majorVersion: 2),
.Package(url: "https://github.com/vapor/fluent-provider.git", majorVersion: 1),
.Package(url: "https://github.com/vapor/postgresql.git", majorVersion: 2),
.Package(url: "https://github.com/vapor-community/postgresql-provider.git", majorVersion: 2, minor: 0)
]


Proposal: filter the tests using a make-variable

I think this is convenient when we'd like to execute specific tests via make command.
Example: make -C src test_terminal TEST_FILTER=wipe_buffer

Codecov Report

Merging #2695 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2695      +/-   ##
==========================================
- Coverage   74.85%   74.85%   -0.01%
==========================================
  Files          92       92
  Lines      133841   133841
==========================================
- Hits       100187   100180       -7
- Misses      33654    33661       +7

Impacted Files
Coverage Δ

src/version.c
80.8% <0%> (-1.02%)
:arrow_down:

src/if_xcmdsrv.c
84.17% <0%> (-0.36%)
:arrow_down:

src/os_unix.c
54.98% <0%> (-0.19%)
:arrow_down:

src/channel.c
82.82% <0%> (-0.13%)
:arrow_down:

src/mbyte.c
61.39% <0%> (-0.07%)
:arrow_down:

src/terminal.c
56% <0%> (-0.06%)
:arrow_down:

src/eval.c
81.24% <0%> (-0.05%)
:arrow_down:

src/gui_gtk_x11.c
47.7% <0%> (ø)
:arrow_up:

src/screen.c
77.28% <0%> (+0.02%)
:arrow_up:

src/syntax.c
78.15% <0%> (+0.02%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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

This is not useful?
https://github.com/ichizok/vim/blob/b3b8a1c765923c4140896f0ce5f86dcca5c907f3/src/testdir/runtest.vim#L277

This is not useful?
https://github.com/ichizok/vim/blob/b3b8a1c765923c4140896f0ce5f86dcca5c907f3/src/testdir/runtest.vim#L277

Unfortunately, this cannot be used from make command.
At first this pull-req was as below. This uses the above (filtering by argv(1)).
--- a/src/testdir/Makefile
+++ b/src/testdir/Makefile
@@ -128,7 +128,7 @@ newtestssilent: $(NEW_TESTS)
 .vim.res: writevimcmd
        @echo "$(VIMPROG)" > vimcmd
        @echo "$(RUN_VIMTEST)" >> vimcmd
-       $(RUN_VIMTEST) $(NO_INITS) -S runtest.vim $*.vim
+       $(RUN_VIMTEST) $(NO_INITS) -S runtest.vim $*.vim $(TEST_FILTER)
        @rm vimcmd

 test_gui.res: test_gui.vim

However, if in this way, Vim will interpret the string of $(TEST_FILTER) as file names and open them, so this may influence the behavior of tests (especially when TEST_FILTER includes wildcard characters).


Unexecutable secrets dockerfile

This file seems to be executable for no reason.

I've merged #344 into the next branch, so if you rebase this PR onto next, CircleCI should pass again.


[BUG] The content of assistant is <promptflow.tracing._trace.TracedIterator object at 0x………>, which causes the chat_history passed to LLM to be wrong

Describe the bug
A clear and concise description of the bug.
通过 pf flow test --flow new-chat-flow-created-at-2024-10-11  --interactive在终端进行交互式问答。
问答中，发现AI好像没有上下记忆，经过trace发现assistant 部分的content都是 <promptflow.tracing._trace.TracedIterator object at 0x………>，只有assistant的最后一次回答的content是正确的

How To Reproduce the bug
Steps to reproduce the behavior, how frequent can you experience the bug:

create new flow->chat flow with  a template

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Running Information(please complete the following information):

Promptflow Package Version using pf -v: [e.g. 0.0.102309906]
Operating System: [e.g. Ubuntu 20.04, Windows 11]
Python Version using python --version: [e.g. python==3.10.12]

{
  "promptflow": "1.16.1",
  "promptflow-core": "1.16.1",
  "promptflow-devkit": "1.16.1",
  "promptflow-tracing": "1.16.1"
}

Executable '/home/xxx/anaconda3/envs/reflextion/bin/python'
Python (Linux) 3.8.19 (default, Mar 20 2024, 19:58:24)
[GCC 11.2.0]

Additional context
Add any other context about the problem here.

I'm experiencing the same issue with Prompt flow 1.16.1.
Using the following code as a workaround:
from promptflow.tracing.contracts.iterator_proxy import IteratorProxy

if isinstance(output, IteratorProxy):
    output= "".join(output.items)

Can someone from Prompt flow team provide a comment on this? Is this a bug or an intended but undocumented change in the API?

Same for me as well. It would be great that some one can help take a check at this issue.
Setting:

Using "iterative mode (text only).
In the second round of the conversation, I printed out the chat history that was automatically constructed. The previous round's output from the chat module becomes a promptflow TracedIterator object, which is not JSON serializable and cannot be used in the second round of the conversation properly.

Versions:
Requirement already satisfied: promptflow in d:\programs\anaconda3\envs\py311\lib\site-packages (1.16.1)
Requirement already satisfied: promptflow-core==1.16.1 in d:\programs\anaconda3\envs\py311\lib\site-packages (from promptflow) (1.16.1)
Requirement already satisfied: promptflow-devkit==1.16.1 in d:\programs\anaconda3\envs\py311\lib\site-packages (from promptflow) (1.16.1)
Requirement already satisfied: promptflow-tracing==1.16.1 in d:\programs\anaconda3\envs\py311\lib\site-packages (from promptflow) (1.16.1)
Requirement already satisfied: promptflow-tools in d:\programs\anaconda3\envs\py311\lib\site-packages (1.4.0)
D:\Programs\Anaconda3\envs\py311\python.exe -m promptflow._cli._pf.entry flow test --flow d:\Repos\DRICopilot0820\DRICopilot\src\core\copilot_v2 --interactive --user-agent "prompt-flow-extension/1.20.2 (win32; x64) VSCode/1.94.2"


Handle Multiple Selections Gracefully in CollectivePicker.js

Currently the CollectivePicker.js component doesn't seem to handle multi selections very well. The styles seem to get broken;

This is particularly important in the Host Dashboard, Reports section where we need multi selections for the collective picker.
We could handle this by truncating the name and only showing the logo when multiple collectives are selected.

And when hovered over the collective logo we could show the full name of the collective.
Figma Design: https://www.figma.com/file/ZQBMWhnGGtRWeIZknFW1eP/[OC-Design]-Production-Ready-✅?node-id=13722%3A162076

@Betree : Let me know if the above suggestion of only showing the collective logo and a tool-tip sounds good. 😄
cc: @Memo-Es

@SudharakaP It does. Ideally make this responsiveness feature optional (eg <CollectivePicker useCompactMode={true} />).
We'll also need some truncation, but that can be done in a second iteration. Something like:

Filter by Collective
[ (:avocado: x) (:orange_circle: x) (:tomato: x) and  7 others ]

@Betree : I've added the useCompactMode support to the collective picker. I'll integrate this to our dashboard PRs as well. In the above PR, I've added the compactMode to the collective picker in the CreateGiftCardForm.js and in the virtual-card-collective-picker. I searched a bit and it seems these are the only two places in our code-base we use the multi select with collectives. 🤔

compactMode

Thanks for the details. If it's only used in these two places, then it looks safe to enable the new styles whenever isMulti is set. Feel free to remove compactMode if you feel it's a better approach.

compactMode

Thanks for the details. If it's only used in these two places, then it looks safe to enable the new styles whenever isMulti is set. Feel free to remove compactMode if you feel it's a better approach.

I've kept the compact mode for now as I felt it might be useful in the future to separate the compact mode (with the slightly smaller label values and rounded edges). Maybe we can extend that to other things too in the future; currently we only use this with the CollectivePicker. 🤔


Make Uint128 inner field private

Closes #905

Rebased!

LGTM. Just the merge conflict and running the markdown text formatter.

Want to merge #945 first? I think it will cause another conflict.


[Discussion]: DESIGN PRINCIPLE: Support for federation/interconnected TREs/multi-domain

Summary
Propose a principle that SATRE supports data being brought together
Source
DARE federation paper and other discussions
Detail
The SATRE architecture should support federation and connections between different data providers and data domains. This also aligns with the DARE federation paper and the work being done in TRE-FX etc.
Not to sure what this one should say but again it should have a statement, rationale and implications.
Intended Output
No response
Who can help
@jemrobinson @harisood - do you have Rob B's username? would be good to get his input on this one.

Not sure if he has GH, will share the issue with him!

Here I am ;-). Good principle to have; the future's going to be full of connected TREs (probably maybe ;-) ). I think I'd word it as "support for interconnected TREs". Federation is (I'll assert) something that can sit alongside TREs: vis, you don't need a pair of Security Servers to connect TRE A to TRE B (TELEPORT doesn't, f'r instance), but in a future network of many-to-many, you need something to standardise and formalise the trust relationship between them all, and that's what federation (and its standard Security Server gateways) is all about (as Simon T has observed).  The way I draw the "API Services" is meant to indicate they're part-TRE scope, part-Federation scope -- the principal interfaces between TREs. My classification into types -- Query/Result, Data Movement, Indexing and Software -- is pretty abstract and may not necessarily survive contact with the enemy (as in, people like yourselves actually doing the details ;-) ) -- in which case I'll adapt accordingly. Sometime, before the end of October but not too much before, you, I, TELEPORT and TRE-FX should proabbly have a big old integration brainstorm about these connection points.

Interesting @rmbaxter67 as a principle rather than any specific addition to the design I think would look something like the below. I am sure there will be lots of other implications, @harisood , be good to hear the community on this.
Research environments will support interconnectivity and federation
Rationale
The quality, scope and speed to research delivered can be increased by the ability to interconnect data of different types across multiple TREs. While much of the architecture to achieve this may sit outside the scope f the SATRE architecture the architecture must support and enable interconnectedness.
Implications

A cross federation service and service provider will be required to govern standards and manage shared infrastructure and applications.
Existing environments will need to change to align with a set of standards for which they were not originally designed.
Identities, authentication, and authorization needs to be independent of a single organisation.
Increasing need for standards for APIs, software services, indexing and cataloguing.

@all-contributors please add @rmbaxter67 for ideas

Hi team, as this principle wasn't discussed in the Collab Cafe, and haven't seen any further convos since, should it be dropped as a principle? It's loosely/tacitly touched upon in standardisation (see #241) but not very specific on federation. What do we think?

I think we should drop it, but add it as a FAQ-  SATRE can form the basis for future federation/interoperability/etc standards, but in itself is not about interoperability.


Distinguish between GitHub tags and branches

Is your feature request related to a problem? Please describe.
If you have a tag and a branch with the same name, there is only one Dockstore version for it. The Dockstore version will be updated with the change to the most recently changed one, i.e., if the branch is updated after the tag, the Dockstore will reflect the branch.
Describe the solution you'd like
Not sure, just logging it for now. It might be tricky to come up with a backwards-compatible solution. I guess there need to be separate Dockstore versions, one for the tag and one for the branch, but then you need a way to represent that in TRS.
Additional context
A user created a branch foo, created a tag foo, then deleted the branch foo, and the Dockstore version disappeared, even though the tag was still there.
┆Issue is synchronized with this Jira Story
┆Issue Number: DOCK-1874
┆Sprint: Backlog
┆Issue Type: Story

Workaround: don't do this https://stackoverflow.com/questions/12224773/refname-master-is-ambiguous


Thank you apple

For introducing ua agent sniffing into our framework :+1:

Best PR ever

Just a reminder for all of us: we need to remove this hack as soon as iOS will be fixed

I'm laughing reading the PR, but I still feel the pain of @RaananW going on for hours of bug hunting!

Love your choice of variable names, Raanan!! LOL

flushOS ?  ;-)


Multiplayer fighting game added

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes #4062

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Sypher0Dronzer ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

i have added the Readme.md file as requested
even tried deleting and adding again
yet this shows error
can you please review @kunjgit

@Sypher0Dronzer resolve the merge conflicts !

i have resolved the conflicts please review it @kunjgit


Not waiting for the stack to be removed

I'm running into an issue where the script is not waiting for the stack to be removed after docker stack rm <STACK> is run.
I know a bit of an odd use case, but in testing I stand up a stack then remove it before standing up again. However, without waiting for the stack to fully remove the next deploy fails because the stack is still being removed.

Hi @jeff-cook. That's not a use case I designed this script to handle. It could probably be added, but watching for a stack to be deleted should be a short loop similar to:
while ! docker stack services ${stack_name} 2>&1 | grep -q 'Nothing found in stack:'; do sleep 5; done

Closing since this is easy enough to do outside of this script.


Ensure compatible version of numpy in isolated_notebook_test.py

Keep numpy version in the isolated Python environment at 1.23 as
numpy-1.24 is incompatible with cirq and numba.
Fixes stuck notebook tests which import numba.
Related to #5967

ping - can somebody PTAL?

This PR LGTM, but as a general reflection: it replicates the constraints in requirements.txt, so I'm wondering whether there is a way to avoid the duplication?

Ack.  To my understanding this list of packages should simulate the jupyter/colab environment of a user running the examples for the first time.  The cirq is installed as a part of the notebook execution in that environment later.
As such the package lists can be different.
BTW, the !pip install cirq in the notebook will cause a numpy downgrade to 1.23 per cirq requirements, but the papermill process which executes the notebook seems to already have numpy-1.24 imported by that point.
The combination of import numpy, numba causes a SystemError with numpy-1.24.


Wording clarification and information additions

Under the "Synchronizing temporary passwords and "Force Password Change on Next Logon"" section, can we clarify the wording here? Especially for tenants that have synced users whose on-prem passwords have expired but the cloud password policy wasn't matching on-prem or a similar situation.
When the admin turns on this flag does it make everyone have to change their password at next logon or does nobody have to change it? Is there a way to make specific users have to change their password in Azure AD after enabling this flag at the tenant level?
In my understanding if I turn this feature on, then I need to individually go to each on-prem AD user with an expired password and set the "User must change password at next logon" flag and then run a sync in AD Connect to force them to change.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c900f942-4456-5238-9f4c-a7a5bd685c04
Version Independent ID: a5d7d971-765f-0977-f531-232ea5924121
Content: Implement password hash synchronization with Azure AD Connect sync
Content Source: articles/active-directory/hybrid/how-to-connect-password-hash-synchronization.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

Closing as opened under wrong Github account. Reopening with correct MS internal account.

@oneringmordor Thank you for updating the thread.


*_ignore_missing_prop tests failing in Linux

The three test_*_ignore_missing_prop() tests are failing for me using numpy 1.11.
Do they pass for you under Windows @birocoles?

@leouieda , I have already solved the problems with these tests. Let me know if these tests are still failing for you.

@birocoles everything passes this time


remove access token, use secret instead

I created a new access token for the Docker Hub account and deleted the previous one (because it would appear in older copied of the yaml file)


terra_sdk.exceptions.LCDResponseError: Status 500 - unsupported return type unspecified; supported types: sync, async

terra_sdk version: v2.0.1
Python version: 3.8
Operating System: ubuntu

Description
Describe what you were trying to get done.
Tell us what happened, what went wrong, and what you expected to happen.
 I transfer lunc
What I Did
Paste the command(s) you ran and the output.
`result = coro.send(None)
  File "/usr/local/lib/python3.8/dist-packages/terra_sdk/client/lcd/api/tx.py", line 318, in broadcast
    res = await self._broadcast(tx, "BROADCAST_MODE_BLOCK", options)
  File "/usr/local/lib/python3.8/dist-packages/terra_sdk/client/lcd/api/tx.py", line 265, in _broadcast
    return await self._c._post("/cosmos/tx/v1beta1/txs", data)  # , raw=True)
  File "/usr/local/lib/python3.8/dist-packages/terra_sdk/client/lcd/lcdclient.py", line 312, in _post
    result = await super()._post(*args, **kwargs)
  File "/usr/local/lib/python3.8/dist-packages/terra_sdk/client/lcd/lcdclient.py", line 137, in _post
    raise LCDResponseError(message=result.get("message"), response=response)
terra_sdk.exceptions.LCDResponseError: Status 500 - unsupported return type unspecified; supported types: sync, async`
If there was a crash, please include the traceback here.

@Vritra4 hello sir , can you help me ?


trig library

creating a trigonometric library

Trigonometric functions are functions related to an angle. There are six trigonometric functions: sine, cosine, tangent and their reciprocals cosecant, secant, and cotangent, respectively. Sine, cosine, and tangent are the most widely used trigonometric functions. Their reciprocals, though used, are less common in modern mathematics. Trigonometric functions are also called circular functions

ref

[ ] Implement sine, cosine, tan of an angle

[ ] Implementation/Read of trig functions CORDIC algorithm
[ ] Implementation of trig functions using Taylor Series
[ ] Implementation of trig functions using Chesbyshev Approximation
[ ] Benchmark these methods

I am going on a quick tangent here; I want to understand how exactly Taylor Series work and its applications; I will be writing down the notes on course/taylorseries.md


LIB-330 integrate self signed certificate and key into the project

Test Evidence

Fixed the browser for development purpose to mute the HTTPS self signed certificate notice in browser


Using the hotkeys sometimes will not work.

Sometimes when I need to toggle my brightness on of off then the keys don't work. When I do this then it will only change the setting sometimes, other times it will not do anything. This is happenign with the b key, and the bracket keys.
I am running Sodium and a mod named LambDynamicLights.

Might be just the thing with the latest release that if you toggle the brightness to maximum that the keys will change the normal brightness you had before instead of the maximum brightness currently in use, which is really confusing and unintuitive to be honest. I talked about that with the owner and made some changes and bug fixes myself. He pulled those changes and is currently still working on that I think, so you would have to wait for the release.
Im pretty sure its just that and not a real issue, because I don see a reason why the keybinds shouldnt work, its just that you dont see that as described above, so now you know, if you havent figured that out yourself by now.
If thats actually not it and its a real issue it would be great if you could specify "sometimes" a bit more.

Just put out a new update that may have resolved this issue. Drop a comment if the issue persists.


add task log & fix report url for mta

What this PR does / why we need it:
add task log & fix report url for mta

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story (FLPATH-xxxx):
Fixes #
Change type

[ ] New feature
[ ] Bug fix
[ ] Unit tests
[ ] Integration tests
[ ] CI
[ ] Documentation
[ ] Auto-generated SDK code

Impacted services

[ ] Workflow Service
[ ] Notification Service

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

/lgtm


fix(pressable-role-required): allows radio buttons

Assuming the following component was present in a code base:
<View accessibilityRole="radiogroup">
  <Pressable accessibilityRole="radio" accessibilityState={ checked: checked === "this one" } />
  <Pressable accessibilityRole="radio" accessibilityState={ checked: checked === "that one" } />
</View>

Then the pressable-role-required rule was being triggered due to the role not being button, link or imagebutton.
This PR allows a pressable to have a role of radio.
Let me know if this is okay @aryella-lacerda.
Thanks for this library!

@felipe-roque-web Thanks for the PR! Looks great 👍🏼 😁


feat(MatSelect): MatOptgroup should have programmatic capability

Feature Description
I have a need to programatically manipulate the mat-optgroup. My usecase has a cascade/sequence of filters (MatSelects) that is needed to query the backend for 'Automobiles' that match the query. The filters are things like 'Manufacturer', 'Model' etc..... So as the consumer selects a Manufacturer, the downstream filter for Model only shows the Models that correspond to that Manufacturer (or that set of manufacturers, as I am using 'multiple' on the MatSelect). The final set of filters make a graphql query (could well be a REST API instead) to the backend that return some attributes of the selected group of Autos, e.g. mpg, etc.) So pretty straightforward design.
Each filter is a multiple select filter where the end user can select multiple options on the filter. There is an 'All' option group that contains all of the options in the filter/MatSelect. Visually, the option group does what it should. But I need to programatically manipulate the option group. I have rules like - if none of the options are selected in a group, enable all the options in the group. Essentially, none is not a valid option. I need to:
(1) From an option find the parent option group
(2) Check if the option group has no options enabled and/or all options enabled
(3) Enable/Disable the entire option group in one API call.
I can provide additional details as needed.
I am working with Angular material 14.2.6
Use Case
Use cases provided in the Feature Description

Any thoughts on this request?

We don't really offer programmatic APIs for any of our components, because the idea is that this should be done through the template through something like ngFor.