text:
24 hour test failure using sdk 1.3.0

I am using Raspbian with AVS SDK 1.3.0.
I have a couple different tests I am doing here to ensure connectivity (and "false detects") but the issue I am reporting is specific to the App getting stuck in a bad state and not able to recover:

No active playback on my Alexa device while an external radio source playing on the side.
Playback radio on my Alexa device and at the same time have an external radio source playing on the side.

In both cases, SampleApp stops responding somewhere in the middle. When I look at the terminal, it shows several "Connecting..." messages, I imagine that means it was disconnected from the cloud and trying to reconnect at several different times. Also at some point it goes into a bad state and doesn't recover from there.
I started the app with debug9 (although it wasn't built with debug enabled). Hopefully it may still give some clue. Look for "Connecting.." and then at the end of log you may see it eventually gets stuck.
-==========================================
Running app with log level: DEBUG9
2018-01-24 21:55:47.060 [  1] W Logger:debugLogLevelSpecifiedWhenDebugLogsCompiledOut:level=DEBUG9:
WARNING: By default DEBUG logs are compiled out of RELEASE builds.
Rebuild with the cmake parameter -DCMAKE_BUILD_TYPE=DEBUG to enable debug logs.
2018-01-24 21:55:47.066 [  1] I ConfigurationNode:initializeSuccess
2018-01-24 21:55:47.622 [  1] I AlertScheduler:executeScheduleNextAlertForRendering::no work to do.
2018-01-24 21:55:47.632 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=SpeechSynthesizer,name=Speak,handler=0x269870,policy=BLOCKING
2018-01-24 21:55:47.633 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=AudioPlayer,name=ClearQueue,handler=0x26a1c0,policy=NON_BLOCKING
2018-01-24 21:55:47.633 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=AudioPlayer,name=Stop,handler=0x26a1c0,policy=NON_BLOCKING
2018-01-24 21:55:47.633 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=AudioPlayer,name=Play,handler=0x26a1c0,policy=NON_BLOCKING
2018-01-24 21:55:47.633 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=SpeechRecognizer,name=ExpectSpeech,handler=0x268df0,policy=NON_BLOCKING
2018-01-24 21:55:47.633 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=SpeechRecognizer,name=StopCapture,handler=0x268df0,policy=NON_BLOCKING
2018-01-24 21:55:47.633 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=Alerts,name=DeleteAlert,handler=0x26ac40,policy=NON_BLOCKING
2018-01-24 21:55:47.633 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=Alerts,name=SetAlert,handler=0x26ac40,policy=NON_BLOCKING
2018-01-24 21:55:47.633 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=System,name=SetEndpoint,handler=0x2749a8,policy=NON_BLOCKING
2018-01-24 21:55:47.634 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=System,name=ResetUserInactivity,handler=0x268bac,policy=NON_BLOCKING
2018-01-24 21:55:47.634 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=Speaker,name=AdjustVolume,handler=0x273310,policy=NON_BLOCKING
2018-01-24 21:55:47.635 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=Speaker,name=SetMute,handler=0x273310,policy=NON_BLOCKING
2018-01-24 21:55:47.635 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=Speaker,name=SetVolume,handler=0x273310,policy=NON_BLOCKING
2018-01-24 21:55:47.635 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=TemplateRuntime,name=RenderPlayerInfo,handler=0x273750,policy=HANDLE_IMMEDIATELY
2018-01-24 21:55:47.636 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=TemplateRuntime,name=RenderTemplate,handler=0x273750,policy=HANDLE_IMMEDIATELY
2018-01-24 21:55:48.167 [  1] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
########################################
Alexa is currently idle!
########################################
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround40
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround41
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround50
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround51
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm_dmix.c:990:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
2018-01-24 21:55:50.091 [  1] I SensoryKeywordDetector:License expires on 01 Apr 2018 00:00:00 GMT
2018-01-24 21:55:50.091 [  1] I SensoryKeywordDetector:Sensory library license does not expire for at least 60 more days.
#    #     #  #####      #####  ######  #    #
# #   #     # #     #    #     # #     # #   #
#   #  #     # #          #       #     # #  #
#     # #     #  #####      #####  #     # ###
#######  #   #        #          # #     # #  #
#     #   # #   #     #    #     # #     # #   #
#     #    #     #####      #####  ######  #    #
   #####                                           #
  #     #   ##   #    # #####  #      ######      # #   #####  #####
  #        #  #  ##  ## #    # #      #          #   #  #    # #    #
   #####  #    # # ## # #    # #      #####     #     # #    # #    #
        # ###### #    # #####  #      #         ####### #####  #####
  #     # #    # #    # #      #      #         #     # #      #
   #####  #    # #    # #      ###### ######    #     # #      #

+----------------------------------------------------------------------------+
|                                  Options:                                  |
| Wake word:                                                                 |
|       Simply say Alexa and begin your query.                               |
| Tap to talk:                                                               |
|       Press 't' and Enter followed by your query (no need for the 'Alexa').|
| Hold to talk:                                                              |
|       Press 'h' followed by Enter to simulate holding a button.            |
|       Then say your query (no need for the 'Alexa').                       |
|       Press 'h' followed by Enter to simulate releasing a button.          |
| Stop an interaction:                                                       |
|       Press 's' and Enter to stop an ongoing interaction.                  |
| Privacy mode (microphone off):                                             |
|       Press 'm' and Enter to turn on and off the microphone.               |
| Playback Controls:                                                         |
|       Press '1' for a 'PLAY' button press.                                 |
|       Press '2' for a 'PAUSE' button press.                                |
|       Press '3' for a 'NEXT' button press.                                 |
|       Press '4' for a 'PREVIOUS' button press.                             |
| Settings:                                                                  |
|       Press 'c' followed by Enter at any time to see the settings screen.  |
| Speaker Control:                                                           |
|       Press 'p' followed by Enter at any time to adjust speaker settings.  |
| Info:                                                                      |
|       Press 'i' followed by Enter at any time to see the help screen.      |
| Quit:                                                                      |
|       Press 'q' followed by Enter at any time to quit the application.     |
+----------------------------------------------------------------------------+
############################
Listening...
############################
2018-01-24 21:56:04.811 [  2] I DirectiveProcessor:setDialogRequestIdLocked:oldValue=,newValue=8bfbb6b3-1c24-4e62-918a-184ef7cd1164
2018-01-24 21:56:06.704 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechRecognizer",name:"StopCapture",messageId:"5d8fc7e6-a527-4068-9fb7-c37eeb481d50",dialogRequestId:""}
2018-01-24 21:56:06.705 [  4] I DirectiveRouter:preHandleDirective:messageId=5d8fc7e6-a527-4068-9fb7-c37eeb481d50,action=calling
2018-01-24 21:56:06.705 [  5] I DirectiveRouter:handleDirective:messageId=5d8fc7e6-a527-4068-9fb7-c37eeb481d50,action=calling
###########################
Thinking...
###########################
2018-01-24 21:56:06.714 [  6] I InProcessAttachmentReader:readFailed:reason=SDS is closed
2018-01-24 21:56:06.943 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechSynthesizer",name:"Speak",messageId:"62154923-7581-43d8-a321-cf04af47f1c4",dialogRequestId:"8bfbb6b3-1c24-4e62-918a-184ef7cd1164"}
2018-01-24 21:56:06.944 [  4] I DirectiveRouter:preHandleDirective:messageId=62154923-7581-43d8-a321-cf04af47f1c4,action=calling
2018-01-24 21:56:06.945 [  5] I DirectiveRouter:handleDirective:messageId=62154923-7581-43d8-a321-cf04af47f1c4,action=calling
2018-01-24 21:56:06.950 [  7] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2018-01-24 21:56:07.474 [  7] I InProcessAttachmentReader:readFailed:reason=SDS is closed
###########################
Speaking...
###########################
########################################
Alexa is currently idle!
########################################
############################
Listening...
############################
2018-01-24 22:02:17.108 [  2] I DirectiveProcessor:setDialogRequestIdLocked:oldValue=8bfbb6b3-1c24-4e62-918a-184ef7cd1164,newValue=a48e8bd4-1f18-479a-8ecc-5cc51015a2f9
2018-01-24 22:02:18.797 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechRecognizer",name:"StopCapture",messageId:"e203f03f-9097-453d-a10d-456d950c8514",dialogRequestId:""}
2018-01-24 22:02:18.798 [  4] I DirectiveRouter:preHandleDirective:messageId=e203f03f-9097-453d-a10d-456d950c8514,action=calling
2018-01-24 22:02:18.798 [  5] I DirectiveRouter:handleDirective:messageId=e203f03f-9097-453d-a10d-456d950c8514,action=calling
###########################
Thinking...
###########################
2018-01-24 22:02:18.807 [  6] I InProcessAttachmentReader:readFailed:reason=SDS is closed
2018-01-24 22:02:19.019 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechSynthesizer",name:"Speak",messageId:"a3b33442-f831-4e77-bba8-680caece88c8",dialogRequestId:"a48e8bd4-1f18-479a-8ecc-5cc51015a2f9"}
2018-01-24 22:02:19.020 [  4] I DirectiveRouter:preHandleDirective:messageId=a3b33442-f831-4e77-bba8-680caece88c8,action=calling
2018-01-24 22:02:19.020 [  5] I DirectiveRouter:handleDirective:messageId=a3b33442-f831-4e77-bba8-680caece88c8,action=calling
2018-01-24 22:02:19.025 [  7] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2018-01-24 22:02:19.076 [  7] I InProcessAttachmentReader:readFailed:reason=SDS is closed
###########################
Speaking...
###########################
########################################
Alexa is currently idle!
########################################
############################
Listening...
############################
2018-01-24 22:02:24.581 [  2] I DirectiveProcessor:setDialogRequestIdLocked:oldValue=a48e8bd4-1f18-479a-8ecc-5cc51015a2f9,newValue=395f2784-7264-4a30-aa6e-1ac8c2c6c077
2018-01-24 22:02:27.071 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechRecognizer",name:"StopCapture",messageId:"88348f6c-3c51-41b0-814c-2cd80ff35c5f",dialogRequestId:""}
2018-01-24 22:02:27.072 [  4] I DirectiveRouter:preHandleDirective:messageId=88348f6c-3c51-41b0-814c-2cd80ff35c5f,action=calling
2018-01-24 22:02:27.072 [  5] I DirectiveRouter:handleDirective:messageId=88348f6c-3c51-41b0-814c-2cd80ff35c5f,action=calling
###########################
Thinking...
###########################
2018-01-24 22:02:27.081 [  6] I InProcessAttachmentReader:readFailed:reason=SDS is closed
2018-01-24 22:02:27.293 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechSynthesizer",name:"Speak",messageId:"c58f8905-f273-46ea-bb43-97214f6ed95b",dialogRequestId:"395f2784-7264-4a30-aa6e-1ac8c2c6c077"}
2018-01-24 22:02:27.294 [  4] I DirectiveRouter:preHandleDirective:messageId=c58f8905-f273-46ea-bb43-97214f6ed95b,action=calling
2018-01-24 22:02:27.294 [  5] I DirectiveRouter:handleDirective:messageId=c58f8905-f273-46ea-bb43-97214f6ed95b,action=calling
2018-01-24 22:02:27.297 [  7] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2018-01-24 22:02:27.325 [  7] I InProcessAttachmentReader:readFailed:reason=SDS is closed
###########################
Speaking...
###########################
########################################
Alexa is currently idle!
########################################
2018-01-24 22:54:24.684 [  6] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
########################################
Alexa is currently idle!
########################################
2018-01-24 23:46:45.175 [  8] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
########################################
Alexa is currently idle!
########################################
############################
Listening...
############################
2018-01-25 00:13:25.004 [  2] I DirectiveProcessor:setDialogRequestIdLocked:oldValue=395f2784-7264-4a30-aa6e-1ac8c2c6c077,newValue=764f38fc-cd8e-4017-aa6f-a2c56dfc17f2
2018-01-25 00:13:27.199 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechRecognizer",name:"StopCapture",messageId:"3604dbfd-b680-426f-b391-e94fd89ee826",dialogRequestId:""}
2018-01-25 00:13:27.200 [  4] I DirectiveRouter:preHandleDirective:messageId=3604dbfd-b680-426f-b391-e94fd89ee826,action=calling
2018-01-25 00:13:27.200 [  5] I DirectiveRouter:handleDirective:messageId=3604dbfd-b680-426f-b391-e94fd89ee826,action=calling
###########################
Thinking...
###########################
2018-01-25 00:13:27.209 [  9] I InProcessAttachmentReader:readFailed:reason=SDS is closed
########################################
Alexa is currently idle!
########################################
2018-01-25 00:43:00.677 [  9] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
########################################
Alexa is currently idle!
########################################
############################
Listening...
############################
2018-01-25 01:20:57.411 [  2] I DirectiveProcessor:setDialogRequestIdLocked:oldValue=764f38fc-cd8e-4017-aa6f-a2c56dfc17f2,newValue=f783c9e2-87df-41e2-9e5f-9a3fa636fa9e
2018-01-25 01:21:00.496 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechRecognizer",name:"StopCapture",messageId:"64f14a1a-3186-4e8e-a412-7d8da1e883d9",dialogRequestId:""}
2018-01-25 01:21:00.497 [  4] I DirectiveRouter:preHandleDirective:messageId=64f14a1a-3186-4e8e-a412-7d8da1e883d9,action=calling
2018-01-25 01:21:00.497 [  5] I DirectiveRouter:handleDirective:messageId=64f14a1a-3186-4e8e-a412-7d8da1e883d9,action=calling
###########################
Thinking...
###########################
2018-01-25 01:21:00.510 [  a] I InProcessAttachmentReader:readFailed:reason=SDS is closed
2018-01-25 01:21:00.739 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechSynthesizer",name:"Speak",messageId:"80f7d423-a8a2-498b-a727-af639a19f150",dialogRequestId:"f783c9e2-87df-41e2-9e5f-9a3fa636fa9e"}
2018-01-25 01:21:00.739 [  4] I DirectiveRouter:preHandleDirective:messageId=80f7d423-a8a2-498b-a727-af639a19f150,action=calling
2018-01-25 01:21:00.740 [  5] I DirectiveRouter:handleDirective:messageId=80f7d423-a8a2-498b-a727-af639a19f150,action=calling
2018-01-25 01:21:00.744 [  7] E MediaPlayer:saveOffsetBeforeTeardown - gst_element_query_position failed
2018-01-25 01:21:00.770 [  7] I InProcessAttachmentReader:readFailed:reason=SDS is closed
###########################
Speaking...
###########################
########################################
Alexa is currently idle!
########################################
2018-01-25 01:40:45.163 [  a] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
########################################
Alexa is currently idle!
########################################
2018-01-25 02:33:12.682 [  b] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
########################################
Alexa is currently idle!
########################################
2018-01-25 03:24:30.259 [  c] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
########################################
Alexa is currently idle!
########################################
############################
Listening...
############################
2018-01-25 03:47:23.199 [  2] I DirectiveProcessor:setDialogRequestIdLocked:oldValue=f783c9e2-87df-41e2-9e5f-9a3fa636fa9e,newValue=eac1dc3f-a839-4ffe-b4dd-74cbc717bcf5
2018-01-25 03:47:25.059 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechRecognizer",name:"StopCapture",messageId:"5a40f901-aed4-4a78-93df-8a6bff0b5668",dialogRequestId:""}
2018-01-25 03:47:25.060 [  4] I DirectiveRouter:preHandleDirective:messageId=5a40f901-aed4-4a78-93df-8a6bff0b5668,action=calling
2018-01-25 03:47:25.060 [  5] I DirectiveRouter:handleDirective:messageId=5a40f901-aed4-4a78-93df-8a6bff0b5668,action=calling
###########################
Thinking...
###########################
2018-01-25 03:47:25.069 [  d] I InProcessAttachmentReader:readFailed:reason=SDS is closed
########################################
Alexa is currently idle!
########################################
############################
Listening...
############################
2018-01-25 03:59:40.650 [  2] I DirectiveProcessor:setDialogRequestIdLocked:oldValue=eac1dc3f-a839-4ffe-b4dd-74cbc717bcf5,newValue=f517cfb9-e517-4472-8bc6-1ab4ca85d511
2018-01-25 03:59:51.202 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechRecognizer",name:"StopCapture",messageId:"75f0a4cf-eaba-47d2-bf07-dbad9d41a589",dialogRequestId:""}
2018-01-25 03:59:51.203 [  4] I DirectiveRouter:preHandleDirective:messageId=75f0a4cf-eaba-47d2-bf07-dbad9d41a589,action=calling
2018-01-25 03:59:51.204 [  5] I DirectiveRouter:handleDirective:messageId=75f0a4cf-eaba-47d2-bf07-dbad9d41a589,action=calling
###########################
Thinking...
###########################
2018-01-25 03:59:51.213 [  d] I InProcessAttachmentReader:readFailed:reason=SDS is closed
########################################
Alexa is currently idle!
########################################
2018-01-25 04:22:36.758 [  d] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
########################################
Alexa is currently idle!
########################################
2018-01-25 05:16:35.319 [  e] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
########################################
Alexa is currently idle!
########################################
2018-01-25 06:16:15.793 [  f] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
########################################
Alexa is currently idle!
########################################
############################
Listening...
############################
2018-01-25 06:30:52.618 [  2] I DirectiveProcessor:setDialogRequestIdLocked:oldValue=f517cfb9-e517-4472-8bc6-1ab4ca85d511,newValue=66614fba-0cc7-4765-b8fb-54d445279550
2018-01-25 06:30:54.203 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechRecognizer",name:"StopCapture",messageId:"e62bb838-d5a1-4793-9d68-3b45ed575dda",dialogRequestId:""}
2018-01-25 06:30:54.204 [  4] I DirectiveRouter:preHandleDirective:messageId=e62bb838-d5a1-4793-9d68-3b45ed575dda,action=calling
2018-01-25 06:30:54.204 [  5] I DirectiveRouter:handleDirective:messageId=e62bb838-d5a1-4793-9d68-3b45ed575dda,action=calling
###########################
Thinking...
###########################
2018-01-25 06:30:54.213 [ 10] I InProcessAttachmentReader:readFailed:reason=SDS is closed
########################################
Alexa is currently idle!
########################################
############################
Listening...
############################
2018-01-25 06:51:49.083 [  2] I DirectiveProcessor:setDialogRequestIdLocked:oldValue=66614fba-0cc7-4765-b8fb-54d445279550,newValue=798ed9c0-0058-4d73-a672-d2f8b53c42d3
2018-01-25 06:51:51.639 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechRecognizer",name:"StopCapture",messageId:"7bf1c80d-3d36-4564-ae1e-d678b530c00c",dialogRequestId:""}
2018-01-25 06:51:51.639 [  4] I DirectiveRouter:preHandleDirective:messageId=7bf1c80d-3d36-4564-ae1e-d678b530c00c,action=calling
2018-01-25 06:51:51.640 [  5] I DirectiveRouter:handleDirective:messageId=7bf1c80d-3d36-4564-ae1e-d678b530c00c,action=calling
###########################
Thinking...
###########################
2018-01-25 06:51:51.649 [ 10] I InProcessAttachmentReader:readFailed:reason=SDS is closed
########################################
Alexa is currently idle!
########################################
2018-01-25 07:08:30.316 [ 10] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
########################################
Alexa is currently idle!
########################################
2018-01-25 08:07:17.846 [ 11] I HTTP2Transport:setupDownchannelStream:url=https://avs-alexa-na.amazon.com/v20160207/directives
#############################
Connecting...
#############################
2018-01-25 08:07:18.829 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
########################################
Alexa is currently idle!
########################################
2018-01-25 08:07:19.829 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:20.830 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:21.830 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:22.830 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:23.830 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:24.831 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:25.831 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:26.831 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:27.832 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:28.832 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:29.832 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:30.833 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:31.833 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:32.833 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:33.834 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:34.834 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:35.834 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:36.835 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:37.835 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:38.835 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:39.836 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:40.836 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:41.836 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:42.837 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:43.837 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:44.837 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:45.838 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:46.838 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:47.838 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:48.838 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:49.839 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:50.839 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:51.839 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:52.840 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:53.840 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:54.840 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:55.841 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:56.841 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:57.841 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:58.842 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:07:59.842 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:00.842 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:01.843 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:02.843 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:03.843 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:04.844 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:05.844 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:06.844 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:07.845 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:08.845 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:09.845 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:10.846 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:11.846 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
2018-01-25 08:08:12.846 [ 12] I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut
.................
...........................
(It's stuck in this state forever...)

Hi @frozenberg , any luck in reproducing this?

Attached is a debug log. It took about couple hours to get into the failure situation. BTW, the log is produced from stock SDK 1.3.0 , i.e. doesn't have any changes to it, running on Pi3 using Raspbian stretch.
rpi_alexa_fail.log

BTW, you may already guess but in this situation there's no callback from PortAudio, i.e. "PortAudioCallback" function is never called.

Hi again, sorry for the long delay.
Thanks for those logs, we will be looking through them. We've had issues similar to yours that were fixed with our latest release (which dropped today, v1.5.0). Could you try upgrading and seeing if the issue persists?
Also, from what music service provider are you attempting to stream music?
Fede

I just use an mp3 song I uploaded to Amazon music app a while back. On other occasions I stream 99.9 and 95.5 from iHeart Radio.

Were you able to upgrade to the latest SDK version?

I tried the latest SDK and on my initial test left it running for 12+ hours, and it did not crash, which is great! However I still see "Connecting.." prints in between, i.e. it's being disconnected and reconnected several times in between. Looking at the log I posted earlier, just before the "Connecting..." prints if I look at the reason, I primarily see two reasons:
2018-02-08 20:04:43.233 [  1] 0 MessageRouter:connectionStatusChanged:reason=ACL_CLIENT_REQUEST,newStatus=PENDING
2018-02-08 21:04:16.711 [  3] 1 AlertsCapabilityAgent:executeOnConnectionStatusChanged:status=PENDING,reason=SERVER_SIDE_DISCONNECT
Why does it get disconnected several times?
Also, I will be running more tests for the next few days.

Those server_side_disconnects are expected. The service sends those every 5 or so hours.

I have attached another log here. Just to keep things in perspective, this is a different test (constant Alexa questions going on in back ground) and on a different architecture (uses Raspbian on a Dual core ARM Cortex A9). So, it ran fine for ~14 hours before seeing couple irregularities:
(1) At "2018-02-15 14:24:19.019" time in log - Constantly toggling between Idle and Listening states after this. I thought typically it should go Listening->Thinking and then optionally Speaking states before going to Idle state?
(2) At "2018-02-15 14:29:18.392" time in log  - Constantly trying to reconnect till I stopped the app
alexa_log.tar.gz

Ok, judging from those logs it looks like it could be a network issue. Was your network down at any point? If you see this issue again, could you try quitting the app and immediately starting back up?
If you do that and the app begins working immediately it could point to a bug. If it continues to be in an unconnected state it may just be your network.
Let me know,
Fede

The network was up because next to this test-setup I was running another test setup which was still functioning.

Today after it stopped responding, it was playing some kind of "ding" sounds every few seconds, which I haven't noticed before.

Ok if that's the case I'm still looking into it... Though it might be helpful if you try the app restart idea next time you see the issue. Just so we can be 100% sure.

Whenever I see the app stalled and I restart, it has 100% of the time worked. Please note that I do not restart the processor, just the SampleApp.

On rereading the log (and some help from the rest of the team) it looks like a StateProvider may be locked up: 2018-02-15 18:13:58.095 [  7] E ContextManager:updateStatesLoopFailed:reason=stateProviderTimedOut
Can you try editing ContextManager.cpp? On line 247 right before stateProviderLock.unlock(); add
for (const auto& stateProvider : m_pendingOnStateProviders) {
ACSDK_ERROR(LX("updateStatesLoopFailed").d("waiting on ", stateProvider.name));
}
This will let us see what is locking up, at least.
Thanks,
Fede

Thanks Fede. Due to my travelling it may take a couple days before I try this out but be assured I will try it and get back, unless you figure out something before that :)

@az2022,
Were you able to check Fede's suggestion? Please keep us informed.

Yes, was able to try out Fede's suggestion. Apparently this time the reason for failure is back to what I originally reported with this issue when using sdk 1.4.0, i.e. "AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut". Log attached.
alexa_fail_log_02_23.zip

Hi @az2022,
The steady stream of reader timeouts shown in your log points to a problem with the microphone audio input.  Your keyword detector is trying to read from the SDS circular buffer, but nothing seems to be feeding data into it.
Since you are only reproducing this problem with long test runs, we're going to have to keep chasing it through additional logging.  There are a couple of things we can do from here to get more detail:

Add some trace messages to PortAudioMicrophoneWrapper.cpp.  Something like ConsolePrinter::simplePrint(__func__); at the start of startStreamingMicrophoneData(), stopStreamingMicrophoneData(), and PortAudioCallback().  That last one will be noisy, so you may want to play with logging intermittently if it's too much; the goal is to see in your log whether there is evidence that portaudio is still trying to write data to the SDS once you start seeing reader timeout messages.
If the trace messages above show that portaudio stopped calling PortAudioCallback(), then it may be useful to enable debug messages in portaudio itself.  Unfortunately, the only way to do this is by rebuilding the portaudio library.  Pass the --enable-debug-output flag to portaudio's configure script, then make and make install.  And finally, make sure your build of SampleApp is using the portaudio that you just compiled.  This should turn on some debug messages from PortAudio which may give us further clues.

Ken

With my earlier inputs I already mentioned that "PortAudioCallback" is not being called when in this situation. It's possible there are multiple problems here. Also I mentioned that I tried bumping up the priority of this task, which seemed to help but did not fix the issue. At least one cause I think is, whenever the callback is not serviced within a certain time, it chokes. Running close to 40 threads (when play back in ON) is not a good idea, especially on Linux where lot of time is spent just on context switching threads. Also, I see all threads are at the same priority, hence a thread responsible for printing stuff to the screen is competing against something like "PortAudioCallback" which is not good. Running this app on a more powerful processor may hide some of these problems.
BTW, is there a minimum processor, RAM etc requirement to run the AVS app?
I can spend more time to debug this issue but isn't your team able to reproduce this?? Do you test whether the SDK can be run for several days at a time on something like a Pi3 (or a slower CPU) or am I the only person who sees this?

ok.. so here's another log with the different symptom/failure condition, i.e. not able to connect to AVS, which exercises fede's suggested print:
2018-02-28 01:42:12.332 [  8] E ContextManager:updateStatesLoopFailed:waiting on =SpeechState,nameSpace=SpeechSynthesizer
alexa_fail_zynq_02_28.zip
This log also has the port-audio debug output enabled.

Hi @az2022,
We've written the SDK to be portable by following the C++11 standard. This standard does not provide a way to configure thread priorities, hence all threads having the same priority.
To give you some rough numbers on memory usage numbers, we found the RAM usage to be about 20-40 MB, depending on app state (i.e. idle, playing music, wake word detection built in, etc.). This was conducted on a Raspberry Pi.
We have tested whether the SDK can be run for several days, generally on a Raspberry Pi and haven't seen the same issues you're seeing.
Based on your logs, it looks like we may have some sort of circular dependency between components and one component is getting into a bad state.
Could you give us some specific reproduction steps so that we can verify and provide a fix if it turns out to be a bug?
Thanks,
Sanjay

@sanjayrd
The issue is seen randomly and there's not much involved in reproducing this:

Run the stock SDK on a Pi
Leave it running for a few days

I am able to see the issue in v 1.3, 1.4 and 1.5 (did not try older versions), but it's a bit difficult to get into this state with v1.5, so I would recommend using v1.3 or v1.4 to reproduce this sooner than later.
In some tests, I have had NPR radio running in the background, in another I had continuous "Alexa" triggers running and in the simplest case I just left it as is in ON state, i.e. no induced noises, triggers etc and every few hours I would ask a query to make sure it's still functioning.
In all 3 cases I have run into the issue where Alexa stops responding. Now the underlying issue could be
different (either PortAudio callback failures or the circular dependency you mentioned) as noticed from the logs I provided. I haven't yet co-related whether only a specific type of test induces a specific error, apart from the fact that "Alexa" stops responding.
As for the PortAudio suggested latency, it's currently defaulted to 32 msecs which I thought should be more than enough to process a callback function (it typically takes <200 usecs). I can bump it up to 0.15 (i.e. 150 msecs) but I think it may allow me to run for a longer run with expense of increased latency as time goes by. I can try this and see if I am still able to reproduce the other lockup issue on my end.

I agree with you statement that PortAudio changes will not affect the other issue.

Hi @az2022,
Are you still experiencing issues? If so, can you try upgrading to SDK v1.6 and let us know if it solved the issues?
Thanks,
Benny

I have yet to try v1.6. I will post back once I give it a try.

@az2022, we have recently identified an issue which may be the cause of the issue you are describing.  Please wait for our 1.7 release (which will be shortly), and update to that.  Please let us know if that solves your issue.  Thanks.

@dhpp That's good news and thanks for the update. Will wait for next release to test it.
So, will your fixes affect the PortAudio latency issue as well or the fix is specific to the state machine lockup only?

@az2022, please update to our 1.7 release, which is now available.  It will address the connection state lockup issue.
Regarding the PortAudio latency, then I agree with the others who have advised in this thread that it is quite platform specific, and our Client SDK probably cannot address this specific concern (since, as mentioned above, our general target platform has sufficient processing power that this is not an issue in those use cases).

Has the way refreshtoken acquiring changed? I don't see a "AuthServer" python script in there anymore and instructions still point to use that.

Yes, 1.7 uses Code Based Linking.  Please see https://github.com/alexa/avs-device-sdk/wiki/Code-Based-Linking----Configuration-Update-Guide

Hi az2022,
Which instructions still point to using the "AuthServer" python script?
Thank you,
-SWH

@scotthea-amazon : https://github.com/alexa/avs-device-sdk/wiki/Raspberry-Pi-Quick-Start-Guide

Thanks. Am not able to reproduce the issue anymore with 1.7.1.

sdkVersion: 1.10.0
I also get same issue
I AbstractKeywordDetector:readFromStreamFailed:reason=readerTimeOut

authors: AnupB-REPL BennyAvramson az2022 bandkenamazoncom dhpp frozenberg kencecka mavamazon sanjayrd scotthea-amazon

repo: alexa/avs-device-sdk


text:
New Component gist - manage gist in CLI

run ./gist/gist help or just go to README
for more information
Pull Request Label:

[ ] Bug
[ ] New feature
[ ] Enhancement
[x] New component
[ ] Typo

Pull Request Checklist:

[x] Have you followed the guidelines for contributing?
[x] Have you checked that there aren't other open pull requests for the same fix or component?
[x] Have you ran the tests locally with bats tests?

@alexanderepstein

Have you ran the tests locally with bats tests?

Yes, but since most of commands in this tool require Github API token (with gist scope), the tests I made didn't cover its core utilities. Maybe there is a better way to do the test?
I promise this tool is really useful and user-friendly with prompts for toke validation and other stuffs, please give it a try!

I like this, it will most definitely make it to bash-snippets. I will need to take some time to read through it and review it before I can bring it in but overall it looks like it brings some nice functionality! Good work 👍

@alexanderepstein
Cool! Also, I made some improvement and README in latest commits.
Because I am new to bash, so if you find somewhere in code hard to read,  smells weird or violates some conventions, don't hesitate to ask me to do fix.

@alexanderepstein
Did some improvements.
Also, I add my api token from another Github account into test, so for now the tests should really meaningful for most of the sub-commands. But the weird thing is, all tests pass on my machine (Ubuntu 18.04), but test for gist new and gist edit never works on Travis build. Could you give it a try on your machine?

@alexanderepstein
Thanks for your feedback, I'll resolve/answer them in these two days

README is up to date. Now it has index at the top. Also includes newly-added feature like gist tag, gist lan or pipe feature.

@alexanderepstein
Did some changes/improvements in the last few weeks:

Refactor/Bug fix for gist tag and the way to process description which are stored in local
Update README
Mac compatibility
debug option for JSON parsing
For your latest review, you request to apply checkInternet() on every http request like other scripts.
But since all request goes to github.com in this script, I just removed checkInternet() and integrated its logic into http_method().

All your request are resolved, now you can review this PR again!

Thanks for this, hopefully I will release a new version of bash-snippets soon and this will be part of that release!

Cool! Thanks for the review.
The script I maintain on gist(which doesn't include Bash-Snippets stuff) is ahead of this PR with some refinement. I'll make another PR later to sync them.

source: gharchive/pull-request

authors: alexanderepstein typebrook

repo: alexanderepstein/Bash-Snippets

license: mit

license_type: permissive

license_source: bigquery


text:
Defeito 66 - H12 - Omissão

A falta de detalhes sobre como as sugestões serão submetidas , revisadas e rastreadas.

Correção realizada.

source: gharchive/issue

repo: alexandreggoncalves/appControleEstoque

license: MIT

license_source: github-api


text:
Defeito 90 - H13 - Ambiguidade

Expressões "amigável e intuitiva" podem representar diferentes significados.

Correção realizada.


text:
Ivy repositories support

But for Ivy "configurations", which are a generalization of Maven scopes, the Ivy model seems easier and less error prone / ambiguous than the Maven one. In particular, there's no inheritance, no dependency management, supposedly no property substitution needed for published artifacts, ...

See the points discussed here: https://gitter.im/lihaoyi/Ammonite/archives/2015/06/17
Exclusions are a bit more complex (more matched fields, regexes).

Features that need to be added for that:

[ ] replace Maven scopes (hard-coded compile/runtime/test/...) by Ivy-like configurations, some configuration map is likely to be added to Project, and a default Maven one defined in Resolution,
[ ] create an implementation of Remote (repository) for Ivy repositories, requiring the next point,
[ ] parse Ivy repositories patterns (examples),
[ ] in Project definition, change the type of dependencies: Seq[Dependency] to Seq[(String, Dependency)], where String would stand for the configuration of Project this dependency is added to,
[ ] add support for Ivy more refined exclusions (pattern matching, ...),
[ ] add some support for specified before hand conflict resolution.

Possibly not exhaustive, and hopefully not hiding or implying any show stopper or too complex issues.

Needs https://github.com/alexarchambault/coursier/issues/83.

in particular the ivy local directory

You mean ~/.ivy2/cache? ~/.ivy2/local is already supported, thanks to the Maven POMs that SBT puts in it.

Yes, the ivy cache.

authors: alexarchambault fommil

repo: alexarchambault/coursier


text:
🛑 Secret Website 1 is down

In 720535a, Secret Website 1 ($SECRET_WEBSITE_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Secret Website 1 is back up in 6283349.

repo: alexchapar/status-page


text:
⚠ Secret Website 3 has degraded performance

In 6cfdedb, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2926 ms

Resolved: Secret Website 3 performance has improved in d1fc88f.


text:
QUESTION: How to get the middle of audio?

Hello, Alex.
I asked about extracting part of audio to you, and I solved that problem.
Thank You!
But, got something wrong about getting middle part of audio.
I tried
components.queryItems?.append(URLQueryItem(name: "range", value: "\(contentStart)-\(contentEnd)"))

this to get part of audio from youtube video.
Although, I successed for get 0:00~0:50 audio easily, I failed to get 2:00~2:50 audio.(Exactly, I got Audio Data, but it couldn;'t played with AVAudioPlayer...)
I can't understand why from 0:00 can be played, and others are impossible...
I always got this Error..😂😂
error	NSError	domain: "NSOSStatusErrorDomain" - code: 1954115647	0x000000030342d0e0

So an audio file is, very simply put, set up like this: First bytes in the file is metadata that defines the codec etc for a player to know how to play this file, after that you have actual content. So when you only retrieve data from a point that is not 0, you basically remove the metadata, which is crucial.
Want do you want to achieve? Play the audio file from a certain position?

Yeah right!
Getting whole of the file needs too long time to wait and request too much of LTE or 5G data usage, so I want to get it only parts of audio like 0:00~0:10, 1:00~1:10, 2:00~2:10,...
Then I will use each part to play in the App.

@alexeichhorn  Do you need anything I have to provide more information?

If you plug in the unmodified url straight into AVPlayer (no manual downloading) and seek directly to the desired starting position, it shouldn't load unnecessary parts of the file. Or did you try this already?

I tried that and I couldn't play it.🥲🥲
Then you mean if I need to play the part of audio File, I have to download all data of the file?
And if it's long time to download, use this code several times
var request = URLRequest(url: externalURL)
                    request.addValue("bytes=\(startByte)-\(endByte)", forHTTPHeaderField: "Range")
                    var (data, response) = try await URLSession.shared.data(for: request)

to get each part(ex)0:00~2:00, 2:00~4:00, 4:00~6:00,...) of the audio data. Then append all of the audio data for using in player??

How did you try it?
Works for me. I have an audio app and I'm using AVPlayer (might not work on AVAudioPlayer). See this:
let audioStream = try await YouTube(url: URL(string: "https://www.youtube.com/watch?v=xyz)!)
                .streams
                .filterAudioOnly()
                .filter { $0.isNativelyPlayable }
                .highestAudioBitrateStream()!
let playerItemAudio = AVPlayerItem(url: audioStream.url)

I'm so sorry to answer lately.
I could make it works with getting whole Audio file from your server.
I used a method where a single audio file is divided into 15-minute segments, fetched, and then combined for use.

repo: alexeichhorn/YouTubeKit


text:
Add argument checks and fail early

In each builder, we should have some sort of argument check, like this.
Errors should be caught and thrown as early as possible. If, for example, these checks were done right before the build() function was called, it would be extremely hard to debug since the stack trace would only point to the toString()/build() line and not where the actual error happened.

@alexfu, that's what I normally do for methods exposed to an interface. We can create a separate class which is only responsible for validation or create a new interface containing a 'valid()' method which every builder should implement.
What do you think?

You can use Preconditions for this.

Or we can use the Java [Objects] (http://docs.oracle.com/javase/7/docs/api/java/util/Objects.html) class instead of introducing new library.
public CreateTableBuilder column(Column column) {
  Objects.requireNonNull(column, "A non-null column is required.");
  definitions.add(column);
  return this;
}

If the validation becomes more detailed and specific, then we need to create our own.

Didn't know Objects had those checks. If It's just to check if an argument is null i agree.
Preconditions have other checks such as checkArgument(boolean expression) and throws an  IllegalArgumentException accordingly.
It won't introduce another library, we can just include the Preconditions.java file (or just some methods) as it doesn't have any dependencies.

Just noticed that in case of using on Android the Objects class is only available >= API 19, so just a limitation there.

Oops, it is a limitation. Use other library or check null by yourself then.
What sort of android project are you working on at the moment?

@shadeven just a personal app, ticket manager for train trips here in portugal. It only imports the tickets from pdfs that the company sends by email; notifies of the next trip with convenient information like gate, carriage and seat number.

@monxalo, sounds interesting. I want to up-skill in android development area, please let me know if you need extra hands.

I'm in favor for doing null checks by hand or use Assert.assertNotNull. Using a third party library like Guava brings in unnecessary code in addition to depending on yet another library.

@alexfu Like i said above you don't need to add the library as a dependency, just add the file needed to the util package like u2020.

@monxalo sorry, must of missed that. that works too.

authors: alexfu monxalo shadeven

repo: alexfu/SQLiteQueryBuilder


text:
[Feature] Handle highspeed connections in graphs

Is your feature request related to a problem? Please describe.
When running on Multi-Gig internet connections the Y axis of the download and upload does not scale every well.
It keep showing it in Mbits where I would expect Gbps like 1.95
The single stats do show it in Gbps.

Describe the solution you'd like
Show speeds higher then 1000Mbit in Gbps.
Additional context
Add any other context or screenshots about the feature request here.

Nvm, kind of fixes itself after a couple of tests. Showing it in mbit is better for when speed drops below Gbit. As well as it does not need some conversion.

repo: alexjustesen/speedtest-tracker


text:
Option to disable the Login Page

would be very convenient to have an option to disable the login page or at least set a timeout value for a new login request.

At this point there is no plan to disable auth

Any chance you'd reconsider? I think it's a fairly common pattern to simply self-host the docker container behind another oauth (google, authelia, etc) and so to have a double login is less than optimal. Would be nice to give people the choice to disable.

I'll keep it in mind but at this time it's not a priority as it would result in a major rewrite and the core functionality for v1 isn't done.

authors: afriedl79 alexjustesen dphildebrandt


text:
Button to reload tables / changes

A small option that I don't know how viable it would be. Right now we have the Reset Ideas button that clears the rolls. If I make a new custom table, I need to close the solo tab and open it again. It would be cool to have a "Reload" button that reloads the tab like closing and opening it does, so that we don't need to close and the reopen the tab to see our new options or changes.

Nice catch! Right now you can just click/tap the lightbulb icon again, and it will refresh all the tables. Though I agree it's unintuitive 😅
In the new 0.2.15 version you can also click the reset button, and it will also refresh your custom tables.

authors: RodWarrior alexkurowski

repo: alexkurowski/solo-toolkit


text:
Inner redirect

Hello!
I would like to redirect some pages internaly, e.g. I would like to keep URL as requested but change what gets executed. I use middleware for this purpouse:
router.use(async function (ctx, next) {
// ...some code
    ctx.path = newPath
// ...some code

  await next()
})

But this doesn't work, what is the right way to do this? Is it even possible?
Thank you,
Matous

@matoous i guess ctx.res.redirect will work

repo: alexmingoia/koa-router


text:
Comparing initial segments of many routes

I run a game where the leaderboard has many different routes, but many routes share an initial segment, or even several initial segments in a path. It would be nice to have ways to compare those initial segments.

After playing around with the data model for a bit, I think that this would require a v2 of the S-expression format. I might implement this in my fork, but I wouldn't expect it to be merged here.

repo: alexozer/flitter


text:
color themes not applied

I've updated the theme in my config but don't see it reflected when I open television:

Just to sanity check, I enabled icons and those are reflected:

Another sanity check is that the config symlink reflects the updates in my version-controlled dotfile, so it doesn't look like any funny business there:

I installed television earlier today on my work machine [where all this is happening] and thought maybe I installed it right before the PR to add color themes was merged, just to be sure I force updated:
$ cargo install --locked --force television

Also, some OS details in case they're relevant:
neofetch
                    'c.          zvalenta@Zachs-MacBook-Air.local
                 ,xNMM.          --------------------------------
               .OMMMMo           OS: macOS 14.6.1 23G93 arm64
               OMMM0,            Host: MacBookAir10,1
     .;loddo:' loolloddol;.      Kernel: 23.6.0
   cKMMMMMMMMMMNWMMMMMMMMMM0:    Uptime: 28 days, 6 hours, 4 mins
 .KMMMMMMMMMMMMMMMMMMMMMMMWd.    Packages: 156 (brew)
 XMMMMMMMMMMMMMMMMMMMMMMMX.      Shell: zsh 5.9
;MMMMMMMMMMMMMMMMMMMMMMMM:       Resolution: 1920x1080
:MMMMMMMMMMMMMMMMMMMMMMMM:       DE: Aqua
.MMMMMMMMMMMMMMMMMMMMMMMMX.      WM: Quartz Compositor
 kMMMMMMMMMMMMMMMMMMMMMMMMWd.    WM Theme: Blue (Dark)
 .XMMMMMMMMMMMMMMMMMMMMMMMMMMk   Terminal: iTerm2
  .XMMMMMMMMMMMMMMMMMMMMMMMMK.   Terminal Font: FiraMonoNerdFontComplete-Regular 12
    kMMMMMMMMMMMMMMMMMMMMMMd     CPU: Apple M1
     ;KMMMMMMMWXXWMMMMMMMk.      GPU: Apple M1
       .cooc,.    .,coo:.        Memory: 2512MiB / 16384MiB

@zachvalenta in order to try out new features in between releases you'd have to clone the repo and build from source.
Installing via cargo will always give you the latest release version which in this case is 0.6.2.
You can confirm that with:
tv --version

Sorry about that! For some reason I saw that merge and thought "new release" but didn't actually verify that was true 🫠

authors: alexpasmantier zachvalenta

repo: alexpasmantier/television


text:
Geocoder raises "Google API error: over query limit." error if non-valid address is entered

With the following settings: Geocoder.configure(always_raise: :all)
Expected behavior
When attempting to geocode invalid input via the Google API, it should raise a Geocoder::InvalidRequest (or similar) error – or, return nil, as is the default behavior when the above config is unset.
Actual behavior
When attempting to geocode invalid input via the Google API, it raises a Google API error: over query limit. error.
Steps to reproduce
Geocoder.coordinates("alksdjf") produces a Google API error: over query limit. error.
Geocoder.coordinates("25 Main St, Cooperstown, NY") behaves as expected.
Environment info

Geocoder version: 1.4.7
Rails version: 5.1.4
Ruby version: 2.5

We have this problem as well. Not using always_raise.
property.address
=> "Cheung Chau Ferry Pier, Crooks Rapid, Sai Kung, Islands, Hong Kong"
[9] pry(main)> coordinates = Geocoder.coordinates(property.address)
Google API error: over query limit.
=> nil
[10] pry(main)> coordinates = Geocoder.coordinates('asd4n2gn')
=> nil

The erroring address gives us a partial match -> https://www.google.com/maps/search/Cheung+Chau+Ferry+Pier,+Crooks+Rapid,+Sai+Kung,+Islands,+Hong+Kong/@22.340281,114.0185396,11z/data=!3m1!4b1
asd4n2gn gives us 'No results'

@alexreisner I've been getting over query limit errors more frequently since posting the issue, regardless of the always_raise settings. I'm wondering if they are related to the upcoming changes to the Google Maps API

I can confirm the fact that the over query limit error is starting to show frequently but randomly recently. I'm pretty sure I'm not exceeding the quota.

Are you using an API key? One cause of intermittent query limit errors is a shared hosting environment or other setup in which Google can't distinguish your requests from those of other users.

I specified the API key and it works better. Thank you.

I have specified the API key in config but still getting over query limit error. Anyone still facing the issue?

@Adilhussain003 me too. :/

@Adilhussain003 @sandroqz
I faced the same issue, but solved it.
The query limit error means that your application's request is denied  because your application sent too many requests per second or per day. If you want to solve this issue, you should save your usage  or increase usage limits by purchasing additional allowance for the GooleMap API or Geocoding API.
If you want to know more detail about this, please read below link.
https://developers.google.com/maps/premium/previous-licenses/articles/usage-limits

Hi! I'm in the same boat. Our Google account is unlimited, so I don't think we're going over. I checked the Google console and didn't see so much activity that we would be going over the per-second query limit.

I'm also having this issue where I'm specifying an API key, with billing linked, but still can't geocode more than 100ish addresses without hitting this. Anyone have any insights?

Yes, I have a few. First, this did stop happening to me when I got the latest version of geocoder (probably because the default changed to open street maps, not google anymore), so def do that if you haven't already. Second, and maybe this is obvious, but make sure you aren't making repetitive calls to the api through automation. Yes, stub out your tests, but consider seed data as well. My working theory is that this happened a lot this summer because we did a lot of db:setup because lots of onboarding summer interns and volunteers, and probably calling the api on the very same address multiple times in a day (maybe even within a minute when I was leading both of them in setting up) made google mad. It's also very likely against the Open Street Maps terms of use, so might still cause problems if it's an ongoing issue. (It isn't for us because no more interns, but I would love to hear if someone has a solution to this problem.)

I have the same problem. Keep getting the error "Google API error: over query limit" where the method GeoCoder.search("address") Interestingly, in the newer account's API, it worked well. (I created a new account just for testing and check if it's because of my account or server). I want you guys to do the same thing and test it out, please.

I am having the same issue, there is no data in my account and getting the same results.

I have the same issue.
Any address returns nil.
irb(main):001:0> Geocoder.coordinates('jason statham')
Google API error: over query limit.
=> nil
irb(main):002:0> Geocoder.coordinates('神奈川県川崎市幸区大宮町１３１０ ミューザ川崎１４３')
Google API error: over query limit.
=> nil

I am seeing this as well without even using Google. Here is my initializer:
Geocoder.configure(
  ip_lookup: :geoip2,
  geoip2: {
    file: Rails.root.join('data', 'GeoLite2-City_20181106', 'GeoLite2-City.mmdb'),
  }
)

If I do Geocoder.search('1.2.3.').first, I see Google API error: over query limit. in the console, but it doesn't raise an error in the app.

@monfresh because you're entering an invalid IP address, Geocoder is treating it as a street address (hence using Google).

Gotcha. That makes sense. I was trying to make sure my app could fall back to "unknown location" if the geocoder city, state, and country were all blank, and that's what came to mind. Is there a known valid IP address that would return blank for country?

authors: Adilhussain003 Frexuz Keijun-KUMAGAI LizPrescott MasashiYokota Mizumaki abdelbk alexreisner ankitchachada eric-norcross monfresh rmjutras sandroqz

repo: alexreisner/geocoder


text:
input doesn't get focus when entering detached mode

Description
I'm not sure if I used correct terms in the title, but anyway when clicking a search box, it doesn't get focused even in our example:
https://xbnmy.csb.app/
Reproduction
https://user-images.githubusercontent.com/499898/131669733-dcca5dea-e44a-4459-ba52-9fc395c4ebe6.MP4
Preview →
Steps

Open the page on mobile
Click on the search box
Click on the search box again
Now you see it is focused

Expected behavior
It should've been focused after the first click.
Environment

iOS 15.0 (dev beta 7) on iPhone 12 with Safari and Chrome
iOS 13.0 on iPhone SE with Safari and Chrome
Autocomplete 1.3.0

Interestingly this doesn't happen on desktop Safari. I wonder if this could be related to hover styles?

It would be great if it could be an option exposed to the developer who could then choose between the two behaviours

By default: it focuses
It doesn't focus, and the end-user need to click in the input

I don't think this needs an option, not focusing is simply a bug @seafoox

We've investigated this behavior and unfortunately, we can't work around it without introducing a hack. This hack forces us to change how we schedule DOM updates, which has unintended side-effects such as reopening the search modal on close when the query has been updated.
We'll close it for now, as this is intentional browser behavior and there's no clean, non-invasive way around it.

This is sad, but I understand why you don't want to fight the browser here... Would a better fix be to have the search box that a user sees on mobile that is actually a button right now, be the <input> that gets moved up at the top of detached mode? That way the user clicked an input and we're not trying to trick anyone.
I don't know if it's possible, and if it is, it's probably a bunch of work. As of right now the search feels kind of broken for mobile users since it requires that extra tap.

We did consider that approach, but it would require faking the input to look like a button, which likely is a nightmare for accessibility behaviour.
I definitely see what you mean with it feeling a little broken, but what we found is the best fix is showing some UI on empty query, either query suggestions or static content, which makes that screen more interactive, and also makes more sense not to immediately cover it up with the keyboard.
You can see a similar pattern in many mobile applications (twitter, reddit), where the search button goes to an explore page, which allows people to find that immediately, but also requires two taps to get to the actual search bar.
We might reconsider this in the future, but for the time being this resolution makes sense to us.

@Haroenv could we have a demo of how to work around this problem? 😃
I think it is useful for everyone because we all will have this problem in iOS anyway.

Has there been a change? Or is it still this way

With all due respect to the maintainers' decision, I disagree with this being closed with "wontfix". In our use case, the majority of users are using mobile and the majority of those iOS devices, resulting in a poor user experience for at least half of our users. In fact this is even broken on Algolia's own website.

This is probably related to the fact that iPhones don't let you programmatically assign focus (at least that was the case in the past), just like they don't allow you to autoplay videos, etc. We can set focus if this is done within a user event callback (which is the case here and it works) but we can't open the keyboard, this only happens when the user deliberately taps the input (we can't even simulate it). As far as I know there's no way around it.

iOS Safari does allow programmatic focus() including activating the on-screen keyboard, as long as the focus call is a result of a user interaction. Which appears to be the case when opening the detached panel by clicking on the fake search input (which is a button) with one catch.
However, the code calling focus() is wrapped in requestAnimationFrame, which - in my theory - makes the focus() call look like not having been triggered by a user interaction. Whether this is a bug or a feature in Safari is another question - I have not found any authoritative documentation on this matter, only dozens of StackOverflow threads. (The fact that the bug does not occur in iOS simulator suggests that this is rather a bug in iOS Safari.)
I've tried removing requestAnimationFrame to prove this theory, and it indeed fixed the issue on iOS. It is not obvious to me what purpose requestAnimationFrame serves. Removing it does not break any tests, and things seem to keep working (briefly tested on iOS Safari and various desktop browsers). The code including requestAnimationFrame was added in 1239b63e80dd2351771d74e91b275eda19fb997f by @francoischalifour, maybe he can explain?
For the impatient, I've published my fork on npm: https://www.npmjs.com/package/@salomvary/autocomplete-js

I believe the requestAnimationFrame was to ensure the panel exists and is ready to be shown, however that may not be required as you show in your fork. Are you interested in making a pull request to backport your change? It looks useful to me, this is indeed a recurring problem that we hadn't found a solution for.
Thanks a lot for your contribution already @salomvary

I just spoke with @francoischalifour and the initial reasoning was to slow down the setters a little so "other work on the page" can happen too. As fixing this bug is clearly more important, we should definitely remove the requestAnimationFrame.

Are you interested in making a pull request to backport your change? It looks useful to me, this is indeed a recurring problem that we hadn't found a solution for.

Here we go https://github.com/algolia/autocomplete/pull/1231

Thanks again @salomvary , the fix is now part of autocomplete v1.14.0.

authors: Haroenv amirhega dhayab eunjae-lee meotimdihia salomvary sarahdayan seafoox zwily

repo: algolia/autocomplete


text:
Formatting imported data

Hi, I'm a complete newbie to Algolia but loving what I see so far.  I have a simple faceted search working for 4000 products but I have an issue where the price is being displayed in alphabetical order, not numerical.  I understand this is because the price index is a string and not an integer.
I've used the instructions here: https://www.algolia.com/doc/guides/indexing/import-synchronize-data/php to import my data but am really struggling on how to tell the API to import my price field as an integer.
Any help would be much appreciated.  Thanks.

I guess you fixed this @spindriftwebs, maybe you can add a small comment on how you fixed it for future reference?

authors: spindriftwebs vvo


text:
fix(slider): allow handles to reach the real start and end of the slider

The famous "why can't I reach the start and end?" slider "bug"

Quick fix LGTM, we'll anyway re-work on the styling in the near future.

authors: redox vvo


text:
Script is not resilient to "db crash"

Aug 06 13:07:43 npm-search app/worker.1: [unknown_error: Database encountered an unknown error] {
Aug 06 13:07:43 npm-search app/worker.1:   status: 503,
Aug 06 13:07:43 npm-search app/worker.1:   name: 'unknown_error',
Aug 06 13:07:43 npm-search app/worker.1:   message: 'Database encountered an unknown error',
Aug 06 13:07:43 npm-search app/worker.1:   error: true,
Aug 06 13:07:43 npm-search app/worker.1:   data: '503 Service Unavailable\n' +
Aug 06 13:07:43 npm-search app/worker.1:     'No server is available to handle this request.\n' +
Aug 06 13:07:43 npm-search app/worker.1:     '\n' +
Aug 06 13:07:43 npm-search app/worker.1:     '\n'
Aug 06 13:07:43 npm-search app/worker.1: }
Aug 06 13:07:43 npm-search app/worker.1: error Command failed with exit code 1.

This is something I'm aware of, and don't really have a good solution for in mind. instead of crashing and relying on Heroku to be slow enough, we could back off for e.g. 1 minute & back off more exponentially? I didn't add any code since it seemed to be rare that we didn't wait long enough when crashing

We need to check the error handling with PouchDB, a back off would be good enough I believe as it seems to happen very rarely.

there's a "retry" option, but we should see if it isn't too aggressive https://pouchdb.com/api.html#options-4

Should not happen again

authors: Haroenv bodinsamuel

repo: algolia/npm-search


text:
feat: update vue cli to v5

Motivation
This removes all webpack 4 dependencies which remove several legacy packages as peer deps.

update vue/cli-service to 5.0.8 which is the last supported version before migrating to vite

this uses webpack 5 rather than 4, so we need to change the way that the svg-loader works by adding explicit exclusions for anything outside of the common/icons directory, and then manually configuring only those icons to use the svg loader.
webpack 5 also tries to serve from the root directory, so we change the publicPath based on whether we are running in the node server context or the yarn serve context. This allows the all.css references to stay the same in the index.html

bump search-insights to remove dependencies that used polyfills
add explicit eslint rules to prevent the build from failing - these should be removed over time and the errors corrected
remove the explicit copying of css to all public directories to avoid propagating these to production multiple times.

this means that if you want to run locally, you need to either run .copy-css.sh from the css directory prior to yarn serve from the application directory, or from the root just run yarn prepare-css

Test
note this is probably important for this PR in case I missed something

check out the branch and run:
rm -rf yarn.lock && find . -name 'node_modules' -type d -prune -exec rm -rf '{}' + && find . -name 'dist' -type d -prune -exec rm -rf '{}' + && find . -name 'all.css' -prune -exec rm -rf '{}' + && yarn cache clean && yarn && yarn build && yarn start

Navigate to localhost:80 and navigate through the apps, specifically the insights-ui, metaparams, and index-differ, but all of them would be good 😁

FYI @JonathanMontane maybe we broke the highlighting in insights ui in prod? (separate to this issue but discovered here).

repo: algolia/tools


text:
build: update to go 1.16

Summary
Update to use go 1.16, as well as update the dependent sub-module.
Test Plan
Use existing tests.

Codecov Report

Merging #943 (a7007e5) into develop (99ab66f) will increase coverage by 0.32%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #943      +/-   ##
===========================================
+ Coverage    59.21%   59.53%   +0.32%
===========================================
  Files           42       41       -1
  Lines         5720     5689      -31
===========================================
  Hits          3387     3387
+ Misses        1896     1865      -31
  Partials       437      437

Impacted Files
Coverage Δ

util/diff.go

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 99ab66f...a7007e5. Read the comment docs.

Closed in favor of #980

authors: codecov-commenter tsachiherman winder

repo: algorand/indexer


text:
timestamp alias for uint64

timestamp alias for uint64 for representing a unix epoch timestamp.
Useful when inputting/returning data that interacts with global LatestTimestamp

Great idea but since this list can go on forever , how about another approach to make ABI able to accept user (dev) defined aliases through ABI specification JSON as they see fit? This way instead of having N PRs , we will need one forever!
Example:
`
{...
desc:"This ABI interface contains custom dynamic and configurable aliases"
aliases: [timestamp, my_nice_alias],
aliasTypes:[uint64, byte[]]
`

Closing this PR and the issue is now addressed here: https://github.com/algorandfoundation/ARCs/pull/199

authors: SudoWeezy emg110 joe-p

repo: algorandfoundation/ARCs


text:
Add tests

Finish added tests

Thank you! Looks good.

authors: BoscoCHW aliaaabdulahi

repo: aliaaabdulahi/project-flask-flamingos


text:
Contact Details
No response
What do you want?
feature request
Version
master (Default)

感谢您提出的宝贵问题，我们有7x24小时服务的“HaaS百事通”客服系统，
您可以先尝试能否解决您的问题(https://haas.iot.aliyun.com/?ask=1&f=a2cre.b82925042)

如果“HaaS百事通”没有解决您的问题，请回复“人工支持”，我们会在工作日(10:00-12:00/14:00-18:00)10分钟内回复您。

已实现。

authors: jinliangli skylarCai

repo: alibaba/AliOS-Things


text:
这种节点样式是怎么配出来的，求高力大佬给份代码

这个功能解决了什么问题
你所期望的 API 是怎样的

@gaoli

有相关的代码的，自己翻翻吧。我看了几次了

@Aragornzero  在哪看的代码？

#76

@Aragornzero   大神啊   再请教下 CanvasPanel里里定义了一个 怎样在propsAPI.save()里获取到在输入的值？

@Aragornzero 大神啊 再请教下 CanvasPanel里里定义了一个 怎样在propsAPI.save()里获取到在输入的值？

不是很明白你的意思. 如果是定义了节点,没有数据的话也是不会显示对应的图案的. 输入数据有两种方式,一种是拖动、一种是直接data传入. 如果你是问propsAPI怎么用,那又是另外一回事了.

@Aragornzero   CanvasPanel里里定义了一个Input 输入框 ，又定义了一个保存的ToorButton，在点击保存的时候propsAPI.save()只有nodes和edges ，怎么获取到输入框的值呢？

@Aragornzero CanvasPanel里里定义了一个Input 输入框 ，又定义了一个保存的ToorButton，在点击保存的时候propsAPI.save()只有nodes和edges ，怎么获取到输入框的值呢？

你的描述很不清晰啊。我查看代码，也没有CanvasPanel这个组件。但是根据你的描述，有可能是DetailPanel，单击节点后，右边暂时相关的属性，所有有个input。但只有input不代表就修改了data里面的数据，估计你需要搭配propsAPI中的update来更新数据，然后你再执行save方法，数据才会改变。

@Aragornzero  不是点击节点  是点击空白处会显示CanvasPanel里的组件FlowDetail ，FlowDetail组件里定义了一个Input ，我想在点击"保存"的时候获取到Input里输入的值，应该怎么弄呢？

@Aragornzero 不是点击节点 是点击空白处会显示CanvasPanel里的组件FlowDetail ，FlowDetail组件里定义了一个Input ，我想在点击"保存"的时候获取到Input里输入的值，应该怎么弄呢？

其实是一样的道理，你写个函数，在canvasPanel中的input变化后执行，先用save()读取全部数据，然后把input中的值保存在数据里面，然后在用reac()把数据读回去，这样你在用save()时就会有input的数据了啦。只不过这个不是节点数据，它不会展示而已。

@Aragornzero  这样做save还是取不到值，是我写的有问题吗？

@Aragornzero 这样做save还是取不到值，是我写的有问题吗？

这样啊，我没有这样的需求，所以具体尝试过。或许read的时候，它过滤的一下，只读nodes和edges。你试试看吧，实在不行就当做一个节点id保存进去，不要添加shape等数据，不渲染出来也行。

@Aragornzero  好的  多谢了

这个省略号是怎么造成的

@Aragornzero 这样做save还是取不到值，是我写的有问题吗？

这样啊，我没有这样的需求，所以具体尝试过。或许read的时候，它过滤的一下，只读nodes和edges。你试试看吧，实在不行就当做一个节点id保存进去，不要添加shape等数据，不渲染出来也行。

有相关的代码的，自己翻翻吧。我看了几次了

给个联系方式吧

repo: alibaba/GGEditor


text:
[BugFix][Spark] Fix compile error under JDK8

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to GraphAr?
Put an x in the boxes that apply

[X] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[X] I have read the CONTRIBUTING doc
[X] I have signed the CLA
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

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

repo: alibaba/GraphAr


text:
[BUG] GAE-Java jvm stackoverflow when running giraph apps.

StackOverflow when load graph via Giraph input format.
related pull request (emergency fix)https://github.com/alibaba/GraphScope/pull/2607/files

2023-05-08 08:27:22
Full thread dump OpenJDK 64-Bit Server VM (11.0.18+10-post-Ubuntu-0ubuntu122.04 mixed mode, sharing):
Threads class SMR info:
_java_thread_list=0x00007fc52c13d3d0, length=10, elements={
0x0000564c5448f800, 0x0000564c54491800, 0x0000564c54497000, 0x0000564c54499000,
0x0000564c5449b000, 0x0000564c5449d000, 0x0000564c5449f000, 0x0000564c544e1000,
0x0000564c549b3000, 0x0000564c549b4800
}
"Reference Handler" #2 daemon prio=10 os_prio=0 cpu=0.13ms elapsed=42.75s tid=0x0000564c5448f800 nid=0x7019 waiting on condition  [0x00007fc562e69000]
java.lang.Thread.State: RUNNABLE
at java.lang.ref.Reference.waitForReferencePendingList(java.base@11.0.18/Native Method)
at java.lang.ref.Reference.processPendingReferences(java.base@11.0.18/Reference.java:241)
at java.lang.ref.Reference$ReferenceHandler.run(java.base@11.0.18/Reference.java:213)
"Finalizer" #3 daemon prio=8 os_prio=0 cpu=0.22ms elapsed=42.74s tid=0x0000564c54491800 nid=0x701a in Object.wait()  [0x00007fc562d69000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(java.base@11.0.18/Native Method)
- waiting on <0x00000001000024e8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(java.base@11.0.18/ReferenceQueue.java:155)
- waiting to re-lock in wait() <0x00000001000024e8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(java.base@11.0.18/ReferenceQueue.java:176)
at java.lang.ref.Finalizer$FinalizerThread.run(java.base@11.0.18/Finalizer.java:170)
"Signal Dispatcher" #4 daemon prio=9 os_prio=0 cpu=0.07ms elapsed=42.74s tid=0x0000564c54497000 nid=0x701b runnable  [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"Attach Listener" #5 daemon prio=5 os_prio=0 cpu=0.26ms elapsed=42.74s tid=0x0000564c54499000 nid=0x701c waiting on condition  [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"Service Thread" #6 daemon prio=9 os_prio=0 cpu=0.08ms elapsed=42.74s tid=0x0000564c5449b000 nid=0x701d runnable  [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"C2 CompilerThread0" #7 daemon prio=9 os_prio=0 cpu=594.00ms elapsed=42.74s tid=0x0000564c5449d000 nid=0x701e waiting on condition  [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
No compile task
"Sweeper thread" #9 daemon prio=9 os_prio=0 cpu=0.06ms elapsed=42.74s tid=0x0000564c5449f000 nid=0x701f runnable  [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"Common-Cleaner" #10 daemon prio=8 os_prio=0 cpu=0.17ms elapsed=42.73s tid=0x0000564c544e1000 nid=0x7021 in Object.wait()  [0x00007fc56237e000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(java.base@11.0.18/Native Method)
- waiting on <0x000000010004dec8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(java.base@11.0.18/ReferenceQueue.java:155)
- waiting to re-lock in wait() <0x000000010004dec8> (a java.lang.ref.ReferenceQueue$Lock)
at jdk.internal.ref.CleanerImpl.run(java.base@11.0.18/CleanerImpl.java:148)
at java.lang.Thread.run(java.base@11.0.18/Thread.java:829)
at jdk.internal.misc.InnocuousThread.run(java.base@11.0.18/InnocuousThread.java:161)
"pool-2-thread-1" #16 prio=5 os_prio=0 cpu=346.52ms elapsed=41.72s tid=0x0000564c549b3000 nid=0x7026 waiting on condition  [0x00007fc561b26000]
java.lang.Thread.State: WAITING (parking)
at jdk.internal.misc.Unsafe.park(java.base@11.0.18/Native Method)
- parking to wait for  <0x00000000fe7298f8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(java.base@11.0.18/LockSupport.java:194)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(java.base@11.0.18/AbstractQueuedSynchronizer.java:2081)
at java.util.concurrent.LinkedBlockingQueue.take(java.base@11.0.18/LinkedBlockingQueue.java:433)
at java.util.concurrent.ThreadPoolExecutor.getTask(java.base@11.0.18/ThreadPoolExecutor.java:1054)
at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@11.0.18/ThreadPoolExecutor.java:1114)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@11.0.18/ThreadPoolExecutor.java:628)
at java.lang.Thread.run(java.base@11.0.18/Thread.java:829)
"Thread-2" #17 prio=5 os_prio=0 cpu=1113.09ms elapsed=41.37s tid=0x0000564c549b4800 nid=0x6fef waiting on condition  [0x00007ffe9341f000]
java.lang.Thread.State: WAITING (parking)
at jdk.internal.misc.Unsafe.park(java.base@11.0.18/Native Method)
- parking to wait for  <0x00000000fec610e8> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(java.base@11.0.18/LockSupport.java:194)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.18/AbstractQueuedSynchronizer.java:885)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.18/AbstractQueuedSynchronizer.java:917)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.18/AbstractQueuedSynchronizer.java:1240)
at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.18/ReentrantLock.java:267)
at java.util.concurrent.ThreadPoolExecutor.addWorker(java.base@11.0.18/ThreadPoolExecutor.java:916)
at java.util.concurrent.ThreadPoolExecutor.execute(java.base@11.0.18/ThreadPoolExecutor.java:1354)
at java.lang.ProcessHandleImpl.completion(java.base@11.0.18/ProcessHandleImpl.java:135)
at java.lang.ProcessImpl.initStreams(java.base@11.0.18/ProcessImpl.java:389)
at java.lang.ProcessImpl.lambda$new$0(java.base@11.0.18/ProcessImpl.java:352)
at java.lang.ProcessImpl$$Lambda$130/0x000000084019cc40.run(java.base@11.0.18/Unknown Source)
at java.security.AccessController.doPrivileged(java.base@11.0.18/Native Method)
at java.lang.ProcessImpl.(java.base@11.0.18/ProcessImpl.java:351)
at java.lang.ProcessImpl.start(java.base@11.0.18/ProcessImpl.java:271)
at java.lang.ProcessBuilder.start(java.base@11.0.18/ProcessBuilder.java:1107)
at java.lang.ProcessBuilder.start(java.base@11.0.18/ProcessBuilder.java:1071)
at com.alibaba.graphscope.loader.LoaderUtils.getNumLinesOfFile(LoaderUtils.java:55)
at com.alibaba.graphscope.loader.impl.FileLoader.loadEdgesImpl(FileLoader.java:286)
at com.alibaba.graphscope.loader.impl.FileLoader.loadEdges(FileLoader.java:238)
"VM Thread" os_prio=0 cpu=2.53ms elapsed=42.75s tid=0x0000564c5448c800 nid=0x7018 runnable
"GC Thread#0" os_prio=0 cpu=0.76ms elapsed=42.76s tid=0x0000564c5430d000 nid=0x7013 runnable
"G1 Main Marker" os_prio=0 cpu=0.13ms elapsed=42.76s tid=0x0000564c54329800 nid=0x7014 runnable
"G1 Conc#0" os_prio=0 cpu=0.05ms elapsed=42.76s tid=0x0000564c5432b800 nid=0x7015 runnable
"G1 Refine#0" os_prio=0 cpu=0.11ms elapsed=42.76s tid=0x0000564c54456800 nid=0x7016 runnable
"G1 Young RemSet Sampling" os_prio=0 cpu=3.66ms elapsed=42.75s tid=0x0000564c54458800 nid=0x7017 runnable
"VM Periodic Task Thread" os_prio=0 cpu=12.27ms elapsed=42.73s tid=0x0000564c544df000 nid=0x7020 waiting on condition
JNI global refs: 27, weak refs: 0

