-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[Android] Support isUrgent variable in Event Path #22356
[Android] Support isUrgent variable in Event Path #22356
Conversation
PR #22356: Size comparison from e56afce to 7f94275 Increases (45 builds for bl602, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
Decreases (6 builds for cc13x2_26x2)
Full report (45 builds for bl602, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
@@ -289,6 +289,7 @@ CHIP_ERROR EventManagement::ConstructEvent(EventLoadOutContext * apContext, Even | |||
eventPathBuilder.Endpoint(apOptions->mPath.mEndpointId) | |||
.Cluster(apOptions->mPath.mClusterId) | |||
.Event(apOptions->mPath.mEventId) | |||
.IsUrgent(apOptions->mPath.mIsUrgentEvent) |
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.
Why this change? This does not make sense.
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.
isUrgent is used for requested path for subscribe, and should not be used in event Path builder when constructing event in event management.
@@ -242,6 +242,8 @@ CHIP_ERROR EventDataIB::Parser::ProcessEventPath(EventPathIB::Parser & aEventPat | |||
err = aEventPath.GetEvent(&(aConcreteEventPath.mEventId)); | |||
VerifyOrReturnError(err == CHIP_NO_ERROR, CHIP_ERROR_IM_MALFORMED_EVENT_PATH_IB); | |||
|
|||
err = aEventPath.GetIsUrgent(&(aConcreteEventPath.mIsUrgentEvent)); |
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.
Why do we want to do this? The spec is not very clear on this, but IsUrgent is an input, not an output; EventDataIB should never have it present...
Filed https://github.com/CHIP-Specifications/connectedhomeip-spec/issues/5596 to get this clarified.
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.
agree, it should be input
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.
isUrgent is used for requested path for subscribe, and should not be used in event Path builder when constructing event in event management.
@@ -1326,7 +1332,7 @@ CHIP_ERROR ParseEventPath(jobject eventPath, EndpointId & outEndpointId, Cluster | |||
outEndpointId = static_cast<EndpointId>(endpointId); | |||
outClusterId = static_cast<ClusterId>(clusterId); | |||
outEventId = static_cast<EventId>(eventId); | |||
|
|||
outIsUrgentId = isUrgentEvent; |
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.
there is no need to parse the urgent flag when reading event from report.
as I point out in this PR, you should just modify java event path, #20198 (comment), then modify subscribe request with optional urgent event path in WildcardFragment. when receiving report, there is no need to parse urgent flag in report
|
I will check comments and spec. |
Problem
What is being fixed?
issue #22526
Change overview
Add isUrgent in EventPath class.
Testing
How was this tested? (at least one bullet point required)