Unreliable triggering - Trace message "Stopped because maximum number of parallel runs reached at"

General information
I have noticed an inconsistent/ unreliable triggering of this automation and upon checking the "Trace Timeline" I was getting the following message: "Stopped because maximum number of parallel runs reached at XXXXXX"
Based on the documentation, the default # of parallel runs is 10 so I have updated the Blueprint to 30 which solved this issue:

Blueprint folder: /config/blueprints/automation/IATkachenko/full.yaml

Code change:
max: 30 #line added after "mode: queued" (line 199). The default is 10 as detailed in https://www.home-assistant.io/docs/automation/modes

Maybe others are facing the same issue and this simple change can be updated into the Blueprint. Thanks
Home Assistant
Version: 2023.6.3
Installation method (according to instructions):
[X] Operating System
[ ] Linux VM
[ ] Container
[ ] Supervised
[ ] Core
Integration

Installation method:
[X] HACS
[ ] manual from release
[ ] manual from git
Integration version:
Root topic:
Application settings

topic:
[X] I can see MQTT messages from application at MQTT-server
How it works now?

What do you expect?

Steps to reproduce

step-1
step-2
...

Debug log
Put Home Assistant debug log, related to the issue, here

Additional information

It is very strange error: blueprint does not run steps in parallel. Looks like choose action parsed as parallel action...
Thank you for report and workaround., will update blueprint.

Another thing that may be helpful to others: to allow the troubleshooting, I have also increased the number of traces from the standard 5 traces to 60. This covers the 50 I have in one night from "time_to_bed_alarm_alert" until "sleep_tracking_stopped"
Reference documentation: https://www.home-assistant.io/docs/automation/troubleshooting/#traces
Thanks for your great work and Blueprint. Much appreciated.

Could you check debug log from the integration. While firing new event it writes to debug log: Firing '%s' with payload: '%s', so we may check is the integration spam events or we have some issues while event processing itself.

This is what I get when filtering "Firing" in the logs:
Home Assistant Core
2023-07-01 22:05:00.650 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'time_to_bed_alarm_alert'}'
2023-07-01 23:57:07.872 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_paused'}'
2023-07-01 23:59:07.894 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_resumed'}'
2023-07-02 00:03:07.964 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 00:06:27.978 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 00:11:38.136 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'awake'}'
2023-07-02 00:14:08.149 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'not_awake'}'
2023-07-02 00:23:58.373 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 00:53:08.857 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 01:03:29.107 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 01:18:09.339 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 01:28:29.569 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 01:34:49.646 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 01:45:09.852 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 01:55:40.002 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 02:08:02.267 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 02:22:40.491 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 02:37:10.742 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 02:51:50.959 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 03:04:11.176 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 03:16:41.398 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 03:52:02.081 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 04:02:32.253 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'rem'}'
2023-07-02 04:12:52.424 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'rem'}'
2023-07-02 04:40:02.953 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 04:44:12.963 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 04:58:43.318 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 05:11:13.566 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 05:21:33.745 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'rem'}'
2023-07-02 05:32:04.483 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'rem'}'
2023-07-02 05:44:24.192 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 05:56:54.421 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 06:00:00.719 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'before_alarm'}'
2023-07-02 06:07:24.649 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 06:10:00.701 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'before_smart_period'}'
2023-07-02 06:15:44.873 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 06:19:54.812 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 06:22:14.937 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'awake'}'
2023-07-02 06:28:45.092 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'not_awake'}'
2023-07-02 06:40:35.357 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 06:44:45.435 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 06:55:15.677 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 06:55:46.214 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'alarm_alert_start'}'
2023-07-02 06:56:11.778 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'alarm_alert_dismiss'}'
2023-07-02 06:56:11.935 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_stopped'}'
2023-07-02 11:03:28.326 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_paused'}'
2023-07-02 11:05:28.368 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_resumed'}'
2023-07-02 11:07:02.534 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'alarm_alert_start'}'
2023-07-02 11:07:02.565 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'smart_period'}'
2023-07-02 11:07:58.660 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'alarm_alert_dismiss'}'
2023-07-02 11:07:58.700 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_stopped'}'
2023-07-02 11:14:32.093 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_started'}'
2023-07-02 11:14:32.194 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'smart_period'}'
2023-07-02 11:15:16.885 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_stopped'}'
2023-07-02 11:15:38.666 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_started'}'
2023-07-02 11:17:38.719 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_resumed'}'
2023-07-02 11:20:00.962 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'alarm_alert_start'}'
2023-07-02 11:20:29.533 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'alarm_alert_dismiss'}'
2023-07-02 11:20:29.673 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_stopped'}'
2023-07-02 22:15:00.174 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'time_to_bed_alarm_alert'}'
2023-07-02 22:18:00.155 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'time_to_bed_alarm_alert'}'
2023-07-02 22:20:00.207 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'time_to_bed_alarm_alert'}'
2023-07-02 22:44:25.957 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_started'}'
2023-07-02 22:44:26.185 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_paused'}'
2023-07-02 22:46:25.976 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_resumed'}'
2023-07-02 22:50:44.664 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'time_to_bed_alarm_alert'}'
2023-07-02 22:54:02.231 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 22:54:06.026 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 22:54:32.267 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 22:54:56.134 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'awake'}'
2023-07-02 22:55:02.334 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 22:55:32.393 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 22:56:02.380 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 22:56:32.436 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 22:56:56.219 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'not_awake'}'
2023-07-02 22:59:20.290 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 23:02:56.087 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 23:03:26.100 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 23:03:26.182 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'awake'}'
2023-07-02 23:03:56.122 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 23:04:26.223 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 23:04:56.235 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 23:05:26.233 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sound_event_talk'}'
2023-07-02 23:06:26.328 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'not_awake'}'
2023-07-02 23:08:56.204 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-02 23:13:26.428 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'awake'}'
2023-07-02 23:15:26.401 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'not_awake'}'
2023-07-02 23:25:36.429 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-02 23:56:00.199 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_started'}'
2023-07-03 00:02:30.293 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 00:27:30.522 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 00:40:00.610 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 00:44:10.634 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 00:58:40.796 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 01:48:41.283 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 01:59:01.399 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 02:11:31.514 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 02:17:41.598 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 02:21:51.578 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 02:32:21.737 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 02:46:51.886 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 02:57:22.008 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'rem'}'
2023-07-03 03:03:32.033 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 03:18:02.173 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 03:28:32.314 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'rem'}'
2023-07-03 03:41:02.498 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 03:43:02.413 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 03:51:22.506 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 03:53:32.567 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 04:03:52.641 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 04:08:02.725 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 04:22:32.845 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 04:43:23.030 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 04:53:53.139 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 04:57:53.112 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 05:08:23.287 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'rem'}'
2023-07-03 05:10:00.229 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'before_alarm'}'
2023-07-03 05:10:00.266 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'before_smart_period'}'
2023-07-03 05:18:43.337 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'rem'}'
2023-07-03 05:25:03.389 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 05:37:33.554 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 05:50:03.642 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 05:55:07.111 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'smart_period'}'
2023-07-03 06:10:01.074 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'alarm_alert_start'}'
2023-07-03 06:10:17.868 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'alarm_alert_dismiss'}'
2023-07-03 06:10:18.088 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_stopped'}'
2023-07-03 06:45:01.617 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'smart_period'}'
2023-07-03 07:33:05.938 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'Unknown'}'
2023-07-03 07:35:42.098 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_started'}'
2023-07-03 07:35:42.139 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'time_to_bed_alarm_alert'}'
2023-07-03 07:35:42.484 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_paused'}'
2023-07-03 07:36:26.680 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_stopped'}'
2023-07-03 22:10:00.507 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'time_to_bed_alarm_alert'}'
2023-07-03 22:20:58.852 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_started'}'
2023-07-03 22:20:59.240 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_paused'}'
2023-07-03 22:21:02.598 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'time_to_bed_alarm_alert'}'
2023-07-03 22:22:58.878 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_resumed'}'
2023-07-03 22:32:28.909 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 22:34:29.173 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 22:38:59.086 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'awake'}'
2023-07-03 22:40:59.075 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'not_awake'}'
2023-07-03 22:51:09.155 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 23:14:09.384 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 23:24:29.464 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-03 23:45:19.627 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-03 23:59:49.860 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-04 00:14:29.947 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-04 00:20:39.979 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-04 00:29:00.120 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-04 00:39:20.100 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-04 00:49:50.248 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-04 01:00:10.321 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'rem'}'
2023-07-04 01:06:30.367 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-04 01:40:01.785 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'awake'}'
2023-07-04 01:44:01.811 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'not_awake'}'
2023-07-04 02:00:40.897 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-04 02:33:51.166 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-04 02:44:21.256 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-04 02:46:21.274 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-04 02:56:51.415 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-04 04:07:32.086 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-04 04:17:52.152 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-04 04:26:12.322 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-04 04:40:52.360 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-04 04:51:12.466 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-04 05:01:32.522 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'rem'}'
2023-07-04 05:08:01.134 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-04 05:10:00.435 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'before_alarm'}'
2023-07-04 05:12:02.599 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-04 05:24:32.813 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'deep_sleep'}'
2023-07-04 05:47:22.982 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'light_sleep'}'
2023-07-04 05:55:06.440 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'smart_period'}'
2023-07-04 05:57:53.089 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'rem'}'
2023-07-04 05:58:07.213 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'alarm_alert_start'}'
2023-07-04 05:58:19.732 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'alarm_alert_dismiss'}'
2023-07-04 05:58:19.950 DEBUG (MainThread) [custom_components.sleep_as_android.sensor] Firing 'SleepAsAndroid_Client1' with payload: '{'event': 'sleep_tracking_stopped'}'