repo: alibaba/GraphScope


text:
fix(analytical): Fix Louvain algorithm's move on const message

What do these changes do?

Louvain algorithm may core dump as pointer's "double free", I see there is a std::move() on const message, and it seems that will cause a copy instead of a move.
Related issue number

Fixes #3550

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (d8d1ac3) 45.37% compared to head (696899c) 24.33%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #3551       +/-   ##
===========================================
- Coverage   45.37%   24.33%   -21.05%
===========================================
  Files         176      176
  Lines       16167    16211       +44
===========================================
- Hits         7336     3945     -3391
- Misses       8831    12266     +3435

see 71 files with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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

authors: codecov-commenter songqing


text:
refactor(settings): rename idleReuqest to idleRequest

Signed-off-by: dark dark.lijin@gmail.com
Before submitting a pull request, please make sure the following is done...

[ ] Ensure the pull request title and commit message follow the Commit Specific in English.
[ ] Fork the repo and create your branch from main.
[ ] If you've added code that should be tested, add tests!
[ ] If you've changed APIs, update the documentation.
[ ] Ensure the test suite passes (npm test).
[ ] Make sure your code lints (npm run lint) - we've done our best to make sure these rules match our internal linting guidelines.

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

authors: CLAassistant darkmice

repo: alibaba/designable


