-
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
Fix #13377 for compatibility with #13330 #13382
Conversation
The pull requests project-chip#13330 and project-chip#13377 were merged around the same time, and have caused a small build breakage. This fixes it.
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.
OK to fix build, but as a followup we should figure out whether this is in fact always a SecureSession session, right? @turon
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.
LGTM 👍 Was about to post the same.
Yes, I had the same question for @kghost regarding the new API. Specifically, what happens when |
I guess I would defend this as no better or worse than the original code, which was extracting the chip::Optional GetLocalSessionId.Value without checking whether it exists first. It seems sort of like the same underlying assumptions are at play in either case. edit: Not that this is great. I agree a pretty printer that does the right thing would be much better, and I don't claim this can't break. I'm only claiming that it's probably no more likely to break than the previous code. |
Yes, basically the entire stack now calls I'll prep a follow-up that uses a |
PR #13382: Size comparison from 585cdcb to 8f3933a Increases above 0.2%:
Increases (10 builds for efr32, linux, mbed, nrfconnect)
Decreases (2 builds for nrfconnect)
Full report (31 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
…ject-chip#13382) The pull requests project-chip#13330 and project-chip#13377 were merged around the same time, and have caused a small build breakage. This fixes it.
Problem
The pull requests #13330 and #13377 were merged around the same time,
and have caused a small build breakage.
Change overview
Amend #13377 to work with #13330.
Testing
Tested to build without error.