Merge upstream release 1.2 #9
Closed
Conversation
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
…9687) * Align ICD nommenclature in the app/icd/ file implementation * Restyled by clang-format * rename TestIcdMonitoringTable.cpp --------- Co-authored-by: Restyled.io <[email protected]>
…p#29701) * Add SMOKECO.M.ManuallyControlledTest PICS * Add top-level PICS * Change top-level PICS --------- Co-authored-by: Hare <[email protected]>
…project-chip#29704) The .matter changes are expected, with this ZAP update.
…pec. (project-chip#29707) No codegen changes (codegen does some case-canonicalization already, and is not affected by this bit), so easy fix.
…, InterfaceTypeEnum (project-chip#29694) * First update for radio fault enum * Fix compile (I hope) * Fix compilation again * Fix BLE constant as well * Undo submodule update * Remove InterfaceTypeEnum from the list of weak enums * Replace all scoped constants with new names * Also convert all InterfaceTypeEnum calls * Fix compilation * Fix boufallolab build * Better namespace names for all other platforms (fix compile) --------- Co-authored-by: Andrei Litvin <[email protected]>
* Align OTA cluster XML with the specification. This fixes the enum names to match. The difference in the ProviderLocation name is being addressed in the spec in CHIP-Specifications/connectedhomeip-spec#7580 * Auto-update ZAP files. * Regenerate generated code. * Address review comment.
The on off cluster on EP2 exposes several attributes that require LT feature, but the feature was not marked.
CHIPMem used things from CodeUtils.h which used logging, but logging might need to allocate memory via Memory::Alloc to actually work. This breaks the cycle (both conceptual and real: we could try to Memory::Alloc to log the fact that Memory::Init had not been called!), by making CHIPMem not use any macros that involve logging, at the cost of not having nice error messages when CHIPMem invariants are violated.
* Add tracing dependencies to pycontroller * Restyle --------- Co-authored-by: Andrei Litvin <[email protected]>
* Initial implementaton for kotlin-matter-controller * Address review comments * Use lock.wait(remainingTime) to allow the thread to wait for the remaining time or until it's notified
* Name support is not enforced anymore * Restyled by clang-format * Added value initialisation and check on failure of get featuremap before applying a value for namesupport * Apply suggestions from code review Co-authored-by: mkardous-silabs <[email protected]> --------- Co-authored-by: Restyled.io <[email protected]> Co-authored-by: mkardous-silabs <[email protected]>
…dpoint cluster. (project-chip#29686) * Add support for parsing "handle command" entries in matter files * Make codegen show commands that are handled for each endpoints --------- Co-authored-by: Andrei Litvin <[email protected]>
* Update KeyStore for Check-in keys * fix comments * fix comments
…roject-chip#29557) This significantly reduces the size of the framework and speeds up compilation of MTRBaseClusters.
* Replace glib GError with GAutoPtr<GError> in AdapterIterator * Replace glib GError with GAutoPtr<GError> in ChipDeviceScanner * Replace glib GError with GAutoPtr<GError> in Bluez helper * Replace glib GError with GAutoPtr<GError> in ConnectivityMangaerImpl * Replace glib GVariant with GAutoPtr<GVariant> in ConnectivityManagerImpl * Replace glib GVariant with GAutoPtr<GVariant> in Bluez helper * Replace glib and char with GAutoPtr<char> in Bluez helper * Replace glib and GVariantDict with GAutoPtr<GVariantDict> in Bluez helper - review * Fix badly used MakeUniquePointerReceiver * Review changes * Replace g_variant_dict_lookup_value to g_variant_lookup_value in src/platform/Linux/bluez/Helper.cpp * Add template <> struct GAutoPtrDeleter<const char *> * Convert keyMgmts to GAutoPtr in src/platform/Linux/ConnectivityManagerImpl.cpp * Revert in ConnectionDataBundle GVariant convert to GAutoPtr * Review update - remove GVariantDict * Add errorhandling for keyMgmtsHendle
* changes for wifi sdk 3_1_0 * updating the matter support to point to main * added missed commas * Restyled by clang-format * Restyled by gn --------- Co-authored-by: Restyled.io <[email protected]>
* IDT init * Restyled by whitespace * Restyled by prettier-markdown * Restyled by shellharden * Restyled by shfmt * Restyled by isort * Remove f-strings with no placeholders * Remove unknown Pygments lexer * Spelling * License headers * Restyled by prettier-markdown * First response to PR comments * Restyled by prettier-markdown * Respond Dockerfile and README comments * ble nit, venv script * Make TXT logging better * Respond comments * Clarify single host installation * Respond comments * Respond nits * Cleanup BashRunner * Cleanup BashRunner usage * Respond comments, renames, opts * Nits * Restyled by prettier-markdown * Restyled by shellharden * Restyled by shfmt * Restyled by isort * Spelling * Dynamic loading, comments * README nit * Make README generic, add async, any interface * Restyled by prettier-markdown * Restyled by shellharden * Restyled by shfmt * Restyled by isort * Nits, workaround potential issue with shell input * Restyled by isort * Docs CI --------- Co-authored-by: Restyled.io <[email protected]>
… methods (project-chip#29695) * [Darwin] MTRClusters commands have incorrect nullability for no-param methods * Also added _Nullable to interval and source file
Specific changes: * Make MTRDevice get its MTRBaseDevice in a way that is XPC-friendly. * Implement readAttributePaths (which is what ends up getting called by MTRDevice's readAttributeWithEndpointID) over XPC, as long as there is just a single attribute path. * Implement _invokeCommandWithEndpointID (which is what ends up getting called by MTRDevice's _invokeKnownCommandWithEndpointID) over XPC, as long as serverSideProcessingTimeout is nil. * Writes already called an MTRBaseDevice function that was implemented over XPC. * Tests for the new setup; these were checked to fail without the other changes. This also makes MTRClusters work over XPC.
* Updating wiseconnect to 2.8.2 * Restyled by clang-format --------- Co-authored-by: Restyled.io <[email protected]>
* [Telink] Set default value of COMMON_LIBC_MALLOC_ARENA_SIZE * [Telink] InitBasicOTARequestor after kDnssdInitialized * [Telink] Move OTAUtil into lib * [Telink] restyled
* add different flash sizes * add different flash sizes in exampe's CMake * add offset argument to mfg_tool * generate factory data for different flash sizes * generate factory data for different flash sizes * generate factory data for different flash sizes * generate factory data for different flash sizes * [Telink] Update CI * [Telink] change path * Restyled by prettier-markdown * [Telink] set correct app name --------- Co-authored-by: Dmytro Kashkarov <[email protected]> Co-authored-by: Restyled.io <[email protected]>
…DKs (project-chip#29646) * Adds chages to docker image and build scripts * Adds fix for alignment * Adds bugfix for change directory * Removes changes from other PR * Adds book keeping version checks * Reverts changes to be added after docker update * Adds updated SDK as per release * Updates wiseconnect-wifi-bt-sdk to 2.8.1 * Adds updated docker images * Adds update of WiSeConnect 2 SDK 2.8.2 * Adds requirements file for pip freeze --------- Co-authored-by: Rohan Sahay <[email protected]>
UnauthenticatedSessionTable essentially assumed that non-heap pools were used and was: 1) Never releasing its entries back to the pool. 2) Assuming that the pool would fill up and then its "reuse already allocated entry with zero refcount" code would kick in. Since heap pools never fill up, this meant that every single UnauthenticatedSession allocated was leaked. And we had a helpful "release them all on destruction" to cover up the leak at shutdown and prevent leak tools from finding it. This fix: * Preserves existing behavior for non-heap pools. * Switches to releasing UnauthenticatedSessions back to the pool in the heap case.
* TC-DGGEN-3.1: Add * Restyled by whitespace * Restyled by prettier-yaml --------- Co-authored-by: Restyled.io <[email protected]>
…hip#30036) * Start preparing to store derived clusters * reformat, make sure parsing works * More leniency to allow ModeBase parsing * More leniency and documentation, be ready to attach base clusters * Refactor to add some separate derivation logic * Restyle * More work on actually handling inheritance * Restyle * Implement actual base class derivation * Add unit test for derived, make diffs a LOT better * Restyle * Switch to unified diff for a nicer diff view * Return after the first assert * Make type checker happy at places * Make mypy happy even on an edge case * Fix linter errors * Restyle * more typing for attrs * Some name changes for base clusters: use abstract to make it clear that other clusters could be base too * Also change variable name --------- Co-authored-by: Andrei Litvin <[email protected]>
…ctions are modifying the group table (project-chip#30055)
* Reapply "Cluster conformance checker script (project-chip#29895)" This reverts commit 8140975. * More resiliance to mismatches in spec * Restyled by isort --------- Co-authored-by: Restyled.io <[email protected]>
* Add support for CertDecodeFlags to DecodeChipCert This moves support for generating the TBSHash during decoding from ChipCertificateSet::LoadCert to DecodeChipCert. LoadCert can now delegate to DecodeChipCert and only contains a few extra checks to retain existing behavior. * Add ASN1Writer.IsNullWriter() and use it internally * Avoid conversion work in DecodeConvertECDSASignature if using a null writer The original LoadCert avoided this work by calling DecodeECDSASignature directly, so this brings the refactored version back to baseline. * Add test for DecodeChipCert with different options
* update cluster revision * generated files * Restyled by prettier-yaml --------- Co-authored-by: Restyled.io <[email protected]>
…#30053) * update xml to add UAT attributes * Generated files * fix type and id * fix zap
…#30064) * Add manage restriction to ResetCounts to EthDiag * Zap regen
…ip#30061) * More updates to match sizes of thins * Zap regen
* Change media input xml to spec * Zap regen * minor change to kick CI * minor change to kick CI (featuremap already supported)
* Set the max length of the group name in command arguments * ZAP regen * minor change to kick CI * NOOP change to kick ci
…0065) * More lenient parsing: naming and types * Even better logic * Lenient parsing updates for more type logic * Another constant * Update the test * Restyle * Merge with master with better diffing
* Update dockerfile to version 21 (to get java) and use env variables for paths to make them resilient to change * Version 22 is actually the latest * OpenOCD does not seem to exist in the vscode image currently
…chip#30057) * chip::to_underlying is missing * Apply suggested fix to remove unnecessary cast. --------- Co-authored-by: Boris Zbarsky <[email protected]>
…roject-chip#30042) * Add a _span string literal operator to create constexpr CharSpans * Adopt _span for literals * Tweaks from review
This commit changes the SSID of the Wifi AP to PREFIX-<SERIALNUMBER> in accordance with Eltako wifi ap. This change is likely not compatible with Matter. However we do not support commissioning using Wifi anyway. Yet we need wifi to be available to configure the device by other means. In the future we need to find a way to either enable the ap without using Matter functions or provide proper commissioning over wifi. The latter is likely the better way.
esp_insights pulls in esp_diagnostics which has a bug which adds the --wrap=esp_log_write linker flag to the final link phase. This results in a linker error because the linker cannot find the __wrap_esp_log_write symbol.
When trying to bridge composed devices (devices which functionality is spread hierarchically over multiple endpoints) the aggregator needs to know all endpoints including all children of all aggregated devices. Normally we should use the `SetFlatCompositionForEndpoint` for this purpose, yet this doesn't work as the endpoint needs to be deactivated before setting the flat composition (recursive look up of children endpoints). Therefore we tell the system that all endpoints are flat composition. This will become a problem when we have composed devices of multiple depths levels. In that case we need to set thos devices to tree composition or reset tree composition to the default and find a solution how to set flat composition for the aggregator device type
When trying to bridge composed devices (devices which functionality is spread hierarchically over multiple endpoints) the aggregator needs to know all endpoints including all children of all aggregated devices. Normally we should use the `SetFlatCompositionForEndpoint` for this purpose, yet this doesn't work as the endpoint needs to be deactivated before setting the flat composition (recursive look up of children endpoints). Therefore we tell the system that all endpoints are flat composition. This will become a problem when we have composed devices of multiple depths levels. In that case we need to set thos devices to tree composition or reset tree composition to the default and find a solution how to set flat composition for the aggregator device type
Fix loading reboot count if data ist stored in a partition other than the default partition.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Merge current upstream release 1.2 branch.