text:
设置了retries="0"还会失败重试

我这样配置了之后，为什么还会有失败重试？

看源码好像只有cluster为failover这个参数才有用

@SuperstarSage
if you use failfast cluster, retries does't work.
if you use failover cluser, the minimum number of retries is "retries + 1 ".
refer from : com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker#doInvoke
        int len = getUrl().getMethodParameter(invocation.getMethodName(), Constants.RETRIES_KEY, Constants.DEFAULT_RETRIES) + 1;
        if (len <= 0) {
            len = 1;
        }

Hi,
Please consider using English, Dubbo is a global community, and all the issues may be viewed and discussed by people all over the world.
Please send mail to dev@dubbo.apache.org to discuss questions like this. We'd like github issues to track bugs, features or at least high suspicious bugs. We guarantee that the questions send to the mailing list can get a quicker reply.
How to send and subscrite to dev@dubbo.apache.org: #1393
Thanks

authors: SuperstarSage chickenlj sofay zonghaishang

repo: alibaba/dubbo


text:
Optimize and Comments

1.FastJsonProvider
2.FastJsonHttpMessageConverter
3.FastJsonHttpMessageConverter4
4.FastJsonJsonView
will add wiki

build error :
FastJsonProvider.java:[182,85] diamond operator is not supported in -source 1.5

