Unable to find service notify/alexa_media

Describe the bug
Every restart to HA will cause this error

homeassistant.exceptions.ServiceNotFound: Unable to find service notify/alexa_media

To Reproduce
Steps to reproduce the behavior:
Restart HA
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System details

Home-assistant (version): 0.101.3 from Docker
Hassio (Yes/No): No
alexa_media  (version from const.py or HA startup): 2.3.3 / 2.3.4
alexapy (version from pip show alexapy or HA startup):

Logs

ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 190, in async_run
await self._handle_action(action, variables, context)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 274, in _handle_action
await self._actions[_determine_action(action)](action, variables, context)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 357, in _async_call_service
context=context,
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 97, in async_call_from_config
domain, service_name, service_data, blocking=blocking, context=context
File "/usr/src/homeassistant/homeassistant/core.py", line 1211, in async_call
raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: Unable to find service notify/alexa_media

Additional context
After remove the previous<EMAIL_ADDRESS>file, then restart HA and add Alexa again can make it work again. But restart HA will reproduce this issue.

Please provide startup logs. You should see some logs discussing setting up the notify service.

Please provide startup logs. You should see some logs discussing setting up the notify service.

Here it is.

2019-11-11 03:16:07	stdout	homeassistant.exceptions.ServiceNotFound: Unable to find service notify/alexa_media[0m
2019-11-11 03:16:07	stdout	    raise ServiceNotFound(domain, service) from None
2019-11-11 03:16:07	stdout	  File "/usr/src/homeassistant/homeassistant/core.py", line 1211, in async_call
2019-11-11 03:16:07	stdout	    domain, service_name, service_data, blocking=blocking, context=context
2019-11-11 03:16:07	stdout	  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 97, in async_call_from_config
2019-11-11 03:16:07	stdout	    context=context,
2019-11-11 03:16:07	stdout	  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 357, in _async_call_service
2019-11-11 03:16:07	stdout	    await self._actions[_determine_action(action)](action, variables, context)
2019-11-11 03:16:07	stdout	  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 274, in _handle_action
2019-11-11 03:16:07	stdout	    await self._handle_action(action, variables, context)
2019-11-11 03:16:07	stdout	  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 190, in async_run
2019-11-11 03:16:07	stdout	Traceback (most recent call last):
2019-11-11 03:16:07	stdout	[31m2019-11-11 11:16:07 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved[0m
2019-11-11 03:14:50	stdout	}[0m
2019-11-11 03:14:50	stdout	    "id": 1
2019-11-11 03:14:50	stdout	    ],
2019-11-11 03:14:50	stdout	        "Display Is Turned off"
2019-11-11 03:14:50	stdout	        40005,
2019-11-11 03:14:50	stdout	    "error": [
2019-11-11 03:14:50	stdout	[31m2019-11-11 11:14:50 ERROR (SyncWorker_8) [braviarc.braviarc] JSON request error:{
2019-11-11 03:14:28	stdout	}[0m
2019-11-11 03:14:28	stdout	    "id": 1
2019-11-11 03:14:28	stdout	    ],
2019-11-11 03:14:28	stdout	        "Display Is Turned off"
2019-11-11 03:14:28	stdout	        40005,
2019-11-11 03:14:28	stdout	    "error": [
2019-11-11 03:14:28	stdout	[31m2019-11-11 11:14:28 ERROR (SyncWorker_9) [braviarc.braviarc] JSON request error:{
2019-11-11 03:14:08	stdout	[31m2019-11-11 11:14:08 ERROR (MainThread) [homeassistant.components.automation] Error while executing automation automation.start_homeassistant. Service not found for call_service at pos 2: Unable to find service notify/alexa_media[0m
2019-11-11 03:14:04	stdout	AttributeError: 'bool' object has no attribute 'hass'[0m
2019-11-11 03:14:04	stdout	    notify_service.hass = hass
2019-11-11 03:14:04	stdout	  File "/usr/src/homeassistant/homeassistant/components/notify/init.py", line 96, in async_setup_platform
2019-11-11 03:14:04	stdout	    await async_setup_platform(platform, discovery_info=info)
2019-11-11 03:14:04	stdout	  File "/usr/src/homeassistant/homeassistant/components/notify/init.py", line 162, in async_platform_discovered
2019-11-11 03:14:04	stdout	Traceback (most recent call last):
2019-11-11 03:14:04	stdout	[31m2019-11-11 11:14:03 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved[0m
2019-11-11 03:13:34	stdout	[33m2019-11-11 11:13:34 WARNING (MainThread) [homeassistant.components.switch] Setup of platform alexa_media is taking over 10 seconds.[0m
2019-11-11 03:13:33	stdout	[33m2019-11-11 11:13:33 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform alexa_media is taking over 10 seconds.[0m
2019-11-11 03:13:30	stdout	[31m2019-11-11 11:13:29 ERROR (SyncWorker_0) [braviarc.braviarc] [W] Exception: HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /sony/accessControl (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f06efe4f690>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=10)'))[0m
2019-11-11 03:13:29	stdout	[33m2019-11-11 11:13:29 WARNING (MainThread) [homeassistant.components.media_player] Setup of platform braviatv is taking over 10 seconds.[0m
2019-11-11 03:11:59	stdout	[31m2019-11-11 11:11:59 ERROR (SyncWorker_1) [homeassistant.components.ios.notify] The notify.ios platform was loaded but no devices exist! Please check the documentation at https://home-assistant.io/ecosystem/ios/notifications/ for more information[0m
2019-11-11 03:11:59	stdout	AttributeError: 'bool' object has no attribute 'hass'[0m
2019-11-11 03:11:59	stdout	    notify_service.hass = hass
2019-11-11 03:11:59	stdout	  File "/usr/src/homeassistant/homeassistant/components/notify/init.py", line 96, in async_setup_platform
2019-11-11 03:11:59	stdout	Traceback (most recent call last):
2019-11-11 03:11:59	stdout	[31m2019-11-11 11:11:58 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved[0m
2019-11-11 03:11:26	stdout	[33m2019-11-11 11:11:26 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for colorfulclouds which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.[0m
2019-11-11 03:10:45	stdout	[33m2019-11-11 11:10:45 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for xiaomi_miio_airconditioningcompanion which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (MainThread) [homeassistant.setup] Setting up logger[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (MainThread) [homeassistant.bootstrap] Setting up {'system_log', 'logger'}[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_2) [homeassistant.loader] Loaded ifttt from homeassistant.components.ifttt[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_9) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_4) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_7) [homeassistant.loader] Loaded lovelace from homeassistant.components.lovelace[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (MainThread) [homeassistant.setup] Setup of domain persistent_notification took 0.0 seconds.[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (MainThread) [homeassistant.setup] Setting up persistent_notification[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_3) [homeassistant.loader] Loaded device_automation from homeassistant.components.device_automation[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (MainThread) [homeassistant.setup] Setup of domain homeassistant took 0.0 seconds.[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (MainThread) [homeassistant.setup] Setting up homeassistant[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_0) [homeassistant.loader] Loaded adguard from homeassistant.components.adguard[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_1) [homeassistant.loader] Loaded auth from homeassistant.components.auth[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_9) [homeassistant.loader] Loaded persistent_notification from homeassistant.components.persistent_notification[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_5) [homeassistant.loader] Loaded cloud from homeassistant.components.cloud[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_4) [homeassistant.loader] Loaded automation from homeassistant.components.automation[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_8) [homeassistant.loader] Loaded configurator from homeassistant.components.configurator[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_7) [homeassistant.loader] Loaded webhook from homeassistant.components.webhook[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_3) [homeassistant.loader] Loaded homeassistant from homeassistant.components.homeassistant[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_6) [homeassistant.loader] Loaded mobile_app from homeassistant.components.mobile_app[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_8) [homeassistant.loader] Loaded device_tracker from homeassistant.components.device_tracker[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_5) [homeassistant.loader] Loaded ios from homeassistant.components.ios[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_7) [homeassistant.loader] Loaded homekit from homeassistant.components.homekit[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_1) [homeassistant.loader] Loaded timer from homeassistant.components.timer[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_9) [homeassistant.loader] Loaded plex from homeassistant.components.plex[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_3) [homeassistant.loader] Loaded xiaomi_aqara from homeassistant.components.xiaomi_aqara[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_0) [homeassistant.loader] Loaded logbook from homeassistant.components.logbook[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_6) [homeassistant.loader] Loaded yeelight from homeassistant.components.yeelight[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_8) [homeassistant.loader] Loaded updater from homeassistant.components.updater[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_5) [homeassistant.loader] Loaded alexa from homeassistant.components.alexa[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_4) [homeassistant.loader] Loaded cast from homeassistant.components.cast[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_9) [homeassistant.loader] Loaded climate from homeassistant.components.climate[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_6) [homeassistant.loader] Loaded panel_iframe from homeassistant.components.panel_iframe[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_3) [homeassistant.loader] Loaded weather from homeassistant.components.weather[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_1) [homeassistant.loader] Loaded cert_expiry from homeassistant.components.cert_expiry[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_0) [homeassistant.loader] Loaded apple_tv from homeassistant.components.apple_tv[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_8) [homeassistant.loader] Loaded config from homeassistant.components.config[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_7) [homeassistant.loader] Loaded ps4 from homeassistant.components.ps4[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_0) [homeassistant.loader] Loaded sun from homeassistant.components.sun[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_0) [homeassistant.loader] Loaded light from homeassistant.components.light[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_4) [homeassistant.loader] Loaded zeroconf from homeassistant.components.zeroconf[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_5) [homeassistant.loader] Loaded geofency from homeassistant.components.geofency[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_6) [homeassistant.loader] Loaded system_health from homeassistant.components.system_health[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_4) [homeassistant.loader] Loaded remote from homeassistant.components.remote[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_9) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_9) [homeassistant.loader] Loaded vultr from homeassistant.components.vultr[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_3) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_1) [homeassistant.loader] Loaded history from homeassistant.components.history[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_2) [homeassistant.loader] Loaded logger from homeassistant.components.logger[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_8) [homeassistant.loader] Loaded switch from homeassistant.components.switch[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_7) [homeassistant.loader] Loaded input_boolean from homeassistant.components.input_boolean[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_3) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_0) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_5) [homeassistant.loader] Loaded notify from homeassistant.components.notify[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_6) [homeassistant.loader] Loaded sonos from homeassistant.components.sonos[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_7) [homeassistant.loader] Loaded tts from homeassistant.components.tts[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_0) [homeassistant.loader] Loaded media_player from homeassistant.components.media_player[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_5) [homeassistant.loader] Loaded discovery from homeassistant.components.discovery[0m
2019-11-11 03:10:40	stdout	[32m2019-11-11 11:10:40 INFO (SyncWorker_9) [homeassistant.loader] Loaded api from homeassistant.components.api[0m
2019-11-11 03:10:39	stdout	[32m2019-11-11 11:10:39 INFO (SyncWorker_4) [homeassistant.loader] Loaded ssdp from homeassistant.components.ssdp[0m
2019-11-11 03:10:39	stdout	[32m2019-11-11 11:10:39 INFO (SyncWorker_2) [homeassistant.loader] Loaded map from homeassistant.components.map[0m
2019-11-11 03:10:39	stdout	[32m2019-11-11 11:10:39 INFO (SyncWorker_1) [homeassistant.loader] Loaded http from homeassistant.components.http[0m
2019-11-11 03:10:39	stdout	[32m2019-11-11 11:10:39 INFO (SyncWorker_8) [homeassistant.loader] Loaded sensor from homeassistant.components.sensor[0m
2019-11-11 03:10:39	stdout	[32m2019-11-11 11:10:39 INFO (SyncWorker_3) [homeassistant.loader] Loaded zone from homeassistant.components.zone[0m
2019-11-11 03:10:39	stdout	[32m2019-11-11 11:10:39 INFO (SyncWorker_6) [homeassistant.loader] Loaded google_assistant from homeassistant.components.google_assistant[0m
2019-11-11 03:10:39	stdout	[33m2019-11-11 11:10:39 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.[0m
2019-11-11 03:10:39	stdout	[33m2019-11-11 11:10:39 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.[0m
2019-11-11 03:10:39	stdout	[32m2019-11-11 11:10:39 INFO (SyncWorker_3) [homeassistant.loader] Loaded input_text from homeassistant.components.input_text[0m
2019-11-11 03:10:39	stdout	[32m2019-11-11 11:10:39 INFO (SyncWorker_4) [homeassistant.loader] Loaded group from homeassistant.components.group[0m
2019-11-11 03:10:39	stdout	[32m2019-11-11 11:10:39 INFO (SyncWorker_6) [homeassistant.loader] Loaded script from homeassistant.components.script[0m
2019-11-11 03:10:38	stdout	[32m2019-11-11 11:10:38 INFO (SyncWorker_5) [homeassistant.loader] Loaded input_select from homeassistant.components.input_select[0m
2019-11-11 03:10:38	stdout	[32m2019-11-11 11:10:38 INFO (SyncWorker_1) [homeassistant.loader] Loaded hacs from custom_components.hacs[0m
2019-11-11 03:10:38	stdout	[32m2019-11-11 11:10:38 INFO (SyncWorker_0) [homeassistant.loader] Loaded colorfulclouds from custom_components.colorfulclouds[0m
2019-11-11 03:10:38	stdout	[32m2019-11-11 11:10:38 INFO (SyncWorker_3) [homeassistant.loader] Loaded xiaomi_miio_airconditioningcompanion from custom_components.xiaomi_miio_airconditioningcompanion[0m
2019-11-11 03:10:38	stdout	[32m2019-11-11 11:10:38 INFO (SyncWorker_2) [homeassistant.loader] Loaded alexa_media from custom_components.alexa_media[0m
2019-11-11 03:10:34	stdout	Config directory: /config
2019-11-11 03:10:21	stdout	starting version 3.2.8

Please enable the logger for alexa_media. It will give more detail about how it's failing.

Please enable the logger for alexa_media. It will give more detail about how it's failing.

2019-11-14 04:30:37	stdout	[36m2019-11-14 12:30:37 DEBUG (MainThread) [custom_components.alexa_media.media_player] Sephrioth's Echo Dot: Last_called check: self: G************NWE reported: G************NWE[0m
2019-11-14 04:30:37	stdout	[36m2019-11-14 12:30:37 DEBUG (MainThread) [custom_components.alexa_media.media_player] a********e@g*******m: Refreshing Sephrioth's Echo Dot[0m
2019-11-14 04:30:37	stdout	[36m2019-11-14 12:30:37 DEBUG (MainThread) [custom_components.alexa_media.media_player] a********e@g*******m: No PUSH_AUDIO_PLAYER_STATE in dict_keys(['PUSH_EQUALIZER_STATE_CHANGE']); forcing refresh[0m
2019-11-14 04:30:37	stdout	[36m2019-11-14 12:30:37 DEBUG (MainThread) [custom_components.alexa_media] Updating media_player availability {'destinationUserId': 'A*********ULF', 'bass': 0, 'treble': 0, 'dopplerId': {'deviceSerialNumber': 'G************NWE', 'deviceType': 'A3S5BH2HU6VAYF'}, 'midrange': 0}[0m
2019-11-14 04:30:37	stdout	[36m2019-11-14 12:30:37 DEBUG (MainThread) [custom_components.alexa_media] Adding PUSH_EQUALIZER_STATE_CHANGE to seen_commands: {'PUSH_EQUALIZER_STATE_CHANGE':<PHONE_NUMBER>.482054}[0m
2019-11-14 04:30:37	stdout	[36m2019-11-14 12:30:37 DEBUG (MainThread) [custom_components.alexa_media] a********e@g*******m: Received websocket command: PUSH_EQUALIZER_STATE_CHANGE : {'destinationUserId': 'A*********ULF', 'bass': 0, 'treble': 0, 'dopplerId': {'deviceSerialNumber': 'G************NWE', 'deviceType': 'A3S5BH2HU6VAYF'}, 'midrange': 0}[0m
2019-11-14 04:17:25	stdout	homeassistant.exceptions.ServiceNotFound: Unable to find service notify/alexa_media[0m
2019-11-14 04:17:25	stdout	    raise ServiceNotFound(domain, service) from None
2019-11-14 04:17:25	stdout	  File "/usr/src/homeassistant/homeassistant/core.py", line 1211, in async_call
2019-11-14 04:17:25	stdout	    domain, service_name, service_data, blocking=blocking, context=context
2019-11-14 04:17:25	stdout	  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 97, in async_call_from_config
2019-11-14 04:17:25	stdout	    context=context,
2019-11-14 04:17:25	stdout	  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 357, in _async_call_service
2019-11-14 04:17:25	stdout	    await self._actions[_determine_action(action)](action, variables, context)
2019-11-14 04:17:25	stdout	  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 274, in _handle_action
2019-11-14 04:17:25	stdout	    await self._handle_action(action, variables, context)
2019-11-14 04:17:25	stdout	  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 190, in async_run
2019-11-14 04:17:25	stdout	Traceback (most recent call last):
2019-11-14 04:17:25	stdout	[31m2019-11-14 12:17:25 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved[0m
2019-11-14 04:15:28	stdout	[36m2019-11-14 12:15:28 DEBUG (MainThread) [custom_components.alexa_media.media_player] Disabling polling for Sephrioth's Echo Dot[0m
2019-11-14 04:15:26	stdout	[31m2019-11-14 12:15:26 ERROR (MainThread) [homeassistant.components.automation] Error while executing automation automation.start_homeassistant. Service not found for call_service at pos 2: Unable to find service notify/alexa_media[0m
2019-11-14 04:15:23	stdout	[36m2019-11-14 12:15:23 DEBUG (MainThread) [custom_components.alexa_media.media_player] Sephrioth's Echo Dot: Last_called check: self: G************NWE reported: G************NWE[0m
2019-11-14 04:15:23	stdout	[36m2019-11-14 12:15:23 DEBUG (MainThread) [custom_components.alexa_media.media_player] a********e@g*******m: Refreshing Sephrioth's Echo Dot[0m
2019-11-14 04:15:21	stdout	AttributeError: 'bool' object has no attribute 'hass'[0m
2019-11-14 04:15:21	stdout	    notify_service.hass = hass
2019-11-14 04:15:21	stdout	  File "/usr/src/homeassistant/homeassistant/components/notify/__init__.py", line 96, in async_setup_platform
2019-11-14 04:15:21	stdout	    await async_setup_platform(platform, discovery_info=info)
2019-11-14 04:15:21	stdout	  File "/usr/src/homeassistant/homeassistant/components/notify/__init__.py", line 162, in async_platform_discovered
2019-11-14 04:15:21	stdout	Traceback (most recent call last):
2019-11-14 04:15:21	stdout	[31m2019-11-14 12:15:21 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved[0m
2019-11-14 04:15:04	stdout	[36m2019-11-14 12:15:04 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.switch.async_setup_platform: Try: 2/5 after waiting 10 seconds result: True[0m
2019-11-14 04:15:04	stdout	[36m2019-11-14 12:15:04 DEBUG (MainThread) [custom_components.alexa_media.helpers] a********e@g*******m: Excluding device: <Entity Sephrioth's Echo Dot repeat switch: off>[0m
2019-11-14 04:15:04	stdout	[36m2019-11-14 12:15:04 DEBUG (MainThread) [custom_components.alexa_media.helpers] a********e@g*******m: Excluding device: <Entity Sephrioth's Echo Dot shuffle switch: off>[0m
2019-11-14 04:15:04	stdout	[36m2019-11-14 12:15:04 DEBUG (MainThread) [custom_components.alexa_media.helpers] a********e@g*******m: Excluding device: <Entity Sephrioth's Echo Dot do not disturb switch: off>[0m
2019-11-14 04:15:04	stdout	[36m2019-11-14 12:15:04 DEBUG (MainThread) [custom_components.alexa_media.switch] a********e@g*******m: Found G************NWE repeat switch with status: False[0m
2019-11-14 04:15:04	stdout	[36m2019-11-14 12:15:04 DEBUG (MainThread) [custom_components.alexa_media.switch] a********e@g*******m: Found G************NWE shuffle switch with status: False[0m
2019-11-14 04:15:04	stdout	[36m2019-11-14 12:15:04 DEBUG (MainThread) [custom_components.alexa_media.switch] a********e@g*******m: Found G************NWE dnd switch with status: False[0m
2019-11-14 04:15:04	stdout	[36m2019-11-14 12:15:04 DEBUG (MainThread) [custom_components.alexa_media.switch] a********e@g*******m: Loading switches[0m
2019-11-14 04:15:04	stdout	[33m2019-11-14 12:15:04 WARNING (MainThread) [homeassistant.components.switch] Setup of platform alexa_media is taking over 10 seconds.[0m
2019-11-14 04:15:03	stdout	[36m2019-11-14 12:15:03 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.sensor.async_setup_platform: Try: 2/5 after waiting 10 seconds result: True[0m
2019-11-14 04:15:03	stdout	[36m2019-11-14 12:15:03 DEBUG (MainThread) [custom_components.alexa_media.helpers] a********e@g*******m: Excluding device: <Entity Sephrioth's Echo Dot next Reminder: unavailable>[0m
2019-11-14 04:15:03	stdout	[36m2019-11-14 12:15:03 DEBUG (MainThread) [custom_components.alexa_media.helpers] a********e@g*******m: Excluding device: <Entity Sephrioth's Echo Dot next Timer: unavailable>[0m
2019-11-14 04:15:03	stdout	[36m2019-11-14 12:15:03 DEBUG (MainThread) [custom_components.alexa_media.helpers] a********e@g*******m: Excluding device: <Entity Sephrioth's Echo Dot next Alarm: unavailable>[0m
2019-11-14 04:15:03	stdout	[36m2019-11-14 12:15:03 DEBUG (MainThread) [custom_components.alexa_media.sensor] a********e@g*******m: Found G************NWE Reminder sensor (0) with next: unavailable[0m
2019-11-14 04:15:03	stdout	[36m2019-11-14 12:15:03 DEBUG (MainThread) [custom_components.alexa_media.sensor] a********e@g*******m: Found G************NWE Timer sensor (0) with next: unavailable[0m
2019-11-14 04:15:03	stdout	[36m2019-11-14 12:15:03 DEBUG (MainThread) [custom_components.alexa_media.sensor] a********e@g*******m: Found G************NWE Alarm sensor (0) with next: unavailable[0m
2019-11-14 04:15:03	stdout	[36m2019-11-14 12:15:03 DEBUG (MainThread) [custom_components.alexa_media.sensor] a********e@g*******m: Loading sensors[0m
2019-11-14 04:15:03	stdout	[33m2019-11-14 12:15:03 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform alexa_media is taking over 10 seconds.[0m
2019-11-14 04:15:01	stdout	[36m2019-11-14 12:15:01 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.media_player.async_setup_platform: Try: 1/5 after waiting 0 seconds result: True[0m
2019-11-14 04:15:01	stdout	[36m2019-11-14 12:15:01 DEBUG (MainThread) [custom_components.alexa_media.helpers] a********e@g*******m: Adding [<Entity Sephrioth's Echo Dot: standby>][0m
2019-11-14 04:15:00	stdout	[36m2019-11-14 12:15:00 DEBUG (MainThread) [custom_components.alexa_media.media_player] Sephrioth's Echo Dot: Last_called check: self: G************NWE reported: [0m
2019-11-14 04:15:00	stdout	[36m2019-11-14 12:15:00 DEBUG (MainThread) [custom_components.alexa_media.media_player] a********e@g*******m: Refreshing Sephrioth's Echo Dot[0m
2019-11-14 04:15:00	stdout	[36m2019-11-14 12:15:00 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.media_player.async_setup_platform: Trying with limit 5 delay 2 catch_exceptions True[0m
2019-11-14 04:14:59	stdout	[31m2019-11-14 12:14:59 ERROR (SyncWorker_3) [braviarc.braviarc] [W] Exception: HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /sony/accessControl (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7fc186c629d0>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=10)'))[0m
2019-11-14 04:14:59	stdout	[33m2019-11-14 12:14:59 WARNING (MainThread) [homeassistant.components.media_player] Setup of platform braviatv is taking over 10 seconds.[0m
2019-11-14 04:14:54	stdout	[36m2019-11-14 12:14:54 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.switch.async_setup_platform: Try: 1/5 after waiting 0 seconds result: False[0m
2019-11-14 04:14:54	stdout	[36m2019-11-14 12:14:54 DEBUG (MainThread) [custom_components.alexa_media.switch] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:14:54	stdout	[36m2019-11-14 12:14:54 DEBUG (MainThread) [custom_components.alexa_media.switch] a********e@g*******m: Loading switches[0m
2019-11-14 04:14:54	stdout	[36m2019-11-14 12:14:54 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.switch.async_setup_platform: Trying with limit 5 delay 5 catch_exceptions True[0m
2019-11-14 04:14:53	stdout	[36m2019-11-14 12:14:53 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.sensor.async_setup_platform: Try: 1/5 after waiting 0 seconds result: False[0m
2019-11-14 04:14:53	stdout	[36m2019-11-14 12:14:53 DEBUG (MainThread) [custom_components.alexa_media.sensor] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:14:53	stdout	[36m2019-11-14 12:14:53 DEBUG (MainThread) [custom_components.alexa_media.sensor] a********e@g*******m: Loading sensors[0m
2019-11-14 04:14:53	stdout	[36m2019-11-14 12:14:53 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.sensor.async_setup_platform: Trying with limit 5 delay 5 catch_exceptions False[0m
2019-11-14 04:14:06	stdout	[36m2019-11-14 12:14:06 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Try: 5/5 after waiting 32 seconds result: False[0m
2019-11-14 04:14:06	stdout	[36m2019-11-14 12:14:06 DEBUG (MainThread) [custom_components.alexa_media.notify] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:13:34	stdout	[36m2019-11-14 12:13:34 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Try: 4/5 after waiting 16 seconds result: False[0m
2019-11-14 04:13:34	stdout	[36m2019-11-14 12:13:34 DEBUG (MainThread) [custom_components.alexa_media.notify] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:13:18	stdout	[36m2019-11-14 12:13:18 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Try: 3/5 after waiting 8 seconds result: False[0m
2019-11-14 04:13:18	stdout	[36m2019-11-14 12:13:18 DEBUG (MainThread) [custom_components.alexa_media.notify] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:13:10	stdout	[36m2019-11-14 12:13:10 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Try: 2/5 after waiting 4 seconds result: False[0m
2019-11-14 04:13:10	stdout	[36m2019-11-14 12:13:10 DEBUG (MainThread) [custom_components.alexa_media.notify] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:13:06	stdout	[31m2019-11-14 12:13:06 ERROR (SyncWorker_1) [homeassistant.components.ios.notify] The notify.ios platform was loaded but no devices exist! Please check the documentation at https://home-assistant.io/ecosystem/ios/notifications/ for more information[0m
2019-11-14 04:13:06	stdout	[36m2019-11-14 12:13:06 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Try: 1/5 after waiting 0 seconds result: False[0m
2019-11-14 04:13:06	stdout	[36m2019-11-14 12:13:06 DEBUG (MainThread) [custom_components.alexa_media.notify] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:13:06	stdout	[36m2019-11-14 12:13:06 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Trying with limit 5 delay 2 catch_exceptions True[0m
2019-11-14 04:13:06	stdout	AttributeError: 'bool' object has no attribute 'hass'[0m
2019-11-14 04:13:06	stdout	    notify_service.hass = hass
2019-11-14 04:13:06	stdout	  File "/usr/src/homeassistant/homeassistant/components/notify/__init__.py", line 96, in async_setup_platform
2019-11-14 04:13:06	stdout	Traceback (most recent call last):
2019-11-14 04:13:06	stdout	[31m2019-11-14 12:13:06 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved[0m
2019-11-14 04:13:06	stdout	[36m2019-11-14 12:13:06 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Try: 5/5 after waiting 32 seconds result: False[0m
2019-11-14 04:13:06	stdout	[36m2019-11-14 12:13:06 DEBUG (MainThread) [custom_components.alexa_media.notify] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:12:34	stdout	[36m2019-11-14 12:12:34 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Try: 4/5 after waiting 16 seconds result: False[0m
2019-11-14 04:12:34	stdout	[36m2019-11-14 12:12:34 DEBUG (MainThread) [custom_components.alexa_media.notify] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:12:18	stdout	[36m2019-11-14 12:12:18 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Try: 3/5 after waiting 8 seconds result: False[0m
2019-11-14 04:12:18	stdout	[36m2019-11-14 12:12:18 DEBUG (MainThread) [custom_components.alexa_media.notify] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:12:10	stdout	[36m2019-11-14 12:12:10 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Try: 2/5 after waiting 4 seconds result: False[0m
2019-11-14 04:12:10	stdout	[36m2019-11-14 12:12:10 DEBUG (MainThread) [custom_components.alexa_media.notify] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:12:06	stdout	[36m2019-11-14 12:12:06 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Try: 1/5 after waiting 0 seconds result: False[0m
2019-11-14 04:12:06	stdout	[36m2019-11-14 12:12:06 DEBUG (MainThread) [custom_components.alexa_media.notify] a********e@g*******m: Media player G************NWE not loaded yet; delaying load[0m
2019-11-14 04:12:06	stdout	[36m2019-11-14 12:12:06 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.notify.async_get_service: Trying with limit 5 delay 2 catch_exceptions True[0m
2019-11-14 04:11:04	stdout	[36m2019-11-14 12:11:04 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.alarm_control_panel.async_setup_platform: Try: 1/5 after waiting 0 seconds result: True[0m
2019-11-14 04:11:04	stdout	[36m2019-11-14 12:11:04 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] a********e@g*******m: Skipping creation of uninitialized device: <Entity Alexa Guard: None>[0m
2019-11-14 04:11:04	stdout	[36m2019-11-14 12:11:04 DEBUG (MainThread) [custom_components.alexa_media.alarm_control_panel] a********e@g*******m: No Alexa Guard entity found[0m
2019-11-14 04:11:04	stdout	[36m2019-11-14 12:11:04 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.alarm_control_panel.async_setup_platform: Trying with limit 5 delay 2 catch_exceptions True[0m
2019-11-14 04:11:04	stdout	[36m2019-11-14 12:11:04 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.async_setup_entry: Try: 1/5 after waiting 0 seconds result: True[0m
2019-11-14 04:11:04	stdout	[36m2019-11-14 12:11:04 DEBUG (MainThread) [custom_components.alexa_media] a********e@g*******m: last_called changed:  to {'serialNumber': 'G************NWE', 'timestamp':<PHONE_NUMBER>048}[0m
2019-11-14 04:11:04	stdout	[36m2019-11-14 12:11:04 DEBUG (MainThread) [custom_components.alexa_media] a********e@g*******m: Updated last_called: {'serialNumber': 'G************NWE', 'timestamp':<PHONE_NUMBER>048}[0m
2019-11-14 04:11:04	stdout	[36m2019-11-14 12:11:04 DEBUG (MainThread) [custom_components.alexa_media] a********e@g*******m: Updated 0 notifications for 0 devices[0m
2019-11-14 04:11:03	stdout	[36m2019-11-14 12:11:03 DEBUG (MainThread) [custom_components.alexa_media] a********e@g*******m: Existing: [] New: ["Sephrioth's Echo Dot"]; Filtered out by not being in include: ['Sonos One', 'Sonos', 'This Device', "Sephrioth's Alexa Apps"] or in exclude: [][0m
2019-11-14 04:11:03	stdout	[36m2019-11-14 12:11:03 DEBUG (MainThread) [custom_components.alexa_media] DND False found for G************NWE[0m
2019-11-14 04:11:03	stdout	[36m2019-11-14 12:11:03 DEBUG (MainThread) [custom_components.alexa_media] Locale en-us timezone Asia/Shanghai found for G************NWE[0m
2019-11-14 04:11:03	stdout	[36m2019-11-14 12:11:03 DEBUG (MainThread) [custom_components.alexa_media] a********e@g*******m: Found 5 devices, 1 bluetooth[0m
2019-11-14 04:11:00	stdout	[36m2019-11-14 12:11:00 DEBUG (MainThread) [custom_components.alexa_media] a********e@g*******m: Websocket succesfully connected[0m
2019-11-14 04:10:59	stdout	[36m2019-11-14 12:10:59 DEBUG (MainThread) [custom_components.alexa_media] a********e@g*******m: Websocket created: <alexapy.alexawebsocket.WebsocketEchoClient object at 0x7fc18a0d1cd0>[0m
2019-11-14 04:10:59	stdout	[36m2019-11-14 12:10:59 DEBUG (MainThread) [custom_components.alexa_media] Setting up Alexa devices for a********e@g*******m[0m
2019-11-14 04:10:59	stdout	[36m2019-11-14 12:10:59 DEBUG (MainThread) [custom_components.alexa_media] Testing login status: {'login_successful': True}[0m
2019-11-14 04:10:58	stdout	[32m2019-11-14 12:10:58 INFO (MainThread) [custom_components.alexa_media] Loaded alexapy==1.3.2[0m
2019-11-14 04:10:58	stdout	[0m
2019-11-14 04:10:58	stdout	-------------------------------------------------------------------
2019-11-14 04:10:58	stdout	https://github.com/custom-components/alexa_media_player/issues
2019-11-14 04:10:58	stdout	If you have any issues with this you need to open an issue here:
2019-11-14 04:10:58	stdout	This is a custom component
2019-11-14 04:10:58	stdout	Version: 2.3.4
2019-11-14 04:10:58	stdout	alexa_media
2019-11-14 04:10:58	stdout	-------------------------------------------------------------------
2019-11-14 04:10:58	stdout	[32m2019-11-14 12:10:58 INFO (MainThread) [custom_components.alexa_media]
2019-11-14 04:10:58	stdout	[36m2019-11-14 12:10:58 DEBUG (MainThread) [custom_components.alexa_media.helpers] alexa_media.async_setup_entry: Trying with limit 5 delay 5 catch_exceptions True[0m

Ok, apparently your system is loading the media player platform for Alexa Media slower than the retry delay allows for. Because of this, multiple platforms are not loading including the notify service. Is this a new error or has this been happening for a while?
A workaround would be to edit all files .py files except __init__.py to increase the retry limit or delay.
So in other words, change this (which will try 5 times delaying 2 seconds waiting exponentially longer between tries):
@retry_async(limit=5, delay=2, catch_exceptions=True)

to something like this (try up to 10 times, delaying 5 seconds exponentially increasing:
@retry_async(limit=10, delay=5, catch_exceptions=True)

It's been a week or two,  and not every HA restart causes it.  Thanks for the explanation!

Did some test and found  Alexa component will result the error.
alexa:
  smart_home

That's not this component. This component is alexa_media. You're referring to the official component.

That's not this component. This component is alexa_media. You're referring to the official component.

I see, just for your information.


New page for component doc

Not sure what you can do about this but it would be useful to get the values instead of the name of the type.

The values of the name of type will be displayed in a second step


rewrite middleware not identifying multiple slashes

Problem : Redirect to url with single slash if url has multiple slashes.
http://localhost/segment1///segment2//segment3
The above url when read removes multiple slashes and shows only one slash.
I tried following methods to read url.
request.Path
Microsoft.AspNetCore.Http.Extensions.UriHelper.GetEncodedUri (request)
Microsoft.AspNetCore.Http.Extensions.UriHelper.GetDisplayUri(request)
Thanks.

This issue was moved to aspnet/BasicMiddleware#212


Windows Terminal unavailable immediately after logging into a sysprep Windows 11 image

Windows Terminal version
1.14.1962.0
Windows build number
10.0.22000.0
Other Software
No response
Steps to reproduce
Create an Azure VM with Windows 11 Enterprise image that had sysprep performed.
Login to machine and try to launch Windows Terminal via Start Menu or wt.exe.
Expected Behavior
Windows Terminal is immediately available after first login on a fresh Windows 11 machine that had sysprep performed previously.
Actual Behavior
The wt.exe doesn't respond or shows as not found after login. In Start Menu, if you click Windows Terminal it doesn't launch.
After some time the issue corrects itself and you can launch Windows Terminal but it can be 10+ minutes in some cases.
It is an intermittent issue, doesn't always reproduce.
Have tried to wait for it to become available but 10 minutes is too long to wait. Tried to install Appx packages directly on Windows 11 but it takes Windows Terminal a long time to become available even in this scenario too.
An example of this is the output below, each wait is 5 seconds (2.5 min) which is after installing AppX:
WARNING: Module Appx is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck' syntax.
Package Microsoft.VCLibs.140.00 is already installed and up-to-date.
WARNING: Module Appx is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck' syntax.
Package Microsoft.VCLibs.140.00.UWPDesktop is already installed and up-to-date.
WARNING: Module Appx is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell please use 'Import-Module -SkipEditionCheck' syntax.
Package Microsoft.DesktopAppInstaller is already installed and up-to-date.
        Waiting for Windows Terminal...attempt #1 out of 30
        Waiting for Windows Terminal...attempt #2 out of 30
        Waiting for Windows Terminal...attempt #3 out of 30
        Waiting for Windows Terminal...attempt #4 out of 30
        Waiting for Windows Terminal...attempt #5 out of 30
        Waiting for Windows Terminal...attempt #6 out of 30
        Waiting for Windows Terminal...attempt #7 out of 30
        Waiting for Windows Terminal...attempt #8 out of 30
        Waiting for Windows Terminal...attempt #9 out of 30
        Waiting for Windows Terminal...attempt #10 out of 30
        Waiting for Windows Terminal...attempt #11 out of 30
        Waiting for Windows Terminal...attempt #12 out of 30
        Waiting for Windows Terminal...attempt #13 out of 30
        Waiting for Windows Terminal...attempt #14 out of 30
        Waiting for Windows Terminal...attempt #15 out of 30
        Waiting for Windows Terminal...attempt #16 out of 30
        Waiting for Windows Terminal...attempt #17 out of 30
        Waiting for Windows Terminal...attempt #18 out of 30
        Waiting for Windows Terminal...attempt #19 out of 30
        Waiting for Windows Terminal...attempt #20 out of 30
        Waiting for Windows Terminal...attempt #21 out of 30
        Waiting for Windows Terminal...attempt #22 out of 30
        Waiting for Windows Terminal...attempt #23 out of 30
        Waiting for Windows Terminal...attempt #24 out of 30
        Waiting for Windows Terminal...attempt #25 out of 30
        Waiting for Windows Terminal...attempt #26 out of 30
        Waiting for Windows Terminal...attempt #27 out of 30
        Waiting for Windows Terminal...attempt #28 out of 30
        Waiting for Windows Terminal...attempt #29 out of 30
        Waiting for Windows Terminal...attempt #30 out of 30
WARNING: Windows Terminal wasn't detected

For more reference:

#12023
#7767

I'd check out this comment: https://github.com/microsoft/terminal/issues/12023#issuecomment-1063315838
Does that help at all/?


Enable linter on splunk_otel/cmd directory

splunk_otel/cmd was being ignored by pylint because it did not have an init.py file. Added init.py to enable pylint on it.

I think you can consider also adding __init__.py to examples/falcon

I think you can consider also adding init.py to examples/falcon

Yeah, probably should but in a different PR. We don't lint examples today.


chore(): add tslint.json

R: @robertmesserle @hansl @kara
I based the rules on Google's style guide for JS and from my own preferences. Let me know if you disagree with something.

LGTM

Line length 100, please. LGTM

Added "max-line-length": [true, 100]


Supress the consent screen in the web journey

The self service admin tool provisions clients with consent required = true. This needs setting to false to suppress the additional consent screen in the web journey.

the defaulting is being done by the API that is called by the self service tool so it needs fixing there to avoid having to manually update the configuration


[C++][Parquet] Review logic around automatic assignment of field_id's

At schema deserialization (from Thrift) time, we are assigning a default field_id to the Schema node based on a depth-first ordering of notes. This means that a round trip (load, then write) will cause field_id's to be written that weren't there before. I'm not sure this is the desired behavior.
We should examine this in more detail and possible change it. See also discussion in ARROW-7080 https://github.com/apache/arrow/pull/6408
Reporter: Wes McKinney / @wesm
Assignee: Weston Pace](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=westonpace) / @westonpace
PRs and other links:

GitHub Pull Request #10289

Note: This issue was originally created as PARQUET-1798. Please see the migration documentation for further details.

Antoine Pitrou / @pitrou:
Issue resolved by pull request 10289
https://github.com/apache/arrow/pull/10289

Weston Pace / @westonpace:
FYI for those following the issue.  @pitrou has suggested removing the auto-generation altogether.  If there is no need / request for it I will go ahead and do so.

Weston Pace / @westonpace:
Is there something wrong with the generation algorithm?  Or is it more that there is no way to override the generation algorithm to use existing field IDs?
For example, it would be pretty straightforward to use the existing algorithm when going from Arrow->Parquet if no field id exists in the Arrow metadata.  On the other hand, the field ID algorithm could be updated so a column name (or column path for nested columns) will always generate the same ID (unless there are multiple columns with the same name).
Does the following make sense (independent of which generation algorithm we use):

Parquet -> Arrow
* If field_id is set use that
* If field_id is not set use generation algorithm
Arrow -> Parquet
* If field_id is set use that
* If field_id is not set use generation algorithm

That should be round-trippable since all subsequent read/writes after the first re-use existing field_ids.


Fix 'Config Your App' example config

The yaml example and json example is said to be the same, but defines components with different names. Yaml file defines main while JSON file defines frontend.
In the break down, there is again a mixture of the two component names. It states that frontend is defined, but in the example url for the component, it again referres to main.  According to what we learned in chapter Radix Concepts the url is built up from the component name, and since frontend seems to be the 'winning' component name in the example, the url should reflect that.

Thank you for the contribution @vegar!


Add nplusone and pytest-pythonpath Python packages

Motivation for this change
Add the nplusone Python package, which is a dependency of Faraday.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

I didn't fully undertand the suggestion about the commit messages. Right now, all commits are using the <pkg-name>: <subject-line> convention:
$ git log master..nplusone --reverse --oneline
95027da5267 pythonPackages.pytest-pythonpath: init at 0.7.3
9128e87de66 pythonPackages.nplusone: init at 1.0.0
5dfa72af62d pythonPackages.pytest-pythonpath: cosmetic changes
a5ac33d7b13 pythonPackages.nplusone: don't use patches

Did you mean I should squash 5dfa72af62d and a5ac33d7b13 into the previous commits so we only have the init at ... commits?

I meant that the fixup commits should be squashed into their respective package addition commits

I meant that the fixup commits should be squashed into their respective package addition commits

Done, thanks for clarifying!


Add multi-language support. Fix minor typo.

Suggest move the menu page to Edit post menu. Give the priviledge to role editor.
Suggest rename this project to something like Wechat2Wordpress
同步有双向的意思，我开始理解反了，以为是WP同步到微信，哈哈。
项目做得很好！谢谢！
期待更好的操作界面

There is a debian package called getext, which provides msgfmt command line utility. msgfmt can convert .po file to .mo file.

Please do not use master branch to open the PR. I will close it now.

方便的话加个微信吧。搜1285370731加我
因为hotmail, github太慢，不常看
有些想法关于这个项目。

做成通用的采集。不只针对微信，还可包括美篇，其它网站这些。根据采集链接的域名来配置采集规则，采集界面尽力简化统一，只需输入采集链接，程序分析域名，取出对应的采集规则，自动采集。
增加是否下载图片的选项。因为服务器空间比较宝贵，美篇，秀米这些网站上的文章都用模板，模板中就含有大量图片，文章多的话，空间占用就很可观
有些文章很难采集，因为带着一大堆的js, css。比如秀米做的H5动画。最好增加一个iframe的采集方式，直接把原始文章链接放到iframe里
这个插件做得好的话，可以火起来。以后以插件为基础，帮人定制一下，可以赚点小钱。至于其它商业模式，插件做火了以后，也许能够发现

From: 赵丰 (Zhao Feng<EMAIL_ADDRESS>Sent: March 7, 2020 2:19 PM
To: zhaofeng-shu33/synchronize_wechat<EMAIL_ADDRESS>Cc: tangmeng09<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [zhaofeng-shu33/synchronize_wechat] Add multi-language support. Fix minor typo. (#7)
Closed #7https://github.com/zhaofeng-shu33/synchronize_wechat/pull/7.
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/zhaofeng-shu33/synchronize_wechat/pull/7?email_source=notifications&email_token=ACHZOJE2NDBICFWJIVNV3DTRGKM2RA5CNFSM4KY3AXR2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOXE7T3AI#event-3107929473, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACHZOJB6MSLI5DLF4FPGTQ3RGKM2RANCNFSM4KY3AXRQ.

There has already been general "collecting" plugins, some of which are commercial. I do not oppose Pro version of software. But I do not have much time to add new big features to this plugin. You can reconsider it.
As for "Adding whether the user chooses to download images", you can make a PR. I think it is not difficult to implement.
I do not like using wechat to discuss  tech issues. You can contact me in slack for instant message.
For some articles with H5 for example, I do not oppose to use iframe, but I have no idea how to implement.

Well, time is worth to spend on valued things, or suppose to be valued things. 🙂
It's hard to say how can we spend time and get reward.
I have some customers of pre-education teachers. So I have a little free time before the semester starts.
I think most of the common collection plugins are too complex. Their users are the owner of the website. Not the contributor, author or editor of the website. This might be a chance, if we have a very easy to use plugin.
From: 赵丰 (Zhao Feng<EMAIL_ADDRESS>Sent: March 20, 2020 12:26 AM
To: zhaofeng-shu33/synchronize_wechat<EMAIL_ADDRESS>Cc: tangmeng09<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [zhaofeng-shu33/synchronize_wechat] Add multi-language support. Fix minor typo. (#7)
There has already been general "collecting" plugins, some of which are commercial. I do not oppose Pro version of software. But I do not have much time to add new big features to this plugin. You can reconsider it.
As for "Adding whether the user chooses to download images", you can make a PR. I think it is not difficult to implement.
I do not like using wechat to discuss tech issues. You can contact me in slackhttps://join.slack.com/t/lab2c/shared_invite/enQtODQyMTY4OTcyNTMwLWRkOTlkYmM2MWI3NGYzOWMwYTRkYzEzMTBjNjcxMWMxNTMxZjg2N2U1YzE5ZjI4YTE3ZTQ2ZWU2YzEyODNmMmU for instant message.
For some articles with H5 for example, I do not oppose to use iframe, but I have no idea how to implement.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/zhaofeng-shu33/synchronize_wechat/pull/7#issuecomment-601533222, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACHZOJGMK66K35V74ERIRITRILV5VANCNFSM4KY3AXRQ.

Thanks for your comment.


Add in transitive reduction function to remove more unnecessary edges from target graphs

@benedictpaten, is this still needed?

No, not going this direction anymore.
Benedict
(from phone, forgive extra typos)
On Nov 18, 2016 3:53 PM, "Hannes Schmidt"<EMAIL_ADDRESS>wrote:

@benedictpaten https://github.com/benedictpaten, is this still needed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/BD2KGenomics/toil/issues/126#issuecomment-261672553,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMXKjqqU1rHHHxWm3SimMZr1J9Rc2DoIks5q_jqJgaJpZM4FNTSH
.
--
You received this message because you are subscribed to the Google Groups
"cgloud-jenkins" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to<EMAIL_ADDRESS>To post to this group, send email to<EMAIL_ADDRESS>To view this discussion on the web visit https://groups.google.com/d/
msgid/cgloud-jenkins/BD2KGenomics/toil/issues/126/261672553%40github.com
https://groups.google.com/d/msgid/cgloud-jenkins/BD2KGenomics/toil/issues/126/261672553%40github.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


Checkpoints are not being saved

Hi,
While config.yml files are created in the correct locations, checkpoints are not being saved. Training is running fine but cannot view previous runs.

The nerfstudio_models directory is not being created.
Any help would be appreciated!
thank you!

Right now we don't save any checkpoints. I'd recommend forking the code to add this feature. PRs are also welcome!

Closing this!


Embed YouTube on click

Right now, YouTube links show a clickable thumbnail that open a new tab.
Instead, on click we could replace the thumbnail by its embeded iframe.

Done.


Add instrumentation for Guava caches

Is there any chance this patch will be accepted? We would appreciate it.

One of the reasons I removed metrics-guava was because I didn't think it added enough value. We use Guava's cache functionality quite a bit, so I'm still interested in a solution, but this isn't it. I've added #167 to track that.


Dependent accounts and booking on-behalf-of

Requirements
Dependent accounts
The membership proposal already covers the basic creation and linking of Customer Accounts. This works well for the case when the account holder has an email address and is able to use the Broker interface themselves.
However for scenarios where the Broker system is being used on behalf of children and other adults, there is no mechanism for creating Customer Accounts for these individuals.
Additionally some Sellers might require that new junior accounts are linked to an adult account.
Specific use cases include:

Junior walk-ins: where an adult seeks to create an account on behalf of a child, such that the child can be provisioned a physical card that can be used to walk-in to a Leisure Centre to access e.g. Free Swimming.
Accounts for children under e.g. 8 years old: where an operator such as Everyone Active might require the accounts to be linked to an adult account.
Accounts for juniors that have a monthly paid membership (e.g. "Better Health Junior"), but where the account holder does not have an email address of their own.

Observations:

Google allows Gmail accounts to be created at any age (accounts must be supervised by their parents for children under 13), so it is possible for anyone to have an email address and therefore have their own account. This should be considered in any UX design.
Junior memberships with direct debit are available from age 11 in most operators.

Booking "on behalf of"
Allowing one individual to book on behalf of another.
Specific use cases include:

When one member of a family wants to book on-behalf-of the rest of the family (e.g. the family go swimming, or attend fitness classes together), and make use of the memberships that different family members have.
Friends who regularly participate in an activity together booking on behalf of each other (e.g. attend fitness classes together), and make use of the memberships that they each have.
Adult wants to book on behalf of a child, using the child's membership.

Payments are out of scope of the specifications and handled by the Broker, so the focus of this proposal is on how the booking is achieved.
Concept Options for Dependent accounts
Options are presented below. The last of these is recommended by this proposal.
1) Model full groups and permissions
Different booking systems have different internal models of linking Customer Accounts. One approach is to attempt to create a flexible abstraction from these models, and expose that to the Broker.
For example, by modelling groups similar to WhatsApp groups, or YouTube brand accounts. This attempts to abstract the Booking System's own groups model and permit the Broker to access and update it.
GET /customer-account-groups/0
POST /customer-account-groups/0/members
POST /customer-account-groups/0/owner
POST /customer-account-groups/0/administrators
POST /customer-account-groups/0/invites
DELETE /customer-account-groups/0/owner?id=
DELETE /customer-account-groups/0/administrators?id=
DELETE /customer-account-groups/0/members?id=
DELETE /customer-account-groups/0/invites?id=

Advantages

Secure and GDPR compliant
Any group membership between accounts in the Broker is reflected
implicitly describes permissions for who can book for who

Disadvantages

When the Broker connects to multiple Booking Systems they will need to reconcile not just access, but membership of multiple groups across multiple systems - which is a non-trivial UX challenge and could be quite confusing for the user
It also presents challenges when groups on the Booking System do not fit the model
This doesn't explicitly resolve the issue of dependent accounts, though they may exist and be managed within the group

2) managedBy model for dependent accounts
Rather than attempting to abstract the group model, this approach only abstracts concept of the "owner" of the dependent account.
This means that the Broker is able to add "subaccounts" to the primary authenticated accounts that has been linked, using the OAuth token of the primary account.
E.g. managedBy must include only the current customer account, to simplify implementation, and make the intention explicit.
This Customer Account is accessible only via the OAuth2 keys for the managedBy accounts listed
The result of the endpoint below are similar to initialisation, and the account is created with permission to the Broker from a bookings perspective
POST /customer-accounts

{
  "@context": "https://openactive.io/",
  "@type": "CustomerAccount",
  "managedBy": [
    {
      "@type": "CustomerAccount",
      "@id": "https://eg.com/customer-accounts/fdc14503-275e-46d3-9922-45b986c9f9aa"
    }
  ],
  "customer": {
    "@type": "Person",
    "email"<EMAIL_ADDRESS>    "telephone": "020 811 8055",
    "givenName": "Geoff",
    "familyName": "Capes",
    "birthDate": "1970-01-01",
    "gender": "https://schema.org/Female",
    "address": {
      "@type": "PostalAddress",
      "streetAddress": "Raynes Park High School, 46A West Barnes Lane",
      "addressLocality": "New Malden",
      "addressRegion": "London",
      "postalCode": "NW5 3DU",
      "addressCountry": "GB"
    },
    "emergencyContact": {
      "@type": "Person",
      "name": "Ralph Capes",
      "telephone": "020 811 8055"
    }
  }
}

Advantages

Secure and GDPR compliant
Any group membership between accounts in the Broker is reflected
implicitly describes permissions for who can book for who

Disadvantages

Assumes that the managedBy parent/child model maps cleanly onto the model used within the Booking System. This approach may be confusing to users if this is not the case.
When the Broker connects to multiple Booking Systems they will need to reconcile not just access, but managedBy accounts across multiple systems. This is simpler than reconciling groups, but will still a significant UX challenge and still could be quite confusing for the user
Might be confusing to the user in terms of how they actually log into these created accounts in the Booking System itself, for example to resolve an unpaid debt or upgrade a membership. The accounts are created "behind the scenes".
Requires additional consideration to handle when an account is no longer managedBy (e.g. child comes of age, and no longer wants to be connected to their parent's account), as access is via the parent's OAuth token. For example: "It looks like the account for Little Jonny with Everyone Active is no longer linked to Mary. Please either create a new account for Jonny, or if Jonny has an email address and password, log in with his account". This could be confusing to the user.
Also may require consideration for allowing dependent accounts to move to different primary accounts.

3) Broker managed child accounts
To remove the need to synchronise any relationships with the Booking System, the Broker could exclusively manage dependent accounts.
This approach allows the Broker to create dependent accounts that are not connected to any primary account, but instead are managed entirely by the Broker.
Advantages

Secure and GDPR compliant
Simply allows the allocation of barcodes
Removes issues around reconciling accounts between multiple Booking Systems, as the accounts are simply duplicated

Disadvantages

Does not work for cases where the dependent account is upgraded to a monthly membership (it is duplicated, so which account is upgraded?)
Creates duplicate accounts in the booking system

4) Dependent accounts are handled within the OpenID Connect Flow (Recommended)
To get around the need for the Broker to model dependent accounts, simply put the dependent account creation step within the OpenID Connect flow.
For example by the following additional parameters:
allow_delegation=true
allow_signup and allow_delegation may not be used together, as they specify the mechanism by which a new account is created. allow_signup should be used for the primary Broker account, whereas allow_delegation should be used for all subsequent accounts. This encourages best practice of the authenticated user being the actual user, while allowing for legacy accounts that require the actual user to use another user's credentials.
At least one primary account should have been successfully linked to the Broker in order for allow_delegation to be used. It is expected that the Booking System persists the authenticated session in a cookie so that the user does not need to log in to the Booking System again.
For compatibility with Booking Systems that require an email address for each account, an additional parameter delegation_email_hint is provided, which can optionally be used by the Booking System to inform the user of the email address that is being used to create the account. For such systems this may default to the authenticated user's email address, if the delegation_email_hint is not provided.
Additionally a parameter of delegation_name_hint allows the UI of the Booking System to display the name of the Broker account to be linked, to help signpost the user appropriately.
When a user is created via allow_delegation, the email address is optionally set via initialisation, and the email field is not required.
An illustration of the allow_delegation flow can be seen in the screenshot below. Note the middle screen would be skipped if the primary account was already logged in, e.g. if they had linked an account previously.

Note to facilitate this flow, the primary account must also set a password when created as a new user via the standard flow.
An example of a delegated account creation screen within a system that requires email address for each account is as follows:

Advantages

Secure and GDPR compliant
No additional endpoints required, only a small addition to the OAuth flow
Flexible as allows different grouping or dependent management models to be presented to the user by the Booking System using the Booking System's native rendering. This should should make it easier for the user to log into the Booking System directly, and understand what accounts are being created where.
Removes issues around reconciling accounts between multiple Booking Systems in a consistent way - every account must simply be individually "linked", whether it is an primary or dependent account.
OpenID Connect tokens will survive the primary and dependent accounts being separated, which removes the need to handle this scenario.
More easily allows the user to log in an existing account with an email address, instead of creating a new delegated account, which reduces issues around potential account duplication.
Moving dependent accounts between primary accounts can be performed within the Booking System independently of the Broker.
Does not add any unnecessary constraints to the Booking System.
The same OpenID Connect flow is used, which can be designed to avoid duplicate account creation.
Deleting dependent accounts is handled by the Booking System rather than the Broker.
Similar to the concept of Netflix profiles within accounts, so likely to be familiar.
Encourages best practice of the actual user only authenticating as themselves rather than requiring them to share passwords with others, which allows multi-factor authentication to be supported in future if required.

Disadvantages

Does not allow "auto-matching" or "prepopulation" of dependent accounts across systems with the Broker's accounts. Each dependent account needs to be linked one at a time for each Booking System. Although auto-matching would still require reconciliation for cases where the data in systems does not match exactly, so prepopulation is likely to mostly be a complex process anyway.

Concept Options for Dependent accounts booking "on behalf of"
Options are presented below. The last of these is recommended by this proposal.
1) Consent synchronisation
In this approach, the consent for users to book on behalf of each other is synchronised between the Broker and the Booking System, for example:

POST /booking-on-behalf-of/invite to send an invite
PUT /my-invites/invite to accept an invite, which provides "book on-behalf-of" consent

Alternatively, the /accept endpoint only exists on the accounts that are offering access to their personal data, in order to minimise the number of API calls.
If not applied as part of Option 1 above ("Model full groups and permissions") then this would require e.g. one API call for each member of a group.
Advantages

Secure and GDPR compliant
Allows permissions to be used with the Booking System/Broker, which may reduce the need for a user to provide the same permission in multiple places.

Disadvantages

Requires a group/permissions model to be synchronised between Broker and Booking system
Permissions model may differ between Broker and Booking System, which may not make this initiative the user if one change affects the other unexpectedly
Many API calls required
Does not offer security advantages over Option 2 from a "Broker trust" perspective, as the Broker is still trusted to set the permissions

2) Broker has full authority to make bookings (Recommended)
In this approach, the Booking System allows any accounts that have granted permission to a particular Broker to be used as the subject of an "on-behalf-of" booking.
This is achieved by the Broker simply specifying the @id of any connected Customer Account as the attendee of a booking.
For security, attendee details are not included in the response from C1/C2/B, and must be dereferenced by the Broker if required. The customer details are still included in the response from C1/C2/B, as the customer is always based on the authenticating API key.
For security, an additional /connect/revocation endpoint is required to allow the Customer to explicitly disconnect from the Broker (rather than simply forgetting its authentication tokens). Implementation of this endpoint is also best practice, so it might be helpful to make this explicit in the specification.
Advantages

Secure and GDPR compliant
Simple implementation and low complexity, as it does not require group or permissions synchronisation between the Broker and Booking System
Flexible to accommodate a wide variety of different consent models within the Broker

Disadvantages

"Book on-behalf-of" consent is not communicated to the Booking System from the Broker, and therefore the same consent may need to be expressed separately within the Booking System.
The Broker must be trusted to use this feature in a way that tracks and respect a user's "book on-behalf-of" consent is respected. Use of this feature may require the Seller to audit the Broker to ensure they have implemented such permissions correctly.

Thanks Nick, very comprehensive write up of the potential solutions.
I must admit that I haven't had a chance to go through all of the proposed solutions with a fine toothed comb, but I'm not sure that will even be necessary if we can go through some of the required use cases and apply them to the recommended solution on one of the calls?  IE, take as an assumption that the recommended solution is the right one, and then work through the use cases to figure out exactly and technically how they would work, and to confirm then that there are no GDPR or duplication (which seem to be the major sticking points) issues.
The use cases you have listed are:
For dependent accounts:

Junior walk-ins: where an adult seeks to create an account on behalf of a child, such that the child can be provisioned a physical card that can be used to walk-in to a Leisure Centre to access e.g. Free Swimming.
Accounts for children under e.g. 8 years old: where an operator such as Everyone Active might require the accounts to be linked to an adult account.
Accounts for juniors that have a monthly paid membership (e.g. "Better Health Junior"), but where the account holder does not have an email address of their own.

For booking on behalf of:

When one member of a family wants to book on-behalf-of the rest of the family (e.g. the family go swimming, or attend fitness classes together), and make use of the memberships that different family members have.
Friends who regularly participate in an activity together booking on behalf of each other (e.g. attend fitness classes together), and make use of the memberships that they each have.
Adult wants to book on behalf of a child, using the child's membership.

I think it would be useful to go through the process in a "simple" use case (parent creates child and wants to book a slot on behalf of that child, or set the child as the attendee) and a "complex" use case, and given that the free swimming one is the most contentious one, I think it would be helpful to go through that one in detail.  IE, how that would work both in the case where the parent and the child already have an account with the booking system, and in the case where neither of them do and are just signing up via the broker.  How does that all work from a technical standpoint?  That would help me to get a better understanding of the technical implications and might shake out any issues.
One thing I did notice was this comment:

Note to facilitate this flow, the primary account must also set a password when created as a new user via the standard flow.

IIRC, the ability to skip that requirement had some very attractive advantages in the standard membership sign up bits - though I can't 100% remember what they were.  I think it simplified things as it allowed the user to create the account with the booking system and the understanding would be that to log in they would follow the standard password reset process in the booking system and off they go.  What are the modified implications on the booking system impl if this is no longer the case?

Thanks @matdavies! Your comment has prompted me to rethink the proposal above regarding passwords - the updated proposal above now removes the need for password setting.
Main implications of setting a password were that the user is being asked to set a few different passwords at once if they're hitting the OpenID Connect flow as part of a flow for registering to the Broker, which could be confusing. Additionally the previous proposal for (4) above required users to log out and log in when linking multiple accounts, which creates additional unnecessary steps for the most common use case (i.e. a young family or couple linking accounts together).
I've outlined the old proposal you commented on above below for reference, so we can focus on the issue above in the call shortly. We should be able to address your other comments on the call too.

4b) Dependent accounts are handled within the OpenID Connect Flow, without linking existing accounts
If we remove the ability to link existing accounts from Option 4 described above, then an illustration of the allow_delegation flow can be seen in the screenshot below. Note the middle screen would be skipped if the primary account was already logged in, e.g. if they had linked an account previously.

Note to facilitate this flow, the primary account must also set a password when created as a new user via the standard flow.

To facilitate the flow above when a user is expected to log out and log in to multiple accounts (for example when linking a whole family), it would likely improve the UX for the primary account creation screen to also set a password. This allows the user to log out of the account (for example to connect another account), then log in again to create a delegated subaccount within it, without needing to reset their password and check their email. An example primary account creation screen updated to reflect this is below:

Further considerations from the Technical Working Group call on 20/01/2020:
Dependent accounts
4) Dependent accounts are handled within the OpenID Connect Flow
Agreement that this should be the chosen way forward, with some considerations as below.
It is possible that a Booking System may implement account duplication checks, and therefore the account initialisation could fail if a duplicate account is found on the system.
Add a CustomerAccountDuplicateDetectedError to the initialisation call, to ensure that a mechanism exists for the Broker to inform the Customer of the error, and display an appropriate error from the Booking System. Additional wireframes could be added as guidance to show how error could be displayed by the Broker in the case that a duplicate is detected.
What if, within the booking system screens, a primary account attempts to link another primary account that already has its own child accounts:
This scenario can be handled within the OpenID Connect Flow, with a flow determined by the Booking System depending on what makes the most sense within its context. A recommendation is that the "Link accounts" list of the second primary is simply presented to the user when they attempt to link, for the user to select the second primary or any dependent of that primary to link to the Broker.
Note: Guidance in spec should recommend avoiding requiring the primary to log out at any point as part of any common user journey, as the primary may not necessarily have set a password and would have to reset it to log back in.
What if more than one of the parents can be a primary within the Booking System?
This can be handled within the OpenID Connect Flow, with a flow determined by the Booking System depending on what makes the most sense within its context. For example it might be possible to allow the user to select to make a user a "primary" account at the point that they are selected for linking within the OpenID Connect flow - i.e. perhaps when John is created or linked the UI includes a tick box saying "Allow this person to manage linked accounts" or similar. The proposal is flexible to allow any grouping model (single primary, multiple primary, multiple group, etc).
What about Customer Accounts for Organizations?
This can be handled within the OpenID Connect Flow, with a flow determined by the Booking System depending on what makes the most sense within its context. Organizations with sub-Organizations, Organizations with People within them, etc can all be handled provided the user can select a single Customer to link through its journey.
What about emergency contact details, do they need to be captured for each dependent account?
GLL and Everyone Active already capture contact details for each account separately, and there is no assumption that the relationship between accounts has any connection to the emergency contact details.
Booking "on behalf of"
2) Broker has full authority to make bookings
Is the user going to expect to be booked on behalf of, if they don't provide consent for it within the Booking System?
With all options relating to group synchronisation the Broker is already being given authority to link accounts, and trusted to obtain explicit consent from the Customer. Hence it is the Broker's responsibility to ensure that the Customer is clearly communicated to, and that they have have given explicit consent to enable "book on behalf of" within the Broker system between the relevant users.
Note: "booking on behalf of" permissions must be clearly communicated to the user when they connect their account, along with other permissions.
Are there any GDPR implications of this?
Personal data is not shared via "book-on-behalf-of" in the C1, C2 and B calls, so the Broker must have a valid access token to retrieve personal details for each attendee via the Get Customer Account Details call (in the same way as they would otherwise).
What price will the Customer pay if they are being booked by someone else?
The specification should clarify that the price is expected to be the same price a Customer would pay if they were to book themselves, including any member discounts.
Are there privacy concerns relating the case where an account that's being booked on-behalf-of is banned, has debt, etc.?
For privacy, error messages for failed on-behalf-of bookings that require resolution via a change to the state of the target Customer Account MUST NOT include details of issues relating to that Customer Account (for example, a debt or ban on the account). Such errors at C1/C2/B MUST be generic using the BookingOnBehalfOfError OrderItem error ("A booking could not be made on behalf of this account at this time"), and the resolution MUST be described in an outstandingAction available on the target's Customer Account via their own access tokens. This ensures that debt, bans, etc are issues that remain private to each Customer Account.


Folder table header has inconsistent coloring upon switching themes.

Explain the bug
When switching from dark to light mode and vice versa, the "Details View" table header changes color to either pure white or pure black, which then goes away upon hovering the mouse over it. This also appears to have an effect on the sorting arrows (for sorting by ascending/descending) present in the header, which persists until the app is relaunched.
To reproduce

Switch to "Details View" and open a folder.
Go into settings and change the app theme.

Expected behavior
The header should use the correct coloring upon the theme being switched.
Logfile
Not relevant.
Screenshots
https://user-images.githubusercontent.com/42101043/112924129-34035700-90d5-11eb-93e0-382384ff4a0b.mp4
System Information

OS Version: Windows 10 Dev (21332.1000)
App version: <IP_ADDRESS>

Additional comment
None.

Thank you for opening this issue, it's something we would like to resolve but we are held back because the DataGrid control is outdated. WinUI is planning to create a new DataGrid control, I am linking the discussion here so you can upvote/comment on the issue and hopefully increase the priority for Microsoft. https://github.com/microsoft/microsoft-ui-xaml/issues/1500

This issue should be resolved in main.


New package: StochasticBlockModel v0.1.0

Registering package: StochasticBlockModel
Repository: https://github.com/BSAraujo/StochasticBlockModel.jl
Created by: @BSAraujo
Version: v0.1.0
Commit: 562b29da7e5232b3f5b1b9e1aed15f458ad54b9e
Reviewed by: @BSAraujo
Reference: https://github.com/BSAraujo/StochasticBlockModel.jl/issues/1

Do you want to add the bounds? https://github.com/bcbi/CompatHelper.jl might be of interest. [noblock]
Also, you probably don't want/need SafeTestsets as a dependency.

Thanks for your help.
I have installed CompatHelper as you suggested and added the bounds on the packages Distributions and GLPKMathProgInterface. I have also removed SafeTestsets from the dependencies. I believe it is OK now. I should now open a new issue from the most recent commit, right?
[noblock]


Use uniform batch scripts

Use uniform batch scripts as presented in https://starcounter.gitbooks.io/guidelines/content/batch-files.html
Discussion: https://github.com/Starcounter/Guidelines/issues/6

According to the discussion linked above, make.bat and restart.bat should be removed.

Some projects output the exe files to ./bin/Debug instead of ./src/<appname>/bin/Debug.
The latter form is expected (see https://starcounter.gitbooks.io/guidelines/content/project_structure.html)
If this solution does not output the exe files to the desired paths (both in msbuild and in VS), please fix that immediately too.

Created PR https://github.com/StarcounterApps/Content/pull/21

Closing as done

Done in https://github.com/StarcounterApps/Content/pull/22


Debug mode for app to verify blockerList.json before push

@hansbobby @hanstzou
I've added blockerList.json to the project. Build the app with DEBUG configuration and the content blocker extension will load the file rather than download it from GitHub.

For details, see BlockerListLoader.swift


Find and Replace box show empty Find input after select the whole word

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

VS Code Version: 1.74.2 (Commit: e8a3071ea4344d9d48ef8a4df2c097372b0c5161)
OS Version: Ubuntu 22.04.1 (Wayland), Ubuntu 20.04.5 (X11), Windows 10 22H2 19045.2364

Steps to Reproduce:

Open VS Code with already opened tab.
Add Selection To Next Find Match using Ctrl + D.
Use Find Ctrl + F or Find and Replace Ctrl + H.
The box still shows the results, but the Find input is empty.

@daoducminh can you please share your editor find related settings to help troubleshoot?

@rebornix Sure. But I'm using default settings for Editor > Find.

Also, I downgrad to 1.73.1 and face this issue.

Hey @rebornix, this issue might need further attention.
@daoducminh, you can help us out by closing this issue if the problem no longer exists, or adding more information.

Hey @rebornix, this issue might need further attention.
@daoducminh, you can help us out by closing this issue if the problem no longer exists, or adding more information.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Mistranslation of Top Page in Japanese

Gitea version (or commit ref): All
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[X] Not relevant

Log gist:

Description
Top page slogan in Japanese is awful mistranslation. Native Japanese speaker never writes such a phrase. Well, for example:
'A painless, self-hosted Git service' must be '手軽で簡単な、自分でホストする Git サービス'.
And why lower part of screen isn't translated? If you can tell me what file to modify, I can do it.
Screenshots

Please send a PR to fix it.

The template is: https://github.com/go-gitea/gitea/blob/master/templates/home.tmpl, however these translations should be modified by the crowndin tool if you want to submit the fixes there: https://crowdin.com/project/gitea

I look into them but I couldn't find such phrases on top page...

https://crowdin.com/translate/gitea/68/enus-ja#q=App_desc

Thanks @zacheryph , I fixed it.
BTW, please tell me where I should re-translate lower part of top page.

Search for startpage in crowd-in:
https://crowdin.com/translate/gitea/68/enus-ja#q=startpage
And work through those.

Oh sorry, I lost sight of pagination. Thanks @zacheryph


Fixing bug parsing ReportsEntryPoint CLI

What is the change?
When users use the ReportsEntryPoint CLI, they can pass in various integers. The CLI parser here never converts the CLI strings to integers, leading to an error if you use them.
(Oh, also, I had to add a couple of things to the .gitignore file, and in the process realized it wasn't alphabetized. So that is quite a dizzying diff to read. Sorry.)
Why is the change being made?
To close #1816

Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify any new/changed code.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[x] The release notes have been updated if necessary.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in pyproject.toml.

The bug fix and unit tests for the report entry point looks good to me. Some of the changes appear unrelated to this bug fix, at least on the surface. The specific files that seem possibly unrelated are:

test_reactors.py
mathematics.py
doc/conf.py

Were these changes intended to be included? And if so, how do they relate to the reports entry point?

Were these changes intended to be included? And if so, how do they relate to the reports entry point?

Whoops! The last commit was to the wrong branch. One sec, I'll revert that.


[Artwork] Adds Auction pending registration metadata to the Artwork View

We now need to be able to let someone know if they can bid, and whether they are pending a registration. This is 1/2 dealing with the outside live context.
Sidenote: The GraphQL ArtworkVC can't come fast enough:
        [OHHTTPStubs stubJSONResponseAtPath:@"/api/v1/related/sales" withResponse:@[
            @{
            @"id": @"some-auction",
            @"name": @"Some Auction",
            @"is_auction": @YES,
            @"start_at": @"2000-04-07T16:00:00.000+00:00",
            @"end_at": @"2020-04-17T03:59:00.000+00:00",
            @"auction_state": @"open",
            @"published": @YES,
        }]];
        [OHHTTPStubs stubJSONResponseAtPath:@"/api/v1/me/bidder_positions" withParams:@{
            @"artwork_id":@"some-artwork",
            @"sale_id":@"some-auction"
        } withResponse:@[]];

        [OHHTTPStubs stubJSONResponseAtPath:@"/api/v1/me/bidders" withResponse:@[
@{
             @"qualified_for_bidding": @NO,
             @"id":@"asdada",
             @"sale": @{ @"id" : @"some-auction", @"require_bidder_approval": @YES },
        }]];
        [OHHTTPStubs stubJSONResponseAtPath:@"/api/v1/sale/some-auction/sale_artworks" withResponse:@[]];
        [OHHTTPStubs stubJSONResponseAtPath:@"/api/v1/sale/some-auction/sale_artwork/some-artwork" withResponse:@{
            @"id": @"some-artwork",
            @"sale_id": @"some-auction",
            @"bidder_positions_count": @(1),
            @"opening_bid_cents": @(1700000),
            @"highest_bid_amount_cents": @(2200000),
            @"minimum_next_bid_cents": @(2400000),
            @"highest_bid": @{
                @"id": @"highest-bid-id",
                @"amount_cents": @(2200000),
            }
        }];
        [OHHTTPStubs stubJSONResponseAtPath:@"/api/v1/artwork/some-artwork"
            withResponse:@{ @"id": @"some-artwork", @"title": @"Some Title" }];
        [OHHTTPStubs stubJSONResponseAtPath:@"/api/v1/related/layer/synthetic/main/artworks" withResponse:@[]];

Looks good! GraphQL will save us all.


This tool is really great, thanks.

This tool is really great, thanks.
However, if replicas exist for the service you are trying to overwrite, the tool fails.
Either you'd have to locate the replicas and unregister them - or you'd have to delete the service and the sd file and create the Feature service again (with it's original name).
Quite often sync is only used in these services to be able to take them offline on Collector app, but with no intention to do edits.
Could the script be altered to take care of this scenario where replicas exist?
Best Regards

I dont have a lot of knowledge in the sync/replica area, so a question to you:
How would you handle this case, or expect it to be handled?

Force the delete (but doing so will be like starting fresh, so any apps that hold the itemID reference will break)

Do some search to unregister replicas, and I guess after updating, turn them back on?

Error message for this case, telling the person running the script about the problem and letting them take appropriate action

other?

Kevin,

For this case, where the Sync parameter is only used, because it has to be there to take the map offline, I think deleting and creating the service again with exactly the same name and settings will work fine.
It's correct that the AGO element-ID and the service ItemId is changed, but the REST-URL remains the same and apparently this is all that the webmap needs to keep track of the layers. Meaning that you can drop the old offline map on your Collector app and take the new map offline. Note that this wont work if the plan is to edit the services data in the field, since the replica is gone.

If it's possible to delete all the replicas on the service through a script and run this as the first part of the update service script, that could do the job nicely. I don't think you can reestablish the replicas afterwards, but not needed anyway since you're not going to edit data.

An error message is better than nothing, but still the person would then have to do some manual tasks.

thanks,
Søren

After discussion, the proper thing to do is simply throw a message that sync has been enabled, replicas exist and quit. Its not correct to have the script simply destroy/ignore the existing replicas.
This workflow replaces the entire data inside the service. This practice directly conflicts with edits/replicas workflow.  If sync + replicas are used in your environment this workflow doesn't really fit with that. This conflict needs of two competing workflows needs to be resolved outside this script. (ie. discussion within your organization with a plan on how you'll updating data moving forward with one of these workflows, not both)

Kevin,
Thanks for looking into this.
I agree it is not a good solution to just overwrite a service with replicas.
However that is what is needed in this particular case, so we’ll have to carry on with a manual workflow.
Rgds,
Søren
From: Kevin Hibma<EMAIL_ADDRESS>Sent: 23. marts 2016 16:02
To: khibma/update-hosted-feature-service<EMAIL_ADDRESS>Cc: Søren Tollund Christensen<EMAIL_ADDRESS>Subject: Re: [update-hosted-feature-service] Issue when FS has a replica (#13)
After discussion, the proper thing to do is simply throw a message that sync has been enabled, replicas exist and quit. Its not correct to have the script simply destroy/ignore the existing replicas.
This workflow replaces the entire data inside the service. This practice directly conflicts with edits/replicas workflow. If sync + replicas are used in your environment this workflow doesn't really fit with that. This conflict needs of two competing workflows needs to be resolved outside this script. (ie. discussion within your organization with a plan on how you'll updating data moving forward with one of these workflows, not both)
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com/khibma/update-hosted-feature-service/issues/13#issuecomment-200384037


Crash when I try to use cesium-unreal

Hi there! Almost two weeks ago when I use the cesium-unreal to display my photogrammetry scene, but today, when I try to start a new ue4 project for my new scene, I found that no matter what I have done, the display is always nothing by using censium-unreal and ion, so I tried to change a project, use the old project, down the version to 1.11, change to the old 3dtiles and even with the ue5.
I have done with reinstalling whole UE or the plugin，nothing changed. I also tried to use other scene like CityPark in the marketplace, it shows fine.
Is there a solution？
Here are the screen shots：
all white after I add cesium sky（all black without sky but with the terrain）

crash report after I add a local tiles and the click it

normal for citypark or other project without cesium using

Here is the whole crash log：
And I found that I even don't need to add a local address，just double click could crash the ue4，the key problem also could be why the ion assets did'n display，the output log didnt give any error or warning when I add the terrain or sky to the world.
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000220
UE4Editor_CesiumRuntime!ACesium3DTileset::OnFocusEditorViewportOnThis() [D:\build++Portal\Sync\LocalBuilds\PluginTemp\HostProject\Plugins\CesiumForUnreal\Source\CesiumRuntime\Private\Cesium3DTileset.cpp:396]
UE4Editor_CesiumRuntime!TBaseFunctorDelegateInstance<void __cdecl(TArray<AActor *,TSizedDefaultAllocator<32> > const &),FDefaultDelegateUserPolicy,<lambda_da65987502ec0d657c9e0a63cfc48592> >::ExecuteIfSafe() [D:\RocketSync\4.27.0-17155196+++UE4+Release-4.27\Working\Engine\Source\Runtime\Core\Public\Delegates\DelegateInstancesImpl.h:839]
UE4Editor_UnrealEd
UE4Editor_UnrealEd
UE4Editor_SceneOutliner
UE4Editor_SceneOutliner
UE4Editor_SceneOutliner
UE4Editor_SceneOutliner
UE4Editor_SceneOutliner
UE4Editor_SceneOutliner
UE4Editor_SceneOutliner
UE4Editor_Slate
UE4Editor_Slate
UE4Editor_Slate
UE4Editor_Slate
UE4Editor_ApplicationCore
UE4Editor_ApplicationCore
UE4Editor_ApplicationCore
UE4Editor_ApplicationCore
user32
user32
UE4Editor_ApplicationCore
UE4Editor
UE4Editor
UE4Editor
UE4Editor
UE4Editor
UE4Editor
kernel32
ntdll

I'm not sure what's going on with the access violation, but the all white screen when you add CeisumSunSky is easy fix. You need to enable "Extend default luminance range in Auto Exposure settings" in the Project Settings, as explained in the Getting Started guide: https://cesium.com/learn/unreal/unreal-quickstart/#step-5-add-lighting-with-cesiumsunsky.

Actually I enabled, so that's the most confused thing.

I found that only I click run then I can see the sky and terrain, preview cannot show me the stuff, but what' wrong with the local tileset, click it will totally crash.

Are you on a remote desktop connection? You could be running into https://github.com/CesiumGS/cesium-unreal/issues/660
As for the crash... I'm not sure. Perhaps there's something wrong with the tileset prevening it from loading, and the plugin isn't handling the focus correctly for a broken tileset. I'd suggest keeping the Output Log open and see if anything helpful is printed there just before it crashes.

Finally，I am sure that the problem is the remote realtime rendering，shit bro thanks~


C029 Change ubuntu base image to bionic

This PR is missing any doc updates in the sysadmin guide or app developers guide for Ubuntu. It should mention that gnupg (or gnupg2 or gnupg1) needs to be installed.


ElementWrapper.filterFlattenedEnclosedElementTree is broken

There's an issue with that method. It internally uses filtering for enclosing Elements instead of Enclosed Elements.

Will be released with next version.