-
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 for the non-determinism issue on Command handler and Outgoing Commands #13871
Fix for the non-determinism issue on Command handler and Outgoing Commands #13871
Conversation
PR #13871: Size comparison from 9f1c7e5 to 7d1ac66 Increases (1 build for linux)
Full report (16 builds for cyw30739, efr32, k32w, linux, p6, qpg, telink)
|
Got rid of the incorrect third_party changes.
PR #13871: Size comparison from 9fc0d2e to 50d15d5 Full report (33 builds for cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
examples/light-switch-app/light-switch-common/light-switch-app.matter
Outdated
Show resolved
Hide resolved
PR #13871: Size comparison from 9fc0d2e to 19f684d Decreases (1 build for linux)
Full report (16 builds for cyw30739, efr32, k32w, linux, p6, qpg, telink)
|
Note that at this point #14581 will remove some (but not all!) of the bits being changed in this PR.... |
Seems like the CHIPCluster and CHIPClientCallback templates are going away. Those are still non deterministic. Should I continue looking into fixing that? |
…oing commands are generated with determinism. Using the upto date helpers in the *.zapt templates Currently pointing to a zap repo which has new helpers as well. These changes have not been merged into the github zap repo gihub#342
…de only. - All commands originating on the server sides are response commands which do not need to be generated here Github#342
…nts_with_structs_expanded - Applying changes to chip_cluster_command_arguments_with_structs_expanded such that it can be used within all_outgoing_commands_for_cluster block helper instead of chip_cluster_command_arguments - Github#342
…t we generated before Github#342
…-mfg specific clusters and commands Github#342
…se there is code which depends on this generated code Github#342
…_commands in CHIPClusters-src.zapt just like we do in CHIPClusters.zapt to maintain consistency Also reverting the changes in helper.js since those are no longer required Github#342
Github#342
…upstream master Github#342
Github#342
…ch that request struct should be defined for all incoming commands from client to server and outgoing commands from client to server Github#342
…uch that response struct should be defined for all incoming commands from server to client and outgoing commands from server to client Github#342
Github#342
PR #13871: Size comparison from 8bb93af to a479437 Full report (43 builds for cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
IasZoneType zoneType = 0; | ||
INT16U manufacturerCode = 1; | ||
} | ||
|
||
request struct ZoneStatusChangeNotificationRequest { | ||
response struct ZoneStatusChangeNotification { |
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.
We seem to have removed ZoneEndrollResponse, however that response is used in the command ZoneEnrollREquest.
Also the name of the command argument is 'ZoneEnrollRequestRequest' and above the struct is defined with the wrong name.
Currently pointing to a zap repo which has new helpers as well. These changes have not been merged into the github zap repo
gihub#342
Problem
What is being fixed?
Change overview
Changes to ZAP generation templates: CHIPClusters.*zapt, im-cluster-command-handler.zapt to generate code accurately.
This PR depends on the following ZAP PR:
project-chip/zap#388
Testing
How was this tested? (at least one bullet point required)
Regened multiple times to check that the CHIPClusters and im-cluster-command-handler generated files did not change across regens.