-
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
Update all .zap files #28967
Labels
Comments
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Aug 31, 2023
This fixes non-determinism in .zap files, so they will stop changing every time they are opened/closed. Fixes project-chip#28967
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Aug 31, 2023
This fixes non-determinism in .zap files, so they will stop changing every time they are opened/closed. Fixes project-chip#28967
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Sep 1, 2023
This fixes non-determinism in .zap files, so they will stop changing every time they are opened/closed. Fixes project-chip#28967
mergify bot
pushed a commit
that referenced
this issue
Sep 1, 2023
This fixes non-determinism in .zap files, so they will stop changing every time they are opened/closed. Fixes #28967
abpoth
pushed a commit
to abpoth/connectedhomeip
that referenced
this issue
Sep 12, 2023
This fixes non-determinism in .zap files, so they will stop changing every time they are opened/closed. Fixes project-chip#28967
HunsupJung
pushed a commit
to HunsupJung/connectedhomeip
that referenced
this issue
Oct 23, 2023
This fixes non-determinism in .zap files, so they will stop changing every time they are opened/closed. Fixes project-chip#28967
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reproduction steps
.zap files will see removal of device type ids when opened and saved again. They will also see a deterministic id for endpoint types ids. This should happen only once. The subsequent saves to .zap files should not run into this issue.
This is related to https://csamembers.slack.com/archives/C01B01GH64E/p1693019555053839 and the fix has been placed in project-chip/zap#1117
Also update to ZAP build v2023.08.30-nightly or later for the fix
Bug prevalence
The first time they open a .zap file and save it again.
GitHub hash of the SDK that was being used
79292ad
Platform
other
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: