You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
To support OTA requestor functionality, we need OTA requestor server and
OTA provider client. OTA provider client was enabled in #13246 which
broke the ZAP regen.
Having same cluster's client and server in same app is not supported in
the zap. Removed OTA provider client from all-clusters-app
Removing the OTA requestor support from all-clusters-app/esp32
To support OTA requestor functionality, we need OTA requestor server and
OTA provider client. OTA provider client was enabled in project-chip#13246 which
broke the ZAP regen.
Having same cluster's client and server in same app is not supported in
the zap. Removed OTA provider client from all-clusters-app
Removing the OTA requestor support from all-clusters-app/esp32
I guess the sanest short-term thing is probably to remove OTA Provider Server from all-clusters-app for now. And push for the ZAP bug to be fixed, so we can re-enable it....
I think I misunderstood and reverted the PR. Closing it and will remove the OTA Provider Server from all-clusters-app.
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.
Problem
ZAP CI broken
Change overview
To support OTA requestor functionality, we need OTA requestor server and
OTA provider client. OTA provider client was enabled in #13246 which
broke the ZAP regen.
Having same cluster's client and server in same app is not supported in
the zap. Removed OTA provider client from all-clusters-app
Removing the OTA requestor support from all-clusters-app/esp32
Testing
CI should be green