{"action":"created","issue":{"url":"https://api.github.com/repos/alexa/avs-device-sdk/issues/778","repository_url":"https://api.github.com/repos/alexa/avs-device-sdk","labels_url":"https://api.github.com/repos/alexa/avs-device-sdk/issues/778/labels{/name}","comments_url":"https://api.github.com/repos/alexa/avs-device-sdk/issues/778/comments","events_url":"https://api.github.com/repos/alexa/avs-device-sdk/issues/778/events","html_url":"https://github.com/alexa/avs-device-sdk/issues/778","id":331376384,"node_id":"MDU6SXNzdWUzMzEzNzYzODQ=","number":778,"title":"AVS SDK 1.6:: Context Manager Timeout - Long range test","user":{"login":"adpandit","id":35273504,"node_id":"MDQ6VXNlcjM1MjczNTA0","avatar_url":"https://avatars2.githubusercontent.com/u/35273504?v=4","gravatar_id":"","url":"https://api.github.com/users/adpandit","html_url":"https://github.com/adpandit","followers_url":"https://api.github.com/users/adpandit/followers","following_url":"https://api.github.com/users/adpandit/following{/other_user}","gists_url":"https://api.github.com/users/adpandit/gists{/gist_id}","starred_url":"https://api.github.com/users/adpandit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adpandit/subscriptions","organizations_url":"https://api.github.com/users/adpandit/orgs","repos_url":"https://api.github.com/users/adpandit/repos","events_url":"https://api.github.com/users/adpandit/events{/privacy}","received_events_url":"https://api.github.com/users/adpandit/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2018-06-11T22:44:41Z","updated_at":"2018-10-13T04:19:16Z","closed_at":null,"author_association":"NONE","body":"Hi, \r\n\r\nWe are seeing contextRequestErrorOccurred,error=STATE_PROVIDER_TIMEDOUT. If context fetch done not happen correctly, none of the Capability Agents seem to receive a callback which would *not* allow them to do their routine. E.g. Send Recognize Event, Play Speech, Audio etc. The only way out is to restart the application. \r\n\r\nWe had a long range music test going and music stopped after 4 hours. We attempted barge in during a music playback multiple times. A snippet of the log is shown below. \r\n\r\n>> last recognize. \r\n2018-06-06 23:53:41.530 [  a] 0 EventBuilder:buildJsonEventString:messageId=6318c25c-5d37-47ff-ab0f-7fec23f414d8,namespace=SpeechRecognizer,name=Recognize\r\n\r\n>> could not send a recognize event as it failed during construction. \r\n2018-06-06 23:53:46.530 [  f] E SpeechSynthesizer:onFocusChangeFailed:reason=stateChangeTimeout,messageId=5d2f11a2-9d74-4bca-91da-f27d8507f834\r\n2018-06-06 23:53:46.531 [  f] 0 EventBuilder:buildJsonEventString:messageId=95ca4a69-8273-4867-be26-83388bcfbf52,namespace=System,name=ExceptionEncountered\r\n\r\n>> once this has happened (probably because of alexa disconnect). \r\n2018-06-06 23:55:49.685 [105] 0 PostConnectSynchronize:onServerSideDisconnect()\r\n2018-06-06 23:55:49.686 [105] 0 PostConnectSynchronize:PostConnectSynchronizer::doShutdown().\r\n2018-06-06 23:55:49.687 [105] 0 MessageRouter:connectionStatusChanged:reason=SERVER_SIDE_DISCONNECT,newStatus=PENDING\r\n2018-06-06 23:55:49.692 [105] 9 HTTP2Transport:setupDownchannelStream:url=https\\://avs-alexa-na.amazon.com/v20160207/directives\r\n\r\n>>no recovery possible after context manager gets in the time out loop. \r\n2018-06-06 23:55:51.698 [  7] E ContextManager:updateStatesLoopFailed:reason=stateProviderTimedOut\r\n2018-06-06 23:55:51.698 [  7] E PostConnectSynchronize:contextRetrievalFailed:reason=contextRequestErrorOccurred,error=STATE_PROVIDER_TIMEDOUT\r\n"},"comment":{"url":"https://api.github.com/repos/alexa/avs-device-sdk/issues/comments/429509728","html_url":"https://github.com/alexa/avs-device-sdk/issues/778#issuecomment-429509728","issue_url":"https://api.github.com/repos/alexa/avs-device-sdk/issues/778","id":429509728,"node_id":"MDEyOklzc3VlQ29tbWVudDQyOTUwOTcyOA==","user":{"login":"zeusshuang","id":30188611,"node_id":"MDQ6VXNlcjMwMTg4NjEx","avatar_url":"https://avatars0.githubusercontent.com/u/30188611?v=4","gravatar_id":"","url":"https://api.github.com/users/zeusshuang","html_url":"https://github.com/zeusshuang","followers_url":"https://api.github.com/users/zeusshuang/followers","following_url":"https://api.github.com/users/zeusshuang/following{/other_user}","gists_url":"https://api.github.com/users/zeusshuang/gists{/gist_id}","starred_url":"https://api.github.com/users/zeusshuang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zeusshuang/subscriptions","organizations_url":"https://api.github.com/users/zeusshuang/orgs","repos_url":"https://api.github.com/users/zeusshuang/repos","events_url":"https://api.github.com/users/zeusshuang/events{/privacy}","received_events_url":"https://api.github.com/users/zeusshuang/received_events","type":"User","site_admin":false},"created_at":"2018-10-13T04:19:16Z","updated_at":"2018-10-13T04:19:16Z","author_association":"NONE","body":"Hi @kclchan ,\r\n\r\nSorry for the confused.\r\n\r\n I double check with the tester, after line#10090, and it continues to run hours, but it still cannot be triggered by voice and no response, but a somehow it can response by trigger command (cmd : t), but voice command failed. MIC should be okay due to it can Q&A at that moment.\r\n\r\n"}}
{"actor":{"display_login":"zeusshuang"}}