build error :
FastJsonProvider.java:[182,85] diamond operator is not supported in -source 1.5
fixed this

@wenshao wiki 明天再更新 睡觉了 goodnight~

这个改动会不会导致之前的用户不兼容？

@wenshao 可能会的，需要用户也进行升级

@wenshao 或者 我将1.2.10的方法回退 然后标注废弃 这样会更好

一定要兼容，否则就会给人带来麻烦

??
Best regards.
Yours sincerely, Victor Zeng.?
在 2016年4月27日，上午12:33，高铁 <notifications@github.commailto:notifications@github.com> 写道：
一定要兼容，否则就会给人带来麻烦
―
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com/alibaba/fastjson/pull/583#issuecomment-214803582

有testcase跑不过

authors: VictorZeng wenshao

repo: alibaba/fastjson


text:
[FEATURE] 能不能输出属性不要按字母排序 按javabean代码属性顺序

能不能输出属性不要按字母排序按 javabean属性顺序
public class SystemUser {
	private Integer id;
	private String code;
	private String password;
}

输出{ "id": 1 , code: "10001", password:"123456"  }  效果这样

https://oss.sonatype.org/content/repositories/snapshots/com/alibaba/fastjson2/fastjson2/2.0.13-SNAPSHOT/
请用2.0.13-SNAPSHOT版本验证，2.0.13版本预计在9月12日前发布。需要配置JSONType.alphabetic = true，比如
@JSONType(alphabetic=false)
public class SystemUser {
	private Integer id;
	private String code;
	private String password;
}

