-
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
Generate lock operation events after lock state has changed #27991
Merged
mergify
merged 10 commits into
project-chip:master
from
mmarc:26925-lock-operation-events-after-lock-state-change
Jul 22, 2023
Merged
Generate lock operation events after lock state has changed #27991
mergify
merged 10 commits into
project-chip:master
from
mmarc:26925-lock-operation-events-after-lock-state-change
Jul 22, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mmarc
force-pushed
the
26925-lock-operation-events-after-lock-state-change
branch
from
July 17, 2023 15:12
cc6375a
to
c524dab
Compare
…n-events-after-lock-state-change
jrhees-cae
reviewed
Jul 18, 2023
pullapprove
bot
requested review from
amitnj,
andy31415,
anush-apple,
arkq,
carol-apple,
cecille,
chrisdecenzo,
chshu,
chulspro,
cliffamzn,
CodeChronos928,
Damian-Nordic,
dhrishi,
electrocucaracha,
emargolis,
gjc13,
harsha-rajendran,
hawk248,
hicklin and
jelderton
July 19, 2023 19:10
mmarc
force-pushed
the
26925-lock-operation-events-after-lock-state-change
branch
from
July 20, 2023 07:52
ce8436f
to
88c0999
Compare
mmarc
force-pushed
the
26925-lock-operation-events-after-lock-state-change
branch
from
July 20, 2023 09:42
88c0999
to
53e551b
Compare
…n-events-after-lock-state-change
jrhees-cae
reviewed
Jul 20, 2023
bzbarsky-apple
approved these changes
Jul 20, 2023
pullapprove
bot
requested review from
aronrosenberg,
mlepage-google and
robszewczyk
July 21, 2023 00:45
mmarc
force-pushed
the
26925-lock-operation-events-after-lock-state-change
branch
from
July 21, 2023 06:24
9f91729
to
dad4b1c
Compare
… remote actions
…n-events-after-lock-state-change
bzbarsky-apple
approved these changes
Jul 21, 2023
jrhees-cae
approved these changes
Jul 22, 2023
cecille
reviewed
Jul 22, 2023
cecille
approved these changes
Jul 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #26925
fabricIdx
andnodeId
are now passed to the LockEndpoint so that they can be then later forwarded again back to thedoor-lock-server
when updating the lock state.So now with remote operations (same as with other operations before) the
LockOperationEvent
is generated together with the change of the lock state.Only exception is if an error occurs (credential/pin error) before the execution. That error will be returned directly to the
HandleRemoteLockOperation
and stored immediately.