-
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
Restyle Message counter implementation #5390
Conversation
Re-evaluate the storing of Admin ID in SecureSessionHandleconnectedhomeip/src/transport/SecureSessionHandle.h Lines 48 to 55 in 83a9ee9
This comment was generated by todo based on a
|
control message counter is not implemented yetconnectedhomeip/src/transport/SecureSessionMgr.cpp Lines 368 to 378 in 83a9ee9
This comment was generated by todo based on a
|
"initial Session Establishment bootstrap" is under specified, use message counter sync protocol for both groupconnectedhomeip/src/transport/SecureSessionMgr.cpp Lines 372 to 382 in 83a9ee9
This comment was generated by todo based on a
|
83a9ee9
to
d810327
Compare
"initial Session Establishment bootstrap" is under specified, use message counter sync protocol for both groupconnectedhomeip/src/transport/SecureSessionMgr.cpp Lines 372 to 382 in d810327
This comment was generated by todo based on a
|
A duplicate of #5389 with additional commits that automatically address
incorrect style, created by Restyled.
Since the original Pull Request was opened as a fork in a contributor's
repository, we are unable to create a Pull Request branching from it with only
the style fixes.
The following Restylers made fixes:
To incorporate these changes, you can either:
Merge this Pull Request instead of the original, or
Ask your contributor to locally incorporate these commits and push them to
the original Pull Request
Expand for example instructions
NOTE: As work continues on the original Pull Request, this process will
re-run and update (force-push) this Pull Request with updated style fixes as
necessary. If the style is fixed manually at any point (i.e. this process finds
no fixes to make), this Pull Request will be closed automatically.
Sorry if this was unexpected. To disable it, see our documentation.