No such command : refreshOperatingMode

Did you read the instructions?

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

The problem
Hi Team,
With an io:AtlanticPassAPCZoneControlMainComponent I can see all the climates and sensors, but if I try any action all of them become "unavailable"... For exemple,  -> operation -> from off to heat (only have Auto / heat / off not cool here).
What version of this integration (ha-tahoma) has the issue?
2.5.1
What version of Home Assistant Core has the issue?
core-2021.7.2
Which gateway / hub do you use?
Cozytouch
Device model
Zone Control 2.0
Device type
io:AtlanticPassAPCZoneControlMainComponent
Additional information
No response
Relevant log output
2021-07-16 16:45:14 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration huesyncbox which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-16 16:45:14 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration garbage_collection which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-16 16:45:14 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration sonoff which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-16 16:45:14 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-16 16:45:14 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration tahoma which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-16 16:45:14 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration flipr which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-16 16:45:14 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration shelly which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Initialized DataUpdateCoordinator with 0:00:30 interval.
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.174 seconds
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticDomesticHotWaterProductionV2_CETHI_V4_IOComponent - WaterHeatingSystem - DomesticHotWaterProduction - io://0825-0315-xxxx/3345533#1)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:DHWCumulatedElectricalEnergyConsumptionIOSystemDeviceSensor - ElectricitySensor - CumulativeElectricPowerConsumptionSensor - io://0825-0315-xxxx/3345533#2)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneControlMainComponent - HeatingSystem - AtlanticPassAPCZoneControl - io://0825-0315-xxxx/960379#1)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://0825-0315-xxxx/960379#10)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://0825-0315-xxxx/960379#11)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://0825-0315-xxxx/960379#2)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://0825-0315-xxxx/960379#3)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://0825-0315-xxxx/960379#4)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://0825-0315-xxxx/960379#5)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://0825-0315-xxxx/960379#6)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://0825-0315-xxxx/960379#7)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://0825-0315-xxxx/960379#8)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://0825-0315-xxxx/960379#9)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Added gateway (0825-0315-xxxx - GatewayType.COZYTOUCH - 0)
2021-07-16 16:45:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.055 seconds
2021-07-16 16:46:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.107 seconds
2021-07-16 16:46:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.110 seconds
2021-07-16 16:47:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.152 seconds
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_AVAILABLE/None (device: io://0825-0315-xxxx/960379#1, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_AVAILABLE/None (device: io://0825-0315-xxxx/960379#10, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_AVAILABLE/None (device: io://0825-0315-xxxx/960379#11, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_AVAILABLE/None (device: io://0825-0315-xxxx/960379#2, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_AVAILABLE/None (device: io://0825-0315-xxxx/960379#3, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_AVAILABLE/None (device: io://0825-0315-xxxx/960379#4, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_AVAILABLE/None (device: io://0825-0315-xxxx/960379#5, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_AVAILABLE/None (device: io://0825-0315-xxxx/960379#6, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_AVAILABLE/None (device: io://0825-0315-xxxx/960379#7, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_AVAILABLE/None (device: io://0825-0315-xxxx/960379#8, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_AVAILABLE/None (device: io://0825-0315-xxxx/960379#9, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#1, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#2, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#3, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#4, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#5, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#6, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#7, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#8, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#9, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#10, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#11, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#3, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#7, state: None -> None)
2021-07-16 16:47:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.122 seconds
2021-07-16 16:48:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.122 seconds
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_REGISTERED/afca3fe3-3626-5439-25b9-caf2246d333b (device: None, state: None -> None)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca3fe3-3626-5439-25b9-caf2246d333b (device: None, state: ExecutionState.INITIALIZED -> ExecutionState.NOT_TRANSMITTED)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_STARTED/None (device: None, state: None -> None)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca3fe3-3626-5439-25b9-caf2246d333b (device: None, state: ExecutionState.NOT_TRANSMITTED -> ExecutionState.TRANSMITTED)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_ENDED/None (device: None, state: None -> None)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.037 seconds
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_REGISTERED/afca4038-3626-5439-25b9-caf2a6aa9656 (device: None, state: None -> None)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca4038-3626-5439-25b9-caf2a6aa9656 (device: None, state: ExecutionState.INITIALIZED -> ExecutionState.NOT_TRANSMITTED)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_STARTED/None (device: None, state: None -> None)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca4038-3626-5439-25b9-caf2a6aa9656 (device: None, state: ExecutionState.NOT_TRANSMITTED -> ExecutionState.TRANSMITTED)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_ENDED/None (device: None, state: None -> None)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.039 seconds
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_REGISTERED/afca4091-3626-5439-25b9-caf21b30f65d (device: None, state: None -> None)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca4091-3626-5439-25b9-caf21b30f65d (device: None, state: ExecutionState.INITIALIZED -> ExecutionState.NOT_TRANSMITTED)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_STARTED/None (device: None, state: None -> None)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca4091-3626-5439-25b9-caf21b30f65d (device: None, state: ExecutionState.NOT_TRANSMITTED -> ExecutionState.TRANSMITTED)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_ENDED/None (device: None, state: None -> None)
2021-07-16 16:48:25 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.037 seconds
2021-07-16 16:48:25 ERROR (MainThread) [custom_components.tahoma.tahoma_entity] No such command : refreshOperatingMode on device io://0825-0315-xxxx/960379#2 (io:AtlanticPassAPCZoneControlZoneComponent)
2021-07-16 16:48:26 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca3fe3-3626-5439-25b9-caf2246d333b (device: None, state: ExecutionState.TRANSMITTED -> ExecutionState.IN_PROGRESS)
2021-07-16 16:48:26 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.101 seconds
2021-07-16 16:48:27 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.033 seconds
2021-07-16 16:48:28 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca4038-3626-5439-25b9-caf2a6aa9656 (device: None, state: ExecutionState.TRANSMITTED -> ExecutionState.IN_PROGRESS)
2021-07-16 16:48:28 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca4038-3626-5439-25b9-caf2a6aa9656 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-07-16 16:48:28 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca4091-3626-5439-25b9-caf21b30f65d (device: None, state: ExecutionState.TRANSMITTED -> ExecutionState.IN_PROGRESS)
2021-07-16 16:48:28 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca4091-3626-5439-25b9-caf21b30f65d (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-07-16 16:48:28 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.038 seconds
2021-07-16 16:48:29 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.107 seconds
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_UNAVAILABLE/None (device: io://0825-0315-xxxx/960379#1, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_UNAVAILABLE/None (device: io://0825-0315-xxxx/960379#10, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_UNAVAILABLE/None (device: io://0825-0315-xxxx/960379#11, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_UNAVAILABLE/None (device: io://0825-0315-xxxx/960379#2, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_UNAVAILABLE/None (device: io://0825-0315-xxxx/960379#3, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_UNAVAILABLE/None (device: io://0825-0315-xxxx/960379#4, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_UNAVAILABLE/None (device: io://0825-0315-xxxx/960379#5, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_UNAVAILABLE/None (device: io://0825-0315-xxxx/960379#6, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_UNAVAILABLE/None (device: io://0825-0315-xxxx/960379#7, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_UNAVAILABLE/None (device: io://0825-0315-xxxx/960379#8, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_UNAVAILABLE/None (device: io://0825-0315-xxxx/960379#9, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#1, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#2, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#3, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#4, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#5, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#6, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#7, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#8, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#9, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#10, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://0825-0315-xxxx/960379#11, state: None -> None)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] CommandExecutionStateChangedEvent/afca3fe3-3626-5439-25b9-caf2246d333b (device: io://0825-0315-xxxx/960379#2, state: None -> ExecutionState.FAILED)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca3fe3-3626-5439-25b9-caf2246d333b (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.FAILED)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] CommandExecutionStateChangedEvent/afca4038-3626-5439-25b9-caf2a6aa9656 (device: io://0825-0315-xxxx/960379#2, state: None -> ExecutionState.FAILED)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca4038-3626-5439-25b9-caf2a6aa9656 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.FAILED)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] CommandExecutionStateChangedEvent/afca4091-3626-5439-25b9-caf21b30f65d (device: io://0825-0315-xxxx/960379#2, state: None -> ExecutionState.FAILED)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/afca4091-3626-5439-25b9-caf21b30f65d (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.FAILED)
2021-07-16 16:48:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.145 seconds
2021-07-16 16:49:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.111 seconds
2021-07-16 16:49:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.106 seconds
2021-07-16 16:50:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.109 seconds

Thanks for reporting, @Pol2Tls! It seems that the error is in your io:AtlanticPassAPCZoneControlZoneComponent. I will have a later look to see if we can change this.
2021-07-16 16:48:25 ERROR (MainThread) [custom_components.tahoma.tahoma_entity] No such command : refreshOperatingMode on device io://0825-0315-xxxx/960379#2 (io:AtlanticPassAPCZoneControlZoneComponent)
Device definition.
{
	"commands": [{
		"commandName": "advancedRefresh",
		"nparams": 1
	}, {
		"commandName": "refreshComfortCoolingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshComfortHeatingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshEcoCoolingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshEcoHeatingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshMaximumCoolingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshMaximumHeatingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshMinimumCoolingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshMinimumHeatingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "setActiveCoolingTimeProgram",
		"nparams": 1
	}, {
		"commandName": "setActiveHeatingTimeProgram",
		"nparams": 1
	}, {
		"commandName": "setComfortCoolingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setComfortHeatingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setCoolingOnOffState",
		"nparams": 1
	}, {
		"commandName": "setCoolingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setDerogationOnOffState",
		"nparams": 1
	}, {
		"commandName": "setEcoCoolingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setEcoHeatingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setHeatingOnOffState",
		"nparams": 1
	}, {
		"commandName": "setHeatingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setMaximumCoolingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setMaximumHeatingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setMinimumCoolingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setMinimumHeatingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setName",
		"nparams": 1
	}, {
		"commandName": "refreshPassAPCCoolingMode",
		"nparams": 0
	}, {
		"commandName": "refreshPassAPCCoolingProfile",
		"nparams": 0
	}, {
		"commandName": "refreshPassAPCHeatingMode",
		"nparams": 0
	}, {
		"commandName": "refreshPassAPCHeatingProfile",
		"nparams": 0
	}, {
		"commandName": "setPassAPCCoolingMode",
		"nparams": 1
	}, {
		"commandName": "setPassAPCHeatingMode",
		"nparams": 1
	}],
	"states": [{
		"type": "DataState",
		"qualifiedName": "core:ActiveCoolingTimeProgramState"
	}, {
		"type": "DataState",
		"qualifiedName": "core:ActiveHeatingTimeProgramState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:ComfortCoolingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:ComfortHeatingTargetTemperatureState"
	}, {
		"type": "DiscreteState",
		"values": ["off", "on"],
		"qualifiedName": "core:CoolingOnOffState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:CoolingTargetTemperatureState"
	}, {
		"type": "DiscreteState",
		"values": ["off", "on"],
		"qualifiedName": "core:DerogationOnOffState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:EcoCoolingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:EcoHeatingTargetTemperatureState"
	}, {
		"type": "DiscreteState",
		"values": ["off", "on"],
		"qualifiedName": "core:HeatingOnOffState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:HeatingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:MaximumCoolingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:MaximumHeatingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:MinimumCoolingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:MinimumHeatingTargetTemperatureState"
	}, {
		"type": "DataState",
		"qualifiedName": "core:NameState"
	}, {
		"type": "DiscreteState",
		"values": ["available", "unavailable"],
		"qualifiedName": "core:StatusState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:TargetTemperatureState"
	}, {
		"type": "DiscreteState",
		"values": ["cooling", "heating", "heatingAndCooling"],
		"qualifiedName": "core:ThermalConfigurationState"
	}, {
		"type": "DiscreteState",
		"values": ["available", "unavailable"],
		"qualifiedName": "io:CoolingManualModeAvailabilityState"
	}, {
		"type": "DiscreteState",
		"values": ["available", "unavailable"],
		"qualifiedName": "io:HeatingManualModeAvailabilityState"
	}, {
		"type": "DiscreteState",
		"values": ["absence", "auto", "comfort", "eco", "externalScheduling", "internalScheduling", "manu", "stop"],
		"qualifiedName": "io:PassAPCCoolingModeState"
	}, {
		"type": "DiscreteState",
		"values": ["absence", "comfort", "derogation", "eco", "externalSetpoint", "frostprotection", "manu", "stop"],
		"qualifiedName": "io:PassAPCCoolingProfileState"
	}, {
		"type": "DiscreteState",
		"values": ["absence", "auto", "comfort", "eco", "externalScheduling", "internalScheduling", "manu", "stop"],
		"qualifiedName": "io:PassAPCHeatingModeState"
	}, {
		"type": "DiscreteState",
		"values": ["absence", "comfort", "derogation", "eco", "externalSetpoint", "frostprotection", "manu", "stop"],
		"qualifiedName": "io:PassAPCHeatingProfileState"
	}],
	"dataProperties": [],
	"widgetName": "AtlanticPassAPCHeatingAndCoolingZone",
	"uiProfiles": ["StatefulCoolingThermostat", "CoolingThermostat", "StatefulDualThermostat", "DualThermostat", "ThermostatTargetReader"],
	"uiClass": "HeatingSystem",
	"uiClassifiers": ["emitter", "heatingSystem", "coolingSystem"],
	"qualifiedName": "io:AtlanticPassAPCZoneControlZoneComponent",
	"type": "ACTUATOR"
}

@Pol2Tls, could you give https://github.com/iMicknl/ha-tahoma/archive/refs/heads/fix/484.zip a try? Extract this file and place custom_components/tahoma in your custom_components folder.

Hi @iMicknl
There is no more error, but can't say it's working.
The behavior between the HA sensor and the Atlantic device is weird.
Below an example.
On HA, Climate "Salon" > set the temperature to 25.
2021-07-24 11:41:48 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://xxxxx/8647155#1, state: None -> None)
2021-07-24 11:41:48 DEBUG (MainThread) [custom_components.tahoma] Finished fetching device events data in 0.111 seconds
On HA, Climate "Salon" > click on the Fire icon (even it's in cool mode but I saw an other thread that tells, for now, it's strange but works).
2021-07-24 11:43:18 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_STARTED/None (device: None, state: None -> None)
2021-07-24 11:43:18 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_ENDED/None (device: None, state: None -> None)
2021-07-24 11:43:18 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_STARTED/None (device: None, state: None -> None)
2021-07-24 11:43:18 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_ENDED/None (device: None, state: None -> None)
2021-07-24 11:43:18 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://xxxxx/8647155#1, state: None -> None)
On the Atlantic app
First thing, before setting a target temperature, i must pass it from off to manual then set the temp
MANU
2021-07-24 11:50:19 INFO (MainThread) [custom_components.tahoma] 2021-07-24 11:48:07: setCoolingOnOffState executed via Atlantic iOS: 2.5.3 (217) on io://xxxxx/960379#2, with ['on'].
2021-07-24 11:50:19 INFO (MainThread) [custom_components.tahoma] 2021-07-24 11:48:07: setPassAPCCoolingMode executed via Atlantic iOS: 2.5.3 (217) on io://xxxxx/960379#2, with ['manu'].
25
2021-07-24 11:50:19 INFO (MainThread) [custom_components.tahoma] 2021-07-24 11:50:02: setCoolingTargetTemperature executed via Atlantic iOS: 2.5.3 (217) on io://xxxxx/960379#2, with [25].
2021-07-24 11:50:19 INFO (MainThread) [custom_components.tahoma] 2021-07-24 11:49:51: refreshTargetTemperature executed via Atlantic iOS: 2.5.3 (217) on io://xxxxx/960379#2, with [].
2021-07-24 11:50:19 INFO (MainThread) [custom_components.tahoma] 2021-07-24 11:49:51: refreshPassAPCCoolingProfile executed via Atlantic iOS: 2.5.3 (217) on io://xxxxx/960379#2, with [].
But climate sensor always show "Off" and target temperature "30" ?

Sorry for the late reply! @Pol2Tls could you perhaps create a new issue around the features you find missing / non functional for your device? For now the fix mentioned in this issue is in master and will go with the upcoming release.
Currently we only added limited support for your device, since it is very complex and also hard to develop when you don't physically own the device..


No .NET SDK Found (but installed)

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

VS Code Version: latest version
OS Version: MacOS 13...

Steps to Reproduce:

Open 2 Unity projects
Open 1 script in project A
Open 1 script in project B
Project B vs code page gives a warning that it couldn't find a .NET SDK.

Problem: When you open 2 Unity projects, and open 1 script in each project. The last scripts gives a warning that vs code couldn't find a .NET SDK.

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!


Add back the clear search button

Show the clear-search-button when there is search text
Hide the clear-tag-search-button when the tag-search is empty

Thank you!


some modification

can this work out? just wanted to test out with this library, feel free to correct me if I'm wrong

This code is only ever executed on PHP Versions < 5.5. That's versions that are EOL for over 8 years. So changes in this library are highly unlikely if it's not security related.
The random_bytes function used in your Change was introduced in PHP 7.0. So it's not available in this polyfill.


OpenID support

Describe the enhancement you'd like
Add support for OpenID connect
Describe why this will benefit the LibrePhotos
Improved connectivity with well-established authentication systems encourages a wider user base.
Additional context
One of the major barriers to self/community hosting is encouraging users to use the services you host. One of the biggest barriers to this is multiple logins for different services. Implementing SSO removes this barrier. For the individual user SSO removes having yet another account to manage.
Apologies if this has been requested before. I searched but found nothing.

We mostly rely on JWT authentication and not session based authentication. If you implement this, make sure that django-rest-auth generates proper JWT tokens after logging in with Django-All-Auth.

Yeah that makes sense.


Frequent "Too many queries in the last time." error

Hi, and first off, since I've finally registered, I just wanna say thank you for creating this great script. I have been using it for quite a while now, and it has saved me a whole bunch of time.
So, the problem I came upon is that during the regular download process, after successfully going through around 2-30 profiles, the "Too many queries in the last time." error frequently pops up, saying the script has to wait for ~10 or ~470 seconds, then it resumes normally for another 2-30 profiles, the error pops up again and the cycle continues, slowing down the whole thing by a lot.
I'd like to note that no other instances of Instaloader are launched at the same time, nor is Instagram used on any other device on the same profile.
Another thing to note is that this problem seems to only have appeared after I installed the 4.0 update, so it's most likely related to some changes to the limit of how many API requests can be made in a certain time window.
A screenshot of the error is attached below, with the profile names blurred and the errors highlighted in yellow for clarity.

Even with fast update, it seems to re-query/download all posts to update the json file

Hm, weird. --fast-update doesn't anything like that for me right now, works fine as usual. Although I do think I remember it giving me the 'too many queries' errors when downloading a new profile with a lot of pictures. I reckon it has smth to do with downloading json files, which the script never did before, and the API request limit not yet being adjusted for it.
I'll try downloading a random profile with and without logging into my profile to see if the errors start popping up then.

I can confirm that instaloader 4.0 is way slower than any other version before. In my logfiles, the warning about too many requests appears since the upgrade.
I run instaloader every 2 hours via cron. By monitoring htop I saw that the two instaloder processes runs concurrently which means the first instaloader instance wasn't finished while the second started.
Before instaloder 4, one round trip time was about 45 minutes, since instaloder 4 more than 2h 30 minutes.
example call: instaloader --quiet --no-metadata-json --no-compress-json --sessionfile ../session --login=... --password=... --stories --fast-update dir -AxD | shuf

For those affected by the here-reported problems with Instaloader being slow when downloading stories of many profiles since the version 4.0 update:
Commit a359a66 changes the algorithm for downloading profiles, being more efficient regarding API requests for obtaining story metadata. You may try it with:
pip3 install --upgrade git+https://github.com/instaloader/instaloader@issue_112_fix

The commit summary:
- With --stories and a list of profiles, Instaloader now tries to use a single
  query to get the story metadata

- With @<profile>, Instaloader now reutilizes the profile metadata returned by
  get_followees() method

- Use check_profile_id to obtain profile from username when resolving
  @<profile> target

- Catch KeyError in Profile._obtain_metadata() and wrap it into a
  ProfileNotExistsException to invoke anonymous-retry mechanism, since this is
  the behavior when attempting to download profiles that have blocked viewer

We do not immediately merge this into master and release a new version, since it is a heavy change that needs more testing, and the current Instaloader version works.

Some further remarks regarding what has been mentioned here:

Too many queries in the last time is not an error. It is a notice that the rate limit has almost been reached, according to Instaloader's own rate accounting mechanism. We regularly adjust this mechanism to match Instagram's current rate limiting.
If possible, use :stories target rather than --stories with all your followees. :stories uses fewer API requests.
There were no changes to the --fast-update logic with the v4 update. I think it is actually still the same as in version 1.0 two years ago. For each target, it aborts downloading once the first already-saved picture is encountered. It does NOT update the metadata files of the remaining posts.
The saving of JSON files does not have any effect on the requests that are made to Instagram. Instaloader now just saves by default the JSON metadata that it gets from Instagram during its operation. In case these files are undesired, one could use --no-metadata-json or simply delete these files.

Best regards
Alex

We do not say thank you enough
for all the work that you and your friends have put in. THANK YOU! and happy may the fourth be with you
Matthieu Bonenfant
mmathab<EMAIL_ADDRESS>On May 4, 2018, at 4:44 PM, Alexander Graf <notifications<EMAIL_ADDRESS>wrote:
For those affected by the here-reported problems with Instaloader being slow when downloading stories of many profiles since the version 4.0 update:
Commit a359a66https://github.com/instaloader/instaloader/commit/a359a667d39b71414cd790f495ac2eb825aec0f4 changes the algorithm for downloading profiles, being more efficient regarding API requests for obtaining story metadata. You may try it with:
pip3 install --upgrade git+https://github.com/instaloader/instaloader@issue_112_fix
The commit summary:

With --stories and a list of profiles, Instaloader now tries to use a single
query to get the story metadata

With @, Instaloader now reutilizes the profile metadata returned by
get_followees() method

Use check_profile_id to obtain profile from username when resolving
@ target

Catch KeyError in Profile._obtain_metadata() and wrap it into a
ProfileNotExistsException to invoke anonymous-retry mechanism, since this is
the behavior when attempting to download profiles that have blocked viewer

We do not immediately merge this into master and release a new version, since it is a heavy change that needs more testing, and the current Instaloader version works.

Some further remarks regarding what has been mentioned here:

Too many queries in the last time is not an error. It is a notice that the rate limit has almost been reached, according to Instaloader's own rate accounting mechanism. We regularly adjust this mechanism to match Instagram's current rate limiting.
If possible, use :stories target rather than --stories with all your followees. :stories uses fewer API requests.
There were no changes to the --fast-update logic with the v4 update. I think it is actually still the same as in version 1.0 two years ago. For each target, it aborts downloading once the first already-saved picture is encountered. It does NOT update the metadata files of the remaining posts.
The saving of JSON files does not have any effect on the requests that are made to Instagram. Instaloader now just saves by default the JSON metadata that it gets from Instagram during its operation. In case these files are undesired, one could use --no-metadata-json or simply delete these files.

Best regards
Alex
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/instaloader/instaloader/issues/112#issuecomment-386729587, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEH998y8qDv67LOvAHD73T-Vu0fqgks_ks5tvL22gaJpZM4TylzS.

@aandergr Many thanks for your effort to help! This is awesome!
Unfortunately instaloader freezes after login with the fix.
Loaded session from ../session.
Logged in as <username>.

For version 4.0.1 we implemented a check of whether a profile actually has stories prior the get_stories() request. This saves time costly GraphQL queries in the likely case that a profile doesn't have any story, and promises to be a more reliable fix than the one proposed in issue_112_fix branch.


5x sample CO2

Researching best practices to get an accurate sample from the SCD40, it appears that reading the sensor multiple times and taking the last sample as actual allows the sensor to calibrate properly, versus a single read from a "cold" sensor.

added a config.h define to control the number of times the SCD40 is read before environment data is stored


Windows taskbar icons remain for RD instances that are no longer running

See screenshot:

This should only happen if it crashes instead of exiting normally. Note that should doesn't always mean it happens ;)  In that case, generally mouse-overing the icons will make them go away (because Explorer realizes it can't send messages to the window to handle mouse movement).

generally mouse-overing the icons will make them go away

Not happening for me; they still seem to be functional: I can expand the menu and see e.g. the current kubernetes context:

It turns out the app instances are still running in the background, they just don't seem to have any GUI presence anymore beyond the (hidden) notification icons; the normal app icons are gone:

I wonder if this is related to me clicking on the X close icon on the top right corner instead of picking File | Exit from the menu (which doesn't seem to have a keyboard shortcut, but maybe that is intentional?).

It turns out that I have about 15 of these processes on my machine, and I can't seem to terminate them with End task.
Also any new RD I start now cannot start kubernetes anymore. I guess I could stop the k3s distro to kill the currently running instance, but this is a situation a user should never get into.

I can't seem to terminate them with End task.

Well, it turns out if you are very patient, and willing to terminate task multiple times, you eventually get all tasks cleaned up, and then you can hover over the notification icons, and they too will vanish...

Right; on Windows, closing the Window does not terminate Rancher Desktop. (Actually, it doesn't on Mac either, though it does leave the dock icon.)
You'd need to quit by right-clicking and selecting Exit, though I think we may have issues where failing to stop k3s (possibly because we hit other errors and it never started) will prevent exit.

I'm closing this issue because the multiple notification icons are covered by #238, and the general UX of closing the window vs. closing the app should be discussed in #243.
The is still a possibility that a notification icon remains in the overflow area when RD itself has terminated abnormally, but there isn't really anything we can about it, and it is self-healing once the user hovers the mouse pointer over the orphaned icon.


keyword bug about ghost

Hi, I used Ghost for a while. And i found a keyword bug about Ghost.That is $`;We use this word in JavaScript. But i cant render markdown if i insert this keyword twice in my article. eg:

2、变量名称是 $&: 替换成匹配到的子串.

const string2 = 'abc123abc';
console.log( string2.replace(/\w+?(^\d+)\w+?/g, '$&') ); //abc123abc

3、变量名称是 $`: 替换成当前匹配子串左边的内容.

const string3 = 'abc123abc';
console.log( string3.replace(/(\d+)/g, '$`') ); //abcabcabc

4、变量名称是 $`: 替换成当前匹配子串右边的内容.

const string4 = 'abc123abcd';
console.log( string4.replace(/(\d+)/g, "$'") ); //abcabcabcd

markdown cant work above them.thks!

Hi @Army-U, sorry to hear you're having trouble. I'm afraid I'm not able to reproduce the issue you describe. The examples you've pasted work the same in Ghost as they do here on GitHub:

Duplicating the snippets with and without fenced code blocks (triple backticks) doesn't reveal an issue:

If you do need to include 2 backticks in plaintext, you can escape them using backticks:
.
If I've misunderstood, please reply with a screenshot showing the issue and I'll reopen this :+1:


Introducing :disguise and :incognito

A long-overdue PR with some inspiration from Kronos stuff. Brought to you from NullLand development.
I had originally named :incognito as :vanish but decided the former to be more suitable.

mmmm good stuff

I approve of Expertcoderz's Existence


python3Packages.django-compressor: 4.3.1 -> 4.4

Description of changes
Changes https://github.com/django-compressor/django-compressor/compare/4.3.1...4.4
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 240917 run on x86_64-linux 1

16 packages built:

healthchecks
mailman-web
mailman-web.dist
python310Packages.django-compressor
python310Packages.django-compressor.dist
python310Packages.django-libsass
python310Packages.django-libsass.dist
python310Packages.django-mailman3
python310Packages.django-mailman3.dist
python311Packages.django-compressor
python311Packages.django-compressor.dist
python311Packages.django-libsass
python311Packages.django-libsass.dist
python311Packages.django-mailman3
python311Packages.django-mailman3.dist
seahub


FeignClient: How to use Pageable?

I have been depressed for a few days.
I am build  a MicroService who support Spring Data Pageable functionnality.
like this:

@PostMapping("search")
@Override
public Result<Page> getList(@RequestBody CategoryDTO tDto, Pageable pageable) {
return Result.<Page>builder().data(service.getList(tDto, pageable)).build();
}

so i request(POST) with body like :

POST /search?page=1&size=20&sort=id,desc
{
"test":"aaa"
}

works perfect!
and now i use @FeignClient to request like this:

@PostMapping(value = "search")
Result<Page> getList(@RequestBody CategoryDTO t, Pageable pageable);

it throws exception :Method has too many Body parameters
if i request like this:

@PostMapping(value = "page")
Result<Page> getList(@RequestBody CategoryDTO t,@RequestParam("pageable") Pageable pageable);

but it did not work. so  how can i use @FeignClient to do pageable request with customer body at the same time??

I solve this issue
https://medium.com/backend-habit/using-pagination-on-open-feign-4fc500747b70


Added Jackson support

Signed-off-by: Laird Nelson<EMAIL_ADDRESS>This is a reworking of #305.

Just fix the checkstyle ;)

Oh good grief; yep; duh.

@tomas-langer Good to go?

Yes. Sorry, I meant LGTM once you make the build green ;)

Will repair build again; stand by

Fixed via https://github.com/oracle/helidon/pull/387


How to implement custom coprocessor endpoints?

Question
Hello, I'm building a graph database based on tikv, the existing coprocessor implementation is not suitable for graph database, so I want to know if it is possiable to implement custom pluggable coprocessor endpoints,thx.

Yes, you can build and use your own query engine but need to modify tikv a bit. We don't have a plugin mechanism yet.
In the coprocessor endpoint, you can match your own request type in parse_request and build your own RequestHandler.
The existing request handlers should be a good reference. You can put your own query engine inside of tikv crate like checksum.rs. Or if you'd like to make it a separate crate, refer to dag and tidb_query crate.


Prevent newlines from being stripped out of RSA key upload.

The form was using the password field type in order to
cause the rsa key to be filtered out of the rails logs like
a password normally would be, but that input type was
pulling out newlines from the input. This fixes that problem,
but the file won't be filtered out of the logs.
Fixes #8651

Closing/reopening since #8684 was merged to fix master

@aufi please verify ... Thx, Dan

Does not work for me.
Calling auth_key on the authentication object where key is stored now returns
-----BEGIN RSA PRIVATE KEY-----\n\nMIIEowIBAAKCAQEApncIm4fpkQtCp1cvRdZs2hHgk0ZuQUjEXS0TWMM0pRM4UPJW\n\nhAAuHoD...

note double \ns

With out this patch (on master) I got
-----BEGIN RSA PRIVATE KEY-----MIIEowIBAAKCAQEApncIm4fpkQtCp1cvRdZs2hHgk0ZuQUjEXS0TWMM0pRM4UPJWhAAuHoD...

note no \ns

Before #8173 I got
-----BEGIN RSA PRIVATE KEY-----\nMIIEowIBAAKCAQEApncIm4fpkQtCp1cvRdZs2hHgk0ZuQUjEXS0TWMM0pRM4UPJW\nhAAuHoD

note single \ns

Only the last version works (with groups of single \ns).
Others got me
SSH connection failed for [<IP_ADDRESS>] with [ArgumentError: Could not parse PKey: bad end line]

I'm having a hard time understanding what is happening here. The javascript console shows that the string contains a single \n, by the time it gets into build_credentials the \n has been replaced by \r\n, and when the object gets saved \r\n winds up in the database as \n\n for some reason that isn't clear to me.

@himdel @AparnaKarve @skateman any ideas for https://github.com/ManageIQ/manageiq/pull/8673#issuecomment-219602844?

@mansam What happens when you upload a ssh_keypair file that already has a trailing newline? Does that get truncated when it's passed to the backend?

Yes, at least with the most recent commit in this branch, the trailing newline is truncated.
The last few lines of a file I uploaded, EOL depicted with $:
0RgiwC5MUPrI8+NiJenxCxuG0jwTQDdEisFkXXA2QG68kwFRLPWDCKH3epWFgqZF$
uBttTiFyzkYcP+CefU/tVCzkbUboxW9bcGI97P9eTbfV/0ghoIOVtfXOIXw8smE0$
wudbZ6VWKHcTKwVhvBwxlAHBYll/4lk7em5NmKjsxH6TsLo2nUmD/+PC7Z+NvWxE$
Hj0A0GQEy0sb9gaehe8mzCJu3Ev9gaYSWfKLnQ+vl2kXQalT3gF72kOm18s=$
-----END RSA PRIVATE KEY-----$
$

Here's how it is in the DB:
0RgiwC5MUPrI8+NiJenxCxuG0jwTQDdEisFkXXA2QG68kwFRLPWDCKH3epWFgqZF$
uBttTiFyzkYcP+CefU/tVCzkbUboxW9bcGI97P9eTbfV/0ghoIOVtfXOIXw8smE0$
wudbZ6VWKHcTKwVhvBwxlAHBYll/4lk7em5NmKjsxH6TsLo2nUmD/+PC7Z+NvWxE$
Hj0A0GQEy0sb9gaehe8mzCJu3Ev9gaYSWfKLnQ+vl2kXQalT3gF72kOm18s=$
$
$
-----END RSA PRIVATE KEY-----$

I don't understand where the two newlines are coming from between the end of the key and the delimiter.

@AparnaKarve Figured out what the issue was, there was some code that was processing the key to fix some issues with the way the old password input worked before it got changed to a file upload. Now that we have that file upload it was just corrupting the key by inserting additional newlines, so I've removed it.

Nice @mansam
https://github.com/ManageIQ/manageiq/pull/8673/files#diff-f9cace1fe4fdcec66f962b23f2110fd6L139 -- Is that what you're referring to in authentication_mixin.rb?

That whole block, but especially that line.

@mansam works for me - I can now upload a key and it works :-)
But maybe just a note - I think that text area looks ugly right now - before I have seen text field with dots - that looked nice imho. But I am not a GUI guy... just ranting...

@petrblaho I can't replace it with a text field without causing issues, but I can (and just did) add a parameter to the textarea so it will only be one row in height :)

@mansam that looks better imho. Thanks.
And of course it works too :-)


Remove the inserted command .play after it's bin added

I'm new to your bot, but already loving it so much! I do have a small request.
If i would play a song/vid. It nicely says which song is added. But i don't like that the chat stay's filled with the command i putted in (aka .play  ).
In the picture you can see what i mean with 'spammy'.

Is it an idea to make it optional that the bot removes the .play command a user inserted?
Love your bot dude, you have by far the best looking music bot (that also performs twice as well compared to others).

This is already on the planned features list


Error when loading PDF that uses system fonts

Test file: https://dl.dropboxusercontent.com/u/16283445/PORTRAIT.pdf
File was produced by Muhimbi PDF converter.
Main text (that uses embedded Tahoma font) renders ok; it is the trial message on top of the file that causes the error. After some debugging, I've found that this message references system Helvetica font, and somehow glyphs for it are missing at the time of error.
Error log:
Error: Requesting object that isn't resolved yet Helvetica_path_T pdf.js:205
    at error (http://[skipped]/pdfjs/pdf.js:207:15)
    at Object.PDFObjects_get [as get] (http://[skipped]/pdfjs/pdf.js:4640:9)
    at Object.FontFace.getPathGenerator (http://[skipped]/pdfjs/pdf.js:7675:23)
    at Object.CanvasGraphics.paintChar (http://[skipped]/pdfjs/pdf.js:6105:26)
    at Object.CanvasGraphics_showText [as showText] (http://[skipped]/pdfjs/pdf.js:6291:18)
    at Object.CanvasGraphics_nextLineShowText [as nextLineShowText] (http://[skipped]/pdfjs/pdf.js:6381:12)
    at Object.CanvasGraphics_executeOperatorList [as executeOperatorList] (http://[skipped]/pdfjs/pdf.js:5600:22)
    at Object.InternalRenderTask__next [as _next] (http://[skipped]/pdfjs/pdf.js:4807:39)
    at Object.pdfViewcContinueCallback [as continueCallback] (http://[skipped]/pdfjs/viewer.js:4261:9)

Can there be a solution like one of these:
1 - option to allow use some default font or some font what already been used for exact file
2 - option to allow skip rendering of this item
this can help to continue work with pdf file if some font are absent, and output only as warning, not as breaking error.
What do you think?

We prefer the first option, however we don't embed any fonts yet and rely on system to contain those for some functions. We can certainly ignore, once we find how to properly stub it (For these font, we can generate empty letters outlines when requested)

At least open the possibility to .catch(...) this error instead of just stopping everything until you can find a better solution. Unfortunately this problem breaks functionality in our live environment which is... bad.

Is there any workaround available? Or some sort of error catching mechanism suggested by @xwcg ?

A dupe was filed here: https://bugzilla.mozilla.org/show_bug.cgi?id=1463728

Hello everyone,
I got the same error.
May I know if there is any temporary work-around for this issue before the formal fix?

Any update on this?, Its from 2014 and still not solved

@diego-lipinski-de-castro FYI, that #9809 merge fixed this if you pass in ignoreErrors: true into the getDocument function. If you use the npm pdfjs-dist it's not updated yet. I just built from source and PDFs that used to complaint about fonts now process correctly with canvas output. Everything seems fine.

@sirisian thanks for your update. Looking forward to the release

@sirisian do you know when will be the update for npm pdfjs-dist? and if there is a workaround for npm?
Thanks

Hi, I also encounter this error. Is there a way to substitute font that aren't present on the system with a default one?

with pdfjs-dist": "^2.2.2 set disableFontFace: false fixed this issue on me.

pdfjs.getDocument(     {        url: pdfUrl,        disableFontFace: false,     }

In my opinion, whenever pdf.js fails to load text in a particular font, it should load the same text using a substitute font it could show, rather than stop rendering the page.  This was the behavior in Firefox 61 and earlier when the option "Allow pages to choose their own fonts, instead of your selections above" is disabled.  In my opinion, showing text in a substitute font is better than showing nothing at all.

with pdfjs-dist": "^2.2.2 set disableFontFace: false fixed this issue on me.

pdfjs.getDocument(     {        url: pdfUrl,        disableFontFace: false,     }

This one solved my issue, I'm using pdfjs-dist ^2.0.943
Thank you

I'm working on a project where IE 11 is a requirement and the security settings (managed by the IT team) do not allow custom fonts to be downloaded. This was resulting in a PDF rendering was mostly blank when rendering, only showing a few headlines and italic characters.
setting disableFontFace: true caused the inverse in IE 11 (and all other browsers actually). Most fonts then render but it has introduced a litany errors such that look like this:
Warning: getPathGenerator - ignoring character: "Error: Requesting object that isn't resolved yet Times_path_i.".

The errors all indicate different characters in the Times_path_* portion of the message. The document loads most content but headlines, italics, and other variations are visually missing (although the empty text can be selected due to the transparent text layer on top)
So, I'm stuck between having full font rendering in all browsers except IE 11 (due to the administrator enforced security setting regarding fonts) or semi-broken font rendering everywhere due to trying to implement a fix for IE 11.
Any suggestions?

any news on that ?

hi team,
have any updates ?

This is a major impact to us.  Why is the workaround to set disableFontFace=false?  My understanding is that with disableFontFace=true, it doesn't matter what embedded fonts there are in the pdf.  Is that incorrect?

any news on that ?

6 years ago @AllSeeingEye was having a problem and today this library has 594 unresolved issues. Nobody gives a f*** about this bug or what ? A bug that is for me a no-go, will need to look for other libs like pdf-lib maybe.

Good day everyone!
Faced some similar issues while trying to solve the text layer render issue with disableFontFace params.
On disableFontFace: false some documents looks like this:

While on disableFontFace: true the previous document render well, there is an issue with a different document:

All these cells were not empty.
Some docs render well in one way, some - in other way.
How should I act?

I'm having a similar issue as @Hatgor
Is there a fix or somehting that can be done in order to get this right? The above solutions don't work. :|

I'm having the exact same issue.  Trying to run it in a lambda on Node12, which runs amazonlinux2 - meaning no fonts installed by default.  It would be REALLY nice if we could embed the standard 14 fonts into pdfjs by default, or expose an API for loading them rather than relying on them being installed in the base system.  Thus far my efforts to install the fonts to the system have been... less than successful.
At this point I'm thinking I might pre-process every PDF with another library, like pdf-lib, explicitly to embed the 14 standard fonts, THEN pass it to this library for rendering.  A bit excessive and annoying, but if it resolves the problem....
After tinkering for literal hours with amazonlinux2 to install fonts, I CAN get the non-included fonts to render by setting disableFontFace to false explicitly, but then the embedded fonts from the PDF fail with the same symbol seen in @Hatgor 's comment.

OK, so far no dice in pre-processing PDFs to embed fonts.  Is there, perhaps, a way to inject a font that's not embedded in the PDF?  I can host the necessary .ttf(s) somewhere else, but I'm not seeing anything in the API to load an arbitrary font.

@Snuffleupagus Is there a fix for this https://github.com/mozilla/pdf.js/issues/4244#issuecomment-630379377 ? I just spent a whole day researching about this but could not find anything...

@Snipeye Did you find a way to inject fonts?

@Snipeye Did you find a fix for this https://github.com/mozilla/pdf.js/issues/4244#issuecomment-636934578 ?   A lot of people are running into this bug and a lot. of issues are being closed stating that they are a duplicate of this issue .  If someone has a fix please do post it here.

There is some code in #12711 that falls back to disableFontFace: false behaviour when a font can't be loaded to at least render the text. It seems to work in the scenarios I needed it for, but probably still needs more work. You may want to apply this as a patch in your applications if you find it works in your scenarios.

This one bug renders the whole library useless. We can't depend on a library that cannot open PDFs while every major browser and app can. There is no workaround, and the lack of commitment for a fix is frustrating.

This one bug renders the whole library useless.

That's not really true since the vast majority of PDF files simply embed their fonts (or a subset), in which case there is no problem at all. In fact, that's highly recommended everywhere, also in the PDF specification, since it ensures that PDF files render consistently across viewers and platforms. By not embedding (a subset of the) fonts you simply cannot assume that the file will look correctly in all viewers, so that's taking a risk.

the lack of commitment for a fix is frustrating

You have to realize that this is not a trivial issue, and in the meantime work has been done to investigate how we can resolve this. There is a pull request just above (#12726) that aims to provide an implementation for this. While not completely done yet, there is effort being put into this.
If you think this issue deserves more attention, use the thumbs up emoji on the original comment so it shows up higher in the priority list (see https://github.com/mozilla/pdf.js/issues?q=is%3Aissue+sort%3Areactions-%2B1-desc+is%3Aclosed for issues that have been solved that also had a high number of thumbs up), but please keep comments constructive at all times.

Same problem here. We use PDF.js to display PDFs on mobile devices in WebView. And on some devices with Android 5, 6 or 7 it doesn't work. It displays some documents with images and scanned documents just ok, but when we want to display any PDF exported from Word, it misses every other letter. It's really bad that this issue is here for 7 years...

I see this is closed, but what's the solution? I recently updated my pdfjs-dist dependency and a file that used to work just fine now throws the following:
Warning: fetchStandardFontData: failed to fetch file "FoxitSans.pfb" with "UnknownErrorException: The standard font "baseUrl" parameter must be specified, ensure that the "standardFontDataUrl" API parameter is provided.".

For anyone else getting an error during fetchStandardFontData when using pdfjs-dist in node / not web:
Warning: fetchStandardFontData: failed to fetch file "FoxitSans.pfb" with "UnknownErrorException:  The standard font "baseUrl" parameter must be specified, ensure that the "standardFontDataUrl" API parameter is provided.".
pdfjs-dist has a folder standard_ fonts but for some reason, it doesn't default to loading the fonts from there when used with node.
You have to set the standardFontDataUrl during getDocument:
  const loadingTask = getDocument({
    data: buffer, // or src
    standardFontDataUrl: join(__dirname, '../../../../node_modules/pdfjs-dist/standard_fonts/'),
  });

You can use a relative path, too, but note that it must be relative to the script entry directory. I wrap getDocument for use in node, so I don't have to set standardFontDataUrl all the time.

Whats wrong with Mozilla Developers? PDFs works fine with FireFox 52.9.0 ESR but cause you Update all the time Firefox its unsupported now by some Webpages. People forced to Update, most Addons that make working with Firefox possible are incompatible now or having problems, like the Settings with Noscript. In the newer Versions(about 68-78) almost no PDF works if "gfx.downloadable_fonts.enabled" is false.
All Webfonts looks like sh** without Antiantialiasing, i dont set it to true. With Firefox 52.9.0 still displayed correct, it can load and use the Windows System Fonts. A System Font is not
a downloaded Font!!! Cause latest FF Versions(about 91) and future Versions works only in slowmotion/sluggish it makes not much sense to post that Bug or is it posible to exchange the PDF module only(if you fix the bug in some years)?

I try do this:
const loadingTask = getDocument({     data: buffer, // or src      standardFontDataUrl: join(__dirname, '../../../../node_modules/pdfjs-dist/standard_fonts/'),   });
But then i get either get
TS2769: No overload matches this call.   Overload 1 of 3, '(url: string, pdfDataRangeTransport?: PDFDataRangeTransport, passwordCallback?: (fn: (password: string) => void, reason: string) => string, progressCallback?: (progressData: PDFProgressData) => void): PDFLoadingTask<...>', gave the following error.     Argument of type '{ data: Buffer; standardFontDataUrl: string; }' is not assignable to parameter of type 'string'.   Overload 2 of 3, '(data: Uint8Array | ArrayBufferView | ArrayBuffer, pdfDataRangeTransport?: PDFDataRangeTransport, passwordCallback?: (fn: (password: string) => void, reason: string) => string, progressCallback?: (progressData: PDFProgressData) => void): PDFLoadingTask<...>', gave the following error.     Argument of type '{ data: Buffer; standardFontDataUrl: string; }' is not assignable to parameter of type 'Uint8Array | ArrayBufferView | ArrayBuffer'.       Object literal may only specify known properties, and 'data' does not exist in type 'Uint8Array | ArrayBufferView | ArrayBuffer'.   Overload 3 of 3, '(source: PDFSource, pdfDataRangeTransport?: PDFDataRangeTransport, passwordCallback?: (fn: (password: string) => void, reason: string) => string, progressCallback?: (progressData: PDFProgressData) => void): PDFLoadingTask<...>', gave the following error.     Argument of type '{ data: Buffer; standardFontDataUrl: string; }' is not assignable to parameter of type 'PDFSource'.       Object literal may only specify known properties, and 'standardFontDataUrl' does not exist in type 'PDFSource'.
Or the it does not do anything. Is there a fix for this?

Coming back to this:
Both solutions from @Narretz and @nickmanning214 are working equally great for me!

I was able to disable the warning with: getDocument({ url: pdfPath, useSystemFonts: true });
But now I'm thinking maybe I should embed the font directly so that it will be consistent on all machines.

THIS IS what iam llong for in past week


Removed county field

Royal Mail states county is not required for delivering mail. The Royal Mail address finder provides a correct address to customers and this does not contain county https://www.royalmail.com/find-a-postcode
Royal Mail states:

“There is no need to include a county name, your letters and parcels will reach your intended recipient without one.” https://personal.help.royalmail.com/app/answers/detail/a_id/81/~/how-to-address-your-mail-(clear-addressing)
“The county is not required as part of a correct postal address.” https://www.poweredbypaf.com/wp-content/uploads/2015/02/Latest-Programmers_guide_Edition-7-Version-6.pdf
“County data was removed from the core PAF files over ten years ago, has not been actively maintained and is not needed for delivery purposes” (dated 2017) https://www.poweredbypaf.com/wp-content/uploads/2018/09/BFPO-Data_-Factsheet.pdf

County has not been required for many years for larger towns, islands, and towns that gave their name to the county. https://en.wikipedia.org/wiki/Postal_counties_of_the_United_Kingdom#Special_post_towns
Some UK addresses do not have a county, such as BFPO addresses. If an interface asks the user to give a county, Royal Mail tells the user "probably the most logical solution is to duplicate the Town entry". This is what some people do for London, Birmingham, Bristol, etc.
County has multiple meanings:
When Royal Mail used county as part of addresses, each address could have three different entries against it:

Postal county. https://en.wikipedia.org/wiki/Postal_counties_of_the_United_Kingdom
Administrative county. https://en.wikipedia.org/wiki/Administrative_counties_of_England
Traditional or historical county. https://en.wikipedia.org/wiki/Historic_counties_of_England

There is a fourth meaning:

Ceremonial county. https://en.wikipedia.org/wiki/Ceremonial_counties_of_England

There are welsh equivalents of one or more of the above.
Databases frequently fail to manage counties correctly
For example Argos records Manchester as being in Lancashire (it isn’t).
Royal Mail does not encourage use of county as error mitigation
Postcode errors.
The postcode enables machine sorting. The rest of the address enables human delivery. If the postcode is absent or incorrect then it may affect the machine but not the human capability to deliver post without the county.
Combined errors.
I've heard people say county can be useful if all the following are true:

postcode is absent
AND two towns share a name, each of which will have an unambiguous correct postal town name
AND the user fails to use the correct postal town name
AND the delivery service chooses the wrong one of the two towns
AND the delivery service halts delivery rather than using street information to recover from the error

However, neither that scenario nor any other error has been mentioned by Royal Mail or by the PAF advisory board (who made the decision to delete counties from the PAF).
See also:

"Royal Mail set to delete counties from addresses" https://www.bbc.co.uk/news/uk-10825499
"What's the point of counties?" https://www.bbc.co.uk/news/magazine-10853705
"'Humberside' removed from Royal Mail address lists" https://www.bbc.co.uk/news/uk-england-humber-29440246

Approved, thanks @terrysimpson99!
I usually step back from reviewing code changes but it's clear to me that you're just removing the county text input in the 'Multiple text inputs' example.


Approval Needed for Next Step

Please comment "approve" to proceed with the third workflow.
Minimum Approvals: 1
Approval Words: approve, approved
Rejection Words: deny, denied, reject, rejected

approved

approved

approve

Approved by MdShimulMahmud.

approved

approved


Define webhook unit tests (37203)

Questions
Answers

Description?
Create webhook unit tests

Type?
refacto

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes 37203

How to test?
Unit tests

added a test for mentioned case


FindElement by LinkText is not working on non-latin text

I have a page like this:
тест

And code like
wd.FindElement(selenium.ByPartialLinkText, "тест")

will produce the no such element error. When using latin text everything is working as expected.
(Anonymous in bitbucket issue 12)

Playing a bit with this example, the Selenium server return 500 on the get element request with a huge Java stack trace. Here's the relevant part (which IMO points to an encoding problem).
            "localizedMessage": "Unable to locate element: {\"method\":\"partial link text\",\"selector\":\"\u00d1\u0082\u00d0\u00b5\u00d1\u0081\u00d1\u0082\"}\nBuild info: version: '2.41.0', revision: '3192d8a', time: '2014-03-27 17:17:32'\nSystem info: host: 'archie.bunker', ip: '<IP_ADDRESS>', os.name: 'Linux', os.arch: 'amd64', os.version: '3.14.4-1-ARCH', java.version: '1.7.0_55'\nDriver info: driver.version: unknown",

This was fixed at some point. I just committed a test that proves it.


fix: update invalid logs when DNS feature disabled

Ensure that when a DNS feature is disabled it is not logged as a DHCP feature.

@henworth Thank you very much for your contribution

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.022%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/types/features.go
0
3
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
681

Relevant Lines:
1116

💛  - Coveralls


Feature request: ability to pause and resume the slide show

Maybe this can already be done, but I haven't figured out how to do it.  I'd like to have a button underneath the slide show that's labeled "Pause" or "Resume" based on whether the slide show is in a currently paused state or not, and have the onPressed() handler call a "pause" or "resume" function.  You can't just set the autoPlayInterval to 0 -- the ImageSlideshow class has that set as final.
If you consider adding this feature, it might be nice to also accept a tap on the slide slow to pause or resume.

I created a fork of the current flutter_image_slideshow repository with a possible solution to pause / resume.  I'm not entirely happy with it though, it relies on a callback to check to see if the user has asked for the slideshow to be paused or resumed, and that callback has to be made repeatedly (after some experimentation, I decided 1/4 second was fast enough that users would perceive instantaneous response).
I don't like the idea of having to do continuous callbacks, but I wasn't able to come up with a better solution.

@abhlabs
Sorry for the late reply!
Do you want to control the "Pause" and "Resume" of the slideshow?
Actually you can use several feature like "goToPage" and "stopAutoPlay".
Please refer to this PR(#9 ).
Can't you use this feature?

Thanks, I missed seeing that in the changelog on pub.dev.  I see the "stopAutoPlay" -- which seems easy enough, but how do you resume?  Is it as simple as performing a "goToPage" with the next page in sequence?

Didn't see any way to resume, so I did a pull request to incorporate that feature.

Thanks for pull request👍
I'll review it!


BUG: modin-on-hdk have inconsistent types for dates with some pd.read_csv arguments

Modin version checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest released version of Modin.

[X] I have confirmed this bug exists on the main branch of Modin. (In order to do this you can follow this guide.)

Reproducible Example
import modin.config as cfg
cfg.IsExperimental.put(True)
cfg.Engine.put('Native')
cfg.StorageFormat.put('HDK')

import pandas as pd
import modin.pandas as mpd

keep_cols = ["pickup_datetime"]

def write(path, content):
    with open(path, 'w') as f:
        f.write(content)
HDK
data_2014 = """pickup_datetime,store_and_fwd_flag

2014-01-09 20:45:25,N
"""

data_2015 = """pickup_datetime
2015-01-15 19:05:39
"""

write('2014.csv', data_2014)
write('2015.csv', data_2015)

data_types_2014 = {"store_and_fwd_flag": "object"}

data_types_2015 = {}

def clean(ddf):
    to_drop = ddf.columns.difference(keep_cols)
    if not to_drop.empty:
        ddf = ddf.drop(columns=to_drop)
    return ddf

def load(path, dtypes, pd):
    df = clean(pd.read_csv(path, parse_dates=['pickup_datetime'], dtype=dtypes))
    df.shape
    print('\n\n\nPandas API response\n', df.dtypes)
    try:
        print('\n\n\nHDK hidden API resonse:')
        print(df._query_compiler._modin_frame._partitions[0][0].get())
    except (TypeError, AttributeError):
        print('Problem: couldnt locate type data')
    return df

def reproduce(data_types_2014, data_types_2015, pd):
    df1 = load('2014.csv', data_types_2014, pd)
    df2 = load('2015.csv', data_types_2015, pd)

    print('\n\n\nResult shape is:')
    print(pd.concat([df1, df2]).shape)
    print('*****No error found*****')

for d1, d2 in ((None, None), (data_types_2014, data_types_2015)):
    print('\n\n\n**********dtype is None: ', d1 is None)
    print('\n\n\n**********Pandas')
    reproduce(d1, d2, pd)
    print('\n\n\n**********Modin')
    reproduce(d1, d2, mpd)

Issue Description
Background:
I am using modin on hdk on a real dataset.  The data loading consists of loading many csvs of about 2GB each. After the load I perform concatenation of cleaned data. During concatenation I get an error. The error is not present on Pandas, it is not present with modin on ray, it is only present with modin on HDK.
Reproduction example
The issue only appears with the following conditions:

I am reading from a file (hence I write my data to a file in an example)
I provide dtype argument with "object" dtype to one pd.read_csv but not the other (hence I show that without that argument everything is fine).

I guess that the problem could be that one of the read csv defaults to pandas implementation (you can see that from a log) and the other is not, later they end up with different data types. I think that's a bug, because behavior right now is inconsistent between (pandas or modin on ray) vs (modin on HDK) and in the end with that defaulting we end up with inconsistent data types. Another issue is that pd.dtype is different from the internal information (provided in the log)
Expected Behavior
To get consistent behavior between pandas and modin on hdk
Error Logs
Here is a stdout of a provided code sample

**********dtype is None:  True

**********Pandas

Pandas API response
 pickup_datetime    datetime64[ns]
dtype: object

HDK hidden API resonse:
Problem: couldnt locate type data

Pandas API response
 pickup_datetime    datetime64[ns]
dtype: object

HDK hidden API resonse:
Problem: couldnt locate type data

Result shape is:
(2, 1)
*****No error found*****

**********Modin
FutureWarning: the 'mangle_dupe_cols' keyword is deprecated and will be removed in a future version. Please take steps to stop the use of 'mangle_dupe_cols'
FutureWarning: The squeeze argument has been deprecated and will be removed in a future version. Append .squeeze("columns") to the call to squeeze.

Pandas API response
 pickup_datetime    datetime64[ns]
dtype: object

HDK hidden API resonse:
pyarrow.Table
F_pickup_datetime: timestamp[s]
----
F_pickup_datetime: [[2014-01-09 20:45:25]]
FutureWarning: the 'mangle_dupe_cols' keyword is deprecated and will be removed in a future version. Please take steps to stop the use of 'mangle_dupe_cols'
FutureWarning: The squeeze argument has been deprecated and will be removed in a future version. Append .squeeze("columns") to the call to squeeze.

Pandas API response
 pickup_datetime    datetime64[ns]
dtype: object

HDK hidden API resonse:
pyarrow.Table
F_pickup_datetime: timestamp[s]
----
F_pickup_datetime: [[2015-01-15 19:05:39]]

Result shape is:
(2, 1)
*****No error found*****

**********dtype is None:  False

**********Pandas

Pandas API response
 pickup_datetime    datetime64[ns]
dtype: object

HDK hidden API resonse:
Problem: couldnt locate type data

Pandas API response
 pickup_datetime    datetime64[ns]
dtype: object

HDK hidden API resonse:
Problem: couldnt locate type data

Result shape is:
(2, 1)
*****No error found*****

**********Modin
FutureWarning: the 'mangle_dupe_cols' keyword is deprecated and will be removed in a future version. Please take steps to stop the use of 'mangle_dupe_cols'
FutureWarning: The squeeze argument has been deprecated and will be removed in a future version. Append .squeeze("columns") to the call to squeeze.

UserWarning: `read_csv` is not currently supported by ExperimentalHdkOnNative, defaulting to pandas implementation.
Please refer to https://modin.readthedocs.io/en/stable/supported_apis/defaulting_to_pandas.html for explanation.
FutureWarning: the 'mangle_dupe_cols' keyword is deprecated and will be removed in a future version. Please take steps to stop the use of 'mangle_dupe_cols'
FutureWarning: The squeeze argument has been deprecated and will be removed in a future version. Append .squeeze("columns") to the call to squeeze.

Pandas API response
 pickup_datetime    datetime64[ns]
dtype: object

HDK hidden API resonse:
pyarrow.Table
F_pickup_datetime: timestamp[ns]
----
F_pickup_datetime: [[2014-01-09 20:45:25.000000000]]
FutureWarning: the 'mangle_dupe_cols' keyword is deprecated and will be removed in a future version. Please take steps to stop the use of 'mangle_dupe_cols'
FutureWarning: The squeeze argument has been deprecated and will be removed in a future version. Append .squeeze("columns") to the call to squeeze.

Pandas API response
 pickup_datetime    datetime64[ns]
dtype: object

HDK hidden API resonse:
pyarrow.Table
F_pickup_datetime: timestamp[s]
----
F_pickup_datetime: [[2015-01-15 19:05:39]]

Result shape is:
Traceback (most recent call last):
  File "./taxi_ml/bug1.py", line 67, in <module>
    reproduce(d1, d2, mpd)
  File "./taxi_ml/bug1.py", line 58, in reproduce
    print(pd.concat([df1, df2]).shape)
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/pandas/base.py", line 3429, in __getattribute__
    attr = super().__getattribute__(item)
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/pandas/dataframe.py", line 344, in shape
    return len(self.index), len(self.columns)
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/pandas/base.py", line 3429, in __getattribute__
    attr = super().__getattribute__(item)
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/pandas/base.py", line 540, in _get_index
    return self._query_compiler.index
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/experimental/core/storage_formats/hdk/query_compiler.py", line 471, in _get_index
    return self._modin_frame.index
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/experimental/core/execution/native/implementations/hdk_on_native/dataframe/dataframe.py", line 1892, in _get_index
    self._execute()
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/logging/logger_decorator.py", line 128, in run_and_log
    return obj(*args, **kwargs)
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/experimental/core/execution/native/implementations/hdk_on_native/dataframe/dataframe.py", line 1669, in _execute
    new_table = self._execute_arrow()
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/logging/logger_decorator.py", line 128, in run_and_log
    return obj(*args, **kwargs)
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/experimental/core/execution/native/implementations/hdk_on_native/dataframe/dataframe.py", line 1759, in _execute_arrow
    return self._arrow_concat(self._op.input)
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/logging/logger_decorator.py", line 128, in run_and_log
    return obj(*args, **kwargs)
  File "/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/modin/experimental/core/execution/native/implementations/hdk_on_native/dataframe/dataframe.py", line 1848, in _arrow_concat
    return pyarrow.concat_tables(frame._execute_arrow() for frame in frames)
  File "pyarrow/table.pxi", line 2338, in pyarrow.lib.concat_tables
  File "pyarrow/error.pxi", line 143, in pyarrow.lib.pyarrow_internal_check_status
  File "pyarrow/error.pxi", line 99, in pyarrow.lib.check_status
pyarrow.lib.ArrowInvalid: Schema at index 1 was different:
F___index__: int64
F_pickup_datetime: timestamp[ns]
vs
F___index__: int64
F_pickup_datetime: timestamp[s]

Installed Versions

>>> import pandas
>>> pandas.show_versions()
/nfs/site/home/ekrivov/large/tryrun1/miniconda3/envs/taxi/lib/python3.8/site-packages/_distutils_hack/__init__.py:33: UserWarning: Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
  In practice, you should construct these with dtype1 = pd.ArrowDtype(arr1.type) and dtype2 = pd.ArrowDtype(arr2.type).  Once you have these dtypes...
left = dtype1.construct_array_type()._from_sequence(arr1, dtype=dtype1)
right = dtype2.construct_array_type()._from_sequence(arr2, dtype=dtype2)

dtype = pd.core.dtypes.cast.find_common_type([left.dtype, right.dtype])

If you are concating these in modin and only need to cast them to a common dtype, then dtype here is what you want.  If you are concating them in pandas:
ser1 = pd.Series(left)
ser2 = pd.Series(right)

result = pd.concat([ser1, ser2])

@Egor-Krivov could you please check if the issue is still exists? The attached code works for me on the master branch.

HDK engine is deprecated and will be removed in a future version.


error: command ':/usr/local/cuda-10.1/bin/nvcc' failed with exit status 1

Is this question related to the version of my Cuda, but I heard that 10.2 is also possible for other people.

pcdet/ops/iou3d_nms/src/iou3d_cpu.cpp:12:18: fatal error: cuda.h: No such file or directory
compilation terminated.
error: command 'gcc' failed with exit status 1

same problem ..
how solved ...

Please provide more context. 🤯

Is this question related to the version of my Cuda, but I heard that 10.2 is also possible for other people.

try 'export CUDA_HOME='/cuda/path/' in terminal


Tap on dropdown button in tests does not work

Reported by customer:Leafy...
We have a test that tries to change the value of a dropdown button by tapping on it. However, we are getting exceptions regarding the theme.
code:
await tester.tap(find.text('Flighted'));
result:
══╡ EXCEPTION CAUGHT BY GESTURE LIBRARY ╞═══════════════════════════════════════════════════════════
The following NoSuchMethodError was thrown while dispatching a pointer event:
The null object does not have a getter 'isMaterialAppTheme'.

NoSuchMethodError: method not found: 'isMaterialAppTheme'
Receiver: null
Arguments: []

When the exception was thrown, this was the stack:
#0      Object._noSuchMethod (dart:core-patch/object_patch.dart:44)
#1      Object.noSuchMethod (dart:core-patch/object_patch.dart:47)
#2      Theme.of (package:flutter/src/material/theme.dart:65:37)
#3      _DropdownButtonState._handleTap (package:flutter/src/material/drop_down.dart:494:20)
#4      TapGestureRecognizer._checkUp (package:flutter/src/gestures/tap.dart:148:14)
#5      TapGestureRecognizer.acceptGesture (package:flutter/src/gestures/tap.dart:119:7)
#6      GestureArenaManager.sweep (package:flutter/src/gestures/arena.dart:119:27)
#7      BindingBase&SchedulerBinding&GestureBinding.handleEvent (package:flutter/src/gestures/binding.dart:126:20)
#8      BindingBase&SchedulerBinding&GestureBinding.dispatchEvent (package:flutter/src/gestures/binding.dart:100:22)
#9      TestWidgetsFlutterBinding.dispatchEvent (package:flutter_test/src/binding.dart:181:24)
#10     WidgetTester.sendEventToBinding.<anonymous closure>.<<anonymous closure>_async_body> (package:flutter_test/src/widget_tester.dart:236:15)
#20     AutomatedTestWidgetsFlutterBinding.asyncBarrier (package:flutter_test/src/binding.dart:520:16)
#21     TestWidgetsFlutterBinding._runTest (package:flutter_test/src/binding.dart:366:5)
#22     AutomatedTestWidgetsFlutterBinding.runTest.<anonymous closure> (package:flutter_test/src/binding.dart:506:24)
#28     AutomatedTestWidgetsFlutterBinding.runTest (package:flutter_test/src/binding.dart:504:16)
#29     testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:54:50)
#30     Declarer.test.<anonymous closure>.<<anonymous closure>_async_body>.<anonymous closure>.<<anonymous closure>_async_body> (package:test/src/backend/declarer.dart:106:19)
#42     Declarer._runSetUps.<_runSetUps_async_body> (package:test/src/backend/declarer.dart:183:3)
(elided 61 frames from class _FakeAsync, package dart:async, package dart:async-patch, and package
stack_trace)

Event:
  PointerUpEvent(Point(77.0, 268.0))
Target:
  <AutomatedTestWidgetsFlutterBinding>

The bug is one line 105 of theme.dart.  It needs to handle the case of theme being null.


Fetch improvement

Fetching playlist for Spotify is taking a long time and it doesn't show progress.
It would be nice to have a graphic interpretation of the fetching progress.

That's a great idea but,  we basically get all the playlist-tracks in 1 to 3 'HTTP Post requests' implemented deep deep down somewhere in spotipy, we'd have to either modify the spotipy source (and having to maintain a fork of spotipy) or hook a cli display to the search module which is a very bad idea when it comes to maintainability. That the reason we haven't done this yet.
As much as that would be a good convenience, its impractical to implement.
Nice to know that there's other people on the same wavelength as us guys. We'll implement some sort of solution as soon as someone cooks up something like that.
Cheerio!


Move basic graph concepts in Core module

OrientDB is a multi-model database, but in the Core module there is no concept of graph concepts, even though all the components are there to manage graph data.
Graph module is currently separated from Core just to avoid to constrain Core to all the dependencies required by TinkerPop.
We should move basic graph concepts in Core module, implement TinkerPop stack as a layer on top of them and rename current Graph module in TinkerPop2.
This way we will also be able to have two different TinkerPop implementations (2.x and 3) that rely on the same low level graph components.

:+1

+1

-1
Graph support require >20Mb in WAR. It's heavily redundant if only document functionality is required.
Please do not get everything into core...

The idea is to move only the basic concepts, not Blueprints for this reason.

Done and available in v3.0-M2.


Add local cache/sqlite db

youtube-dl lookup is slow. Cache the downloaded path key: backend_type+video_id, struct: BackendSearchResult, persist this HashMap to a text file in ~/.surge/cache.

Youtube-dl can cache itself.


UI for the repeater and set fields

From what I understood, the set and repeater fields just implement a fields option. How about having the whole fields configuration as part of the UI instead of custom error prone json text field?

The reason right now for the current implementation: flexibility. No need for a ui for every new or custom field type. just a simple json config and you're ready to go. This helps to progress more quickly. Repeaters and sets are edge cases, for the other fields you normally don't even need special options.

No need for a ui for every new or custom field type

But the UI is kind of already there no? it could just be re-used.

I thought about a simple way for an UI a few days ago and I just tried it here:
https://github.com/agentejo/cockpit/compare/next...raffaelj:field-options-ui
The usage is simple. Just add a json string with ui options to the field or somewhere in a custom javascript file
App.Utils.fieldUi['text'] = {
    "slug": {"type":"boolean","width":"1-3"},
    "placeholder": {"type":"text","width":"1-3"},
    "pattern": {"type":"text","width":"1-3"},
    "maxlength": {"type":"text","options":{"type":"number"},"width":"1-3"},
    "minlength": {"type":"text","options":{"type":"number"},"width":"1-3"},
    "step": {"type":"text","options":{"type":"number"},"width":"1-3"},
    "size": {"type":"text","options":{"type":"number"},"width":"1-2"},
    "cls": {"type":"text","label":App.i18n.get('Class'),"width":"1-2"},
};

For granular output add a function
App.Utils.fieldUi['simple-repeater'] = function() {
    return '
test
';
};

@aheinze What do you think? It doesn't break anything, it's invisible if no ui definitions are stored and a complete list could be delivered as addon.


Add shader lab package and support shader framework

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Featutres:

Create shader directly using galacen shader code

import { ShaderLab } from "@galacean/engine-shaderlab";

// Create engine with shaderLab
const engine = await WebGLEngine.create({ canvas: "canvas", shaderLab });

......

// Create shader by galacean shader code directly!
const shader = Shader.create(galaceanShaderCode);

shaderLab should use snake-case name style


New install api

This pull request includes the changes to support the addition of a new BundleContext::InstallBundles API. It also includes some changes to remove extraneous output to stdout. Please let me know of any code changes that are needed, questions that you have, or any other issues. There is an accompanying RFC here: https://github.com/CppMicroServices/rfcs/blob/master/text/0006-BundleContext-Install-API.md. I forgot to branch before writing it. Sorry about that. Please review this as well. If there are changes requested (as I'm sure there will be) I'll make them on a separate branch before issuing a pull request with them.
Thanks everyone!

Done.


Add test case that makes the program crash

@AngusJohnson
Here's a test case that makes the program crash (as a result of trying to dereference a null pointer).
The first subject path is still a bit long. I can try to trim it down to the bare minimum that is required to reproduce the problem. But I don't have time to do that right now, and anyway I can't do it any better than you (or anyone else) can... So I'll just make this available now, and if needed, will continue a bit later.

NB: I didn't test the C# or the Delphi versions, at least just yet.

Also, I'm not saying that the input isn't somehow ill-formed.

Dear Angus, thank you so much for looking into this right away!
I can already confirm that your recent changes fix all the immediate problems I was having with Clipper2 (when migrating my code to use it instead of Clipper1).
Now running many more tests. :)


Investigate the bug causing inputs from a controller and the keyboard to conflict

There's a bug in Godot where assigning both a key and an analog stick to the same action (like Moving) will sometimes cause conflicts between the two. If a controller is connected while playing with a keyboard, moving left/right will sometimes not work properly, because Godot is reading the input from the controller and updating Bob's movement to 0.
A workaround must be developed is a fix is not released in a timely manner.

This is indeed a bug with Godot, and it seems it's affecting more people. I'll implement a workaround for now

Fixed in #68


Add retrying to tag listing

Add exponential backoff retrying to list tag call and add a dependency on guava-retrying.

Looks good to me.


[tree] Undefined index: rootIdentifierMethod

Hi there,
We are running v2.4.24 on top of Symfony v2.8.38 and our test suite now fails with error:
Undefined index: rootIdentifierMethod

vendor/symfony/phpunit-bridge/DeprecationErrorHandler.php:71
vendor/gedmo/doctrine-extensions/lib/Gedmo/Tree/Strategy/ORM/Nested.php:128
vendor/gedmo/doctrine-extensions/lib/Gedmo/Tree/TreeListener.php:111
vendor/symfony/symfony/src/Symfony/Bridge/Doctrine/ContainerAwareEventManager.php:61
vendor/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php:3318
vendor/doctrine/orm/lib/Doctrine/ORM/UnitOfWork.php:367
vendor/doctrine/orm/lib/Doctrine/ORM/EntityManager.php:356

I guess this is related to Nested.php#L128 where value $config['rootIdentifierMethod'] is checked but array key might not be defined.

Fixed by https://github.com/Atlantic18/DoctrineExtensions/pull/1911


Custom ActionFilterAttribute on Razor PageModel Get method

Hi,
I'm trying to get a custom ActionFilterAttribute to get working on the Get method of my Razor Pages.
Starting with a simple .NetCore Web project, I created a custom ActionFilterAttribute as :
`
public class MyCustomActionFilterAttribute : ActionFilterAttribute
{
///
/// Title of the current item
///
public string Title { get; set; }
    public override void OnActionExecuting(ActionExecutingContext context)
    {
          // This method is NEVER called!!
        System.Diagnostics.Debugger.Break();
    }
}

`
Then I use it in my Index.cshtml.cs :
     public class IndexModel : PageModel     {         [MyCustomActionFilter(Title ="My Title", Order =1)]         public void OnGet()         {         }     }
But the method OnActionExecuting is never called.
What am I missing ?
Regards.
François
TestCustomActionFilterAttribute.zip

@fmaeseele page filters can only be applied to a page model, and not individual handler methods. Additionally, you need to use IPageFilter when working with a Razor Page. IActionFilter \ ActionFilterAttribute only applies to controller actions. Unfortunately the docs for page filters is a bit lacking, I'll add some details in a follow up comment

Razor Page Filters
Analogous to action filters, IPageFilter or IAsyncPageFilter surround the selection and execution of page handlers. Filters on Razor Page or Razor Page models can only be applied at the type level i.e. you may only apply an IPageFilter or an IAsyncPageFilter to the model type and not to individual handler methods.
Here's a sample page filter:
public class SamplePageFilter : IPageFilter
{
    public void OnPageHandlerSelected(PageHandlerSelectedContext  context)
    {
        // do something during page handler selection.
    }

    public void OnPageHandlerExecuting(PageHandlerExecutingContext context)
    {
        // do something after handler selection, but before a handler method executes.
    }

    public void OnPageHandlerExecuted(PageHandlerExecutedContext context)
    {
        // do something after a handler method executes.
    }
}

The PageModel type implements an IPageFilter and IAsyncPageFilter. Applications may override these methods in their model types to provide an implementation. Example:
public class Index : PageModel
{
    public string Title { get; private set; }

    public override void OnPageHandlerExecuting(PageHandlerExecutingContext context)
    {
        Title = "Title set in handler executing";
    }
}

Page filters can be applied globally by adding to MvcOptions.Filters e.g.
public void ConfigureServices(IServiceCollection services)
{
    services.AddMvc(options =>
    {
        options.Filters.Add(new CustomPageFilter());
    });
}

They may also be applied to a subset of pages by using AddFolderApplicationModelConvention:
public void ConfigureServices(IServiceCollection services)
{
    services.AddMvc()
        .AddRazorPagesOptions(options =>
        {
            options.Conventions.AddFolderApplicationModelConvention("/MyDir", model => model.Filters.Add(new CustomPageFilter()));
        });
}

Hi @pranavkm ,
Thank you very much for your quick and clear answer.
I finally ended up with your IPageFilter solution for my filter to intercept OnGet() requests.
That said, this is unfortunate that we cannot filter on a specific handler method by putting the attribute directly on it. Thanks to RazorPages, we may not need controller in most of the case. So it could be useful to be able to use a kind of action attribute on a specific method handler.
Thanks again.
Best Regards,
François

Razor pages is a recommended way of development... You just have to rewrite all your staff - filters, attributes and so on...  :(

How do I suppress exception?
        public override void OnPageHandlerExecuted(PageHandlerExecutedContext context) {             if(context.Exception != null && context.Exception is AMyException) {                 // do something..                 context.ExceptionHandled = true;             }          }
produces empty page.