这个取决于编译器的行为，顺序不确定的

https://os.sonatype.org/jsoncontent/repositories/snapshots/com/alib/fastjson2/fastaba/2.0.13-SNAPSHOT/ 用2.0.13-SNAPSHOT版本，验证2.0.13版本请在9月12日前发布发布。需要配置JSONType.alphabetic = true，比如
@JSONType(alphabetic=false)
public class SystemUser {
	private Integer id;
	private String code;
	private String password;
}

什么是这个编译器的行为，目的是

我是过滤中得到Bean,有可能是各种形式的bean, 我不可在所有bean上加@JSONType, 能不能加个SerializerFeature参数

https://github.com/alibaba/fastjson2/releases/tag/2.0.13
2.0.13版本已经发布，请用帮忙用新版本验证

authors: javahui wenshao


text:
查询筛选组件设置表单项为选择器时，选项设置表达式输入，下拉提示显示空白

Describe the bug (required) / 详细描述 bug（必填）
查询筛选组件设置表单项为选择器时，选项设置表达式输入，下拉提示显示空白
A clear and concise description of what the bug is. / 请提供清晰且精确的 bug 描述

To Reproduce (required) / 如何复现 bug？（必填，非常重要）
Steps to reproduce the behavior: / 详细复现步骤：

English version example：

