Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SDL-0188] Interior Vehicle Data Resumption #3480

Conversation

LitvinenkoIra
Copy link
Contributor

@LitvinenkoIra LitvinenkoIra commented Aug 20, 2020

Implements #2661

This PR is ready for review.

Summary

SDL-0188 Interior Vehicle Data Resumption feature implementation

Use API from smartdevicelink/rpc_spec#274

Testing Plan

ATF Tests from smartdevicelink/sdl_atf_test_scripts#2444

Dependencies:

!! Please note that this feature is based on the [SDL-0190] and this PR should be merged after #3475
Commits started from 6bd4011 contain [SDL-0188] implementation

CLA

ychernysheva and others added 30 commits August 14, 2020 12:47
Fix RAI default timeout

As RAI request does not depend on any HMI response
there is no need to track any timeout for it. RAI
request will be removed from/ RequestController
queue upon RAI response which will be sent anyway
Update UT
Update SDL logic to avoid sending of unsubscribeVD
to HMI during vehicle data resumption for case
when another application is also have pending
subscription for the same vehicle data.
Changed SDL logic to update subscription results for
each pending subscription request before notifying
resumption processor about current subscription is
processed.
This should be done beforehand because after raising
event to processor it can finish resumption process
and if it has failed then it can trigger sending of
the next subscription request. So at that point, each
subscription request should contain updated subscriptions
status, otherwise some redundant requests might be sent.
@jacobkeeler jacobkeeler changed the base branch from develop to feature/reference_sdl_0190_resumption_data_error_handling September 3, 2020 14:08
@SNiukalov
Copy link
Contributor

Please be informed, we have added one more additional commit 1cccc48,
according to comment #3480 (comment)
that fix avoids sending redundant OnHashChange notification to a mobile device.

@jacobkeeler jacobkeeler force-pushed the feature/reference_sdl_0190_resumption_data_error_handling branch from 2e48d88 to 1bda351 Compare September 4, 2020 13:47
@jacobkeeler jacobkeeler changed the base branch from feature/reference_sdl_0190_resumption_data_error_handling to develop September 4, 2020 13:48
@jacobkeeler jacobkeeler changed the base branch from develop to feature/reference_sdl_0190_resumption_data_error_handling September 4, 2020 13:48
@IGapchuk
Copy link
Contributor

IGapchuk commented Sep 4, 2020

@jacobkeeler Regarding comment #3480 (comment) :
We believe that is redundant to change the sequence of function calls.
The resumption reverting could spend enough long time and mobile device will await along all resumption reverting processes.
Also, the transport SDL-HMI and transport SDL-Mobile Device are different transports and
we can't be sure about exactly the RPCs sequence between SDL, Mobile, and HMI.
We believe to improve UX, SDL should first at all notify the mobile device and after that start resumption reverting.

@jacobkeeler jacobkeeler changed the base branch from feature/reference_sdl_0190_resumption_data_error_handling to develop September 4, 2020 16:51
@jacobkeeler
Copy link
Contributor

@AKalinich-Luxoft I should be able to approve after conflicts are fixed with develop

@AKalinich-Luxoft
Copy link
Contributor

@AKalinich-Luxoft I should be able to approve after conflicts are fixed with develop

@jacobkeeler resolved in b46d79e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.