Continous 'Not authenticated' errors in log since 2.12.1

Did you read the instructions?

[X] I have read the README, including the advanced debugging section.

The problem
Updated to 2.12.1 and the log continuously fills with log shown below. No other changes since using 2.11.0.
Somfy blinds are RTS so stateless in HA. Rolled back in case this causes me to get banned.
What version of this integration (ha-tahoma) has the issue?
2.12.1
What version of Home Assistant Core has the issue?
2021.12.10
Which gateway / hub do you use?

Will try to, it hasnt happened today, will keep an eye on it.

Will try to, it hasnt happened today, will keep an eye on it.

But you did downgrade? Isn't that why you don't face the errors anymore?

No I have upgraded again.
Restarting fixes it. Whilst it was doing it, an automation closed all the blinds in the house, and that went through fine.
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810427, name=<EventName.EXECUTION_REGISTERED: 'ExecutionRegisteredEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=None, type=1, sub_type=1, time_to_next_state=None, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label='Home Assistant', metadata='', camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e3f7a-0a32-0482-5c07-b861547995fb', device_url=None, device_states=[], old_state=None, new_state=None)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810427, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=0, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e3f7a-0a32-0482-5c07-b861547995fb', device_url=None, device_states=[], old_state=<ExecutionState.INITIALIZED: 'INITIALIZED'>, new_state=<ExecutionState.NOT_TRANSMITTED: 'NOT_TRANSMITTED'>)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810427, name=<EventName.GATEWAY_SYNCHRONIZATION_STARTED: 'GatewaySynchronizationStartedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=None, type=None, sub_type=None, time_to_next_state=None, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=****-****-2775, exec_id=None, device_url=None, device_states=[], old_state=None, new_state=None)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810429, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=0, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e3f7a-0a32-0482-5c07-b861547995fb', device_url=None, device_states=[], old_state=<ExecutionState.NOT_TRANSMITTED: 'NOT_TRANSMITTED'>, new_state=<ExecutionState.TRANSMITTED: 'TRANSMITTED'>)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810429, name=<EventName.GATEWAY_SYNCHRONIZATION_ENDED: 'GatewaySynchronizationEndedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=None, type=None, sub_type=None, time_to_next_state=None, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=****-****-2775, exec_id=None, device_url=None, device_states=[], old_state=None, new_state=None)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.086 seconds (success: True)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810616, name=<EventName.EXECUTION_REGISTERED: 'ExecutionRegisteredEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=None, type=1, sub_type=1, time_to_next_state=None, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label='Home Assistant', metadata='', camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e4037-0a32-0482-5c07-b86163d5f521', device_url=None, device_states=[], old_state=None, new_state=None)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810616, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=0, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e4037-0a32-0482-5c07-b86163d5f521', device_url=None, device_states=[], old_state=<ExecutionState.INITIALIZED: 'INITIALIZED'>, new_state=<ExecutionState.NOT_TRANSMITTED: 'NOT_TRANSMITTED'>)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810616, name=<EventName.GATEWAY_SYNCHRONIZATION_STARTED: 'GatewaySynchronizationStartedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=None, type=None, sub_type=None, time_to_next_state=None, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=****-****-2775, exec_id=None, device_url=None, device_states=[], old_state=None, new_state=None)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810617, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=0, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e4037-0a32-0482-5c07-b86163d5f521', device_url=None, device_states=[], old_state=<ExecutionState.NOT_TRANSMITTED: 'NOT_TRANSMITTED'>, new_state=<ExecutionState.TRANSMITTED: 'TRANSMITTED'>)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810617, name=<EventName.GATEWAY_SYNCHRONIZATION_ENDED: 'GatewaySynchronizationEndedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=None, type=None, sub_type=None, time_to_next_state=None, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=****-****-2775, exec_id=None, device_url=None, device_states=[], old_state=None, new_state=None)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.087 seconds (success: True)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810828, name=<EventName.EXECUTION_REGISTERED: 'ExecutionRegisteredEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=None, type=1, sub_type=1, time_to_next_state=None, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label='Home Assistant', metadata='', camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e410b-0a32-0482-5c07-b8611294c8be', device_url=None, device_states=[], old_state=None, new_state=None)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810828, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=0, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e410b-0a32-0482-5c07-b8611294c8be', device_url=None, device_states=[], old_state=<ExecutionState.INITIALIZED: 'INITIALIZED'>, new_state=<ExecutionState.NOT_TRANSMITTED: 'NOT_TRANSMITTED'>)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810828, name=<EventName.GATEWAY_SYNCHRONIZATION_STARTED: 'GatewaySynchronizationStartedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=None, type=None, sub_type=None, time_to_next_state=None, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=****-****-2775, exec_id=None, device_url=None, device_states=[], old_state=None, new_state=None)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810830, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=0, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e410b-0a32-0482-5c07-b8611294c8be', device_url=None, device_states=[], old_state=<ExecutionState.NOT_TRANSMITTED: 'NOT_TRANSMITTED'>, new_state=<ExecutionState.TRANSMITTED: 'TRANSMITTED'>)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535810830, name=<EventName.GATEWAY_SYNCHRONIZATION_ENDED: 'GatewaySynchronizationEndedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=None, type=None, sub_type=None, time_to_next_state=None, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=****-****-2775, exec_id=None, device_url=None, device_states=[], old_state=None, new_state=None)
2022-01-30 20:13:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.088 seconds (success: True)
2022-01-30 20:14:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535811687, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=0, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e3f7a-0a32-0482-5c07-b861547995fb', device_url=None, device_states=[], old_state=<ExecutionState.TRANSMITTED: 'TRANSMITTED'>, new_state=<ExecutionState.IN_PROGRESS: 'IN_PROGRESS'>)
2022-01-30 20:14:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535813284, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=0, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e4037-0a32-0482-5c07-b86163d5f521', device_url=None, device_states=[], old_state=<ExecutionState.TRANSMITTED: 'TRANSMITTED'>, new_state=<ExecutionState.IN_PROGRESS: 'IN_PROGRESS'>)
2022-01-30 20:14:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535814571, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=0, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e410b-0a32-0482-5c07-b8611294c8be', device_url=None, device_states=[], old_state=<ExecutionState.TRANSMITTED: 'TRANSMITTED'>, new_state=<ExecutionState.IN_PROGRESS: 'IN_PROGRESS'>)
2022-01-30 20:14:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.282 seconds (success: True)
2022-01-30 20:14:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535841966, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=-1, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e3f7a-0a32-0482-5c07-b861547995fb', device_url=None, device_states=[], old_state=<ExecutionState.IN_PROGRESS: 'IN_PROGRESS'>, new_state=<ExecutionState.COMPLETED: 'COMPLETED'>)
2022-01-30 20:14:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535843280, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=-1, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e4037-0a32-0482-5c07-b86163d5f521', device_url=None, device_states=[], old_state=<ExecutionState.IN_PROGRESS: 'IN_PROGRESS'>, new_state=<ExecutionState.COMPLETED: 'COMPLETED'>)
2022-01-30 20:14:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] Event(timestamp=1643535844593, name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, setupoid=_CountingAttr(counter=382, _default=None, repr=<function obfuscate_id at 0xa241a220>, eq=True, order=True, hash=None, init=True, on_setattr=None, metadata={}), owner_key=0a8ab47e-ff7d-4e****-b3c****-1add27fa3eca, type=1, sub_type=1, time_to_next_state=-1, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='aa5e410b-0a32-0482-5c07-b8611294c8be', device_url=None, device_states=[], old_state=<ExecutionState.IN_PROGRESS: 'IN_PROGRESS'>, new_state=<ExecutionState.COMPLETED: 'COMPLETED'>)

Can you include your full debug log? The reason why I asked this previous time, is I need to understand which devices you have and why it seems that sometimes your interval is not set to every hour.

Sorry I thoughts thats what I did. Is that using 'tahoma.get_execution_history'?

No, but there should be more lines like 'Added device' and more.