Go to '...'
Click on '....'
Scroll down to '....'
See error

中文版示例：

打开 demo；
点击标题；
在右侧修改标题内容为「修改后的标题」；
渲染画布标题组件没有更新显示为「修改后的标题」；

Expected behavior (required) / 预期行为（必填，非常重要）
A clear and concise description of what did you expect to happen. / 请清晰和精确的描述你预期的行为

Screenshots (optional) / bug 截图（可选）
Sceenshots for further information. (If applicable.) / 一些有用的截图将会帮助我们更好的明确以及定位问题

Environments (please complete the following information) (required): / 请提供如下信息（必填）

AliLowCodeEngine version: [e.g. v1.0.1-beta.]

AliLowCodeEngineExt version: [e.g. v1.0.2]

Browser [e.g. chrome] / 99.0.4844.82（正式版本） （64 位）

materials / plugins / tools / 其他物料 / 插件 / 工具链版本

(this information can be collected via the manual plugin / 版本信息可通过低代码用户手册插件收集)

Additional context (optional) / 更多额外信息（可选）
Any other context of the problem here. / 可以追加更多的额外信息，帮助定位问题

用最新版 demo 试试

用最新版 demo 试试

没问题了，感谢！

authors: LeoYuan baieceo

repo: alibaba/lowcode-engine


text:
Delete clusterrolebinding system:controller:node-controller to disable node-controller.

Delete clusterrolebinding system:controller:node-controller to disable node-controller.

Ⅰ. Describe what this PR does
(1) delete clusterrolebinding system:controller:node-controller when convert to OpenYurt cluster.
(2) create clusterrolebinding system:controller:node-controller when revert to k8s cluster.
Ⅱ. Does this pull request fix one issue?

because when revert openyurt to kubernetes, a new serviceaccount and secret need to be created, so node-controller must be restarted before new serviceaccount and secret can take effect.
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
make test
make build
_output/bin/yurtctl convert --provider [minikube|ack|kubeadm]
Ⅴ. Special notes for reviews

@zyjhtangtang maybe we need to add more information that clusterrolebinding deletion is better than serviceaccount deletion for disabling node-controller. because when revert openyurt to kubernetes, a new serviceaccount and secret need to be created,  so node-controller must be restarted before new serviceaccount and secret can take effect.

@zyjhtangtang maybe we need to add more information that clusterrolebinding deletion is better than serviceaccount deletion for disabling node-controller. because when revert openyurt to kubernetes, a new serviceaccount and secret need to be created,  so node-controller must be restarted before new serviceaccount and secret can take effect.

LGTM

LGTM

authors: rambohe-ch zyjhtangtang

repo: alibaba/openyurt


text:
feature: add pouch daemon config file

Signed-off-by: Ace-Tang aceapril@126.com

1.Describe what this PR did
Add daemon configuration file for pouch, so there is two ways for set config, command line and config file.
Notice that, a flag can not be set in two places simultaneously.
2.Does this pull request fix one issue?

3.Describe how you did it
4.Describe how to verify it
5.Special notes for reviews

@allencloud , conflict is resolved.

@HusterWan , @allencloud  , PTAL

repo: alibaba/pouch


text:
1.7.12 became stable, probably should merge

1.7.12 (actually 1.8) became stable. Probably should merge.

+1

+1

+1 :)

+1

+1
1.7.11（或以上版本）

+1

+1

+10

+1 !

now we are working on this.
a lot of collisions at this stage, so a little more time is needed, but it won't be too long.

@cfsego Great that you're working on this!

Any updates about that issue?

@derjohn nginx-1.8 stable has been merged.
You can try the latest tengine git master.

authors: Am1GO Profforgr cfsego chobits deltay derjohn han4235 himpich imleon magro ym yourtion

repo: alibaba/tengine


text:
Add schema-editor

Add schema-editor files, and npm scripts: npm run docs:schema-editor.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.ziyi.hzy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant ascoders

repo: alibaba/uform


text:
点击事件无法触发

<template>
  <div>
     <text @click="click" style="font-size:50px">{{msg}}</text>
  </div>
</template>

<script>
export default {
    data:function() { return {
       msg:'click'
    }},
    methods:{
       click:function(){
             this.msg = "clicked"
    }
  }
}
</script>

在游览器中有效，在playgroundApp中点击后经常没有反应？

This PR/issue doesn't received response since Weex migrated to Apache two years ago and this repository is no longer active yet.
Feel free to ask question in new repository and thanks for your contribution.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.

authors: Hanks10100 YorkShen ghost

repo: alibaba/weex