Error in get_device Expected status code '200' but received '500'

Hi,
Yesterday I updated the integration from 1.0.58 to 1.1.2.
After that the integration stopped working with the error message:
Failed setup, will retry: Invalid response from API: (get_device: Expected status code 200, received: 500: {"code":5005,"message":"Adapter Communication error"}
I was still able to control the aircons with the Panasonic app.
I power cycled the aircons without success.
Today I downgraded the integration to 1.0.58 and all aircons immediately worked again.
I could dense it down that the changes between commit 09b623ca86627cc98a6064be59c4687791568f04 to commit 30f28db2adc87259d32937b7695c1e953a326e86 are causing this issue.
If I run:
action: update.install
target: { entity_id: update.panasonic_comfort_cloud_update }
data: { version: 30f28db2adc87259d32937b7695c1e953a326e86 }

the integration fails
and if I run:
action: update.install
target: { entity_id: update.panasonic_comfort_cloud_update }
data: { version: 09b623ca86627cc98a6064be59c4687791568f04 }

The integration works again.
Here the output of the log:
2024-08-08 14:07:01.251 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'2024-08-08 14:07:01.251 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:01.290 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:01.432 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:12.267 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:12.317 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:12.652 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:33.225 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:33.227 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:33.283 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:08:13.985 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:08:13.999 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:08:14.124 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:09:34.772 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:09:34.853 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:09:34.895 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:45.022 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Starting Session
2024-08-08 14:10:45.025 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsettings] Loaded settings from '/root/.panasonic-settings'
2024-08-08 14:10:45.026 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Access token is valid
2024-08-08 14:10:45.301 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/device/group, response: {"uiFlg":false,"groupCount":1,"groupList":[{"groupId":1397542,"groupName":"XXX","pairingList":[],"deviceList":[{"deviceGuid":"XXX","deviceType":"3","deviceName":"Office","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU12AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Guest Room ","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":22,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Master Bedroom","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":false,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"lastSettingMode":0},"deviceModuleNumber":"CS-XU18ZKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Study Area","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Bed Room 1","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false}]}]}
2024-08-08 14:10:45.302 INFO (MainThread) [custom_components.panasonic_cc] Got 5 devices
2024-08-08 14:10:45.637 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:45.638 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.333 seconds (success: False)
2024-08-08 14:10:45.684 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:45.684 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.378 seconds (success: False)
2024-08-08 14:10:45.800 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:45.800 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.494 seconds (success: False)
2024-08-08 14:10:46.409 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097446357,"permission":3,"summerHouse":0,"iAutoX":true,"nanoe":true,"nanoeStandAlone":true,"autoMode":false,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":false,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"insideTemperature":28,"outTemperature":126,"airQuality":0},"deviceNanoe":3}
2024-08-08 14:10:46.409 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:10:46.410 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 1.104 seconds (success: True)
2024-08-08 14:10:46.534 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097446471,"permission":3,"summerHouse":0,"iAutoX":false,"nanoe":true,"nanoeStandAlone":true,"autoMode":true,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":true,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"insideTemperature":29,"outTemperature":126,"airQuality":0},"deviceNanoe":2}
2024-08-08 14:10:46.534 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:10:46.534 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 1.232 seconds (success: True)
2024-08-08 14:10:50.806 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Starting Session
2024-08-08 14:10:50.810 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsettings] Loaded settings from '/root/.panasonic-settings'
2024-08-08 14:10:50.811 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Access token is valid
2024-08-08 14:10:51.157 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/device/group, response: {"uiFlg":false,"groupCount":1,"groupList":[{"groupId":1397542,"groupName":"XXX","pairingList":[],"deviceList":[{"deviceGuid":"XXX","deviceType":"3","deviceName":"Office","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU12AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Guest Room ","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":22,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Master Bedroom","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":false,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"lastSettingMode":0},"deviceModuleNumber":"CS-XU18ZKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Study Area","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Bed Room 1","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false}]}]}
2024-08-08 14:10:51.157 INFO (MainThread) [custom_components.panasonic_cc] Got 5 devices
2024-08-08 14:10:51.566 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:51.567 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.405 seconds (success: False)
2024-08-08 14:10:51.633 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:51.633 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.472 seconds (success: False)
2024-08-08 14:10:51.678 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:51.679 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.519 seconds (success: False)
2024-08-08 14:10:52.126 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097452058,"permission":3,"summerHouse":0,"iAutoX":true,"nanoe":true,"nanoeStandAlone":true,"autoMode":false,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":false,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"insideTemperature":28,"outTemperature":126,"airQuality":0},"deviceNanoe":3}
2024-08-08 14:10:52.126 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:10:52.127 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.966 seconds (success: True)
2024-08-08 14:10:52.156 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097452096,"permission":3,"summerHouse":0,"iAutoX":false,"nanoe":true,"nanoeStandAlone":true,"autoMode":true,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":true,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"insideTemperature":29,"outTemperature":126,"airQuality":0},"deviceNanoe":2}
2024-08-08 14:10:52.156 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:10:52.156 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.998 seconds (success: True)
2024-08-08 14:11:01.941 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Starting Session
2024-08-08 14:11:01.943 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsettings] Loaded settings from '/root/.panasonic-settings'
2024-08-08 14:11:01.945 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Access token is valid
2024-08-08 14:11:02.151 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/device/group, response: {"uiFlg":false,"groupCount":1,"groupList":[{"groupId":1397542,"groupName":"XXX","pairingList":[],"deviceList":[{"deviceGuid":"XXX","deviceType":"3","deviceName":"Office","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU12AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Guest Room ","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":22,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Master Bedroom","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":false,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"lastSettingMode":0},"deviceModuleNumber":"CS-XU18ZKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Study Area","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Bed Room 1","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false}]}]}
2024-08-08 14:11:02.151 INFO (MainThread) [custom_components.panasonic_cc] Got 5 devices
2024-08-08 14:11:02.504 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:11:02.505 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.351 seconds (success: False)
2024-08-08 14:11:02.704 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:11:02.705 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.549 seconds (success: False)
2024-08-08 14:11:02.717 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:11:02.718 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.562 seconds (success: False)
2024-08-08 14:11:03.228 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097463172,"permission":3,"summerHouse":0,"iAutoX":false,"nanoe":true,"nanoeStandAlone":true,"autoMode":true,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":true,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"insideTemperature":29,"outTemperature":126,"airQuality":0},"deviceNanoe":2}
2024-08-08 14:11:03.228 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:11:03.229 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 1.077 seconds (success: True)
2024-08-08 14:11:03.266 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097463207,"permission":3,"summerHouse":0,"iAutoX":true,"nanoe":true,"nanoeStandAlone":true,"autoMode":false,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":false,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"insideTemperature":28,"outTemperature":126,"airQuality":0},"deviceNanoe":3}
2024-08-08 14:11:03.266 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:11:03.266 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 1.111 seconds (success: True)
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:01.290 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:01.432 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:12.267 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:12.317 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:12.652 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:33.225 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:33.227 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:07:33.283 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:08:13.985 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:08:13.999 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:08:14.124 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:09:34.772 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:09:34.853 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:09:34.895 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:45.022 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Starting Session
2024-08-08 14:10:45.025 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsettings] Loaded settings from '/root/.panasonic-settings'
2024-08-08 14:10:45.026 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Access token is valid
2024-08-08 14:10:45.301 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/device/group, response: {"uiFlg":false,"groupCount":1,"groupList":[{"groupId":1397542,"groupName":"XXX","pairingList":[],"deviceList":[{"deviceGuid":"XXX","deviceType":"3","deviceName":"Office","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU12AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Guest Room ","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":22,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Master Bedroom","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":false,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"lastSettingMode":0},"deviceModuleNumber":"CS-XU18ZKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Study Area","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Bed Room 1","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false}]}]}
2024-08-08 14:10:45.302 INFO (MainThread) [custom_components.panasonic_cc] Got 5 devices
2024-08-08 14:10:45.637 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:45.638 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.333 seconds (success: False)
2024-08-08 14:10:45.684 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:45.684 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.378 seconds (success: False)
2024-08-08 14:10:45.800 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:45.800 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.494 seconds (success: False)
2024-08-08 14:10:46.409 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097446357,"permission":3,"summerHouse":0,"iAutoX":true,"nanoe":true,"nanoeStandAlone":true,"autoMode":false,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":false,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"insideTemperature":28,"outTemperature":126,"airQuality":0},"deviceNanoe":3}
2024-08-08 14:10:46.409 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:10:46.410 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 1.104 seconds (success: True)
2024-08-08 14:10:46.534 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097446471,"permission":3,"summerHouse":0,"iAutoX":false,"nanoe":true,"nanoeStandAlone":true,"autoMode":true,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":true,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"insideTemperature":29,"outTemperature":126,"airQuality":0},"deviceNanoe":2}
2024-08-08 14:10:46.534 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:10:46.534 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 1.232 seconds (success: True)
2024-08-08 14:10:50.806 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Starting Session
2024-08-08 14:10:50.810 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsettings] Loaded settings from '/root/.panasonic-settings'
2024-08-08 14:10:50.811 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Access token is valid
2024-08-08 14:10:51.157 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/device/group, response: {"uiFlg":false,"groupCount":1,"groupList":[{"groupId":1397542,"groupName":"XXX","pairingList":[],"deviceList":[{"deviceGuid":"XXX","deviceType":"3","deviceName":"Office","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU12AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Guest Room ","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":22,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Master Bedroom","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":false,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"lastSettingMode":0},"deviceModuleNumber":"CS-XU18ZKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Study Area","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Bed Room 1","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false}]}]}
2024-08-08 14:10:51.157 INFO (MainThread) [custom_components.panasonic_cc] Got 5 devices
2024-08-08 14:10:51.566 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:51.567 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.405 seconds (success: False)
2024-08-08 14:10:51.633 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:51.633 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.472 seconds (success: False)
2024-08-08 14:10:51.678 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:10:51.679 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.519 seconds (success: False)
2024-08-08 14:10:52.126 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097452058,"permission":3,"summerHouse":0,"iAutoX":true,"nanoe":true,"nanoeStandAlone":true,"autoMode":false,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":false,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"insideTemperature":28,"outTemperature":126,"airQuality":0},"deviceNanoe":3}
2024-08-08 14:10:52.126 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:10:52.127 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.966 seconds (success: True)
2024-08-08 14:10:52.156 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097452096,"permission":3,"summerHouse":0,"iAutoX":false,"nanoe":true,"nanoeStandAlone":true,"autoMode":true,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":true,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"insideTemperature":29,"outTemperature":126,"airQuality":0},"deviceNanoe":2}
2024-08-08 14:10:52.156 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:10:52.156 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.998 seconds (success: True)
2024-08-08 14:11:01.941 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Starting Session
2024-08-08 14:11:01.943 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsettings] Loaded settings from '/root/.panasonic-settings'
2024-08-08 14:11:01.945 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] Access token is valid
2024-08-08 14:11:02.151 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/device/group, response: {"uiFlg":false,"groupCount":1,"groupList":[{"groupId":1397542,"groupName":"XXX","pairingList":[],"deviceList":[{"deviceGuid":"XXX","deviceType":"3","deviceName":"Office","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU12AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Guest Room ","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":22,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Master Bedroom","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":false,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"lastSettingMode":0},"deviceModuleNumber":"CS-XU18ZKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Study Area","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false},{"deviceGuid":"XXX","deviceType":"3","deviceName":"Bed Room 1","permission":3,"temperatureUnit":0,"summerHouse":0,"nanoeStandAlone":true,"autoMode":true,"modeAvlList":{"autoMode":1},"parameters":{"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoFunctionData":1,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":0,"airDirection":1,"lastSettingMode":0},"deviceModuleNumber":"CS-KU9AKH-1","deviceHashGuid":"XXX","modelVersion":2,"coordinableFlg":true,"pairedFlg":false}]}]}
2024-08-08 14:11:02.151 INFO (MainThread) [custom_components.panasonic_cc] Got 5 devices
2024-08-08 14:11:02.504 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:11:02.505 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.351 seconds (success: False)
2024-08-08 14:11:02.704 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:11:02.705 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.549 seconds (success: False)
2024-08-08 14:11:02.717 ERROR (MainThread) [custom_components.panasonic_cc.pcomfortcloud.helpers] Error in get_device
Expected status code '200' but received '500'
Response body: {"code":5005,"message":"Adapter Communication error"}
2024-08-08 14:11:02.718 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 0.562 seconds (success: False)
2024-08-08 14:11:03.228 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097463172,"permission":3,"summerHouse":0,"iAutoX":false,"nanoe":true,"nanoeStandAlone":true,"autoMode":true,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":true,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":0,"temperatureSet":25,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":1,"iAuto":0,"airDirection":1,"insideTemperature":29,"outTemperature":126,"airQuality":0},"deviceNanoe":2}
2024-08-08 14:11:03.228 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:11:03.229 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 1.077 seconds (success: True)
2024-08-08 14:11:03.266 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicsession] GET url: https://accsmart.panasonic.com/deviceStatus/XXX, response: {"timestamp":1723097463207,"permission":3,"summerHouse":0,"iAutoX":true,"nanoe":true,"nanoeStandAlone":true,"autoMode":false,"heatMode":false,"fanMode":false,"dryMode":true,"coolMode":true,"ecoNavi":false,"powerfulMode":false,"quietMode":true,"airSwingLR":true,"autoSwingUD":true,"ecoFunction":1,"temperatureUnit":0,"modeAvlList":{"autoMode":1},"nanoeList":{"visualizationShow":0},"clothesDrying":false,"insideCleaning":true,"fireplace":false,"pairedFlg":false,"parameters":{"ecoFunctionData":1,"insideCleaning":1,"fireplace":0,"lastSettingMode":0,"operate":0,"operationMode":2,"temperatureSet":23,"fanSpeed":0,"fanAutoMode":0,"airSwingLR":2,"airSwingUD":2,"ecoMode":0,"ecoNavi":0,"nanoe":4,"iAuto":1,"airDirection":0,"insideTemperature":28,"outTemperature":126,"airQuality":0},"deviceNanoe":3}
2024-08-08 14:11:03.266 DEBUG (MainThread) [custom_components.panasonic_cc.pcomfortcloud.panasonicdevice] Loading device parameters, has data: True
2024-08-08 14:11:03.266 DEBUG (MainThread) [custom_components.panasonic_cc.coordinator] Finished fetching Panasonic Device Coordinator data in 1.111 seconds (success: True)

Had this exact same error on anything higher than 1.1 and downgrading to 1.0.56 immediately solved it. Did you by chance have any devices that were having issues in the app also? I had one unit that (still) needs the reset button to be pushed, and I'm wondering if that failing knocked the whole thing over?

Hi, the {"code":5005,"message":"Adapter Communication error"} indicates that the Panasonic servers couldn't connect to your devices.
One thing that has changed in the v1.1 is that it's fully async, maybe that is causing an issue when you have many devices. I can change, so the integration doesn't do any parallel calls to the API.

Hi, the {"code":5005,"message":"Adapter Communication error"} indicates that the Panasonic servers couldn't connect to your devices.

But that would mean also the ComfortCloud app wouldn't work when I'm not in the network,
and that is not the case.
Furthermore downgrading wouldn't help.

One thing that has changed in the v1.1 is that it's fully async, maybe that is causing an issue when you have many devices. I can change, so the integration doesn't do any parallel calls to the API.

I just have 5 devices.
Sounds like a plan.
Can I try that by my self? Could that be added as a configuration parameter?

Try v1.1.6 see if it helps, I've limited the concurrent api calls to one

Try v1.1.6 see if it helps, I've limited the concurrent api calls to one

I'll have a look in the morning and let you know

Hi, just updated to v.1.1.6 and then to v.1.1.7 and it is working 👍
Thank you!


Your a element should be nested within your new p element.

Challenge Nest an Anchor Element within a Paragraph has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
 -You want to nest paragraph around existing anchor (you have an extra one that  has the wrong text (look in the instructions for correct text/string) - help is a great place for questions like this.

@Naresh713
Thanks for reporting this. But your code is incorrect.
GitHub Issues are for reporting bugs on the website only.
Please use the Help chat room for getting challenge related help.
Happy Coding!

Your a element should be nested within your new p element.
Your p element should have the text "View more " (with a space after it).
MY CODE IS:
CatPhotoApp

cat photos

Here's a  link to cat photos.org "View more".

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.

Help please.

CatPhotoApp

cat photos

Here's a  link to cat photos.org "View more".

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.

CODE.docx


Panic diffing yaml

Hello, I received a panic in difftastic when updating a Github Actions job.
Here is difftastic's output:
thread 'main' panicked at 'index out of bounds: the len is 2 but the index is 2', src/display/side_by_side.rs:185:35
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::panic_bounds_check
   3: difft::display::side_by_side::print
   4: difft::print_diff_result
   5: difft::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I have managed to produce the following minimal diff that causes the panic:
Before:
foo: |
  ${{ BAR }}

After:
foo: |
  bar

Note: The trailing newlines are important -- no panic without them.
$ difft --version
Difftastic 0.52.0
$ uname -a
Linux ubuntu 6.2.0-36-generic #37~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct  9 15:34:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Note: while I'm on Ubuntu, difftastic is installed via nix.

Thanks for this tool, by the way! I'm always sad on the rare occasions (like now) when I need to git diff --no-ext-diff.

Thanks, I can repro.


Add #![no_std] Support

In theory winapi-rs should be able to work with #![no_std], however there are a few cases where std is used that prevents winapi-rs from being used with a #![no_std] crate:

std::raw::os is used to get C types without depending directly on libc. To get around this we simply copy the definitions from std::raw::os. This is a potential source of issues if the definitions in std are updated and the local ones aren't, but that seems unlikely since C types aren't likely to change any time soon.
std::mem and std::ops are used within the RIDL!{} macro to make using COM types more ergonomic. mem and ops are already being re-exported by std from core, however we can't just use core directly in winapi because core is unstable and can only be used on nightly. To get around this we create a local std module to re-export those features and only compile it when #![no_std] is used.

To allow users to choose whether they want #![no_std] support I've added a "no_std" feature.
I don't know if this feature is desirable, so I've only done a proof of concept in this initial PR. If it is decided that this feature is worth adding there are a few more things that will need to be done before this is ready to merge:

The "no_std" feature will need to be added to all of the -sys crates, as well as the conditional compilation flags for applying #![no_std].
Additional settings will need to be added to the continuous integration settings for Travis and Appveyor so that this "no_std" feature can be tested.

Unresolved Questions

Should the dummy std module be left inline in lib.rs or should it be moved to a separate file.
Will RIDL!{} and the other macros that rely on std::mem/std::ops ever be used outside of winapi? If so any references to std will need to be replaced with $crate::std.

Theoretically yes, I did actually have winapi using no_std before, however it isn't entirely practical. Since this library will only ever be used on Windows, which isn't really an embedded platform, there isn't really a need to not use std, nor are there any alternate std libraries. As such I'd rather wait until if and when no_std becomes stable.

Fair enough. I was only playing with no_std on my machine as an experiment anyway, so it's not like I have a valid use case.


Steps for checking that your html_root_url is correct

Hyper has been using a bad html_root_url since 0.10.7 (https://github.com/hyperium/hyper/issues/1193). Let's explain or link to an explanation of how to pick the right html_root_url so users are not forced to guess.

I would much rather this somehow be automated in Cargo or something, maybe via env!("CARGO_PKG_VERSION") or something.

Yes keeping the version updated automatically would be great! That would solve the problem of an outdated version in html_root_url like https://github.com/carllerche/mio/issues/613.
I don't think it would solve https://github.com/hyperium/hyper/commit/aee7c991e6af3e6a4baf528e7ff107f412c7bebf and similar. Rustdoc urls have a tendency to be confusing. Which of these is the right html_root_url?

https://hyperium.github.io/hyper/hyper/index.html
https://hyperium.github.io/hyper/hyper/
https://hyperium.github.io/hyper/hyper
https://hyperium.github.io/hyper/
https://hyperium.github.io/hyper
https://hyperium.github.io/
https://hyperium.github.io

Let's check the book.

You can control a few aspects of the HTML that rustdoc generates through the #![doc] version of the attribute:
#![doc(html_logo_url = "https://www.rust-lang.org/logos/rust-logo-128x128-blk-v2.png",
       html_favicon_url = "https://www.rust-lang.org/favicon.ico",
       html_root_url = "https://doc.rust-lang.org/")]

This sets a few different options, with a logo, favicon, and a root URL.

:crying_cat_face:

The html_root_url attribute is not (yet?) mentioned in the second edition of the book so for now we will need to provide more explanation here than we may like. https://github.com/rust-lang/book/issues/725

We removed the html_root_url recommendation.


Add speed and streak points counter

First PR, small changes, adds the feature streak feature + additional points for 1st, 2nd and 3rd.
Relates to https://github.com/sQuiz-2/Core/issues/6

Really clear and nicely done :100::100::100:


loading svg previewers

The same only for the "beta" version

I see this was merged? Does that mean we can close the following issue?

#59


refactor(frontend): move hide info utils to common folder

Motivation
Since we are going to re-use them, we move the hide info utils to the common lib folder. And we add tests.
Note
I am not using zod for the keys list because I am replicating the way we do for modals, defining explicit string types. I am not 100% sure that zod enforces the strings in the same way.

@peterpeterparker you are right, I will do the rename in another PR

[OISY-130]


Changes to IPF scraper to expose versioning and stop stall during scihub query

Changes to IPF scraper to expose versioning and stop stall during scihub query

expose release in AOI_based_ipf_submitter job so we can configure ipf_scraper job's release to run on (currently hardcoded to master)

If ipf_scraper falls back to Scihub, hitting the product scihub downlaod url here to check if prod_available (due to Long term Archive). However, if product is online, we will hit causeSoftTimeLimit exceeded as the request attempts to download the SLC which takes a long time:

The requests timeout does not work either since it is receiving bytes from server.
Issue is prevalent when ipf_scraper attempts to scrape IPF for the latest acquisitions which ASF does not have the SLC online yet... (when cron is trigerred)
Changed logic to:
i) check if product is online by checking product entry xml
ii) if product is online, proceed to extract manifest
iii) if product is not online, proceed to hit download_url to make it online for later (should return 202), exit with Exception
Tests:

Fall back to Scihub if ASF does not have SLC yet: gist
If ASF is down, Scihub's in LongTermArchive:  gist

PR for consideration? @NamrataM @pymonger

Please do not merge yet. Still testing. Apparently, some of the requests to get manifest form Scihub are timing out, not sure if it is common.

We have merged this in https://github.com/earthobservatory/scihub_acquisition_scraper/pull/4

This is a great patch. Thanks!
For condition:

if product is not online, proceed to hit download_url to make it online for later (should return 202), exit with Exception
It would not publish update of IPF to ES.

The philosophy of these recent scraper jobs is to make each run in a "best effort" basis for improved operations in mind. Therefore it is recommended to make each produce offline state logged out to file. Later one, we will have SDSWatch for logging out this SDS-level condition to inform operators.
Also, since each runtime will be "best effort" basis, the next time this scraper is run, the IPF offline last time should go through once it has been resurrected from colder archive.

Closing this PR since IPF scraper has been changed to be decoupled


fileload do not fire when using cache.manifest to cache the sounds

fileload event do not fire when using cache.manifest to cache the sounds.
The first time.it didnt use the cache to load the sounds, everthing works fine. But when load the sounds from manifest cache.It wont fire the fileload event;
var Sound = createjs.Sound,
        sounds = [
            {id:"coin", src:"coin.mp3"},
            {id:"over", src:"over.mp3"},
            {id:"ready", src:"ready.mp3"}
        ];

    var listener = Sound.on('fileload', function () {
        alert('loaded');
    });
    Sound.registerSounds(sounds, 'static/');

my cache.mainfest is as followed
CACHE MANIFEST
#2015-08-03 v1.0.13
static/coin.mp3
static/over.mp3
static/ready.mp3

NETWORK:
*

Is there any workaround?


Enable betterMatchTypeExtractors in >= 3.6

Closes #20538.

baseVersion is already 3.6.0 so I think we can just make the feature non-experimental now

This should also be deprecated in 3.6.0.

Done ✅

Wait, should it really be merged now? I thought we should wait for a minor release.

We are on a minor release cycle, we are currently working on 3.6.0


mysql

Description

I have no idea of how to configure agent to collect the performance data of mysql. Could you tell how to modify the configuration of agent? Ths.
Environment

Pinpoint version:1.6.2
OS Red Hat Enterprise Linux Server release 6.8 (Santiago)

Additional Info

Hi @scdxl
We don't directly monitor mysql so there isn't a way to collect performance data of mysql instances.
Instead, we intercept calls made by the mysql jdbc client (applications) to trace query information and call statistics.

Hi @Xylus
Could you tell how can I intercept mysql calls? That's will be thankful you give me an example. Ths.

They should automatically be traced without configuring anything. Are they not showing up in your server map / call stack?
(Note that support for mysql java connector 6+ has only been recently added to master and isn't available in 1.6.2)

@Xylus Any plan on getting them on version 1.6.2?

@xbblq7n We can't get them on version 1.6.2 as it's already been released. It'll however be included in the 1.7.0 release.
Of course, you can always build from master for 1.7.0-SNAPSHOT and use that.

It may be caused by profiler.sampling.rate in pinpoint.config which default value is 20.
As the comment along with this said "1 out of n transactions will be sampled where n is the rate. (20: 5%)"

@tedli Do you want to change the default value to 50 to get the SQL calls in PInpoint

@xbblq7n the sampling rate varies depending on everyone's business logic needs. I think it is significant to put the comment in a more conspicuous place like the readme doc to let ones who fresh to pinpiont know about it.
And I don't think alter to 50 means sampling more as it says "1 out of n", so if you want 50% sampling rate you can try altering 20 to 2.
P.S. if you speak Chinese, here is what I mean:
采样率取决于各家的业务逻辑，如果被采样的接口调用并发量非常大，那么高采样率开销太大了，搞不好 pinpoint 的 collector 都受不了，这种情况降低采样率得到的数据也非常有参考价值，反之，如果采样的接口总共也没几次调用，那么采样率很低的话，很有可能采样不到，或采到的数据参考价值很低。
而且改成 50 应该不是提高采样率，注释说的是 n 分之 1，想得到 50% 采样率的话，应该改成 2。

@tedli Thanks


Only build wheels on rc tags

Which issue does this PR close?

Part of https://github.com/apache/arrow-datafusion-python/issues/7
Rationale for this change

We want to vote on the release candidate wheels and then publish those wheels to PyPi when the vote passes, rather than building new wheels when we tag the release.
What changes are included in this PR?

Change the pattern from "*" to "*-rc*"
Are there any user-facing changes?

@isidentical @francis-du fyi

Don't you also need to build wheels for absolute versions (like 0.7.0 vs `0.7.0rc1) since they also need final wheels (you are changing the version which changes the wheel contents)

Don't you also need to build wheels for absolute versions (like 0.7.0 vs `0.7.0rc1) since they also need final wheels (you are changing the version which changes the wheel contents)

The version number in the Cargo.toml and in the wheel filename is 0.7.0. The rc1 part only appears as the GitHub tag name.
datafusion-0.7.0-cp37-abi3-manylinux_2_12_x86_64.manylinux2010_x86_64.whl
datafusion-0.7.0-cp37-abi3-win_amd64.whl
datafusion-0.7.0-cp37-abi3-macosx_10_7_x86_64.whl

This means we can vote on the source tarball and these wheels and then publish them once the vote passes, and add the 0.7.0 tag to the repo.
The key ASF restriction here is that we need to release the artifacts that we voted on rather than build new ones.


Is RETURNING supported in Postgres inserts?

For some reason I cannot get the RETURNING clause appended to my Postgres query so I can use the last inserted primary id (I'm hoping to be able to use account.AccountID after the returning clause starts working):
_, err := db.NewInsert().
  Model(account).
  Returning("*").
  Exec(ctx)

Returns a query like this (without the RETURNING * clause):
INSERT INTO "accounts" ("account_id", "uid") VALUES (DEFAULT, 'c4uvnil9481e93skjcb0');

What am I missing? :(

github.com/uptrace/bun v1.0.21
github.com/uptrace/bun/dialect/pgdialect v1.0.20
github.com/uptrace/bun/driver/pgdriver v1.0.20
PostgreSQL 13.3 on x86_64-apple-darwin

Try replacing v1.0.20 with v1.0.21 for all packages. See https://github.com/uptrace/bun/issues/401

Wow, that did it. Thank you so much!


Incorrect plugin version match

Currently the cookbook returns the same version for all plugins installed. This means that if you specify plugin versions for several different plugins, they get repeatedly reinstalled because the version doesn't match the very first plugin for all of them.
That's because of this code, from providers/plugin.rb:
def load_current_resource
  @current_resource = Chef::Resource::VagrantPlugin.new(new_resource)
  vp = shell_out("vagrant plugin list")
  if vp.stdout.include?(new_resource.plugin_name)
    @current_resource.installed(true)
    @current_resource.installed_version(vp.stdout.split[1].gsub(/[\(\)]/, ''))
  end
  @current_resource
end

See how the installed_version line with the regexp doesn't depend on which plugin name is being queried? The cookbook will probably need to actually parse the output. Here's example output with constraints, as sample input:
Athanor:madscience_gem noah$ vagrant plugin list
vagrant-aws (0.6.0)
vagrant-digitalocean (0.7.3)
  - Version Constraint: 0.7.3
vagrant-host-shell (0.0.4)
  - Version Constraint: 0.0.4
vagrant-librarian-chef (0.2.1)
  - Version Constraint: 0.2.1
vagrant-linode (0.1.1)
  - Version Constraint: 0.1.1
vagrant-omnibus (1.4.1)
  - Version Constraint: 1.4.1
vagrant-share (1.1.4, system)

This is annoying me right now, so maybe I'll make a pull request happen for this.

#21 was merged.


option to specify columns in config.ini by letter

New user here. Upon first time using this app, I got an error about wrong data type in a column. It took me a minute to realize that the column numbering in config.ini is 0-based. While that is typical for a python application, it is unexpected for regular users of spreadsheets (or for me at least). As you know, in spreadsheets, the first row is row 1 (not 0) and the first column is A. So, I propose that the config.ini file allow for the user to specify the columns by letter. Furthermore, the readme could be updated to instruct users to input column letters in the config.ini. The old numeric input could still be accepted, so this would not be a breaking change. Thoughts?

Thanks for sharing this perspective: the case you're making to improve user friendliness for spreadsheet users is solid. I think it should be done as a non breaking change, as you suggested (i.e. the config file should accept both letters and numbers). I'd be happy to review a PR if you or anybody else wants to do this.


Refactor

Good to think about refactoring the code, and great from you to share it :+1:  .. Thanks for your contributions.

I just wanted to put the code somewhere else and call it.
The main goal is to make the the whole package ready to have unit tests.

Since we are resolving the new classes through the IOC container (app() helper function) now we can mock them and replace them with mock objects.


Bugfix Flutter build web

Thanks for your great YT lib 👍
and for the great documentation 🥇
I had an issues with building for the web:
../../yt/lib/src/provider/data/videos.dart:3:1:
Error: 'HttpResponse' is imported from both 'package:retrofit/dio.dart' and
'package:universal_io/src/http/http.dart'.
import 'package:universal_io/io.dart';
^^^^^^^^^^^^
../../yt/lib/src/provider/data/videos.g.dart:126:26:
Error: 'HttpResponse' is imported from both 'package:retrofit/dio.dart' and
'package:universal_io/src/http/http.dart'.
final httpResponse = HttpResponse(value, _result);
^^^^^^^^^^^^
Error: Compilation failed.
I fixed this in my PR.

@udiedrichsen, I've published v1.2.2 with your changes merged.


Some markdown tutorials for the important modules

Description
Describe your changes in detail.
Motivation and Context
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
You can use the syntax close #15213 if this solves the issue #15213

[ ] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation (update in the documentation)
[ ] Example (update in the folder of example)

Implemented Tasks

[ ] Subtask 1
[ ] Subtask 2
[ ] Subtask 3

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[x] I have read the CONTRIBUTION guide. (required)
[ ] My change requires a change to the documentation.
[ ] I have updated the tests accordingly. (required for a bug fix or a new feature)
[ ] I have updated the documentation accordingly.

Hi @hidjq. Thanks for the PR. Some of the modules have been changed. Would you mind splitting the PR into multiple ones? How about let's get started with the ChatAgent?

@lightaime I think I will merge this

@Obs01ete I believe some of the files are outdated in this PR.
For instance, in the ChatAgent, we have
user_msg = BaseMessage(
    role_name="Patient",
    role_type=RoleType.USER,
    role = "user",
    meta_dict=dict(),content="Hello!"
)

however, the role was removed.

Closed since not active.


Adding UI and logic to upload file and display results

@kirantejatummuri There are conflicts in this one.


Allow passing additional arguments to renamePageCommand and renamePrefixCommand

Adds the ability to send additional arguments to renamePageCommand and renamePrefixCommand of the index plug, as well as returning true or false from each command to indicate whether the action was successful.
The arguments are completely optional, and the existing behavior remains the default when the additional arguments aren't provided, so everything remains fully backward-compatible.
Why
I've created a tree view component/plug and one of the desired features is to allow dragging and dropping nodes to rename pages. That renaming functionality already exists via these two methods, but we need to be able to pass in some values that are currently hard-coded in those functions. We also need to know whether the operation succeeded or failed to determine if the tree should be updated, and - in some cases - whether the user should be redirected to the renamed page.
renamePageCommand
This command already allowed a page argument to be provided that specified the name to rename to. If this wasn't provided the user is prompted for a new name. The following additional arguments can now be passed:

oldPage - This is the page to be renamed from. Previous behavior always used the current page (editor.getCurrentPage()), and this is still the case if oldPage is not provided. But in the case of the tree view, the user may be dragging  page other than the current one.
navigateThere - Specifies whether, after the rename, the user should be navigated to the new page. Previously this was always true, because it was always the current page being renamed, so it made sense to navigate to the updated page. This still defaults to true, but can be override to prevent that behavior. If the user drags a node from the tree view that isn't the current page, we don't want to redirect them to that page.

renamePrefixCommand
This command is written in a way that always prompts the user for the prefixes to rename from and to, as well as showing a confirmation dialog before performing the rename. It did not have the ability to be given any arguments at all. This update allows the following arguments to be provided programmatically:

oldPrefix - The prefix to rename from
newPrefix - The prefix to rename to.
disableConfirmation - When true, disables showing the confirmation prompt before renaming.

This looks very nice, but you'll have to wait a bit until I merge it since I'm not near a laptop for the next week or so. Very excited about the tree plug!

Edit: scratch that. I'll have a closer look now and get this in. I really like to unblock you. Your tree looks great.

Awesome, thanks!!
I've actually already got drag-and-drop working, but realized I can't release that version yet because it's not going to work correctly with anyone running an older version of SilverBullet (it will actually do some very unexpected and unwanted things!). I thought I could just check the version, and enable drag/drop if > 0.7.1, and disable it otherwise. But I actually don't think there's currently a way for a plug to get the current system version, unless I'm missing something? So I just threw up another #721 that adds a system.getVersion syscall. Does that seem like the best way to deal with this sort of thing? Or is there a better way or some other functionality I'm missing?

I think that's a sensible approach for the future yes


Adding parent document retrieval in default RAG pipeline

Changes made:

Removed redundant call to format_for_json_mqr() at the end of getTopContexts(). The contexts are already formatted in context padding.
Querying SQL data for top 5 contexts at once (making queries based on either urls or s3_paths) and supplying it to supabase_context_padding. Now performing 2 SQL queries (worst case) instead of 5.
Modified padding functions to remove key checks in dictionaries.

Total context retrieval time ranges from 2.5s to 4s


Field level permissions

How to set field level permissions in form/dialog?

There are no field level permissions.

Based on Issue https://github.com/volkanceylan/Serenity/issues/1221 I wrote this as a possible workaround:
On XYZDialog.ts:
`afterLoadEntity() {
super.afterLoadEntity();
        if (!BaseNamespace.Authorization.hasPermission("Admin:UserType:Boss")) {
            this.form.UserId.getGridField().toggle(false);
        }
    }

`

Also you need check permission before add or update entity repostory. If has permission you can clear field assigments.
Your solution will be modified on user browser.

@VictorTomaili Yes, for security precautions.


AppMouseStruct to MouseStruct x64/x86 determination

Is there a way to determine whether or not to use the differences in offsets from within the structs?
I'm not sure what #L47 in AppMouseStruct is supposed to do.  Both [FieldOffsets(0x**)] work respectively for x64/x86 processes, however our application is compiled as AnyCPU, so on x64 systems the FieldOffset attribute will use [FieldOffset(0x16)] and will throw off the conversion of raw mouse data.
To clarify the basis of our problem, we made the switch from using the global hook mouse events to the application hook mouse events because the global hook events caused noticeable performance decrease in our application.  When disposing the global hook with the mouse events set, our application displayed strange behaviors, but only when the aero-theme was used by the OS.  The behaviors were causing form disposal/closure to hang for a large amount of time (~5 seconds on average) upon closing the forms.  However, when the classic-theme was set on the OS, this behavior was not apparent.
Is there anything that can be done to fix either of these two problems?

Thanks for your hint. Are you bale to prepare a fix and pull request it?
I will test and publish it with the next version.

Sure thing, done. #37
I can create a separate issue for the other problem, until someone or myself has found the source cause/fix!


[Question]: What's the recommended way to save summaries from multiple documents?

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I've been reading this https://docs.llamaindex.ai/en/stable/examples/usecases/City_Analysis-Decompose-KeywordTable.html and I've been trying to do something similar by using the index saved in the vector db.
Is it generally recommended to save the document text as well as its summary in the metadata if we want to later fetch it to initialize a graph?
Or is it better to use the same summary for each document regardless of the document's content?
Is there a resource I can take a look to load the documents & summaries from the vector db?

The composable graph has not been updated in a hot minute (and will likely be removed at a later date)
Current approaches for multi-doc revolve around a few things, mostly they boil down to providing methods to route queries to the proper locations
https://docs.llamaindex.ai/en/stable/module_guides/querying/router/root.html
https://docs.llamaindex.ai/en/stable/examples/query_engine/sub_question_query_engine.html
https://docs.llamaindex.ai/en/stable/examples/agent/multi_document_agents.html
https://docs.llamaindex.ai/en/stable/examples/retrievers/recursive_retriever_nodes.html

The composable graph has not been updated in a hot minute (and will likely be removed at a later date)
Current approaches for multi-doc revolve around a few things, mostly they boil down to providing methods to route queries to the proper locations
https://docs.llamaindex.ai/en/stable/module_guides/querying/router/root.html https://docs.llamaindex.ai/en/stable/examples/query_engine/sub_question_query_engine.html https://docs.llamaindex.ai/en/stable/examples/agent/multi_document_agents.html https://docs.llamaindex.ai/en/stable/examples/retrievers/recursive_retriever_nodes.html

Thanks


🙅🏽♂[Swift 5.0] Cherry-pick swiftSyntax related changes

I am going to gather some more swiftSyntax related changes that I'd like to cherry-pick into Swift 5.0 here.

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 410a065fcdade0dfa38c81784113cf149df9b4df

CC @akyrtzi
This PR was open before the final swift-5.0-branch was cut.  If this was in master as of November 16, 2018, then this change was pulled into the final re-branching of Swift 5.  Closing as this PR was opened against an older version of this branch.  If this change should be pulled in, please open a new PR.


Cadl init support commands

Should there be a way to have cadl init support running commands.
That way we could have the scafolding template shell out to dotnet new for the RPaaS template

pri: 1


Add test json with funders list

This change is

Coverage increased (+0.04%) to 46.431% when pulling 31e1be82d368781bc58e6a28f9e647edfc442193 on annawzz:a448207762065014_funders_field into a97d5bddb2bef81b7156af1e80426af89971217e on openprocurement:production.


feat: add yaml format target

Since we are adding yaml as a dependency in https://github.com/einride/mage-tools/pull/61

I pushed a new commit to preserve blank lines. It does the job, in a somewhat hacky manner.

Files ending in multiple blank lines might be able to be handled by doing bytes.TrimSpace and then appending a single trailing endline.

Files ending in multiple blank lines might be able to be handled by doing bytes.TrimSpace and then appending a single trailing endline.

Ah true!


Bump version

Pull Request Test Coverage Report for Build 5992

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 5988:
0.0%

Covered Lines:
881

Relevant Lines:
881

💛  - Coveralls


[UUX] Administrator - Notification creation/editing

Hints / Details

R24.05 UUX feedback:
-- blocking --
Quality notifications – Received
Functionality Issue – signed in as role administrator this is unavailable with tooltip below
Same, e.g. when creating a quality alert. Get to the point of entering all data – but Save button is disabled (with role Admin) à should not be able to get to the entry screen in the first place

Why can an admin not create/edit notifications?
Administrator can not create notifications from the quality notifications screen:

But he can get to the "Create quality notification" screen through the parts page:

The save button will not work in this case
Acceptance Criteria

[ ] 'Create quality notification' button in part table disabled for Administrator role
[ ] Prevent admin to get on edit and creation screen by URL
[ ] (alternatively) Make it possible for Administrators to create and edit notifications

@mmaul
Disabling tooltip is missing if part is selected in table.  Role admin does not get any info that function is disabled because of missing role.

Tested on E2E-A:
Works properly now.
Ready for review.

Tested locally with the updated branch.
This works correctly now. Even after selecting parts the tooltip about having the wrong role will show up.
Ready for review

Review:

Create Quality Alerts is enabled in case no data in Trace-X. Disabling tooltip with user information that no data is available.

PO acceptance in behalf of @jzbmw
Admin has no possibility and  right to edit or create notifications. LGFM


handle special attribute data types

Handle two special attribute data types of:

'continuous_integer', those that have only integer values and should be treated as continuous rather than categorical
'two_value_categorical', those that have only two values and should be treated as categorical rather than binary

Do this by adding two new optional parameters to Layout.py and create_colormaps.py. These options in layout.py would simply be passed to colormaps.py. Maybe an error should be thrown in layout.py if a colormap file and these options are used since create_colormaps.py has already determined the data types.
Workaround:
2-value categoricals can be identified as such by creating a colormap entry.
continuous integers can be identified by adding 0.0001 to one of the values.
This cannot be done until this is complete: https://github.com/ucscHexmap/hexagram/issues/10

The new process_categorical handles these two special cases.


MergeStrategy with ExtensionGraphAssociation Option for GraphCollector

This adaption is required to fix apple/swift-docc#210
Summary
Adds a strategy option to GraphCollector's init. The ExtensionGraphAssociation option decides if extension graphs are merged with the extending or extended graph.
Dependencies
This PR does not introduce a breaking change and can be merged independently.
Testing
I added a new unit test to test the merging behavior for both ExtensionGraphAssociation options.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test macOS


Exec tachikoma update<PHONE_NUMBER>3331

:hamster::hamster::hamster:   Strategy none
Powered by Interval Pull Request as a Service - Tachikoma.io Announcement: 2015-06-28 Updated permissions - Tachikoma.io

Coverage remained the same at 67.647% when pulling 9c7219d65dbed44c1cf6be3e83c50bb8ef8289e4 on pazjacket:tachikoma/update-20170402163331 into 8adcad1ec54a7c518c29209245596a627c403fcb on sanemat:master.


Added frontend dependency management with Grunt + Bower + NodeJS.

This allows to have automatic dependency resolution at compile time. It downloads all the required libraries noted by bower and packages into a single minified file.  This simplifies the development of the dashboard, and reduces the overhead of the project on Github. This addition is totally transparent for the user.
If this PR is merged, EVERY contribution to the Dashboard module MUST use bower to handle the dependencies.
Note: This PR adds nodejs, bower and grunt as a requirement to build the Dashboard.
@andreaturli @rosogon could you review this? @andreaturli should I add something to travis to install Node,Bower and Grunt in order to make this to build automatically?

Is it possible to install bower in the build?
[INFO] OS Name: Windows 7
'bower' is not recognized as an internal or external command,
operable program or batch file.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] SeaClouds Platform ................................. SUCCESS [ 17.116 s]
[INFO] common ............................................. SUCCESS [01:30 min]
[INFO] deployer ........................................... SUCCESS [01:00 min]
[INFO] planner ............................................ SUCCESS [  2.464 s]
[INFO] matchmaker ......................................... SUCCESS [ 33.025 s]
[INFO] optimizer .......................................... SUCCESS [ 13.673 s]
[INFO] optimizer-core ..................................... SUCCESS [ 14.385 s]
[INFO] optimizer-service .................................. SUCCESS [01:38 min]
[INFO] planner-core ....................................... SUCCESS [  4.939 s]
[INFO] planner-service .................................... SUCCESS [ 29.035 s]
[INFO] aamwriter .......................................... SUCCESS [ 26.979 s]
[INFO] discoverer ......................................... SUCCESS [ 31.349 s]
[INFO] monitor ............................................ SUCCESS [  0.310 s]
[INFO] nuro-data-collector ................................ SUCCESS [ 57.312 s]
[INFO] reconfiguration-data-collector ..................... SUCCESS [ 11.218 s]
[INFO] Dashboard .......................................... FAILURE [06:30 min]
[INFO] SLA ................................................ SKIPPED
[INFO] SLA core parent .................................... SKIPPED
[INFO] SLA repository database ............................ SKIPPED
[INFO] SLA Enforcement .................................... SKIPPED
[INFO] SLA Tools .......................................... SKIPPED
[INFO] SLA Project Personalization ........................ SKIPPED
[INFO] SLA Service ........................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14:51 min
[INFO] Finished at: 2015-10-26T12:49:26+00:00
[INFO] Final Memory: 106M/658M
[INFO] ------------------------------------------------------------------------

We don't have a section for "Compiling SeaClouds" in the README. Maybe we should add one (not to be covered by this PR).

When trying to load a file in the last step...
TypeError: Cannot read property '0' of undefined
    at Object.fn (add-application-wizard.js:340)
    at n.$digest (dependencies.js:13)
    at n.$apply (dependencies.js:13)
    at $$debounceViewValueCommit (dependencies.js:15)
    at $setViewValue (dependencies.js:15)
    at n (dependencies.js:29)
    at dependencies.js:29
    at dependencies.js:13
    at e (dependencies.js:11)
    at dependencies.js:11

+1
@adriannieto : Can you squash in two different commits. One for the grunt+bower, and one for the fixes. Thanks

@rosogon Job done.


Error when I'm trying to add plugin

running 'cordova plugin add https://github.com/Rohfosho/CordovaCallNumberPlugin.git' in console and get this:
Error: Failed to fetch plugin https://github.com/Rohfosho/CordovaCallNumberPlugin.git via registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Failed to get absolute path to installed module
Whit connection all is ok, checked. Cordova version: 7.0.1

Hey @Jenq, I noticed the same thing when I was trying to install it but it ended up not actually being related to the connection. You may have the plugin already installed, and may need to uninstall it first.
In my case, I had initially successfully installed the plugin through "cordova plugin add ...", but was trying to install it again using "ionic cordova plugin add ...", which is when I got the error. I then ran "cordova plugin remove ..." and after that the "ionic cordova plugin add ..." command worked fine. Hope this helps.

this fixed my issues of always wanting to install the 'mx.ferreyra.callnumber'
just remove all plugins 'mx.ferreyra.callnumber' and 'call-number'
then past this in your config file:
<plugin name="call-number" spec="1.0.4" />
then run ionic cordova prepare and it will install the latest version and the console will never try to install 'mx.ferreyra.callnumber ' again.... happy days!


WAGMI and NEXTJS latest have conflicts

Describe the bug
Hi the issue is on NextJS latest.

Anything else?
The bot here is pretty agressive. Think is the 3 close of the same issue with no explaination. If you guys dont support NEXTJS please let us know. Or provide some kind of explaintion before closing please.

Wagmi supports Next.js and the message you pasted looks like a warning, not an error.
Looks like conflicting dependency version between @metamask/sdk and your project. You should open an upstream issue there.


Beginner Question: Including whole yaml template from dependency

I am getting the following error running helm install . --generate-name --dry-run --debug inside my charts folder.
$ helm install . --generate-name --dry-run --debug
install.go:173: [debug] Original chart version: ""
install.go:190: [debug] CHART PATH:
<EMAIL_ADDRESS>
Error: YAML parse error on .ci/templates/deployment.yaml: error converting YAML to JSON: yaml: did not find expected node content
helm.go:81: [debug] error converting YAML to JSON: yaml: did not find expected node content
YAML parse error on .ci/templates/deployment.yaml
helm.sh/helm/v3/pkg/releaseutil.(*manifestFile).sort
        /home/circleci/helm.sh/helm/pkg/releaseutil/manifest_sorter.go:146
helm.sh/helm/v3/pkg/releaseutil.SortManifests
        /home/circleci/helm.sh/helm/pkg/releaseutil/manifest_sorter.go:106
helm.sh/helm/v3/pkg/action.(*Configuration).renderResources
        /home/circleci/helm.sh/helm/pkg/action/action.go:165
helm.sh/helm/v3/pkg/action.(*Install).Run
        /home/circleci/helm.sh/helm/pkg/action/install.go:240
main.runInstall
        /home/circleci/helm.sh/helm/cmd/helm/install.go:242
main.newInstallCmd.func2
        /home/circleci/helm.sh/helm/cmd/helm/install.go:120
github.com/spf13/cobra.(*Command).execute
        /go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:850
github.com/spf13/cobra.(*Command).ExecuteC
        /go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:958
github.com/spf13/cobra.(*Command).Execute
        /go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:895
main.main
        /home/circleci/helm.sh/helm/cmd/helm/helm.go:80
runtime.main
        /usr/local/go/src/runtime/proc.go:204
runtime.goexit
        /usr/local/go/src/runtime/asm_amd64.s:1374

I followed this tutorial HELM Docs - Library Charts
Here is the content of packages/my-package/.ci/templates/deployment.yaml
{{- include "nodejs-backend.deployment" . }}

Here is the content of .ci/nodejs-backend/templates/_deployment.yaml
{{- define "nodejs-backend.deployment" -}}
apiVersion: apps/v1
kind: Deployment
...
{{- end }}

The dependency is defined inside packages/my-package/.ci/Chart.yaml
dependencies:
  - name: nodejs-backend
    version: 0.0.1
    repository: file://../../../.ci/nodejs-backend

Here is my folder structure.
+ .ci
  + nodejs-backend
    + charts
    + templates
       _deployment.yaml
       _service.yaml
    Chart.yaml
+ packages
  + my-package
    + .ci
      + charts
      + templates
         deployment.yaml
         service.yaml
      Chart.yaml

Ive read the docs the douzen times and played with the yaml's, without success.

Seems like a problem is with the YAML formatting, majorly with an indentation or in the values file. Please try to use the YAML lint, you can give it a try with any of the following YAML linting solutions if there will be any formatting issues you can recognize.
https://github.com/rasshofer/yaml-lint#readme
https://github.com/adrienverge/yamllint

I tried something similar from your reference
This is what your chart structure looks like after adding the dependency to your actual chart, please don't use the template chart i.e "mylibchart" it won't work.
Make sure your library chart is installable
helm install mylibchart mylibchart/
Error: library charts are not installable

Note: you have to pull the dependencies before using the actual chart
helm dependency update mychart

├── mychart
│   ├── Chart.lock
│   ├── Chart.yaml
│   ├── charts
│   │   └── mylibchart-0.1.0.tgz
│   ├── templates
│   │   └── configmap.yaml
│   └── values.yaml
├── mylibchart
│   ├── Chart.yaml
│   ├── charts
│   └── templates
│       ├── _configmap.yaml
│       └── _util.yaml

helm install mydemo mychart/ --debug --dry-run
install.go:173: [debug] Original chart version: ""
install.go:190: [debug] CHART PATH:  ~/Projects/kubernetes/chartstest/mychart

NAME: mydemo
LAST DEPLOYED: Sat Mar  6 11:24:51 2021
NAMESPACE: default
STATUS: pending-install
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
{}

COMPUTED VALUES:
affinity: {}
autoscaling:
  enabled: false
  maxReplicas: 100
  minReplicas: 1
  targetCPUUtilizationPercentage: 80
fullnameOverride: ""
image:
  pullPolicy: IfNotPresent
  repository: nginx
  tag: ""
imagePullSecrets: []
ingress:
  annotations: {}
  enabled: false
  hosts:
  - host: chart-example.local
    paths: []
  tls: []
mylibchart:
  global: {}
nameOverride: ""
nodeSelector: {}
podAnnotations: {}
podSecurityContext: {}
replicaCount: 1
resources: {}
securityContext: {}
service:
  port: 80
  type: ClusterIP
serviceAccount:
  annotations: {}
  create: true
  name: ""
tolerations: []

HOOKS:
MANIFEST:
---
# Source: mychart/templates/configmap.yaml
apiVersion: v1
data:
  myvalue: Hello World
kind: ConfigMap
metadata:
  name: mychart-mydemo

I try this ASAP and report if it worked.

It works now. The problem was, that my dependency "nodejs-backend" was a library chart.
After changing to type "application" it now works.
Thanks!


Add option to ignore simulated keystrokes

Change in UI

Reason
There are some software tools that will simulate keystrokes to do automatic copy/paste operations or trigger hotkeys.
The user do not need to know what is simuated, what they need to know is the keys inputed on keyboard.
Thanks.

Thank you.


Traceback
Traceback (most recent call last):
File "/usr/bin/thefuck", line 9, in
load_entry_point('thefuck==3.2', 'console_scripts', 'thefuck.real')()
File "/usr/share/thefuck/thefuck/main.py", line 77, in main
fix_command()
File "/usr/share/thefuck/thefuck/main.py", line 31, in fix_command
selected_command.run(command)
File "/usr/share/thefuck/thefuck/types.py", line 281, in run
shells.put_to_history(self.script)
File "/usr/share/thefuck/thefuck/shells.py", line 293, in put_to_history
return _get_shell().put_to_history(command)
File "/usr/share/thefuck/thefuck/shells.py", line 51, in put_to_history
with open(history_file_name, 'a') as history:
IOError: [Errno 13] Permission denied: '/home/REDACTED/.bash_history'
Environment
Debian sid
thefuck (3.2-1)
python3 (3.5.0-2)

In 3.3 it only shows warning when histfile is readonly. Also now alter_history can be used for disabling writing to histfile:
alter_history = False

Or:
export THEFUCK_ALTER_HISTORY=false


Allow mysql compatible packages

Allow cookbook to install mysql compatible package from wrapper cookbook. compatible packages may be percona and mariadb, or community mysql.
We needed this to use the rs-mysql cookbook with other mysql compatible packages.

@lopaka how should I proceed.  what is the preferred method to correct the removed comment?

Just manually add it back in and commit. The method of commit is not that important on external commits, it the end results that matter in this case.


TaxonomyPicker - Markdown table issue

Q
A

Bug fix?
[x]

New feature?
[ ]

New sample?
[ ]

Related issues?
Currently no related issue

What's in this Pull Request?
Issue within TaxonomyPicker documentation
The table of the ITermAction interface contains a column issue.
More specifically for the property 'applyToTerm'

Fixed with a backslash

Thank you @Jwaegebaert for the fix!