Ah, well at boot I get this,
2022-01-31 21:23:10 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.108 seconds (success: True)
2022-01-31 21:23:10 DEBUG (MainThread) [custom_components.tahoma] All devices have assumed state. Update interval has been reduced to: 1:00:00
2022-01-31 21:23:10 DEBUG (MainThread) [custom_components.tahoma] Added device (Device(attributes=States(_states=[State(name='rts:diy', type=<DataType.BOOLEAN: 6>, value=False)]), available=True, enabled=True, label=** **, device_url=rts://****-****-2775/16732264, controllable_name='rts:BlindRTSComponent', definition=Definition(commands=CommandDefinitions(_commands=[CommandDefinition(command_name='close', nparams=1), CommandDefinition(command_name='down', nparams=1), CommandDefinition(command_name='identify', nparams=0), CommandDefinition(command_name='my', nparams=1), CommandDefinition(command_name='open', nparams=1), CommandDefinition(command_name='rest', nparams=1), CommandDefinition(command_name='stop', nparams=1), CommandDefinition(command_name='test', nparams=0), CommandDefinition(command_name='up', nparams=1), CommandDefinition(command_name='openConfiguration', nparams=1)]), states=[], widget_name='UpDownScreen', ui_class='Screen', qualified_name='rts:BlindRTSComponent'), data_properties=None, widget=<UIWidget.UP_DOWN_SCREEN: 'UpDownScreen'>, ui_class=<UIClass.SCREEN: 'Screen'>, states=States(_states=[]), type=<ProductType.ACTUATOR: 1>, place_oid='6cc426e1-61d2-420b-a807-d0687da74e0b'))
2022-01-31 21:23:10 DEBUG (MainThread) [custom_components.tahoma] Added device (Device(attributes=States(_states=[State(name='rts:diy', type=<DataType.BOOLEAN: 6>, value=False)]), available=True, enabled=True, label=** **, device_url=rts://****-****-2775/16742596, controllable_name='rts:BlindRTSComponent', definition=Definition(commands=CommandDefinitions(_commands=[CommandDefinition(command_name='close', nparams=1), CommandDefinition(command_name='down', nparams=1), CommandDefinition(command_name='identify', nparams=0), CommandDefinition(command_name='my', nparams=1), CommandDefinition(command_name='open', nparams=1), CommandDefinition(command_name='rest', nparams=1), CommandDefinition(command_name='stop', nparams=1), CommandDefinition(command_name='test', nparams=0), CommandDefinition(command_name='up', nparams=1), CommandDefinition(command_name='openConfiguration', nparams=1)]), states=[], widget_name='UpDownScreen', ui_class='Screen', qualified_name='rts:BlindRTSComponent'), data_properties=None, widget=<UIWidget.UP_DOWN_SCREEN: 'UpDownScreen'>, ui_class=<UIClass.SCREEN: 'Screen'>, states=States(_states=[]), type=<ProductType.ACTUATOR: 1>, place_oid='6cc426e1-61d2-420b-a807-d0687da74e0b'))
2022-01-31 21:23:10 DEBUG (MainThread) [custom_components.tahoma] Added device (Device(attributes=States(_states=[State(name='rts:diy', type=<DataType.BOOLEAN: 6>, value=False)]), available=True, enabled=True, label=**, device_url=rts://****-****-2775/16763048, controllable_name='rts:BlindRTSComponent', definition=Definition(commands=CommandDefinitions(_commands=[CommandDefinition(command_name='close', nparams=1), CommandDefinition(command_name='down', nparams=1), CommandDefinition(command_name='identify', nparams=0), CommandDefinition(command_name='my', nparams=1), CommandDefinition(command_name='open', nparams=1), CommandDefinition(command_name='rest', nparams=1), CommandDefinition(command_name='stop', nparams=1), CommandDefinition(command_name='test', nparams=0), CommandDefinition(command_name='up', nparams=1), CommandDefinition(command_name='openConfiguration', nparams=1)]), states=[], widget_name='UpDownScreen', ui_class='Screen', qualified_name='rts:BlindRTSComponent'), data_properties=None, widget=<UIWidget.UP_DOWN_SCREEN: 'UpDownScreen'>, ui_class=<UIClass.SCREEN: 'Screen'>, states=States(_states=[]), type=<ProductType.ACTUATOR: 1>, place_oid='6cc426e1-61d2-420b-a807-d0687da74e0b'))
2022-01-31 21:23:10 DEBUG (MainThread) [custom_components.tahoma] Added device (Device(attributes=States(_states=[State(name='rts:diy', type=<DataType.BOOLEAN: 6>, value=False)]), available=True, enabled=True, label=** **, device_url=rts://****-****-2775/16764082, controllable_name='rts:BlindRTSComponent', definition=Definition(commands=CommandDefinitions(_commands=[CommandDefinition(command_name='close', nparams=1), CommandDefinition(command_name='down', nparams=1), CommandDefinition(command_name='identify', nparams=0), CommandDefinition(command_name='my', nparams=1), CommandDefinition(command_name='open', nparams=1), CommandDefinition(command_name='rest', nparams=1), CommandDefinition(command_name='stop', nparams=1), CommandDefinition(command_name='test', nparams=0), CommandDefinition(command_name='up', nparams=1), CommandDefinition(command_name='openConfiguration', nparams=1)]), states=[], widget_name='UpDownScreen', ui_class='Screen', qualified_name='rts:BlindRTSComponent'), data_properties=None, widget=<UIWidget.UP_DOWN_SCREEN: 'UpDownScreen'>, ui_class=<UIClass.SCREEN: 'Screen'>, states=States(_states=[]), type=<ProductType.ACTUATOR: 1>, place_oid='6cc426e1-61d2-420b-a807-d0687da74e0b'))
2022-01-31 21:23:10 DEBUG (MainThread) [custom_components.tahoma] Added gateway (Gateway(partners=[], functions='INTERNET_AUTHORIZATION,SCENARIO_DOWNLOAD,SCENARIO_TELECO_LAUNCHING,INTERNET_UPLOAD,INTERNET_UPDATE,TRIGGERS_SENSORS', sub_type=<GatewaySubType.TAHOMA_BASIC: 1>, id=****-****-2775, gateway_id=****-****-2775, alive=True, mode='NO_AUTO', place_oid='6cc426e1-61d2-420b-a807-d0687da74e0b', time_reliable=True, connectivity=Connectivity(status='OK', protocol_version='2021.2.4'), up_to_date=True, update_status=<UpdateBoxStatus.UP_TO_DATE: 'UP_TO_DATE'>, sync_in_progress=False, type=<GatewayType.CONNEXOON_RTS_AUSTRALIA: 62>))

Might need to roll back for now, got banned today, after it started auth'ing every minute for 6 hours.

I have the same issue as well. I originally had polling option on which created a lot of Backing Off Info messages. Turning it off reduced the number  but it still does it every time I open/close a blind, but everything works fine except for the Info message. I too am using the Connexoon RTS in Australia. I  have upgraded to the core integration, and other than the INFO messages all works fine.

@Tarawera could you share your debug logs? Same as for @callifo, we need to understand which devices you have and if you poll the event listener every 30 seconds or every hour. Please include all logs.

Is there anything I can do to collect further info?

I have no clue where to look for it... According to your logs, the polling interval is already set to 1 hour.
2022-01-31 21:23:10 DEBUG (MainThread) [custom_components.tahoma] All devices have assumed state. Update interval has been reduced to: 1:00:00

I tried 2.13, and it does it straight away, heres the full log,
2022-02-25 00:18:34 INFO (MainThread) [homeassistant.setup] Setting up tahoma
2022-02-25 00:18:34 INFO (MainThread) [homeassistant.setup] Setup of domain tahoma took 0.0 seconds
2022-02-25 00:18:35 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
2022-02-25 00:18:35 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.0 seconds
2022-02-25 00:18:35 INFO (MainThread) [homeassistant.setup] Setting up tplink
2022-02-25 00:18:35 WARNING (MainThread) [homeassistant.components.alarm_control_panel] Setup of alarm_control_panel platform manual is taking over 10 seconds.
2022-02-25 00:18:35 WARNING (MainThread) [homeassistant.setup] Setup of hacs is taking over 10 seconds.
2022-02-25 00:18:36 WARNING (SyncWorker_5) [pyhik.hikvision] Sensor type "faceSnap" is unsupported.
2022-02-25 00:18:36 INFO (MainThread) [homeassistant.setup] Setup of domain camera took 3.8 seconds
2022-02-25 00:18:36 WARNING (SyncWorker_9) [pyhik.hikvision] Sensor type "faceSnap" is unsupported.
2022-02-25 00:18:36 INFO (MainThread) [homeassistant.setup] Setting up synology_dsm
2022-02-25 00:18:36 INFO (MainThread) [homeassistant.setup] Setup of domain synology_dsm took 0.0 seconds
2022-02-25 00:18:36 INFO (MainThread) [homeassistant.setup] Setting up template
2022-02-25 00:18:36 INFO (MainThread) [homeassistant.setup] Setup of domain template took 0.0 seconds
2022-02-25 00:18:37 INFO (MainThread) [homeassistant.setup] Setting up tts
2022-02-25 00:18:37 INFO (MainThread) [homeassistant.setup] Setup of domain smartir took 16.5 seconds
2022-02-25 00:18:37 INFO (MainThread) [homeassistant.setup] Setting up google_assistant
2022-02-25 00:18:37 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 16.2 seconds
2022-02-25 00:18:37 INFO (MainThread) [homeassistant.setup] Setup of domain notify took 6.5 seconds
2022-02-25 00:18:37 INFO (MainThread) [homeassistant.setup] Setup of domain timer took 16.8 seconds
2022-02-25 00:18:37 INFO (MainThread) [homeassistant.setup] Setup of domain input_boolean took 17.0 seconds
2022-02-25 00:18:38 INFO (MainThread) [homeassistant.setup] Setup of domain input_number took 16.8 seconds
2022-02-25 00:18:38 INFO (MainThread) [homeassistant.setup] Setup of domain input_select took 16.5 seconds
2022-02-25 00:18:38 INFO (MainThread) [homeassistant.setup] Setup of domain google_assistant took 0.8 seconds
2022-02-25 00:18:38 INFO (MainThread) [homeassistant.setup] Setting up climate
2022-02-25 00:18:38 INFO (MainThread) [homeassistant.setup] Setup of domain climate took 0.0 seconds
2022-02-25 00:18:38 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 1.3 seconds
2022-02-25 00:18:38 INFO (MainThread) [homeassistant.setup] Setup of domain input_datetime took 16.8 seconds
2022-02-25 00:18:39 INFO (MainThread) [homeassistant.setup] Setting up mobile_app
2022-02-25 00:18:39 INFO (MainThread) [homeassistant.setup] Setting up device_tracker
2022-02-25 00:18:39 INFO (MainThread) [homeassistant.setup] Setting up weather
2022-02-25 00:18:39 INFO (MainThread) [homeassistant.setup] Setup of domain weather took 0.0 seconds
2022-02-25 00:18:39 INFO (MainThread) [homeassistant.setup] Setup of domain mobile_app took 0.7 seconds
2022-02-25 00:18:40 INFO (MainThread) [homeassistant.setup] Setting up cast
2022-02-25 00:18:40 INFO (MainThread) [homeassistant.setup] Setup of domain cast took 0.0 seconds
2022-02-25 00:18:40 INFO (MainThread) [homeassistant.setup] Setting up sensor
2022-02-25 00:18:40 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 0.0 seconds
2022-02-25 00:18:40 INFO (MainThread) [homeassistant.setup] Setting up tasmota
2022-02-25 00:18:40 INFO (MainThread) [homeassistant.setup] Setup of domain tasmota took 0.0 seconds
2022-02-25 00:18:40 INFO (MainThread) [homeassistant.setup] Setting up traccar
2022-02-25 00:18:40 INFO (MainThread) [homeassistant.setup] Setup of domain traccar took 0.0 seconds
2022-02-25 00:18:40 INFO (MainThread) [homeassistant.setup] Setting up ping
2022-02-25 00:18:41 INFO (MainThread) [homeassistant.setup] Setting up rest
2022-02-25 00:18:41 INFO (MainThread) [homeassistant.setup] Setup of domain rest took 0.0 seconds
2022-02-25 00:18:41 INFO (MainThread) [homeassistant.setup] Setup of domain ping took 0.5 seconds
2022-02-25 00:18:41 INFO (MainThread) [homeassistant.setup] Setup of domain hacs took 17.1 seconds
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setup of domain tplink took 6.6 seconds
2022-02-25 00:18:42 INFO (MainThread) [custom_components.izone_custom.climate] Controller UID=000036424 discovered
2022-02-25 00:18:42 DEBUG (MainThread) [custom_components.izone_custom.climate] Found external temperature sensor=sensor.living_room_temperature_f, for device_id=000036424
2022-02-25 00:18:42 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.109 seconds (success: True)
2022-02-25 00:18:42 DEBUG (MainThread) [custom_components.tahoma] All devices have assumed state. Update interval has been reduced to: 1:00:00
2022-02-25 00:18:42 DEBUG (MainThread) [custom_components.tahoma] Added device (Device(attributes=States(_states=[State(name='rts:diy', type=<DataType.BOOLEAN: 6>, value=False)]), available=True, enabled=True, label=** **, device_url=rts://****-****-2775/16732264, controllable_name='rts:BlindRTSComponent', definition=Definition(commands=CommandDefinitions(_commands=[CommandDefinition(command_name='close', nparams=1), CommandDefinition(command_name='down', nparams=1), CommandDefinition(command_name='identify', nparams=0), CommandDefinition(command_name='my', nparams=1), CommandDefinition(command_name='open', nparams=1), CommandDefinition(command_name='rest', nparams=1), CommandDefinition(command_name='stop', nparams=1), CommandDefinition(command_name='test', nparams=0), CommandDefinition(command_name='up', nparams=1), CommandDefinition(command_name='openConfiguration', nparams=1)]), states=[], widget_name='UpDownScreen', ui_class='Screen', qualified_name='rts:BlindRTSComponent'), data_properties=None, widget=<UIWidget.UP_DOWN_SCREEN: 'UpDownScreen'>, ui_class=<UIClass.SCREEN: 'Screen'>, states=States(_states=[]), type=<ProductType.ACTUATOR: 1>, place_oid='6cc426e1-61d2-420b-a807-d0687da74e0b'))
2022-02-25 00:18:42 DEBUG (MainThread) [custom_components.tahoma] Added device (Device(attributes=States(_states=[State(name='rts:diy', type=<DataType.BOOLEAN: 6>, value=False)]), available=True, enabled=True, label=** **, device_url=rts://****-****-2775/16742596, controllable_name='rts:BlindRTSComponent', definition=Definition(commands=CommandDefinitions(_commands=[CommandDefinition(command_name='close', nparams=1), CommandDefinition(command_name='down', nparams=1), CommandDefinition(command_name='identify', nparams=0), CommandDefinition(command_name='my', nparams=1), CommandDefinition(command_name='open', nparams=1), CommandDefinition(command_name='rest', nparams=1), CommandDefinition(command_name='stop', nparams=1), CommandDefinition(command_name='test', nparams=0), CommandDefinition(command_name='up', nparams=1), CommandDefinition(command_name='openConfiguration', nparams=1)]), states=[], widget_name='UpDownScreen', ui_class='Screen', qualified_name='rts:BlindRTSComponent'), data_properties=None, widget=<UIWidget.UP_DOWN_SCREEN: 'UpDownScreen'>, ui_class=<UIClass.SCREEN: 'Screen'>, states=States(_states=[]), type=<ProductType.ACTUATOR: 1>, place_oid='6cc426e1-61d2-420b-a807-d0687da74e0b'))
2022-02-25 00:18:42 DEBUG (MainThread) [custom_components.tahoma] Added device (Device(attributes=States(_states=[State(name='rts:diy', type=<DataType.BOOLEAN: 6>, value=False)]), available=True, enabled=True, label=**, device_url=rts://****-****-2775/16763048, controllable_name='rts:BlindRTSComponent', definition=Definition(commands=CommandDefinitions(_commands=[CommandDefinition(command_name='close', nparams=1), CommandDefinition(command_name='down', nparams=1), CommandDefinition(command_name='identify', nparams=0), CommandDefinition(command_name='my', nparams=1), CommandDefinition(command_name='open', nparams=1), CommandDefinition(command_name='rest', nparams=1), CommandDefinition(command_name='stop', nparams=1), CommandDefinition(command_name='test', nparams=0), CommandDefinition(command_name='up', nparams=1), CommandDefinition(command_name='openConfiguration', nparams=1)]), states=[], widget_name='UpDownScreen', ui_class='Screen', qualified_name='rts:BlindRTSComponent'), data_properties=None, widget=<UIWidget.UP_DOWN_SCREEN: 'UpDownScreen'>, ui_class=<UIClass.SCREEN: 'Screen'>, states=States(_states=[]), type=<ProductType.ACTUATOR: 1>, place_oid='6cc426e1-61d2-420b-a807-d0687da74e0b'))
2022-02-25 00:18:42 DEBUG (MainThread) [custom_components.tahoma] Added device (Device(attributes=States(_states=[State(name='rts:diy', type=<DataType.BOOLEAN: 6>, value=False)]), available=True, enabled=True, label=** **, device_url=rts://****-****-2775/16764082, controllable_name='rts:BlindRTSComponent', definition=Definition(commands=CommandDefinitions(_commands=[CommandDefinition(command_name='close', nparams=1), CommandDefinition(command_name='down', nparams=1), CommandDefinition(command_name='identify', nparams=0), CommandDefinition(command_name='my', nparams=1), CommandDefinition(command_name='open', nparams=1), CommandDefinition(command_name='rest', nparams=1), CommandDefinition(command_name='stop', nparams=1), CommandDefinition(command_name='test', nparams=0), CommandDefinition(command_name='up', nparams=1), CommandDefinition(command_name='openConfiguration', nparams=1)]), states=[], widget_name='UpDownScreen', ui_class='Screen', qualified_name='rts:BlindRTSComponent'), data_properties=None, widget=<UIWidget.UP_DOWN_SCREEN: 'UpDownScreen'>, ui_class=<UIClass.SCREEN: 'Screen'>, states=States(_states=[]), type=<ProductType.ACTUATOR: 1>, place_oid='6cc426e1-61d2-420b-a807-d0687da74e0b'))
2022-02-25 00:18:42 DEBUG (MainThread) [custom_components.tahoma] Added gateway (Gateway(partners=[], functions='INTERNET_AUTHORIZATION,SCENARIO_DOWNLOAD,SCENARIO_TELECO_LAUNCHING,INTERNET_UPLOAD,INTERNET_UPDATE,TRIGGERS_SENSORS', sub_type=<GatewaySubType.TAHOMA_BASIC: 1>, id=****-****-2775, gateway_id=****-****-2775, alive=True, mode='NO_AUTO', place_oid='6cc426e1-61d2-420b-a807-d0687da74e0b', time_reliable=True, connectivity=Connectivity(status='OK', protocol_version='2021.2.4'), up_to_date=True, update_status=<UpdateBoxStatus.UP_TO_DATE: 'UP_TO_DATE'>, sync_in_progress=False, type=<GatewayType.CONNEXOON_RTS_AUSTRALIA: 62>))
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setting up scene
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setting up button
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setup of domain button took 0.0 seconds
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setting up number
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setup of domain number took 0.0 seconds
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setting up lock
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setup of domain lock took 0.0 seconds
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setting up water_heater
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setup of domain water_heater took 0.0 seconds
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setting up select
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setup of domain select took 0.0 seconds
2022-02-25 00:18:42 INFO (MainThread) [homeassistant.setup] Setup of domain scene took 0.1 seconds
2022-02-25 00:18:44 INFO (MainThread) [homeassistant.setup] Setting up vacuum
2022-02-25 00:18:44 INFO (MainThread) [homeassistant.setup] Setup of domain vacuum took 0.0 seconds
2022-02-25 00:18:46 INFO (MainThread) [homeassistant.setup] Setting up automation
2022-02-25 00:18:46 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 0.4 seconds
2022-02-25 00:18:46 INFO (MainThread) [homeassistant.setup] Setting up script
2022-02-25 00:18:47 INFO (MainThread) [homeassistant.setup] Setup of domain script took 0.1 seconds
2022-02-25 00:18:49 WARNING (MainThread) [homeassistant.components.fan] Setup of fan platform mqtt is taking over 10 seconds.
2022-02-25 00:18:49 INFO (MainThread) [homeassistant.setup] Setup of domain device_tracker took 9.8 seconds
2022-02-25 00:18:49 INFO (MainThread) [homeassistant.setup] Setting up proximity
2022-02-25 00:18:49 INFO (MainThread) [homeassistant.setup] Setup of domain proximity took 0.1 seconds
2022-02-25 00:18:50 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform mqtt is taking over 10 seconds.
2022-02-25 00:18:52 ERROR (Thread-11) [pychromecast.socket_client] [Living Room Chromecast(<IP_ADDRESS>):8009] Failed to connect to service ServiceInfo(type='mdns', data='Chromecast-088b196438104da762045b21153b6749._googlecast._tcp.local.'), retrying in 5.0s
2022-02-25 00:18:52 ERROR (Thread-12) [pychromecast.socket_client] [All Speakers(<IP_ADDRESS>):32205] Failed to connect to service ServiceInfo(type='mdns', data='Google-Cast-Group-ac71dafb59d54d8db0d4c6f32a03acf1._googlecast._tcp.local.'), retrying in 5.0s
2022-02-25 00:18:53 ERROR (Thread-13) [pychromecast.socket_client] [Living Room speaker(<IP_ADDRESS>):8009] Failed to connect to service ServiceInfo(type='mdns', data='Nest-Audio-6b83de3ef3f037a53fc674215239b639._googlecast._tcp.local.'), retrying in 5.0s
2022-02-25 00:18:55 ERROR (Thread-14) [pychromecast.socket_client] [Study speaker(<IP_ADDRESS>):8009] Failed to connect to service ServiceInfo(type='mdns', data='Google-Home-Mini-468655f877969ea384429ff8c13fba53._googlecast._tcp.local.'), retrying in 5.0s
2022-02-25 00:18:57 ERROR (Thread-15) [pychromecast.socket_client] [Master Bedroom display(<IP_ADDRESS>):8009] Failed to connect to service ServiceInfo(type='mdns', data='google-nest-hub-9bc47025247c008e8d66a4b544ad6298._googlecast._tcp.local.'), retrying in 5.0s
2022-02-25 00:19:05 INFO (MainThread) [homeassistant.setup] Setting up remote
2022-02-25 00:19:05 INFO (MainThread) [homeassistant.setup] Setup of domain remote took 0.0 seconds
2022-02-25 00:19:07 ERROR (MainThread) [custom_components.hacs] HacsTask<update_critical_repositories> failed: <Integration custom-components/sensor.custom_aftership> Repository has been requested to be removed.
2022-02-25 00:19:15 ERROR (Thread-26) [pychromecast.socket_client] [Kitchen display(<IP_ADDRESS>):8009] Failed to connect to service ServiceInfo(type='mdns', data='JBL-Link-View-c247ec6cd6ec4bff95f2a9c2c17819f2._googlecast._tcp.local.'), retrying in 5.0s
2022-02-25 00:19:42 ERROR (Thread-12) [pychromecast.socket_client] [All Speakers(<IP_ADDRESS>):32205] Error reading from socket.
2022-02-25 00:19:42 WARNING (Thread-12) [pychromecast.socket_client] [All Speakers(<IP_ADDRESS>):32205] Error communicating with socket, resetting connection
2022-02-25 00:19:42 ERROR (Thread-12) [pychromecast.socket_client] [All Speakers(<IP_ADDRESS>):32205] Failed to connect to service ServiceInfo(type='host', data=('<IP_ADDRESS>', 32205)), retrying in 5.0s
2022-02-25 00:54:47 WARNING (Thread-11) [pychromecast.socket_client] [Living Room Chromecast(<IP_ADDRESS>):8009] Heartbeat timeout, resetting connection
2022-02-25 00:54:49 WARNING (Thread-15) [pychromecast.socket_client] [Master Bedroom display(<IP_ADDRESS>):8009] Heartbeat timeout, resetting connection
2022-02-25 00:54:50 WARNING (Thread-26) [pychromecast.socket_client] [Kitchen display(<IP_ADDRESS>):8009] Heartbeat timeout, resetting connection
2022-02-25 00:54:50 WARNING (Thread-12) [pychromecast.socket_client] [All Speakers(<IP_ADDRESS>):32205] Heartbeat timeout, resetting connection
2022-02-25 01:12:37 WARNING (MainThread) [homeassistant.helpers.entity] Updating state for sensor.washing_machine_today_s_consumption (<class 'homeassistant.components.tplink.sensor.SmartPlugSensor'>) took 0.546 seconds.  You can just drag and rop the file in a new comment.

log.txt

It seems that you included the same log as above? You can download your diagnostics information by going to your integrations page. Click on the 3 dots next to Overkiz. Select "Download diagnostics".

Ah, sorry I thought it was the service, 'tahoma.get_execution_history' you meant. The Advanced Debugging page above doesn't mention that debug option 'Download diagnostics'.
As I had to roll back, I will get that in about an hour.
For comparison in case its any worth, I have attached 2.11 which works as expected.
log_1.txt
Download Diagnostics doesn't seem to be an option in 2.11 so I can't provide that.

Diagnostics from when it was updating every minute.
config_entry-tahoma.json.txt

The problem seems to have resolved itself with the latest version. Thanks

On 29/03/2022, at 3:05 PM, github-actions[bot] @.***> wrote:
'There hasn't been any activity on this issue recently. Is this issue still present?
Please make sure to update to the latest Home Assistant version and version of this integration to see if that solves the issue. Let us know if that works for you by adding a comment 👍.
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.'
—
Reply to this email directly, view it on GitHub https://github.com/iMicknl/ha-tahoma/issues/736#issuecomment-1081323254, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIZQ6PS3VXA6YLFMZHRH2QDVCJQPLANCNFSM5M5RHTWA.
You are receiving this because you were mentioned.

Hi @Tarawera, do you mean the latest HA version or latest tahoma 2.13.0?

I meant latest HA
Regards
David

On 3/04/2022, at 8:54 PM, callifo @.***> wrote:

Hi @Tarawera, do you mean the latest HA version or latest tahoma 2.13.0?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Cool thanks, will try, I've been running for 2.11 for a while, as for me, 2.13 was having said issue previously with older HA versions.

Bugger not for me, exactly an hour after HA start, it reverts back to 60 seconds polling,
2022-04-06 12:42:14 INFO (MainThread) [homeassistant.setup] Setting up proximity
2022-04-06 12:42:14 INFO (MainThread) [homeassistant.setup] Setup of domain proximity took 0.1 seconds
2022-04-06 13:42:14 INFO (MainThread) [backoff] Backing off fetch_events(...) for 0.5s (pyoverkiz.exceptions.NotAuthenticatedException: Not authenticated)
2022-04-06 13:43:45 INFO (MainThread) [backoff] Backing off fetch_events(...) for 0.9s (pyoverkiz.exceptions.NotAuthenticatedException: Not authenticated)

Interestingly I moved from the custom component over to the native HA integration and the issue has not appeared.

@callifo perhaps this has been fixed in the core integration. My advice would for sure be to stay on the core integration, since we are updating that one more frequently.
However, if it is on the service side, big chance that this will happen with the core integration as well eventually...

Will do, will keep an eye on it, and see if it does reoccur what release version it does relapse. Might provide more insight on where its being introduced.

@callifo can you share a new log with the Overkiz core integration on debug? I can have a look.
We focus on the core integration mainly now.

Attached,
debug.txt
config_entry-overkiz.json.txt

@callifo I wouldn't know to be honest, this is a HA setting. You should just try it.

It seems to stop the polling completely except for after a cover action, and I've not noticed any issue so far.


Update 404 & no access page(ux edits)

-update not found & no access sites to new designs
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #1609 (216c851) into main (47f6e4c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1609   +/-   ##
=======================================
  Coverage   71.73%   71.73%
=======================================
  Files         338      338
  Lines       10154    10154
  Branches      770      770
=======================================
  Hits         7284     7284
  Misses       2747     2747
  Partials      123      123

Flag
Coverage Δ

metweb
65.00% <ø> (ø)

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


Adding standard license and code of conduct

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[stable/postgresql] Setting persistence.enabled=false breaks the chart

Version of Helm and Kubernetes:
Helm: v2.11.0
Kubernetes: v1.12.2
Which chart:
stable/postgresql
What happened:
$ helm install --set "persistence.enabled=false" --name pg-demo stable/postgresql
Error: YAML parse error on postgresql/templates/statefulset.yaml: error converting YAML to JSON: yaml: line 88: mapping values are not allowed in this context
What you expected to happen:
The chart to install successfully
How to reproduce it (as minimally and precisely as possible):
$ helm install --set "persistence.enabled=false" --name pg-demo stable/postgresql
Anything else we need to know:
Happens since commit c8330f2dbcf1075f1ed1d112f66c922a4a926083
Maybe because we now have a duplicate updateStrategy in the stafulset.yaml.
I'll try to make a PR for this.

I've noticed this error also.

Fixed in https://github.com/helm/charts/pull/9952


SQL targets should allow configurable insert vs upsert behavior by default

Similar to https://github.com/meltano/sdk/issues/1781 we should add a default configuration enum to SQL targets to configure whether to run the target in insert (append only) mode or upsert mode. Some targets will want this behavior so they'll implement it in a custom way, its better to get in front of it so we have a consistent config option and enum for all targets.
In addition we should consider recommending insert as the default option even if upsert is support and a key property is provided. This avoids challenges with deduplicating within a sync (i.e. unsorted streams, no timestamp or incrementing sort key, etc.).

There could also be the option to run in trunc and load mode. This mode would truncate the table prior to loading. Its a bit risky so we should document it well. Snowflake has the time travel feature that allows you to recover any dropped tables or truncated rows back to a certain timestamp (default 24hr retention) so its a little safer if the developer accidentally uses this feature and drops their data.


[ASIM: NXLog ASIM DNS PARSER UPDATES]

This PR addresses the feedback received from Microsoft / @devikamehra about contributing my changes to the ASIM DNS NXLog parser direcly, instead of as part of a solution.
CHANGES:

Updated schema version
Extended the list of known DNS query types
Trying to re-introduce the DvcIpAddr field
Removed deprecated fields

REASONS FOR CHANGE(S):

The previous version of the parser was over a year old
New schema versions were released since then
Aiming to sync up the two parser versions that are in the repository

VERSION UPDATED:

Yes, to version 0.5

TESTING COMPLETED:

Need Help / How can I test this unreleased parser in my environment?

RAN VALIDATIONS:

Yes, all validations passed successfully

This work is associated with NXLog's Jira Issue IN-366

Dear @devikamehra , as requested in PR 8154, these are the changes that I would like to contribute to the Microsoft-maintained, NXLog-related ASIM parsers.
Please let me know if there is anything that needs to be changed or updated.

@vakohl Could you please give me some feedback, to see if there are any necessary changes, that I'd need to make?

@vakohl Could you please give me some feedback, to see if there are any necessary changes, that I'd need to make?

@jszigetvari-nxlog thankyou for your contributing in making Microsoft Sentinel better. I'll try to complete my review this week.
Can you please run the ASIM parser test functions for schema and data and attach both output with this PR? would be 4 file csv files, two for ASIM and two for vim.
Also, if possible please attach the sample logs as well, would help me with the review.

@vakohl Thanks for your feedback and kind words. Unfortunately I will have very little time in the upcoming few days to work on the tests. Perhaps next Monday, I can allot some time for this. Either way, I will let you know once I'm done with it, or get stuck somewhere.

@vakohl Hi Varun,
I tried saving the parsers into my workspace manually, by pasting the ParserQuery parts to the Sentinel Logs view/query editor, and saving them under a unique name, as functions. But unfortunately in case of the vim one, I get an error, and the save operation fails with:

Error saving function. Error code: InvalidOperationArgument. Error message: Invalid function parameters string. Encountered possible syntax errors: 'Missing expression (90,90)', 'Expected: ')' (91,93)', 'Expected: '{' (91,93)', 'Expected: '}' (91,93)'. Please see relevant documentation 'https://docs.microsoft.com/en-us/azure/kusto/query/'.

Hi @jszigetvari-nxlog, thanks for sharing the information, we will get back soon on this.

@vakohl Hi Varun,
I tried saving the parsers into my workspace manually, by pasting the ParserQuery parts to the Sentinel Logs view/query editor, and saving them under a unique name, as functions. But unfortunately in case of the vim one, I get an error, and the save operation fails with:

Error saving function. Error code: InvalidOperationArgument. Error message: Invalid function parameters string. Encountered possible syntax errors: 'Missing expression (90,90)', 'Expected: ')' (91,93)', 'Expected: '{' (91,93)', 'Expected: '}' (91,93)'. Please see relevant documentation 'https://docs.microsoft.com/en-us/azure/kusto/query/'.

Try replacing last line:
ASimDnsMicrosoftNXLog (starttime=datetime(null), endtime=datetime(null), srcipaddr='', domain_has_any=dynamic([]), responsecodename='', response_has_ipv4='*', response_has_any_prefix=dynamic([]), eventtype='Query', disabled=false)

Try replacing last line:
ASimDnsMicrosoftNXLog (starttime=datetime(null), endtime=datetime(null), srcipaddr='', domain_has_any=dynamic([]), responsecodename='', response_has_ipv4='*', response_has_any_prefix=dynamic([]), eventtype='Query', disabled=false)

@vakohl Thank you Varun for your review comments! I will try your suggestion when I will have some time.
In the other cases, I will make the changes, once we agree on what to do exactly.

Try replacing last line: ASimDnsMicrosoftNXLog (starttime=datetime(null), endtime=datetime(null), srcipaddr='', domain_has_any=dynamic([]), responsecodename='', response_has_ipv4='*', response_has_any_prefix=dynamic([]), eventtype='Query', disabled=false)

@vakohl Hi Varun,
Your recommendation worked, I was able to save the vim parser with your changes.
I also installed and ran the parser tests, and generated the csv files for you. Please find them attached.
vimDnsMicrosoftNXlog_ASimSchemaTester_query_out.csv
vimDnsMicrosoftNXlog_ASimDataTester_query_out.csv
ASimDnsMicrosoftNXLog_ASimSchemaTester_query_out.csv
ASimDnsMicrosoftNXLog_ASimDataTester_query_out.csv

@vakohl Hello Varun,
I realized that in my previous comment the outputs for ASimDnsMicrosoftNXLog were wrong, as I used an older version of the function. I corrected that now and the outputs look a lot better. I included the outputs for both functions in this comment. Those can be regarded as the latest ones.
Please let us agree on the still open questions, and I will push the resulting corrections to this branch, and then hopefully we can move towards merging this PR.
ASimDnsMicrosoftNXLog_ASimSchemaTester_query_out.csv
ASimDnsMicrosoftNXLog_ASimDataTester_query_out.csv
vimDnsMicrosoftNXlog_ASimSchemaTester_query_out.csv
vimDnsMicrosoftNXlog_ASimDataTester_query_out.csv

@vakohl Hello Varun, I realized that in my previous comment the outputs for ASimDnsMicrosoftNXLog were wrong, as I used an older version of the function. I corrected that now and the outputs look a lot better. I included the outputs for both functions in this comment. Those can be regarded as the latest ones.
Please let us agree on the still open questions, and I will push the resulting corrections to this branch, and then hopefully we can move towards merging this PR.
ASimDnsMicrosoftNXLog_ASimSchemaTester_query_out.csv ASimDnsMicrosoftNXLog_ASimDataTester_query_out.csv vimDnsMicrosoftNXlog_ASimSchemaTester_query_out.csv vimDnsMicrosoftNXlog_ASimDataTester_query_out.csv

I'll take a look and respond by this week.

@vakohl do you have any update on this?

@vakohl Hello Varun, I realized that in my previous comment the outputs for ASimDnsMicrosoftNXLog were wrong, as I used an older version of the function. I corrected that now and the outputs look a lot better. I included the outputs for both functions in this comment. Those can be regarded as the latest ones.
Please let us agree on the still open questions, and I will push the resulting corrections to this branch, and then hopefully we can move towards merging this PR.
ASimDnsMicrosoftNXLog_ASimSchemaTester_query_out.csv ASimDnsMicrosoftNXLog_ASimDataTester_query_out.csv vimDnsMicrosoftNXlog_ASimSchemaTester_query_out.csv vimDnsMicrosoftNXlog_ASimDataTester_query_out.csv

I'll take a look and respond by this week.

@jszigetvari-nxlog can you upload the result as mentioned in the guidelines here?
https://learn.microsoft.com/en-us/azure/sentinel/normalization-develop-parsers#test-results-submission-guidelines

@jszigetvari-nxlog can you upload the result as mentioned in the guidelines here?
https://learn.microsoft.com/en-us/azure/sentinel/normalization-develop-parsers#test-results-submission-guidelines

Okay, I can try, but if I follow them, the output filenames will be the same for ASimDnsMicrosoftNXLog and vimDnsMicrosoftNXLog which doesn't make much sense. I have to suffix them with the function name so that they are unique.

@vakohl Dear Varun, I believe I addressed all of your findings and requests.

@vakohl During the next 2 weeks I will have some dedicated time to work on this, so if you would be so kind to do another iteration in the review, then we would be able to move forward with this PR.

@vakohl During the next 2 weeks I will have some dedicated time to work on this, so if you would be so kind to do another iteration in the review, then we would be able to move forward with this PR.

@jszigetvari-nxlog thankyou. I'll review this today

@vakohl Thanks for the review, I will start working on it on next Monday.

@vakohl After the latest corrections I tried to run
vimDnsMicrosoftNXlog | limit 10000 | invoke ASimDataTester('Dns')```
But they both returned no results. (The time range was set to the last 4 months, and I used this very same setting during the last round of testing.)

@vakohl Apparently some of the tests are failing, but to me they don't seem to be tightly related to the changes I've made. Could you please help in finding out what may be wrong?

But they both returned no results. (The time range was set to the last 4 months, and I used this very same setting during the last round of testing.)

when running the parser for testing results, you can use the filter/parameters you were using before i.e. giving specific values. But with PR submission, you should declare the filter as I suggested in one of my previous comment

@vakohl Apparently some of the tests are failing, but to me they don't seem to be tightly related to the changes I've made. Could you please help in finding out what may be wrong?

For validation errors, Please see https://dev.azure.com/azure/Azure-Sentinel/_build/results?buildId=64957&view=logs&jobId=2bbe2297-1b5b-54f3-6060-67e7b289f6c3&j=2bbe2297-1b5b-54f3-6060-67e7b289f6c3&t=293f4a23-e36d-5efa-3a4e-ea46d4ab6d83
Please add '_ItemId' field of type string in the custom table here: https://github.com/Azure/Azure-Sentinel/blob/d798b63ced54f34a701e4893e0066b857b4ced72/.script/tests/KqlvalidationsTests/CustomTables/NXLog_DNS_Server_CL.json

Please add '_ItemId' field of type string in the custom table here: https://github.com/Azure/Azure-Sentinel/blob/d798b63ced54f34a701e4893e0066b857b4ced72/.script/tests/KqlvalidationsTests/CustomTables/NXLog_DNS_Server_CL.json

Thanks for pointing to the source of the problem. It really helped.
Fixed.

But they both returned no results. (The time range was set to the last 4 months, and I used this very same setting during the last round of testing.)

when running the parser for testing results, you can use the filter/parameters you were using before i.e. giving specific values. But with PR submission, you should declare the filter as I suggested in one of my previous comment

It turned out that there was a different problem, but I sorted it now, so I am submitting the latest results for the data tests too.

@vakohl All the necessary changes were carried out, and the tests are passing now.

@vakohl This has been an exhausing process. I assume it was the same for you. Thanks for your efforts!

@jszigetvari-nxlog thankyou for your contribution. I'll approve this PR once the validation are through.

@jszigetvari-nxlog thankyou for your contribution. I'll approve this PR once the validation are through.

@vakohl The KqlValidations task failed for some reason, and I tried to look at the error(s) but the error log doesn't seem to be too helpful: https://dev.azure.com/azure/43fcaf68-ba3d-474b-97f3-7a1e6fbb5c8d/_apis/build/builds/65361/logs/155

@v-atulyadav can you please check the validation error?

@vakohl, validations are cleared now.

@vakohl, validations are cleared now.

Thaknyou @v-atulyadav


Update aks-cicd-azure-pipelines-content.md - Increase readability

Increase readability

These minor editorial changes look good to merge. Thanks @lukemurraynz


enhanced error message for getEmailTemplate() in EmailTemplate.js

Updated error messages as discussed in #125

Thank you!


previously declared functions (conflicts)

Q
A

Issue Type
Bug

Deployer Version
3.3.0 (all versions?)

Local Machine OS
os x 10.11

Remote Machine OS
N/A

Description
fatal errors with some global functions conflicting with other packages.
Steps to reproduce
install deployer globally, run dep with laravel/valet also installed globally
or run dep with locally installed a laravel app (or anything with hamcrest/hamcrest-php installed)
Output log
installed globally along with laravel/valet:
Fatal error: Cannot redeclare output() (previously declared in /Users/username/.composer/vendor/laravel/valet/cli/includes/helpers.php:39) in /Users/username/.composer/vendor/deployer/deployer/src/functions.php on line 520

or installed locally with hamcrest/hamcrest-php installed (via something else, not sure what.. just part of Laravel maybe?)
Fatal error: Cannot redeclare set() (previously declared in /Users/username/Code/codecomp/vendor/hamcrest/hamcrest-php/hamcrest/Hamcrest.php:455) in /Users/username/Code/codecomp/vendor/deployer/deployer/src/functions.php on line 420

To fix it I guess use namespaced global functions?
Will PR if I get a chance - deadlines though :(

..confirmed it can be fixed by either wrapping all the global function definitions in:
namespace Deployer {
   // functions
}

then importing all functions in deploy.php e.g. Deployer\task();
This would be a breaking change though.
Version 4.0?

This issue is discussed in other issues.
In version 4.x will be fix with function namspace.
With version 3.x, you should using deployer.phar file to deploy.

i'm on 4.x-dev, and got this fatal error:
PHP Fatal error:  Cannot redeclare set() (previously declared in /var/www/sources/xxx/vendor/hamcrest/hamcrest-php/hamcrest/Hamcrest.php:455) in /var/www/sources/xxx/vendor/deployer/deployer/src/functions.php on line 420


Data Pie Chart - Selection and Highlighting samples shouldn't require user input

The selection AND highlighting samples in Data Pie Chart topic do not change unless users change Auto settings to some other values. This looks like chart are broken but in fact they require an extra action from user to see selection AND highlighting features. Please change AUTO values to some other values so selection AND highlighting features are showcased without user's input
https://www.infragistics.com/products/ignite-ui-blazor/blazor/components/charts/types/data-pie-chart#blazor-data-pie-chart-highlighting
https://www.infragistics.com/products/ignite-ui-blazor/blazor/components/charts/types/data-pie-chart#blazor-data-pie-chart-selection

@HUSSAR-mtrela
There is currently a bug in the property editor default value. Investigating


Java 8 - Jena 3.1

Update to Java 8, Jena 3.1.0 (which requires Java >= 8), other libraries updated as well. Tried to change the code as little as possible. This could be a basis for further development.
Cheers,
Gerald

It does not need to be merged in the master branch, since companies still might use Java 7...

Do the library updates require Java 8?
If not, these library updates could be merged into the master branch, and the Java 8 code changes to develop?

I think this version of log4j requires java 8. But it can be changed to a version < 2.4, which I think doesn't. As far as I can tell, the other libraries don't require Java 8.

Java 8 is the default version now, the Java 7 version is no longer supported.


Remove GpuAttributeReference and GpuSortOrder

This fixes #199
This fixes #187
This takes over for #244

@tgravescs @jlowe Because this does have a potential impact to a lot of downstream PRs I would like to merge this in even if CI is not set up yet. All of the release changes are in except for CI.  I upmerged to the latest on branch-0.2 and ran the full set of tests locally are you OK if I merge this in?

are you OK if I merge this in?

I'm OK with it.  Worst-case scenario the build is broken and we fix it with a followup or revert.  We need to keep making progress.


[dio] Revert changes to CancelToken.cancel behavior

New Pull Request Checklist

[x] I have read the Documentation
[x] I have searched for a similar pull request in the project and found none
[x] I have updated this branch with the latest main branch to avoid conflicts (via merge from master or rebase)
[x] I have added the required tests to prove the fix/feature I'm adding
[x] I have updated the documentation (if necessary)
[x] I have run the tests without failures
[x] I have updated the CHANGELOG.md in the corresponding package

Additional context and info (if any)
Fixes #1765

@kuhnroyal Plz also takes another look at #1386 since you've requested a change request. (Hide this as off-topic after you read)

I guess we should release this asap.


feat(appengine): Port StaticContent sample to .NET 6

Same idea as #2164 and #2172 . This one seems way simpler.

It's till showing as having conflicts. Can you rebase your PR locally on HEAD and fix the conflicts.

Nope, that's fine, I think something like this has happened before, that the message saying "There are conflicts" is not refreshed for some reviewers even when the conflicts are fixed. I couldn't see any specific conflicts either, just a message saying there were some.
If I see this again I'll report it as an issue to GitHub.


VSCode Does not Clean Up After Itself. workspaceStorage has Gigabytes of Useless Data!

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:
OS Version:

Steps to Reproduce:

Go to  %APPDATA%\Code\User\
Alt +Enter on workspaceStorage

These are all workspace folders from 2019 - 2021. 2GB for basically nothing.
VSCode should scan these folders every 3 months and remove 3 month old data. Please respect my storage.

See #32461


style: use single quotes everywhere and add a rule to eslint

Which problem is this PR solving?

#582

Short description of the changes

Added ESlint rule for single quote
Ran ESlint:fix on the entire repo
Went over the README's and changed to single quotes there
fixed single quotes in scripts

(There's also eslint.config.js itself, but I wasn't sure if everywhere includes it, tell me if I should also edit it)

So it failed the test because of a package that came out a few minutes ago (@babel/parser):

that's interesting 😅

It's probably just bad timing. @babel/core was published, the dependency was not.
Trigger new CI run with an empty commit git commit --allow-empty.

i've restarted the build myself but you should be able to do it if you go on the build page (by clicking on either tasks) and click on "Restart all jobs" on something like this at the top right

When i look at my own repos, i have a button that says "re-run jobs",
but it doesn't show up here.


Watchlist Component - Fix#4, Fix#27

Added Watchlist Component
Fixes #4 #27
https://user-images.githubusercontent.com/67220225/152403935-fdd8d9c3-7032-4f8c-b5f3-33eeeadeed2d.mp4

Yes, the database has been joined to Firebase - Cloud Firestore. It fetches real-time data from the firestore every time the app is opened.


ASNField is too small

ASNField is a PositiveIntegerField, which means its range is from 0 to<PHONE_NUMBER> (2^31-1) because it is still stored as a signed integer in the database. An ASN is a unsigned 32-bit integer these days, and therefore has a range of 0 to<PHONE_NUMBER> (2^32-1). To be able to store all valid ASNs a PositiveBigIntegerField should be used.

I'm amazed that PositiveIntegerField is a 31bit number, but you're absolutely correct, and thank you for the catch and PR. :)

I'm amazed that PositiveIntegerField is a 31bit number, but you're absolutely correct, and thank you for the catch and PR. :)


Add Budget App

It's a budget app that takes care of your expenses and shows the details of the items on which you have to spend your money.
Its working video,
https://user-images.githubusercontent.com/75881393/116507299-a174f400-a8dc-11eb-9ae0-7df9dfb38290.mp4

Please @ridsuteri @urvashi-code1255 @991rajat review this issue.

@K-jais someone is already working on this issue,will  get back to you in couple of days!

I am asking for this budget app.

@ridsuteri not that brick breaker game as now I know someone is working on it. But please look into this budget app issue.

@ridsuteri This is a budget app and I have attached the wokring video of it.

@ridsuteri This is a budget app and I have attached the wokring video of it.

@K-jais another budget app issue is also open! let's wait for it

Let's merge this one, will Tell other to replace it.


Automated e2e stack test

Create e2e_test script that will init, build, deploy, and black box test the common gp scenarios - empty, client+geoprocessor+processor.  Should call the black box test script, exercising all APIs.
Current status - stubbed via e2e_test in top-level package.json calling initTestProjects.mjs, exercising simple build and deploy and destroy but not fully implemented.

Pulled out as unfinished task from #115

Potential steps/tests within a stack: get manifest, run sync function and get results, async long poll, verify socket subscription set, verify cache set, run async function, verify cache hit, get async results, etc.


SynchronousOnlyOperation execption since Version 0.46.2

Describe the Bug
If I want to access a foreign key in a resolver, I get this error since version 0.46.2:
django.core.exceptions.SynchronousOnlyOperation: You cannot call this from an async context - use a thread or sync_to_async.
System Information

Operating system:

Windows 10

Strawberry version (if applicable):

0.235.2

Additional Context
Here is my implementation:
# book.py
async def resolve_books(info: Info) -> book_types.BooksResult:
    try:
        user = info.context.get("request").consumer.scope.get("user")
        result = await sync_to_async(services.book.all)(user=user)
        return book_types.Books(books=result)
    except PermissionDenied as err:
        return PermissionProblem(code=err.code, message=err.message)

@strawberry.type
class BookQueries:
    books: book_types.BooksResult = strawberry.field(resolver=resolve_books)

# book_types.py
from core.graphql.author import author_resolver

BooksResult = Annotated[
    Union[Books, PermissionProblem],
    strawberry.union("BooksResult"),
]

@strawberry_django.type(
    model=models.Book, filters=BookFilter, order=BookOrder, pagination=True
)
class Book:
    id: auto
    name: auto
    author: AuthorResult = strawberry.field(resolver=author_resolver)

# author.py
def author_resolver(root, info: Info) -> author_types.AuthorResult:
    id_ = root.author_id
    return resolve_author(id=id_, info=info)

async def resolve_author(id: uuid.UUID, info: Info) -> author_types.AuthorResult:
    try:
        user = info.context.get("request").consumer.scope.get("user")
        result = await sync_to_async(services.author.get)(
            user=user,
            id=id,
        )
        return result
    except PermissionDenied as err:
        return PermissionProblem(code=err.code, message=err.message, object_id=id)
    except DoesNotExist as err:
        return DoesNotExistProblem(code=err.code, message=err.message, object_id=id)

The problem is the call root.author_id in def author_resolver. In version 0.46.2 the author_id was already loaded at this point. This is why there was no error message.
What is the best way to change my implementation so that it works again with the current version?

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Hi @MaehMaeh ,
Yes, this got changed in this PR to fix some issues with custom resolvers.
In summary, when you define a custom resolver for a field, you need to provide hints for anything that you are going to access inside it. That means that the fix would be to do this:
@strawberry_django.type(
    model=models.Book, filters=BookFilter, order=BookOrder, pagination=True
)
class Book:
    id: auto
    name: auto
    author: AuthorResult = strawberry_django.field(
        resolver=author_resolver,
        only=["author_id"],
    )

On a side note, you could simply type this directly and the optimizer would take care of doing select_related for you. Is there a reason why you are using a custom prefetch in this case?

Going to close this as the question is probably already answered, but please let me know if we need to reopen it for some reason

First of all, a big thank you for solving my problem.
About the reason:
The idea behind the structure is that I would like to have the option of returning a union for each object. So in this example Author or PermissionProblem. This should also be possible in the subquery. This should make such queries possible:
query Books {
  books {
    ... on Books {
      books(
        order: {creator: {email: ASC}}
        filters: {creator: {email: {contains: "rwt"}}}
        pagination: {limit: 3, offset: 0}
      ) {
        id
        name
        author {
          ... on Author {
            name
          }
          ... on PermissionProblem {
            objectId
            code
            message
          }
        }
      }
    }
    ... on PermissionProblem {
      objectId
      code
      message
    }
  }
}

My permission check takes place exclusively in the layer below the GraphQL layer, as several “front ends” can access the back end. I'm beginning to regret my approach too. And of course it could easily be that there could be an easier, more sensible variant.


UP-grading the feedback form with more details

Is your feature request related to a problem? Please describe.
The emojis are not properly given.
I also want to add more details.

@ayush-848 what details do you want to add?

@ayush-848 what details do you want to add?

First The emoji will be properly displayed and on clicking submit the emoji will scale up and then down like a sort of animation
Additional Questions:-
How did you hear about us?
What could we do to improve?
What specific services you liked?
(and why)
Any scope for improvement?

@Priyaaa1 can you assign this to me?


Reorganize annotation_and_masks and saliency modules

Two minor changes for code clarity/modularity and forward compatibility.
1. Create a module of general utilities:
This is located at histomicstk.utils.general_utils  and includes a base class that is inherited to avoid duplication of basic behavior like assigning default attributes.
2. Reduce unit test fragility:
Existing unit tests in the annotations_and_masks and saliency modules were a bit fragile. This is handled here.

@manthey Please ignore the commit history here. I was working halfway through an extension to the saliency module when I realize I needed to do the refactoring/reorganization shown here. So to keep PRs separate and somewhat modular, I removed the updates to the saliency module and only kept the reorganization bits here. I ran all the unit tests again and made sure none of these changes affect the tests, but feel free to run if you like.
Thanks!


New release ?

Hi, any chance of releasing a new version with support for Ubuntu 18.04 or should I just use master?

Hi @tarjei,
Because we have a backward incompatible PR #305 , this will be a new major version.
We have also in the pipe some others PR #308 and #309 also backward incompatibles.
And we try to change the major version in a frequency that is not too high.
But i understand that Ubuntu 18.04 is expected. Lets try to move forward about the two others PR.
Thank you for your question.

Thank you for a great module and a very quick answer :)
I'm closing this for now.


Support absolute imports than only relative

Looks like currently we only support relative paths https://github.com/evenchange4/graphql.macro/blob/master/src/macro.js#L31

this is a killer for me, I have a mono-repo setup and it isn't finding my graphql imports

same issue for me, especially you need to import fragment which located in different folder as query file, that would be the hell

Would it be possible to handle absolute imports using tsconfig as well?


avoid dependencies for the core of reason

the core part of reason is the parser, which currently consists of these modules: reason_config, reason_utils, reason_lexer, reason_parser.
In module reason_utils, it used a function Str.global_replace which can be easily replaced by a little function. (It introduced dependencies on str library, which  is not supported by js backend, also str itself relies on c stubs, better to avoid it)
about menhir, according to the manual

Can I ship a generated parser while avoiding a dependency on MenhirLib? Yes. One option is to use the code-based back-end (that is, to not use --table). In this case, the generated parser is self-contained. Another option is to use the table-based back-end (that is, use --table) and include a copy of the files menhirLib.{ml,mli}togetherwiththegeneratedparser.Thecommandmenhir --suggest-menhirLibwill tell you where to find these source files.

So, if we use --table, we just need check in generated files and two other files menhirLib.{ml,mli}

so for real use (not playground), there is no need to get rid of dependencies on str, the only thing is to check in menhir generated code and (menhirLib.ml(i)), and you are happy to keep the core dependency minimal
see https://github.com/bloomberg/bucklescript/issues/396

@bobzhang Thanks. Now I understand the motivations behind removing the dependencies. I will start working on this soon.

@bobzhang In order to support bucklescript, do you also want us to provide build procedures based on the generated Menhir file, or are you going to integrate it into bucklescript ?

@yunxing thanks for having a look, I have a pack tool which will bundle all files from reason into a single ocaml file, so there is no build procedure required, we only need the core of reason does not introduce 3rd party dependencies, in that case, I would also need include the source of the third party library.
Btw, str is fine, since it is in the core distribution of ocaml

@bobzhang nice, good to know. I will write a replacement for Str.

@yunxing @jordwalke  is it possible to check in generated ml file from menhir ?
We do have menhir in production, however, menhir required by reason is the latest one. I see https://github.com/jordwalke/npm-menhir, so I might give it a try if the decision is not checking in generated files, the main issue with npm-menhir is that it takes too much time to dowload and compile and I see no obvious disadvantages if we check in generated files, it would save reason's user's time.

Is it ok if we check in the one generated by --table?
Btw the checked-in ml file would be 2-8MB.
--
Yunxing
![](https://link.nylas.com/open/2gjtyq1vxam8jgrgiizrfc7pl/local-
3076b2b5-56e9?r=cmVwbHkrMDAwZjg3NTkyODAzOWRhMTU3YjA3MWE2YmY5Njk3Yjg2OTM1MmI1YjYxOWMwZTIxOTJjZjAwMDAwMDAxMTM3YzA4ZTY5MmExNjljZTA5MmM3ZTA2QHJlcGx5LmdpdGh1Yi5jb20=)
On Jun 17 2016, at 11:52 am, Hongbo Zhang<EMAIL_ADDRESS>wrote:

@yunxing
@jordwalke
is it possible to check in generated ml file from menhir ?

We do have menhir in production, however, menhir required by reason is the
latest one. I see [https://github.com/jordwalke/npm-
menhir](https://github.com/jordwalke/npm-
menhir&r=cmVwbHkrMDAwZjg3NTkyODAzOWRhMTU3YjA3MWE2YmY5Njk3Yjg2OTM1MmI1YjYxOWMwZTIxOTJjZjAwMDAwMDAxMTM3YzA4ZTY5MmExNjljZTA5MmM3ZTA2QHJlcGx5LmdpdGh1Yi5jb20=),
so I might give it a try if the decision is not checking in generated files,
the main issue with npm-menhir is that it takes too much time to dowload and
compile and I see no obvious disadvantages if we check in generated files, it
would save reason's user's time.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on
GitHub,
or [mute the thread](https://github.com/notifications/unsubscribe/AA-HWQbZ-
yN02Th_wVlWSMxHi0O4JJKbks5qMuzmgaJpZM4Iasnm&r=cmVwbHkrMDAwZjg3NTkyODAzOWRhMTU3YjA3MWE2YmY5Njk3Yjg2OTM1MmI1YjYxOWMwZTIxOTJjZjAwMDAwMDAxMTM3YzA4ZTY5MmExNjljZTA5MmM3ZTA2QHJlcGx5LmdpdGh1Yi5jb20=).![](https://github.com/notifications/beacon
/AA-HWWiTJ6Pozz3YCrsnJ8mHWdXnyrJDks5qMuzmgaJpZM4Iasnm.gif)

I think --table is the one used in reason, no?

@yunxing Yes, for --table backend, we also need menhirLib.ml and menhirLib.mli for the runtime support (for the specific version of menhir). For best performance, people would use --code backend to parse it first, when finding an error, it would fallback to --table backend for better error message, but it is not necessary.
I would like to spend some time in the next few weeks to integrate the parser with bucklescript, ideally, we should have commands below work out of the box
bsc --bs-rest-files *.re *.rei

To make this happen and maintainable in the future, my vision of reason parser is that it would be a self contained library, its dependency is limited to the core distribution (it's fine to have more dev-dependencies for example, menhir), do you think this is the right direction?
thanks for looking into this issue!


fix: Duplicated CLI output related to read files

fix duplicate logs
fix: #1734
/claim #1734

Summary:
Briefly describe the changes made in this PR.
Issue Reference(s):
Fixes #... (Replace "..." with the issue number)
Build & Testing:

[x] I ran cargo test successfully.
[x] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[ ] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[ ] I have performed a self-review of my code.
[ ] PR follows the naming convention of <type>(<optional scope>): <title>

Summary by CodeRabbit

Refactor

Improved handling of file reading in the configuration settings, ensuring more efficient processing for different file types.
Adjusted logic for reading files based on link type, with a separate handling for Protobuf files.
Refactored Protobuf link handling to a separate block for better organization.

@tusharmath the PR is ready for review.

@35C4n0r I think it would be better to build caching inside of ResourceReader, something like:
ResourceReader::init(runtime, true)

ResourceReader, could maintain a HashMap of file path and content and cache it locally when enabled.

@tusharmath added cache feature, kindly give it a review.

@35C4n0r The issue was attempted by @Shylock-Hg and I think that PR is going in the right direction, so closing this one.
https://github.com/tailcallhq/tailcall/pull/1741


Dropdowns are missing their gradients and scroll bars

Context
All the dropdowns are missing their gradients and scroll bars so it's not clear when there's more content on them.
Current Result
Looks like there's nothing else there,

but...

(Notice that the scroll bar is only appearing when you scroll...)
Expected result
Dropdowns with more content than what they can show, need a visible scroll bar at all times, as well as a gradient on the bottom part.

I opened mine first 😛  -> https://github.com/CartoDB/cartodb/issues/11597

Hey, what about if we follow the same behaviour we already have in the infowindows? No gradient, but scroll bar visible always.

If we start adding gradients also in dropdowns, we could have performance problems due to we should listen all scroll movements in all dropdowns.

Where's the PR for this ticket?

Found it: https://github.com/CartoDB/cartodb/pull/11609

Ouch sorry, already referenced :(.


Dataset type autofilled now?

Issue in ./help/connections/create-connection.md
Hi you guys. I think that the dataset type is autofilled now, so you may want to update the documentation to show that, instead of saying that you have to choose one. Just a thought.
thanks,
Doug

Thanks @mugdoor - I had fixed this but forgot to close this issue.


Support for encryption

Hi!
I'm loving this gem and use it extensively through some core components of my product.
We're workings towards integrations and want to save some arbitrary data based on the integration a user chooses.
This data can vary from sensitive data like access_tokens to just ids for specific resources in a system.
I tried setting up attr_json & lockbox together but they do not seem to work together properly.
I was wondering if there is a way to make attr_json & lockbox/ encrypts rails 7 work together nicely.

Hi thanks for getting in touch!
I think it would take some work, because of the way attr_json needs to make a copy of the attribute in the JSON hash.  The attr_json code is already a bit convoluted.
I'm looking to find some time to refactor a bit to simplify (now that we can drop support for old Rails; there were some improvements to attributes API around Rails 5.0 I think, that came after the first version of this!), and want to look to jsonb_accessor for patterns when I do.  jsonb_accessor is pretty good, and in some ways has a cleaner implementation -- but doesn't handle nested models like we do here.
I'd be curious if encrypted attributes work with jsonb_accessor -- want to check it out and report back? (You'd want to actually look at the json hash itself and confirm the attributes are really encrypted in the DB). If you don't need nested models you might just want to use it, but either way I'm curious for the report back, because if it does work, then perhaps it would show a path to making attr_json work too.
Back to attr_json....  you could just mark the whole json(b) column/attribute encrypted with standard Rails or lockbox, and I believe that should work fine (let me know if it does/doesn't?), although that may be inconvenient (you aren't really going to be able to DB query on individual attributes at all ever) and not what you're looking for.

Hi, I'm going to close this for now due, but if you comment again and want to discuss/investigate more, I can re-open it!  I am interested in the results of any further investigations you do.


Make it extensible

Working with Proxy for this is a real PITA since the syntax is overly complex. We should implement something like this:
// Add a selector-level flexibility
// dom.class.important
dom.api.selector = {
  id: () => {},
  class: () => {},
  attr: () => {},
};

// Once we get an array of elements, add attribute-level options
// let html = dom.a.html; let attr = dom.a.
// dom.a.html = "a";
// delete dom.a.html;
dom.api.attributes.html = {
  get: () => {},
  set: () => {},
  delete: () => {}
};

Or maybe not, but a review to the code for clarity is needed for sure since that's what is stopping development mainly. So this is a reminder of that.

This has been merged, now the last bits are being re-added.


Dapp shows "Switch your network"

DApp: https://omni.xdaichain.com/bridge
It works fine in Metamask Trust and imtoken.
But in AlphaWallet, it shows "Switch your network", no matter the browser is connected to Ethereum or xDai.

@vladyslav-iosdev if you are up for some JavaScript fun. Otherwise assign it back to me :)


testing: TempDir RemoveAll cleanup failures with "The process cannot access the file because it is being used by another process."

--- FAIL: TestRWithNonexistentFile (0.83s)
    testing.go:1090: TempDir RemoveAll cleanup: remove C:\Users\gopher\AppData\Local\Temp\1\TestRWithNonexistentFile1599077814\001\pack.exe: The process cannot access the file because it is being used by another process.
FAIL
FAIL	cmd/pack	4.916s

This can probably be fixed by expanding the set of errors handled by the retry loop added for #50051.
greplogs --dashboard -md -l -e 'TempDir RemoveAll cleanup: .* The process cannot access the file because it is being used by another process\.'

2022-02-25T23:38:11-01e522a/windows-amd64-2012
2021-10-28T18:10:50-2bc8ed8/windows-amd64-2012
2021-10-14T18:43:59-765c911/windows-amd64-2012
2021-09-30T19:56:27-70b1a45/windows-amd64-2012
2021-09-17T19:32:44-74e384f/windows-amd64-2012
2021-03-09T08:19:14-b70a2bc/windows-386-2008
2021-03-09T08:19:14-b70a2bc/windows-amd64-2008
2021-03-09T08:19:14-b70a2bc/windows-amd64-2012
2021-03-09T08:19:14-b70a2bc/windows-amd64-2016
2021-03-09T08:19:14-b70a2bc/windows-amd64-longtest
2021-03-09T08:19:14-b70a2bc/windows-amd64-race
2021-03-09T08:19:14-b70a2bc/windows-arm-zx2c4
2021-03-09T07:44:18-437d229/windows-amd64-2008
2021-03-09T07:44:18-437d229/windows-amd64-2012
2021-03-09T07:44:18-437d229/windows-amd64-race
2021-03-09T07:44:18-437d229/windows-arm-zx2c4
2021-03-09T02:20:55-618b66e/windows-amd64-2008
2021-03-09T02:20:55-618b66e/windows-amd64-2012
2021-03-09T02:20:55-618b66e/windows-amd64-2016
2021-03-09T02:20:55-618b66e/windows-amd64-race
2021-03-09T02:20:55-618b66e/windows-arm-zx2c4
2021-03-08T23:13:52-b6def6a/windows-amd64-2008
2021-03-08T23:13:52-b6def6a/windows-amd64-2012
2021-03-08T23:13:52-b6def6a/windows-amd64-2016
2021-03-08T23:13:52-b6def6a/windows-amd64-race
2021-03-08T20:41:06-a08adda/windows-386-2008
2021-03-08T20:41:06-a08adda/windows-amd64-2008
2021-03-08T20:41:06-a08adda/windows-amd64-2016
2021-03-08T20:41:06-a08adda/windows-amd64-longtest
2021-03-08T20:41:06-a08adda/windows-amd64-race
2021-03-08T20:03:01-bd37284/windows-386-2008
2021-03-08T20:03:01-bd37284/windows-amd64-2008
2021-03-08T20:03:01-bd37284/windows-amd64-2012
2021-03-08T20:03:01-bd37284/windows-amd64-2016

(This error message is 0x20 ERROR_SHARING_VIOLATION.)

Apologies for commenting on a closed issue. However, I wanted to ask if there is any chance this makes its way out prior to 1.19?

@bhasden Are you encountering this yourself?  What Go version and what GOOS/GOARCH?  Thanks.

FWIW, this fix would be easy to backport to Go 1.18, but somewhat less trivial to backport to Go 1.17 (it would also need CL 371296, which is a bit more invasive).
There is also a workaround that you can apply for your own specific tests independent of the Go version: you can defer (or t.Cleanup) your own function that iterates os.RemoveAll on the directory returned by TempDir until it is successfully removed.

@bhasden Are you encountering this yourself? What Go version and what GOOS/GOARCH? Thanks.

I believe I'm running into this same issue in Golang 1.18.1 and 1.18.2 (only two versions I've tested) with some casbin tests that are loading a model configuration file. It's only reproducible in Windows. Team members on non-Windows machines are not running into the issue.

go env output:
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\BrianHasden\AppData\Local\go-build
set GOENV=C:\Users\BrianHasden\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\BrianHasden\go\pkg\mod
set GONOPROXY=github.com/merit
set GONOSUMDB=github.com/merit
set GOOS=windows
set GOPATH=C:\Users\BrianHasden\go
set GOPRIVATE=github.com/merit
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Users\BrianHasden\go\go1.18.2
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Users\BrianHasden\go\go1.18.2\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.18.2
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=C:\code\issuance\go.mod
set GOWORK=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\BRIANH~1\AppData\Local\Temp\go-build2379612813=/tmp/go-build -gno-record-gcc-switches

I'm still experiencing this issue in go1.20.3.

There is also a workaround that you can apply for your own specific tests independent of the Go version: you can defer (or t.Cleanup) your own function that iterates os.RemoveAll on the directory returned by TempDir until it is successfully removed.

@bcmills this workaround still works.
It looks like the 2 seconds timeout in the removeAll workaround of the testing package is not enough...
https://cs.opensource.google/go/go/+/master:src/testing/testing.go;l=1248-1276;drc=master

@i4ki This issue has been closed for almost a year, and we think it is fixed.  If you are seeing a problem with 1.20, please open a new issue with reproduction details.  It may be the same problem, but it may be a new one.  Thanks.

I'm experiencing the same error in syncthing's test suite on go 1.20.3:
go test -r TestHandleFile ./...
...
--- FAIL: TestHandleFile (1.60s)
    testing.go:1206: TempDir RemoveAll cleanup: remove C:\Users\ross\AppData\Local\Temp\TestHandleFile1557195908\001: The process cannot access the file because it is being used by another process.
FAIL
FAIL    github.com/syncthing/syncthing/lib/model        1.821s
...
--- FAIL: TestHandleFileWithTemp (1.45s)
    testing.go:1206: TempDir RemoveAll cleanup: remove C:\Users\ross\AppData\Local\Temp\TestHandleFileWithTemp2880978547\001: The process cannot access the file because it is being used by another process.
FAIL
FAIL    github.com/syncthing/syncthing/lib/model        1.578s

Syncthing is solving this by rewriting the code to use an emulated file system in https://github.com/syncthing/syncthing/pull/8889

@rasa, as far as we know the retry loop that was added for this issue works.
It is likely that your test is actually leaking an open file when the test returns.
If you can definitely rule that out, please file a new issue.


Life cycle issue

Writing a wct test to cover a new feature I'm adding to the Polymer Dom API, I noticed a strange life cycle issue with Safari (9.0.1) and Firefox.
The issue appears when creating programmatically a Polymer component. For example, given the following component:
<dom-module id="x-focusable">
 <template>

x-focusable

 </template>

</dom-module>

The following unit test fails on Safari and Firefox (browers without native shadow):
test('Polymer.dom should have one child with a dynamic allocation', function () {
    if (Polymer.Settings.useNativeShadow) {
      return;
    }
    var a = document.createElement('x-focusable');
    Polymer.dom(document.body).appendChild(a);
    Polymer.dom.flush();
    if (Polymer.Settings.useShadow) {
      assert.equal(a.childElementCount, 0);
      assert.equal(window.unwrap(a).childElementCount, 1);  // <-- fails here
    } else {
      assert.equal(a.childElementCount, 1);
      assert.equal(Polymer.dom(a).children.length, 0);
    }
    Polymer.dom(document.body).removeChild(a);
  });

However x-focusable has 1 div in its definition. I created a branch to illustrate this issue: https://github.com/MartinMoizard/polymer/tree/lifeCycleIssue.
Thank you

+1

This is sort of a known issue: https://github.com/Polymer/polymer/blob/master/src/lib/dom-api-flush.html#L50-L54.
Basically, the ShadowDOM polyfill is hiding the creation of the shadowroot from Polymer's MutationObserver it uses for Polymer.dom.flush. You can wait one async call to work around.

This is quite an old issue and I can't find the definition of window.unwrap in either the polyfills or Polymer. When trying to reproduce this problem, I was unsuccesful (http://jsbin.com/zulinipoco/edit?html,console,output) This returns 1 for me all the time.
Therefore I think this has been solved along the way. Feel free to reopen with an updated JSBin if you are still experiencing issues.


Voyager::image function - Storage::disk( not returning url with port no

Laravel Version: 5.4..13
Voyager Version: v0.11.3
PHP Version: 7
Database Driver & Version: NA

Description:
your url method used not getting reference of port no
so all images path broken,
this may also due to Storage::disk(config('voyager.storage.disk'))->url($file);
Steps To Reproduce:
php artisan server --port=8001
http://<IP_ADDRESS>:8001/admin/posts
returning:
http://localhost/storage/posts/7uelXHi85YOfZKsoS6Tq.jpg
so without port in url image broken,
even though image file exits

Can you show me your APP_URL in .env ?
Anyway, I tried different port and that still work in mine.

APP_URL is likely set incorrectly as @uchsarath mentioned.  Please check this and respond here whether this is resolved.

Its working now. have to explicit
APP_URL=http://<IP_ADDRESS>:8001

@uchsarath You just need to restart the server

@tamersolieman, this issue has been closed for nearly a year. Your comment adds nothing to it. Please refrain from doing so

there is no way to make voyager get the current port? Instead of hardcoding it?

Thats a Laravel limitation(or feature), not specific to Voyager

👍 ..ok

my problem is that I´m running on different ports and I´m having to change every time the port in the APP_URL in the .env file...
so the avatars pictures aren´t showing if I do not change

What you're describing is a limitation in how Laravel renders asset URLs, and is only tangentially related to Voyager, so I'm going to have to stop the discussion here.  Feel free to discuss all you want in slack or elsewhere if you wish.
I will say, however, that if your port is changing all the time, you need to take a closer look at your deployment process and webserver configuration.  Perhaps you need a proxy layer to provide a consistent endpoint


Publish accessibility acceptance criteria for Design System components

What
Draft and publish accessibility acceptance criteria to be used when contributing new components to GOV.UK Design System.
Why
Whilst building the Notification banner and Cookie banner components we used a template to check how components in the Design System should behave with various assistive technologies. We feel there is value publishing this information so it can be used by future contributors.
Who needs to know about this
Hanna, Eoin
Done when

[x] Documentation scoped
[ ] Documentation drafted
[x] Identified where documentation will live
[ ] 2i'd
[ ] Published

This may change in future, but for now the likeliest location for this content is probably within https://github.com/alphagov/govuk-frontend/tree/main/docs/contributing.

Unless we wanted to add it here: https://design-system.service.gov.uk/community/?

Early draft here: https://docs.google.com/document/d/133tfhMrCzpZizAOtggzgXGJJRCJKt7KR6M3WUWZekk0/edit

We've shared the doc with the rest of the Design System team for internal review.

@vanitabarrett has kindly offered to do a frontend dev review of the draft.

We've updated the doc following feedback from the Frontend and accessibility communities. I've now sent the doc for 2i.

Doc has passed 2i. Will now publish it.


feature(hyphenate): convert camelCase to kekab-case

add feature to  convert camelCase to kekab-case.  Inspired by same feature in vue-bem-cn
refactor bem function. Change it to generator for lock plugin config.

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket: