-
Notifications
You must be signed in to change notification settings - Fork 99
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
Fix:service detail res #144
Conversation
self.stop_state_machine( | ||
f"[V2G2-425] {service_detail_req.service_id} is not offered", | ||
message, | ||
ResponseCode.FAILED_SERVICE_ID_INVALID, | ||
) | ||
return |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is no reason to stop the communication. we just need to communicate that that service ID is invalid and continue waiting for the next ServiceDetailReq or the next state
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
5f92ce4
to
6137fc9
Compare
4bd8dd6
to
46da79f
Compare
571fa9a
to
2d25484
Compare
746b7da
to
df58534
Compare
df58534
to
2a5093b
Compare
fix AB#2821
checks if the requested services ids in ServiceDetailReq are ids that were offered by the SECC in ServiceDiscoveryRes. if not, FAILED_SERVICE_ID_INVALID is returned.