Looks fine, there is not a lot of parallel (even for one minute) events...
Have no idea why HA complains on maximum number of parallel runs...
ps. hint: you may turn off unnecessary events in the Sleep As Android application settings.

Looks fine, there is not a lot of parallel (even for one minute) events... Have no idea why HA complains on maximum number of parallel runs... ps. hint: you may turn off unnecessary events in the Sleep As Android application settings.

Thanks for the hint.  In SaA's Settings => Services => Automation => Events => I have unselected the events that I dont have any automation e.g. REM, Anti Snoring, Light Sleep, etc
I dont get more "Firing" entries in HA's log now:
Home Assistant Core
No issues found for search term 'Firing'


⚠ ClamAV has degraded performance

In 7d258ff, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 82 ms

Resolved: ClamAV performance has improved in 551eee5.


panic explanation could use some fleshing out

The first C program I wrote (on an DOS PC) took out the whole computer. Unix systems always behaved better, and only the process died with a segfault. Why is this worse than a Rust (or Go) program panicking? Because the panic happens when the original problem happens, not when the program has become hopelessly confused and eaten all your homework.

This is true, but it's not the root of the issue: the root is that panics don't introduce memory unsafety, nor undefined behavior. This means a panic can't cause a security issue in the same way a segfault can.

Yes, that was the intention - I must just make it clearer. I have lived through enough C++ segfaults to know the difference ;)


Custom Logger - Backend

Problem
Currently, in the old training service, we have a custom logger class here. This custom logger gives us color coded output in the terminal to clearly identify the error logs, info logs, etc using the logging framework in python.
Solution
Migrate this custom logger class to the Django backend.
Refer to these resources for approach

https://docs.djangoproject.com/en/4.2/topics/logging/
https://docs.djangoproject.com/en/dev/ref/django-admin/#syntax-coloring

Solved using logger


[Sema] Non-exhaustive switch statements are always an error in Swift 6.

Implements the amendment to SE-0192 described in https://forums.swift.org/t/amendment-se-0192-handling-future-enum-cases/68321.

@swift-ci please smoke test

@swift-ci please smoke test


Transitional synthax for 'Dict'

Adapt the construction of the Dict to a synthax that is compatible with
both julia 0.3 and 0.4. This avoids the startup warning
WARNING: deprecated syntax "[a=>b, ...]" at /Users/julian/.julia/v0.4/Markdown/src/render/terminal/formatting.jl:4.
in julia 0.4/devel.

Thanks for having a go at this, but I'm not sure if it's the right thing to accept it, since Markdown.jl doesn't officially support 0.4 anyway. In 0.4 you can just do using Base.Markdown to use the built-in Markdown parser (which is exactly the same code).
An easy way to do this would be
if VERSION < v"0.4-"
  using Markdown
else
  using Base.Markdown
end

This is now fixed in master via #23
https://github.com/one-more-minute/Markdown.jl/blob/ae6064d8d506efb0ad4ff6c87ff506d94efd51d6/src/render/terminal/formatting.jl#L5-L18


Remaining work needed to be completely free of CLI for install and setup process

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/789
Originally created by @dmor on 2019-07-15 15:30:02

In order to set up an AMI on Amazon that can be utilized by AWS users, we need to remove the remaining CLI steps.

[ ]  @mbergeron dogfood install and project setup process and identify any steps where you need to go back to the command line to complete the process
[ ]  @mbergeron write up issues for each major piece of corresponding remaining work and get started on these items (or delegate if they're frontend)

View 4 previous comments from the original issue on GitLab


Decide if we want to support Xcode 7.3.

We got a bug report, the code fails to compile with Xcode 7.3, which was released around 2015.  The problem is actually in the compiler (e.g. does not support thread_local), and will submit a workaround shortly.
We need to decide if the compiler is something we want to support long term, thus this bug to make us revisit the decision.

@devjgm @devbww I propose we remove the Xcode 7.3 build, but continue to accept patches if folks volunteer them (to a point, this is technically a pre C++11 compiler). Any thoughts?

I see no problem with dropping support for Xcode 7.x. It's quite old. My contacts in our Apple dev team tell me that Apple devs tend to update compilers (and xcode versions) quickly. Apple requires modern Xcode for distributing apps in their stores too. I believe our internal Apple team only supports the most recent version of Xcode and the latest release of the previous version. So, today, I think that would be 10.1 and 9.4.1. Of course, we may choose to support more Xcode versions that that, but if 7.x doesn't fully support C++11, then I support dropping it.

SGTM.

I just sent a PR to disable the Xcode 7.3 build.


Nuget release

Is there any plans to have a new nuget release created from master?

Yes, 2.0.11 is the latest release


SDWebImage randomly not showing in UITableViewCell

Hello I have a script that downloads an image and dynamically sets the UITableView height after it finishes the download, but some images randomly do not show , the curious think is that when i change back and forth the tab the images suddenly appear . in the options argument i am passing SDWebImageRetryFailed.
Any idea would be more than welcome , thanks.
-(UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath {
    item = [news objectAtIndex:[indexPath row]];
    cell = [tableView dequeueReusableCellWithIdentifier:@"FrontPageNewsCell"];
    [[cell newsTitle] setText:[item title]];
    [[cell newsVideo] setAlpha:0.0];
    if ([item newsImageURL]){
        descFrame = [[cell newsBody] frame];
        [[cell newsImage] setImageWithURL:[item newsImageURL] placeholderImage:[UIImage<EMAIL_ADDRESS>options:SDWebImageRetryFailed  completed:^(UIImage *image, NSError *error, SDImageCacheType cacheType){
            if (image) {
                CGRect newsImageFrame = [[cell newsImage] frame];
                float downImageWidth = image.size.width;
                float downImageHeight = image.size.height;
                float newsImageWidth = 304.00; //imageViewSize.size.width;
                if (downImageWidth > newsImageWidth) {
                    float scaleFactor = newsImageWidth / downImageWidth;
                    newWidth = downImageWidth * scaleFactor;
                    newHeight = downImageHeight * scaleFactor;
                } else {
                    newWidth = downImageWidth;
                    newHeight = downImageHeight;
                }
                newFrame = CGRectMake(newsImageFrame.origin.x, newsImageFrame.origin.y, newWidth, newHeight);
                [[cell newsImage] setFrame:newFrame]; //asigno el nuevo frame a la imagen .
                float newOriginY = newFrame.origin.y + newFrame.size.height + 10.00;
                descFrame = CGRectMake(cell.newsBody.frame.origin.x,
                                       newOriginY,
                                       304.00,
                                       cell.newsBody.frame.size.height);
                blockHeight = newHeight;
            }
            NSLog(@"image %@ cached ? %u", image ,cacheType);
            if (error) {
                NSLog(@"Error: %@",error);
            }
        }];

Have encountered similar issue.  The image cannot be shown in UITableViewCell. I tried to scroll the table view to trigger the dequeuing of UITableViewCell, but it still cannot show.
I opened other views, the images' downloading is normal.

Hey is you are still having issues with this I found a way to fix it..you need to use the SD_set image call with options and set the SdWebimageOptions Accordingly. Here is what I did. I am user Firebase Also if that helps you in any way..
itemImage.sd_setImage(with: URL(string: passedItem.itemImage), placeholderImage: #imageLiteral(resourceName: "Watch_Item"), options: [SDWebImageOptions.progressiveDownload, SDWebImageOptions.continueInBackground]) { (image, error, CatahType, url) in
self.itemImage.image = image (this is obviously the image you want to set)
}


SWARM-1615 Fixed MicroProfile link

Updated the link to MicroProfile.io to display correctly.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?


OpenWindowsTerminalAdminContext, issue when launch a Directory ending with a Backslash (fix included!)

Prerequisites

[X] Verify that this is not a Windows issue;
[X] Refer to the Before running.
[X] Refer to the How to use.
[ ] If you issue concerns the Wrapper, please mention @BenchTweakGaming in issue

Steps to reproduce
hi there,
as already known here: https://github.com/microsoft/terminal/issues/4571
Windows Terminal has an issue to launch from a Directory with a Backslash at the end.
To fix this also for your script, you need to change:
wt.exe -d "%V" to wt.exe -d "%V\."
and it will work again in both, with and without ending Backslash!
gretings

Hi. I heard about that issue. Is it really happen? How can reproduce it?

Hi. I heard about that issue. Is it really happen? How can I reproduce it?

hmm, let me think how can you reproduce:

launch from a Directory with a Backslash at the end

Well... An Example:
wt.exe -d "C:\" or wt.exe -d "C:\Users\" or wt.exe -d "C:\Program Files\" or... as mentioned before:
ANY other Directory with a Backslash at the end
sorry for my sarcasm, but i can't get more clear because the issue is the answer "how to reproduce" 🤣

Well, I have time to get down to your so-called issue. Hm, I still cannot get the point where is the issue in the script. The context menu the script creates works from a GUI, so how this bug can be reproduced within it? I know how it works using a CLI, but within a GUI? Could you record a GIF with the bug?

Well, I have time to get down to your so-called issue. Hm, I still cannot get the point where is the issue in the script. The context menu the script creates works from a GUI, so how this bug can be reproduced within it? I know how it works using a CLI, but within a GUI? Could you record a GIF with the bug?

Just... No!
I can not because i fixed the bug/issue already and im not willing to revert it.
It was just a recommendation to fix the bug in your script, so you can either use it or ignore it -> your choise!
if you can not reproduce it with ALL the "more then clear" information WHY and HOW the Bug occurs (with also an external link in the WT Repository), and also gave you ALL the information you need to fix it, i really can not help you...
gl

Implemented in 6.1.0. LOL :)


ReadConsoleInputA returns wrong character in KeyEvent.uChar.AsciiChar

Microsoft Windows [Version 10.0.14393] : Anniversary Update
Microsoft Windows [Version 10.0.15063] : Creators Update
Our console application uses ReadConsoleInputA to read a character from the input buffer. In Windows 10 Creators Update (CU), some characters are different than they were in Anniversary Update (AU). Enabling the legacy console in CU restores the characters to what they were in AU.
The console program below demonstrates this. Run it with the Spanish (Espana) keyboard and hit the tilde key. You should see different output on AU and CU.
AU:
Down: 1 Repeat: 1 KeyCode: 0xdc ScanCode: 0x29 CharW: ║ (0xba) CharA: º (0xffffffa7) KeyState: 0x0
CU (new console):
Down: 1 Repeat: 1 KeyCode: 0xdc ScanCode: 0x29 CharW: ║ (0xba) **CharA: ║ (0xffffffba)** KeyState: 0x0
CU (legacy console):
Down: 1 Repeat: 1 KeyCode: 0xdc ScanCode: 0x29 CharW: ║ (0xba) CharA: º (0xffffffa7) KeyState: 0x0

Note that CharA appears to be the Unicode version of the character (same as CharW sign extended) when running on CU with the new console. The behavior is the same on AU and CU with the legacy console. The program shows the console code page, which is IBM437.
#include <windows.h>
#include <wchar.h>
#include <stdlib.h>
#include <stdio.h>

int __cdecl wmain(int argc, WCHAR* argv[])
{
    HANDLE hIn = GetStdHandle(STD_INPUT_HANDLE);

    printf("GetConsoleCP: %d\r\n", GetConsoleCP());

    for (;;)
    {
        INPUT_RECORD rc;
        INPUT_RECORD rcA;
        DWORD dwRead = 0;

        PeekConsoleInputW(hIn, &rc, 1, &dwRead);

        if (dwRead > 0)
        {
            ReadConsoleInputA(hIn, &rcA, 1, &dwRead);

            if (rcA.EventType == KEY_EVENT)
            {
                printf("Down: %d Repeat: %d KeyCode: 0x%x ScanCode: 0x%x CharW: %c (0x%x) CharA: %c (0x%x) KeyState: 0x%x\r\n",
                    rc.Event.KeyEvent.bKeyDown,
                    rc.Event.KeyEvent.wRepeatCount,
                    rc.Event.KeyEvent.wVirtualKeyCode,
                    rc.Event.KeyEvent.wVirtualScanCode,
                    rc.Event.KeyEvent.uChar.UnicodeChar,
                    rc.Event.KeyEvent.uChar.UnicodeChar,
                    rcA.Event.KeyEvent.uChar.AsciiChar,
                    rcA.Event.KeyEvent.uChar.AsciiChar,
                    rc.Event.KeyEvent.dwControlKeyState);
                }
        }
    }
}

I'm pretty sure miniksa's already hunting this down :)

This is a duplicate of #2049. I've written a fix and it's on its way to insider builds.


Refactor Preemption to interact with Quota/Usage through ClusterQueueSnapshot interface

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Follow up to #2592. In preparation for https://github.com/kubernetes-sigs/kueue/issues/79.
Copied from #2592: we will change the Scheduler, FlavorAssigner, and Preemption logic to only interact with the ClusterQueueSnapshot's capacity through high level queries. E.g. "am I borrowing" or "how much capacity do I have left".
Additionally, we fix the test preempting locally and borrowing other resources in cohort, without cohort candidates. Since we were only looping over CQ resource groups, we didn't
find out that we had no capacity in CQ for this flavor code. We fix this by adding the alpha flavor to that CQ, and adding a CQ which lends resources to those FlavorResources
Does this PR introduce a user-facing change?
NONE

/lgtm
/approve
I believe all comments are addressed.


Update ActionType.java to include NOT_AGAIN_RYAN

Adding NOT_AGAIN_RYAN option, according to Discord's Change Log for 2019 December 19 .
Pull Request Etiquette

[x ] I have checked the PRs for upcoming features/bug fixes.
[x ] I have read the contributing guidelines.

Changes

[x ] Internal code
[ ] Library interface (affecting end-user code)
[ ] Documentation
[ ] Other: _____

Closes Issue: NaN
Description
Replace this sentence with general description of what your Pull Request does.

This feature is not documented in the official api documentation.


Issue with "Arcsight - Get events related to the Case" in @site/docs/reference/playbooks/arcsight---get-events-related-to-the-case.md

Getting 404 error while adding entries in active list of arcsight using cmd as-add-entries using active list resource id.. And as checked the xsoar resource id is matching with arcsight resource id... But still issue persits.

@nkanon @ShahafBenYakir Who should be assigned to this PR?

Hi @kishanpise This repo holds the XSOAR content documentation, issues raised here should reference problems within the aforementioned documentation. looking at your comment it sounds like you are experiencing issues with the as-add-entries command, to receive the best support for your problem, you need to work with the relevant PANW support to create the appropriate support ticket.


Automatic Prefix Caching (#2792) might conflict with multi-LoRA (#1804)

#2762 Provides a great way to improve efficiency when multiple requests share the same prefix through KV-cache reuse. Nevertheless, the user probably does not want to share KV-cache across two different LoRA adapters since the values would most likely be different.
As the test cases in PR #3263 suggest, the code changes in #2762 might require a bit more work to distinguish between blocks from different LoRA adapters. Previously, #1804 avoided this conflict by including adapter_id in the tuple while generating hashes for prefixes. (source). The fix proposed in #3263 drew inspiration from this approach.

Resolved in #3263.


[3601] Update 403/forbidden page content

Context
Update 403 page

Changes proposed in this pull request
Update 403 page title to read "You do not have permission to perform this action"
Guidance to review
TBC
Important business

~Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?~
~Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?~

 403 Page content doesn't reflect the new world of authorisation possibilities


Optimise the loading of the home page (root)

Hi,
This is an optimisation for serving the home page of a static site. Stops the whole bucket contents being read and parsed.
thanks,
David

Mered :-) Thanks!
Quick question: What are you using s3rver for? Thanks!

I am building a site which deploys to S3, and I am using s3rver for a local dev server.

Excellent. Thanks for your contributions. I've just pushed another commit (formatted and linted files). :-)

Thanks

Would you mind pushing a new release, thanks.

Done! Sorry for the delay. Cheers.

Np. Thanks


[T6A3][W11-C2] Vishnu Prem

Ready for review

@burnflare  PR title still needs your name. Name to be dropped only on team PRs. Its assigned to me this time. So no problem.

@cmkumar87 Sorry about that, I got confused with the instructions there. Fixed.


[WIP] Alternative Array.Filter implementation

Optimized for memory usage, and average performance

@jackmott
OK; well here is an alternative version, I have started collecting some data on from runs with various parameters, and they can be seen in this spreadsheet.
So what magic is included in this version? Well there is a bit of magical IL used to convert a bool into an int (safer than my previous struct magic, but probably would like a CIL guru to confirm if it is kosher or not... passes peverify and runs on all the JITS so I .. umm... assume it is...)
Anyway, have a look...

@manofstick Looks like you took out the CIL modification? Didn't work? Not safe?

@jackmott
I think it was safe, but really it was just taking the complexity level up a bit too high (documentation for instructions like ceq said they pushed 0 for false, 1 for true which was of type int32 - this would seem like you wouldn't even need any instructions, other than type change, but playing around it appeared that true was valid for command like brtrue for any non-negative value - so the cgt.un should have been fine).
Anyway, maybe worth it if the results I got for my first trial were replicated across all parameters, but once I removed the fully random data source then the results were just worse that the previous, simpler version. (And @KevinRansom was already making comments about complexity!)
Anyway, I'll just polish a couple of edge cases, and then check the test suite to see if it sufficiently covers the added complexity, and then I think I'm done.  Your choice :-)

@manofstick @jackmott .
I don't know what to do ... you have presented a very real conundrum.  The performance gains are very real, the memory savings are equally real ... and yet the code is impressively sized, and I wouldn't really want to have to debug an issue with it.
However I expect you can factor out the mask stuff and make choose benefit from this approach too ...
I am going to pull it, since speed is a real thing ... and there is no law that says we must write easy code ...
Please take a look at choose and see if you can apply the same technique.  And a quick gander through the rest of the libraries to see where else we can leverage this goodness.
Thanks
Kevin

@KevinRansom
Ha, yeah I felt like sighing when I saw the end result; not particularly the most beautiful work I have ever done as far as code elegance goes... But then performance related code rarely is I guess; and hopefully it will never need to be changed again! (here's hoping!)
Anyway, assuming that my test does what it is supposed to do (maybe worth stepping through) then it should be exhaustively tested... hopefully not famous last words!!
Probably can't be extended for "choose" as you want to store the result of mapping, not just true/false. Possibly could be extended for "partition"...

I think you could reduce memory use for partition, but not speed it up.
distinct is worth a look.

@jackmott
Hmm... not sure if could really improve distinct; still need some sort of hash, and then some populate step... Don't think it would beat:
let distinct (array:'T[]) =
    checkNonNull "array" array

    let mutable i = 0

    let distinctItems = Dictionary HashIdentity.Structural
    for item in array do
        if not <| distinctItems.ContainsKey item then
            distinctItems.[item] <- i
            i <- i + 1

    let result = Array.zeroCreateUnchecked distinctItems.Count
    for item in distinctItems do
        result.[item.Value] <- item.Key

    result

which save on memory, at the cost of performance...

@manofstick maybe parallel.partition?


Handle single and alternate substs for single glyphs in math mode

Fixes #1431.

I considered invoking rustybuzz for this case, but it’s possible for a single-character string to yield multiple glyphs when shaped.


Update lowrisc_ibex to lowRISC/ibex@66823369

Update code from upstream repository
https://github.com/lowRISC/ibex.git to revision
668233699df9ec2a40413e69e0de0a5b10185980

[dv] Add spurious responses to memory agent (Greg Chadwick)
[dv] Add riscv_ram_intg_test This test injects a fault into different MuBi encoded signals within the prim_ram_1p_scr and prim_ram_1p_adv and checks whether a fatal alert is triggered. (Pascal Nasahl)
[cosim] Clang lint fix (Greg Chadwick)
[dv] Output warning message on problematic MIP changes (Greg Chadwick)
[cosim] Correctly deal with checking top of range memory accesses (Greg Chadwick)
[dv] Update testbench to use new 'pre_val' MIP (Greg Chadwick)
[dv] Fix model mismatches in cases where an access crosses PMP regions (Greg Chadwick)
[dv] Fix exception_stall_instr_cross illegal bins (Greg Chadwick)
[dv] Add riscv_rf_ctrl_intg_test (Greg Chadwick)
[dv] Add cover points for memory interface behaviour (Greg Chadwick)
[dv] Fix race condition in ibex_mem_intf_agent (Greg Chadwick)

CHANGE AUTHORIZED: hw/vendor/lowrisc_ibex/rtl/ibex_core.sv
CHANGE AUTHORIZED: hw/vendor/lowrisc_ibex/rtl/ibex_lockstep.sv
CHANGE AUTHORIZED: hw/vendor/lowrisc_ibex/rtl/ibex_top.sv
CHANGE AUTHORIZED: hw/vendor/lowrisc_ibex/rtl/ibex_top_tracing.sv
This PR only touches code sections relevant for simulation (e.g. the RVFI) which are not synthesized. This is okay.

CHANGE AUTHORIZED: hw/vendor/lowrisc_ibex/rtl/ibex_core.sv
CHANGE AUTHORIZED: hw/vendor/lowrisc_ibex/rtl/ibex_lockstep.sv
CHANGE AUTHORIZED: hw/vendor/lowrisc_ibex/rtl/ibex_top.sv
CHANGE AUTHORIZED: hw/vendor/lowrisc_ibex/rtl/ibex_top_tracing.sv

Thanks @andreaskurth . I am merging this PR. It doesn't touch any synthesizable RTL, the CI failure for CW310 SiVal non-ROM_EXT Tests is spurious.


Clips

support for Twitch clips

@PetterKraabol can you create a release for this please?

Released 1.5.0


Mono/C#: Anonymous async lambda function freezes editor

Godot_v3.2-beta5_mono_win64
Windows 10 1909 x64
Issue description:
Anonymous async lambda function freezes editor
Steps to reproduce:

Open Godot editor, Add following code inside any C# script, then F5 once.
void NoNeedToInvoke() { Func<Task> func = async () => await Task.CompletedTask; }
With editor OPENED use Notepad or VS Code modify anything in this script, like rename method name or just add a comment. The important thing is to SAVE externally.
Back to the editor, it should freeze.

new_game_project.zip
Sorry for the late reply. The issue appears 100% on my computer with 3.2-beta to 3.2-stable.

Can anyone still reproduce this bug in Godot 3.2.3 or any later release?

Unable to reproduce on 3.5-rc8.
Any modification made in external editor (in my case VS Code), were shown in editor immediately, despite Game was running or not.


Additional log levels - eg to see files transfers  only

Is there a way to tune the log message to print information for files / folders that are being copied? in Regular mode, it does not tell you what files are being copied, but you get final statistics.. in Verbose mode, i get too much information that includes analysts and skipping of the files..
I am trying to log only artifacts that are being copied to the destination..
I am doing "rclon copy"  - v 1.3.3
Thanks

I'm also wondering a similar thing. See the issue I just filed Maybe a combination of my question and your issue?

There isn't a way of doing that at the moment.  What would you like to see - a --log-transferred flag or something like that?

Maybe a log level flag something like
--log-levels-transfers
So you can have something like
--log-level=debug
--log-level=verbose
--log-level=transfers
And if you don't want to see any of it just do
-q
in  Your script a along with the --log-file=filename.log
Thoughts? I hope I understand what the poster and you were saying.

Yes something like that seems sensible.
At the moment there are 3 log levels

errors only -q
info (no flag)
debug -v

We'd need to slip a fourth one in, say

errors only -q --log-level errors
info (no flag) --log-level info
transfers --log-level transfers
debug -v --log-level debug

The transfers level should log the Copied lines that you get from -v and any deleted lines, but nothing else (no skipping etc)

sounds like a good idea.  Still getting used to scripting, so that was off the top of my head.
Hopefully the original poster will chime in with their idea.

I was able to scrap the rclone output in my calling go programm.. Here is what i did if anyone intrestead:
c := exec.Command(rclone, rcloneArgs...)
var outbuf, errbuf bytes.Buffer
c.Stdout = &outbuf
c.Stderr = &errbuf
c.Run()
//log.Warning("Waiting for command to finish...")
done := make(chan error, 1)
go func() {
done <- c.Wait()
}()
resp := buildRcloneResponse(outbuf, errbuf)
.....
func buildRcloneResponse(outbuf bytes.Buffer, errbuf bytes.Buffer) map[string]map[int]string {
resp := make(map[string]map[int]string)
//Scann sterror for summary
scanner := bufio.NewScanner(&errbuf)
summaryResp := make(map[int]string)
i := 0
for scanner.Scan() {
	s := strings.TrimSpace(scanner.Text())
	// Take usefull summary
	if strings.HasPrefix(s, "Transferred") || strings.HasPrefix(s, "Errors") || strings.HasPrefix(s, "Checks") || strings.HasPrefix(s, "Elapsed") {
		summaryResp[i] = s
		i++
		//log.Warning("se:", s)
	}
}

if i > 0 {
	resp["summary"] = summaryResp
	i = 0
}
detailResp := make(map[int]string)
scanner = bufio.NewScanner(&outbuf)

//scan stout for file transfer details
for scanner.Scan() {
s := strings.TrimSpace(scanner.Text())
//log.Warning("$" + s + "$")
// Strip stuff that not needed
if strings.Contains(s, "Go routines") || strings.Contains(s, "Sizes identical") || strings.Contains(s, "Unchanged skipping") ||
strings.Contains(s, "rclone: Version") || strings.Contains(s, "Local file system at") || strings.Contains(s, "Sizes differ") {
continue
}
else {
// Strip out log date from
sub := s[20:len(s)]
detailResp[i] = sub
i++
}

if i > 0 {
	resp["detail"] = detailResp
}

return resp

}

My suggestion is to classify the log entries better and use a level approach like 'WARN|ERROR|CRTICAL|FATAL" etc. Then we can just select the verbosity level.
We could then prefix each level in the log for a greppable/searchable reasons.
ERROR:
WARN:
…

After a bit of thought about this, I think that I should take rclone back to its rsync roots and make -v only show file transfers and do this

errors only -q --log-level errors
info (no flag) --log-level info
transfers -v --log-level transfers
debug -vv --log-level debug

At the moment transfers and debug are combined into one level.  I'd split them and into transfers I'd put any files which were

uploaded
downloaded
renamed
server side copied
server side moved
deleted

Everything else would go into the debug level which I'd make a shortcut of -vv to use.
I'm also proposing to send all logs to stderr by default (at the moment the -v log goes to stdout).
Being able to send the logs to syslog would be extremely useful, so I propose adding a --syslog optionc (especially for rclone mount) and in that case the rclone log levels should probably match up with syslog levels

LOG_EMERG      system is unusable
LOG_ALERT      action must be taken immediately
LOG_CRIT       critical conditions
LOG_ERR        error conditions
LOG_WARNING    warning conditions
LOG_NOTICE     normal, but significant, condition
LOG_INFO       informational message
LOG_DEBUG      debug-level message

I'd propose making the 4 levels match up like this

errors only -q --log-level errors - LOG_ERR
info (no flag) --log-level info - LOG_NOTICE
transfers -v --log-level transfers - LOG_INFO
debug -vv --log-level debug  LOG_DEBUG

As for @calisro's suggestion of prefixing the log messages with an identifier - I'm not sure about that.  It could be an option?

Is there a reason why you'd default to stderr vs stdout?  If someone is enabling logging, they'll want it without having to do "2>&1" or something.
Im trying to see if I would be able to use the new log scheme in my approach but i'm not sure.  What I do today is this:
rclone sync "remote:/" 2>&1 | egrep -v "$CRYPTLOGFILTER"
For the LOGFILTERs I prune out things that clutter my logs and I have no use for as follows:
LOGFILTER="eading|Sizes identical|Unchanged skipping|time the same|Excluding from sync|transfer non file/directory|Excluded from sync|Size and MD5 of src and dst objects identical"
CRYPTLOGFILTER="$LOGFILTER|File found with same name but different case"
What are you intending on sending to INFO (default) versus the transfers/debug?  I'm just trying to see how that matches up to my pruning.

@calisro

Is there a reason why you'd default to stderr vs stdout?
Sorry that was a typo!  Have corrected the above post - logs will go to stdout!

I think all the things in your LOGFILTER would be in the debug level so you'd need -vv to see them.
Not sure about "File found with same name but different case" - is that a debug or an info?  It is currently an info.  Why do you see that in your transfers?

What are you intending on sending to INFO (default) versus the transfers/debug? I'm just trying to see how that matches up to my pruning.

I plan to leave info (default) level pretty much as is.  That doesn't receive a lot of logs normally anyway.
The transfers level will match up with what you want to see I think - that is my intention.

I have reworked the logging - please have a go with it in this beta
http://beta.rclone.org/v1.35-87-g006227b/ (uploaded in 15-30 mins)
Here are the bits from the docs
Logging
rclone has 4 levels of logging, Error, Notice, Info and Debug.
By default rclone logs to standard error.  This means you can redirect
standard error and still see the normal output of rclone commands (eg
rclone ls).
By default rclone will produce Error and Notice level messages.
If you use the -q flag, rclone will only produce Error messages.
If you use the -v flag, rclone will produce Error, Notice and
Info messages.
If you use the -vv flag, rclone will produce Error, Notice,
Info and Debug messages.
You can also control the log levels with the --log-level flag.
If you use the --log-file=FILE option, rclone will redirect Error,
Info and Debug messages along with standard error to FILE.
If you use the --syslog flag then rclone will log to syslog and the
--syslog-facility control which facility it uses.
Rclone prefixes all log messages with their level in capitals, eg INFO
which makes it easy to grep the log file for different kinds of
information.

I messed up with that beta - try this one instead http://beta.rclone.org/v1.35-92-g18c75a8/ (uploaded in 15-30 mins)

After this discussion is there a conclusion on how I can log transfers only?
Right now I have this line in my INFO log:
2018/05/12 15:03:15 INFO  : Google drive root '': Modify window is 1s
I don't want this, I only want to log files that have had some action taken, e.g. copied new or something

@hongkongkiwi the INFO level will be nearly all file transfers but there are a few other things in there.  There isn't a way at the moment to only show file transfers.


Remote connection API

I would like to run this software on my Ubuntu VM, and a compute heavy python script to run on Windows.
If possible, it would be awesome to have a remote API, where you could enter the IP of the nxbt interface such as:
import nxbt
nxbt.openconnection(<IP_ADDRESS>:8000)
This would make it possible to have the relatively lightweight NXBT running on a VM or raspberry pi, and the more compute heavy workload could run on a networked computer.
I realize this is not a simple request, but I think it could prove extremely useful.
Right now, I am using selenium to run the web interface on my pc, and my python script enters macros by pushing buttons on the keyboard, but that requires that geckodriver is the always the active window while the macro is running.

Hey, I'm trying to do something similar! I figured I could write some javascript into the webapp's webpage to poll an API, but I came here to ask about creating webhooks or, I guess, networking the API. I think that would be really beneficial.

I could really use an API while keeping the webapp or similar up. Even MQTT would be a great addition for integrating IoT automations!


function added to print paths from source to destination with the shortest number of link

Added function _print_path to print path from source to destination.
The logic used is to backtrack from destination id to source id and print the shortest path.

Hi, have you reviewed the code yet? Please let me know if anything needs to be done


Fix #408, remove reference to device driver

Describe the contribution
Remove reference to device driver.
Testing performed
Steps taken to test the contribution:

make prep
make install
Run cfs

System(s) tested on

Hardware: [e.g. PC, SP0, MCP750]
Ubuntu 18.04
cfe 6.6, osal 1.4.2a

Contributor Info - All information REQUIRED for consideration of pull request
Anh Van, NASA Goddard

closed. Mess up pull request. Reference https://github.com/nasa/cFE/pull/477


Two levels ul list

Hi,
Is it possible make two levels ul/ol list?
I have data:
	type Ddd struct {
		Doc      string
		Pastabos []string
	}
	type TemplateData struct {
		DocPastabos         []Ddd
	}

	data := TemplateData{
		DocPastabos: []Ddd{
			{
				Doc: "sdfsdf",
				Pastabos: []string{
					"dfdfdf", "sdfsdfsdf",
				},
			},
			{
				Doc: "sdfwerwerwesdf",
				Pastabos: []string{
					"dfdwerwefdf", "sdfertertertsdfsdf",
				},
			},
		},
	}

I get this result in docx:

I need this result:

Hi! Did you get any further? This project is not actively developed, but I will look into this problem. I think you found bug on incorrect element looping.


Crashed when running in background

Microsoft PowerToys version
0.33.1
Running as admin

[X] Yes

Area(s) with issue?
General
Steps to reproduce
PowerToys was running in the background this a ran into an issue message appeared
[PowerToysReport_2021-04-16-10-29-11.zip](https://github.com/microsoft/PowerToys/files/6325829/PowerToysReport_2021-04-16-10-2
✔ Expected Behavior
No response
❌ Actual Behavior
Crashed
Other Software
No response

@Jacksole
thanks for reporting the issue.
Since we have released 0.35 https://github.com/microsoft/PowerToys/releases/download/v0.35.0/PowerToysSetup-0.35.0-x64.exe we don't investigate issues in previous versions.
Please update and if the problem happens again open a new issue, thanks.


Test other dataset

What should i modify if i want to test VOT2022 or VOT2023 dataset?
I found that you have some methods to change the groundtruth file format from VOT to the specified format that the algorithm can use and found that you have set VOT2016--2019 dataset in eao_benchmark, when i modify a yaml file in experiments like change tester name to "VOTTester", i received the following error: (I want to test vot2023 dataset)
d_coerce_cfg_value_type
raise ValueError(
ValueError: Type mismatch (<class 'yacs.config.CfgNode'> vs. <class 'str'>) with values (VOT2018: datasets/VOT/vot2018
VOT2019: datasets/VOT/vot2019 vs. /Users/jorny/docu_gatech/votcmu/vot2023/vots2023-old) for config key: test.track.tester.VOTTester.data_root

same question, I wanna test on OTB100, how can I rewrite the test ymal. Looking forward to your reply!

Sorry, the code framework is supported up to VOT2018. higher versions need to be ported by yourself.

Hellow. Only the last part of yaml needs to be changed.
Reference experiments/tatrack/test/tiny/otb.yaml
tester:
  names: ["OTBTester",]
  OTBTester:
    exp_name: *TEST_NAME
    exp_save: *TEST_SAVE
    subsets: [ "otb2015" ]
    device_num: 1

From: Kunpeng Huang @.>
Sent: Thursday, June 29, 2023 0:18
To: hekaijie123/TATrack @.>
Cc: Subscribed @.***>
Subject: Re: [hekaijie123/TATrack] Test other dataset (Issue #13)
same question, I wanna test on OTB100, how can I rewrite the test ymal. Looking forward to your reply!
―
Reply to this email directly, view it on GitHubhttps://github.com/hekaijie123/TATrack/issues/13#issuecomment-1611726611, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARLIHY5RQ3DSTTQE4YEZN6TXNRKMNANCNFSM6AAAAAAYHR5L4A.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


6.0.0 backports

@gunnarmorling here are the backports for 6.0.0

https://hibernate.atlassian.net/browse/HV-1458
https://hibernate.atlassian.net/browse/HV-1438 (fixVersion needs to be moved to 6.0.0.Final if we backport it)

Looks good; thanks, @gsmet!


Docker container has a huge layer because of chown of /var

There is
RUN chown -R wavefront:wavefront /var

done when building Docker container - https://github.com/wavefrontHQ/wavefront-proxy/blob/master/proxy/docker/Dockerfile#L20
As docker does copy-on-write, this operation creates a huge layer - docker image history shows
<missing>      2 days ago   /bin/sh -c chown -R wavefront:wavefront /var    180MB

which is quite a lot compared to seemingly innocent operation.
I suspect you do not need to change ownership to the entire /var hierarchy...

Fixed


Update usersignup BPEL for APIMANAGER-2994 fix

correlation and exit event listener was added in order to implement
task cleanup process for user sign up.

Since you are updating the BPEL file inside the zip file, your changes will not recorded in git version history. But having version history of the BPEL file is very useful for trouble shooting.
IMO correct way is convert these artifacts to BPEL maven projects and build them at build time. Do the same for HumanTask as well.

Added APIMANAGER-4602 to fix at a later time.


Improve Navbar 09

Need to improve this component on Navbar/src/navbar-09.html
Improvements required :

The navbar breaks at a breakpoint, make sure it does't

Any reference image?

You can checkout this one for better understanding.

@Rajdip019 Please assign this to me

Done #733


[QUESTION] Will be async patches in future version of DXVK

Some guy made async shader compile patches for DXVK, but it little buggy
So, maybe if Wine Esync merged to staging - DXVK async will be?

Short version: No.
Long version: It alters rendering without the game being aware of it, which is unacceptable especially in the context of multi-player games. I know it helps some games tremendously, but use it at your own risk.

@doitsujin But can it be at least possible to add this as a disabled option by default in the configuration file?

Short version: No.
Long version: It alters rendering without the game being aware of it, which is unacceptable especially in the context of multi-player games. I know it helps some games tremendously, but use it at your own risk.

No.


Latest update broke mic functionality

After newest update the mic mute/unmute doesn't seem to work. I can hear game audio with headset on android and PC but I can't hear chat nor can I anyone hear me. I've narrowed it down to xcloud. Everything works fine through the browser with better xcloud disabled.

Try to disable the "volume control" feature in the Settings

Yeah, That did it. I must have accidentally turned that on. Is that option supposed to mess with mic input?

Maybe? Is there any game that allows me to test the voice chat feature by myself?

 Was quicker to get into for tests than halo.


Builds and deploys to HoloLens but creates only a pink sphere.

When I first ran the app, it only created a pink sphere. There were no other color transitions. Nothing else happened until I executed an airtap. The sphere disappeared, then a few moments later a pink sphere reappeared. Using Unity 2018.4.1f1. Deployed with Visual Studio 2019. Tried it with script that I assembled from directions in tutorial and also by copying code above verbatim. Results were identical. I ran a debugging session in VS19 and saw no errors. However, in addition to a pink sphere at the site of the original raycast, an additional large pink sphere appeared at the location of the HoloLens (i.e. origin) when the original raycast was performed.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e3aab4c6-3e00-857c-e9a1-0a4023897b2f
Version Independent ID: b92bc135-0ced-3eea-00ae-1a941c6f4c65
Content: Tutorial - Step-by-step instructions to create a new HoloLens Unity app using Azure Spatial Anchors
Content Source: articles/spatial-anchors/tutorials/tutorial-new-unity-hololens-app.md
Service: azure-spatial-anchors
GitHub Login: @julianparismorgan
Microsoft Alias: pmorgan

@ggorby Thanks for the feedback! We are currently investigating and will update you shortly.

@ggorby Would you please try with Visual Studio 2017?

You mean for deploying the Sharing Anchors Service?
Sent from my iPhone
On Jun 12, 2019, at 6:18 PM, Alberto Vega <notifications<EMAIL_ADDRESS>wrote:
@ggorbyhttps://github.com/ggorby Would you please try with Visual Studio 2017?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/32988?email_source=notifications&email_token=AI5IZ6FSXOUBMNKI4RKQPVDP2F753A5CNFSM4HWQJPI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXSBZFI#issuecomment-501488789, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AI5IZ6EGL5X42KFGUC37VS3P2F753ANCNFSM4HWQJPIQ.

Yes please

The Quickstart HoloLens app worked, but the "Starting a new Unity HoloLens app" gave the results described above. I have not tried anything else on the "sharing in Unity" tutorial for iOS after I submitted the issue with the error messages. I thought your request to use Visual Studio 2017 pertained to the iOS issue, but I see you meant it in reference to this one. I tried VS 2017, and I am seeing the same pink spheres.

What are you getting in the Visual Studio Output window? Ideally you would see the anchor identifier coming back from the cloud service.

@ggorby / @Alberto-Vega-MSFT, I don't think this is an issue with ASA returning anchors. Rather, it looks like either an issue with the shader or with the material not being assigned properly. I'll look into this and get back to you. cc. @darax / @vriveras

Hey @ggorby, could you try doing assets->reimport all from unity, then rebuilding?

I'm doing the same tutorial and have the same problem,
I also did some test, I removed all Azure related code and just spawn the sphere to the world and it still purple, it seems like primitive object created by "GameObject.CreatePrimitive"  command has corrupted material/shader in HoloLens build, but works fine in Unity or remote play to HoloLens.
I'm thinking a way to bypass the issue by placing a prefab sphere and override the object color. But I haven't tested it yet, I will test my method two days later once I have time.

Hi, I found that placing prefab instead of spawn 3d sphere directly can bypass the issue, here's the change I made:

Create a sphere prefab(can be done by creating a 3d sphere in hierarchy and drag it to asset folder, then remove it from hierarchy)

add a public game object in AzureSpatialAnchorsScript.cs:
public GameObject target_object;  // use prefab instead of create primitive object
protected GameObject sphere;
protected Material sphereMaterial;

find and replace the sphere creation line (line 182)
sphere = GameObject.Instantiate(target_object, new Vector3(0, 0, 0), Quaternion.identity) as GameObject; // sphere = GameObject.CreatePrimitive(PrimitiveType.Sphere);

In Unity, click "MixedRealityCloud" from hierarchy, drag or add the prefab sphere to "target_object"

The solution works on my device (I'm using HoloLens Gen 1)
Hope it helps
Cheers

Thanks @mcoy001 for looking into this! Using a prefab makes sense (and is probably more extensible anyways!), so I'll update the docs to use that instead.

The update to the docs is live now - thanks all for the investigations!

@julianparismorgan Thanks for an update.
@ggorby We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Add Datadog APM

Motivation
Current production system monitoring is very limited. We have only AWS Cloudwatch metrics for infra and basic endpoint monitoring via custom logging of API endpoint requests in Cloudwatch. The team has no central dashboards for full system observability. See tech proposal.
Definition of Done
Enable APM for this repo and document steps to ensure others understand if any work is needed to enable APM going forward.
Tasks
The work would involve taking the changes from the associated PR, https://github.com/chanzuckerberg/single-cell-data-portal/pull/3610/files, and getting them on to main (which has progressed considerably since this spike, so it won't be a straight merge), retesting in testing in rdev, and then in dev, etc. And updating some documentation.
Review related ticket for context.

[ ]
[ ]

@prathapsridharan , can this be closed?

@dsadgat - There is definitely more to do to flesh this out but is the v1 of datadog sufficient to close this particular ticket (cc: @metakuni )

If the scope of this issue was v1, then I think we can close this, but I defer to @dsadgat .


Use of HTTP Without TLS

Greetings,
I am a security researcher, who is looking for security smells in Puppet scripts. I found instances where the HTTP protocol is used instead of HTTPS (HTTP with TLS). I think this is a smell, and I was wondering why HTTP is used? Is it because of lack of tool support?
I am trying to find out if developers are forced to adopt bad practices due to lack of tool support when it comes to the HTTPS protocol. Maybe it is due to dependency on a resource that uses HTTP?
Any feedback is appreciated.
Source: https://github.com/deric/puppet-mesos/blob/master/manifests/repo.pp (Line#20, 84)

Good catch. This was probably caused by lack of documentation or absence of https endpoint at the time of writing. Should be fixed in next release.


Update readme.

Jenkins job mixerclient/presubmit passed

Jenkins job mixerclient/proxy-regression passed

Jenkins job mixerclient/presubmit passed


Project.js Updated for Tip-Calculator

@ianshulx I have added the Tip-Calculator code in project.js, Please merge this,
Thank you

@Krishnap2k4 thank you


Fix the python version problem in CI

The CI workflow file uses conda to install the latest version of Python, which will produce an error when running pylint. To fix this, the python version in the CI environment is pinned to 3.10. However, conda produces another error when installing python 3.10, so I feel it's better to remove conda in the workflow and simply use pip to install the dependencies. Therefore I replaced the requirements.conda.yaml with requirements.txt to let pip install the packages.
In addition, I updated the Github actions setup-python and checkout to their latest corresponding versions.

I think going with the current (requirements.txt) approach is fine for now.


C++ gradients for MaxPool3D, AvgPool, AvgPool3D

Looks like these just need to connect the gradient to an existing core op. Anyone already working on it? Otherwise, I'll sign up for these three.
/cc @bpiel @suharshs

@kbsriram I'm not. thanks

Nor am I. Thanks!

Can you please provide more details? AvgPoolingGradOp already exists.

@bignamehyp This is referring to C++ gradients: https://github.com/tensorflow/tensorflow/tree/master/tensorflow/cc/gradients


Generate changelog in orchestrator:release

Generate changelog as part of orchestrator:release command
Modify changelog interfaces to include hashId, buildNumber and orgs
Refactor changelog logic into classes & methods
Add unit tests for commit, work item and org generation
Preview changelog in the terminal
Tabulate commits

Codecov Report

Merging #511 (8bdc086) into develop (b95ce64) will increase coverage by 0.94%.
The diff coverage is 92.30%.

:exclamation: Current head 8bdc086 differs from pull request most recent head 0a9abdc. Consider uploading reports for the commit 0a9abdc to get more accurate results

@@             Coverage Diff             @@
##           develop     #511      +/-   ##
===========================================
+ Coverage    78.59%   79.53%   +0.94%
===========================================
  Files           35       38       +3
  Lines         1210     1300      +90
  Branches       212      230      +18
===========================================
+ Hits           951     1034      +83
- Misses         259      266       +7

Impacted Files
Coverage Δ

...powerscripts-cli/src/impl/changelog/OrgsUpdater.ts
89.79% <89.79%> (ø)

...werscripts-cli/src/impl/changelog/CommitUpdater.ts
91.66% <91.66%> (ø)

...rscripts-cli/src/impl/changelog/WorkItemUpdater.ts
100.00% <100.00%> (ø)

...rscripts-cli/src/impl/release/ReleaseDefinition.ts
92.85% <100.00%> (ø)

Continue to review full report at Codecov.

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


Message Writer Problem

Hi,
I got this error when I want to install mainflux with docker. Whats the reason?
ERROR: repository mainflux/message-writer not found: does not exist or no pull access
Thanks

Starting NATS, Cassandra and Nginx...
Starting nats ... done
Starting cassandra ... done
Waiting for Cassandra to start. This takes time, please be patient...
.............OK
Starting Mainflux composition...
Pulling mqtt-adapter (mainflux/mqtt-adapter:latest)...
latest: Pulling from mainflux/mqtt-adapter
Digest: sha256:d17b25a10c1f5ad53d8865ceb714bca29e7f9179a4275596fa4ccaa25f577422
Status: Image is up to date for mainflux/mqtt-adapter:latest
Pulling manager (mainflux/manager:latest)...
latest: Pulling from mainflux/manager
Digest: sha256:8119f293e2c275df2c7008d1ab9db9fbdec6ea3ff59789f2c619d662bfba5543
Status: Image is up to date for mainflux/manager:latest
Pulling message-writer (mainflux/message-writer:latest)...
ERROR: repository mainflux/message-writer not found: does not exist or no pull access
Aborting due to errexit on line 122. Exit code: 1
Starting mqtt-adapter ... done
Starting manager ... done
Starting message-writer ... done
Starting http-adapter ... done
Starting Nginx...
Starting nginx ... done
ERROR: No containers to start
Aborting due to errexit on line 136. Exit code: 1
Stopping Nginx...
Stopping Mainflux composition...
Stopping mainflux-http ... done
Stopping mainflux-message-writer ... done
Stopping NATS and Cassandra...
Stopping mainflux-cassandra ... done
Stopping mainflux-nats ... done
*** MAINFLUX IS OFF ***

We did a transition to monorepo yesterday, merging all repos into main one. Transition is not finished yet, so things might be broken.
Please check Mainflux DockerHub to see if container names have been changed.

Thanks for fixing the problem, but now there is the same problem for mqtt-adaptor.

siavash@ubuntu:~/Desktop/Mainflux2/mainflux/bin$ sudo ./mainflux-docker.sh startStarting NATS and Cassandra...
Starting nats ... done
Starting cassandra ... done
Waiting for Cassandra to start. This takes time, please be patient...
............OK
Starting Mainflux composition...
Pulling mqtt-adapter (mainflux/mqtt-adapter:latest)...
ERROR: repository mainflux/mqtt-adapter not found: does not exist or no pull access
Aborting due to errexit on line 122. Exit code: 1
Starting mqtt-adapter ... done
Starting manager ... done
Starting message-writer ... done
Starting http-adapter ... done
Starting Nginx...
Starting nginx ... error
ERROR: for nginx  Cannot start service nginx: Cannot link to a non running container: /mainflux-mqtt AS /mainflux-nginx/mainflux-mqtt
ERROR: No containers to start
Aborting due to errexit on line 136. Exit code: 1
Stopping Nginx...
Stopping Mainflux composition...
Stopping mainflux-http ... done
Stopping mainflux-message-writer ... done
Stopping mainflux-manager ... done
Stopping NATS and Cassandra...
Stopping mainflux-cassandra ... done
Stopping mainflux-nats ... done
*** MAINFLUX IS OFF ***

@2014siavash Can you try to pull composition now ?

Do a git pull to fetch the new code
Remove old containers docker ps -a and remove all mainflux containers
run composition again, navigate to /bin folder and run ./mainflux-docker.sh start

yes of course.
First, I cloned the new code. Then I removed old containers and then continued according to your instruction.
here is the results for "docker ps" and "docker ps -a":

siavash@ubuntu:~/Desktop/Mainflux2/mainflux/bin$ sudo docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
siavash@ubuntu:~/Desktop/Mainflux2/mainflux/bin$ sudo docker ps -a
CONTAINER ID        IMAGE                                            COMMAND                  CREATED             STATUS                       PORTS               NAMES
b0875199d2e3        mainflux/http:latest                             "/exe"                   5 minutes ago       Exited (2) 5 minutes ago                         mainflux-http
25472f7ea01a        mainflux/writer:latest                           "/exe"                   5 minutes ago       Exited (2) 5 minutes ago                         mainflux-message-writer
a96df7ef8f78        mainflux/manager:latest                          "/exe"                   5 minutes ago       Exited (2) 5 minutes ago                         mainflux-manager
948bd073cd6d        mainflux/mqtt-adapter:latest                     "node mqtt.js"           5 minutes ago       Exited (137) 5 minutes ago                       mainflux-mqtt
50c58a226a00        nginx:1.13-alpine                                "nginx -g 'daemon ..."   7 hours ago         Created                                          mainflux-nginx
9eb718660669        cassandra:latest                                 "/docker-entrypoin..."   2 days ago          Exited (143) 5 minutes ago                       mainflux-cassandra
174762ff5cfd        nats:latest                                      "/gnatsd -c gnatsd..."   2 days ago          Exited (2) 5 minutes ago                         mainflux-nats
1df8507565f4        prestashop/prestashop                            "docker-php-entryp..."   2 weeks ago         Exited (0) 2 weeks ago                           some-prestashop
81ccfe5fd35b        mysql                                            "docker-entrypoint..."   2 weeks ago         Exited (0) 2 weeks ago                           some-mysql
3891f5c4b0eb        mainflux/loraserver-docker:lora-app-server       "dockerize -wait t..."   5 weeks ago         Exited (0) 4 weeks ago                           lora-app-server
e24c1e7f079c        mainflux/loraserver-docker:loraserver            "dockerize -wait t..."   5 weeks ago         Exited (0) 4 weeks ago                           lora-network-server
189e0ad907d6        mainflux/loraserver-docker:lora-gateway-bridge   "dockerize -wait t..."   5 weeks ago         Exited (0) 4 weeks ago                           lora-gateway-bridge
f54866deaeb8        ansi/mosquitto                                   "/usr/local/sbin/m..."   5 weeks ago         Exited (0) 4 weeks ago                           brocaar_mosquitto_1
baac900267a9        redis:alpine                                     "docker-entrypoint..."   5 weeks ago         Exited (0) 4 weeks ago                           redis
085fb904f31d        postgres:9.5                                     "docker-entrypoint..."   5 weeks ago         Exited (0) 4 weeks ago                           brocaar_postgres_1
siavash@ubuntu:~/Desktop/Mainflux2/mainflux/bin$

Here is also the results for run composition:

siavash@ubuntu:~/Desktop/Mainflux2/mainflux/bin$ sudo ./mainflux-docker.sh start
Starting NATS and Cassandra...
Starting nats ... done
Starting cassandra ... done
Waiting for Cassandra to start. This takes time, please be patient...
............OK
Starting Mainflux composition...
Pulling mqtt-adapter (mainflux/mqtt-adapter:latest)...
latest: Pulling from mainflux/mqtt-adapter
Digest: sha256:183e4f40bdb3cbc8132e1054113f40cf3f0a0f00c5b5f1209eaec83ecc2a2c9b
Status: Image is up to date for mainflux/mqtt-adapter:latest
Pulling manager (mainflux/manager:latest)...
latest: Pulling from mainflux/manager
Digest: sha256:f27cc3a0256ad4cae43f0b72561b21002c992e21b7939c0ccc110591e85dc2e4
Status: Image is up to date for mainflux/manager:latest
Pulling message-writer (mainflux/writer:latest)...
latest: Pulling from mainflux/writer
Digest: sha256:86b3d4457258e650e905e3398a93ed18e9d8582fb6e28c7e4e42d9c7ef217298
Status: Image is up to date for mainflux/writer:latest
Pulling http-adapter (mainflux/http:latest)...
latest: Pulling from mainflux/http
Digest: sha256:c28a308123662ed570cf44bc8db043498fb3f391d5374d91bdb58935c2772885
Status: Image is up to date for mainflux/http:latest
Starting mqtt-adapter ... done
Starting manager ... done
Starting message-writer ... done
Starting http-adapter ... done
Starting Nginx...
Starting nginx ... error
ERROR: for nginx  Cannot start service nginx: Cannot link to a non running container: /9b41dbe141a3_mainflux-manager AS /mainflux-nginx/mainflux-manager
ERROR: No containers to start
Aborting due to errexit on line 136. Exit code: 1
Stopping Nginx...
Stopping Mainflux composition...
Stopping mainflux-http ... done
Stopping mainflux-message-writer ... done
Stopping mainflux-manager ... done
Stopping mainflux-mqtt ... done
Stopping NATS and Cassandra...
Stopping mainflux-cassandra ... done
Stopping mainflux-nats ... done
*** MAINFLUX IS OFF ***
siavash@ubuntu:~/Desktop/Mainflux2/mainflux/bin$

I think the problem is just for Nginx now! However as you can see above, Nginx was not worked before.

Wait wait wait. For Nginx it is my fault. Now every thing is ok. Mainflux is on. Thank you.

@2014siavash Sure np, thank you for reporting this one ;)

@2014siavash Closing this one, thank you!

@2014siavash How did you solve the Nginx problem? I am having the same problem.

Same here! Please let us know how you fixed it.

reopening the issue. @aureliocano and @thedavejay do you have maybe local NGINX (or some other server) instance running that prevents eventually NGINX Docker container to map to localhost ports: https://github.com/mainflux/mainflux/blob/master/bin/docker/docker-compose.nginx.yml#L25-L28

Thanks @drasko
Not in my case, no other server is running.
My specific problem is:
Starting nginx ... error
ERROR: for nginx  Cannot start service nginx: Cannot link to a non running container: /mainflux-http AS /mainflux-nginx/mainflux-http
ERROR: No containers to start
Aborting due to errexit on line 136. Exit code: 1
I had a look to the docker log of http and nats container and obtained this:
user@user-VirtualBox:~/mainflux/bin$ docker logs mainflux-nats
[1] 2017/11/29 17:19:56.420181 [INF] Starting nats-server version 1.0.2
[1] 2017/11/29 17:19:56.420304 [INF] Starting http monitor on <IP_ADDRESS>:8222
[1] 2017/11/29 17:19:56.420358 [INF] Listening for client connections on <IP_ADDRESS>:4222
[1] 2017/11/29 17:19:56.420363 [INF] Server is ready
[1] 2017/11/29 17:19:56.424523 [INF] Listening for route connections on <IP_ADDRESS>:6222
user@user-VirtualBox:~/mainflux/bin$ docker logs mainflux-http
{"aborted":"nats: no servers available for connection","ts":"2017-11-29T17:20:46.940750603Z"}
Could the problem be on a nonexistent link between both containers?

@aureliocano ERROR: No containers to start - were all containers pulled? You can eventually use docker-compose -f docker/docker-compose.nginx.yml pull to be sure that you pulled the correct container. You can do this also for other docker files.

Thanks @drasko
There was no luck with that, all containers were pulled aand the problem persists. I will try in other machine just in case.

@aureliocano can you please bump up docker version:
drasko@Marx:~$ dockerd --version
Docker version 17.11.0-ce, build 1caf76c

Also, please try getting us the logs using:
docker-compose -f docker/docker-compose.mainflux.yml logs -f

Hi,
I did the followings:
first, I removed the current container for Nginx. It is done with sudo docker-compose -ps as I remembered. For more details, please search about how one can remove the old container with docker.
Then, I stopped mainflux with sudo docker-compose down.
Finally, I started mainflux again with sudo docker-compose up.
I think it will work for you too. The problem is for your old container of Nginx which should be removed, before pulling the new one.
Hope to be fixed.

@drasko
user@user-VirtualBox:~/mainflux/bin$ dockerd --version
Docker version 17.03.2-ce, build f5ec1e2
user@user-VirtualBox:~/mainflux/bin$ docker-compose -f docker/docker-compose.mainflux.yml logs -f
Attaching to mainflux-mqtt, mainflux-http, mainflux-message-writer, mainflux-manager
mainflux-mqtt     | {"pid":1,"hostname":"9092868d102d","level":30,"time":1512404770725,"msg":"listening","address":"::","family":"IPv6","port":8880,"protocol":"http","v":1}
mainflux-mqtt     | {"pid":1,"hostname":"9092868d102d","level":30,"time":1512404770734,"msg":"listening","address":"::","family":"IPv6","port":1883,"protocol":"tcp","v":1}
mainflux-mqtt     | {"pid":1,"hostname":"9092868d102d","level":30,"time":1512404903461,"msg":"listening","address":"::","family":"IPv6","port":8880,"protocol":"http","v":1}
mainflux-mqtt     | {"pid":1,"hostname":"9092868d102d","level":30,"time":1512404903479,"msg":"listening","address":"::","family":"IPv6","port":1883,"protocol":"tcp","v":1}
mainflux-mqtt     | {"pid":1,"hostname":"9092868d102d","level":30,"time":1512465258788,"msg":"listening","address":"::","family":"IPv6","port":8880,"protocol":"http","v":1}
mainflux-mqtt     | {"pid":1,"hostname":"9092868d102d","level":30,"time":1512465258791,"msg":"listening","address":"::","family":"IPv6","port":1883,"protocol":"tcp","v":1}
mainflux-http     | {"aborted":"nats: no servers available for connection","ts":"2017-11-29T09:36:26.373389332Z"}
mainflux-http     | {"aborted":"nats: no servers available for connection","ts":"2017-11-29T17:20:46.940750603Z"}
mainflux-http     | {"aborted":"nats: no servers available for connection","ts":"2017-12-04T16:26:10.56786591Z"}
mainflux-http     | {"aborted":"nats: no servers available for connection","ts":"2017-12-04T16:28:23.475642599Z"}
mainflux-http     | {"aborted":"nats: no servers available for connection","ts":"2017-12-05T09:14:19.216151662Z"}
mainflux-mqtt exited with code 137
mainflux-http exited with code 1
mainflux-message-writer exited with code 2
mainflux-manager exited with code 2
@2014siavash I removed the nginx container and had the same problem:
....
Starting manager        ... done
Starting mqtt-adapter   ... done
Starting message-writer ... done
Starting http-adapter   ... done
Starting Nginx...
Pulling nginx (nginx:1.13-alpine)...
1.13-alpine: Pulling from library/nginx
Digest: sha256:34aa80bb22c79235d466ccbbfa3659ff815100ed21eddb1543c6847292010c4d
Status: Image is up to date for nginx:1.13-alpine
WARNING: The create command is deprecated. Use the up command with the --no-start flag instead.
Creating mainflux-nginx ...
Creating mainflux-nginx ... done
Starting nginx ... error
ERROR: for nginx  Cannot start service nginx: Cannot link to a non running container: /mainflux-http AS /mainflux-nginx/mainflux-http
ERROR: No containers to start
Aborting due to errexit on line 136. Exit code: 1
Stopping Nginx...
Stopping Mainflux composition...
....

I remembered that removing the container is not enough. Could you please say how you removed it? (pls copy and paste your command line here for removing)
There was an ID which I used it to remove the container. Unfortunately, I have not access to my Ubuntu system now, else I could explain the precise steps I did to make it correct.

Hi @2014siavash
I checked my containers:
user@user-VirtualBox:~/mainflux/bin$ docker ps -a
CONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS                           PORTS               NAMES
a8cae709804e        nginx:1.13-alpine              "nginx -g 'daemon ..."   About an hour ago   Created                                              mainflux-nginx
9092868d102d        mainflux/mqtt-adapter:latest   "node mqtt.js"           17 hours ago        Exited (137) About an hour ago                       mainflux-mqtt
03ff63f803e1        mainflux/http:latest           "/exe"                   6 days ago          Exited (1) About an hour ago                         mainflux-http
edb0c111bc07        mainflux/writer:latest         "/exe"                   6 days ago          Exited (2) About an hour ago                         mainflux-message-writer
a3cae9359efa        mainflux/manager:latest        "/exe"                   6 days ago          Exited (2) About an hour ago                         mainflux-manager
cbcb5baa82df        cassandra:3.0.14               "/docker-entrypoin..."   6 days ago          Exited (143) About an hour ago                       mainflux-cassandra
b97abbfb0323        nats:1.0.2                     "/gnatsd -c gnatsd..."   6 days ago          Exited (2) About an hour ago                         mainflux-nats
And then, I removed it using the container id:
user@user-VirtualBox:~/mainflux/bin$ docker rm a8cae709804e
a8cae709804e

@aurliocano what's the dockerd version?
Also, looks like the NATS was not started correctly.

It seems same as me!!!!! Maybe all containers should be removed, and then started again.
Sorry, I have no idea yet. But, it works for me!

I removed all containers and pulled them all this time and it didn't work.
@drasko my dockerd version is:
Docker version 17.03.2-ce, build f5ec1e2

Covered by #135.