update local master

.devcontainer/devcontainer.json

@@ -16,7 +16,7 @@
     "build": {
         "dockerfile": "Dockerfile",
         "args": {
-            "BUILD_VERSION": "0.5.15"
+            "BUILD_VERSION": "0.5.18"
         }
     },
     "remoteUser": "vscode",

.github/.wordlist.txt

@@ -207,6 +207,7 @@ cpuapp
 cpython
 crypto
 cryptographic
+CSA
 csu
 csv
 ctl

.github/workflows/android.yaml

@@ -34,7 +34,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: connectedhomeip/chip-build-android:0.5.15
+            image: connectedhomeip/chip-build-android:0.5.18
             volumes:
                 - "/tmp/log_output:/tmp/test_logs"
 

.github/workflows/bloat_check.yaml

@@ -30,7 +30,7 @@ jobs:
         runs-on: ubuntu-latest
 
         container:
-            image: connectedhomeip/chip-build:0.5.15
+            image: connectedhomeip/chip-build:0.5.18
 
         steps:
             - name: Checkout

.github/workflows/build.yaml

@@ -32,7 +32,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: connectedhomeip/chip-build:0.5.15
+            image: connectedhomeip/chip-build:0.5.18
             volumes:
                 - "/tmp/log_output:/tmp/test_logs"
             options:
@@ -231,6 +231,11 @@ jobs:
                       scripts/build/gn_build.sh
                       scripts/tests/gn_tests.sh
                   done
+            - name: Run Python library specific unit tests
+              timeout-minutes: 5
+              run: |
+                  scripts/run_in_build_env.sh 'pip3 install ./out/controller/python/chip-0.0-cp37-abi3-linux_x86_64.whl'
+                  scripts/run_in_build_env.sh '(cd src/controller/python/test/unit_tests/ && python3 -m unittest -v)'
             # TODO Log Upload https://github.com/project-chip/connectedhomeip/issues/2227
             # TODO https://github.com/project-chip/connectedhomeip/issues/1512
             # - name: Run Code Coverage

.github/workflows/cirque.yaml

@@ -29,7 +29,7 @@ jobs:
         timeout-minutes: 60
 
         env:
-            DOCKER_RUN_VERSION: 0.5.15
+            DOCKER_RUN_VERSION: 0.5.18
             GITHUB_CACHE_PATH: /tmp/cirque-cache/
 
         runs-on: ubuntu-latest
@@ -38,7 +38,7 @@ jobs:
 # need to run with privilege, which isn't supported by job.XXX.contaner
 #  https://github.com/actions/container-action/issues/2
 #         container:
-#             image: connectedhomeip/chip-build-cirque:0.5.15
+#             image: connectedhomeip/chip-build-cirque:0.5.18
 #             volumes:
 #                 - "/tmp:/tmp"
 #                 - "/dev/pts:/dev/pts"

.github/workflows/examples-infineon.yaml

@@ -37,7 +37,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: connectedhomeip/chip-build-infineon:0.5.15
+            image: connectedhomeip/chip-build-infineon:0.5.18
 
         steps:
             - name: Checkout

.github/workflows/examples-linux-standalone.yaml

@@ -37,7 +37,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: connectedhomeip/chip-build:0.5.15
+            image: connectedhomeip/chip-build:0.5.18
             volumes:
                 - "/tmp/bloat_reports:/tmp/bloat_reports"
                 - "/tmp/output_binaries:/tmp/output_binaries"

.github/workflows/examples-mbed.yaml

@@ -40,7 +40,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: connectedhomeip/chip-build-mbed-os:0.5.15
+            image: connectedhomeip/chip-build-mbed-os:0.5.18
             volumes:
                 - "/tmp/bloat_reports:/tmp/bloat_reports"
                 - "/tmp/output_binaries:/tmp/output_binaries"

.github/workflows/examples-nrfconnect.yaml

@@ -37,7 +37,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: connectedhomeip/chip-build-nrf-platform:0.5.15
+            image: connectedhomeip/chip-build-nrf-platform:0.5.18
             volumes:
                 - "/tmp/bloat_reports:/tmp/bloat_reports"
                 - "/tmp/output_binaries:/tmp/output_binaries"

.github/workflows/examples-qpg.yaml

@@ -37,7 +37,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: connectedhomeip/chip-build:0.5.15
+            image: connectedhomeip/chip-build:0.5.18
             volumes:
                 - "/tmp/bloat_reports:/tmp/bloat_reports"
                 - "/tmp/output_binaries:/tmp/output_binaries"

.github/workflows/examples-telink.yaml

@@ -35,7 +35,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: connectedhomeip/chip-build-telink:0.5.15
+            image: connectedhomeip/chip-build-telink:0.5.18
             volumes:
                 - "/tmp/bloat_reports:/tmp/bloat_reports"
 

.github/workflows/examples-tizen.yaml

@@ -28,7 +28,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: connectedhomeip/chip-build-tizen:0.5.15
+            image: connectedhomeip/chip-build-tizen:0.5.18
             options: --user root
             volumes:
                 - "/tmp/bloat_reports:/tmp/bloat_reports"

.github/workflows/tests.yaml

@@ -40,7 +40,7 @@ jobs:
         runs-on: ubuntu-latest
 
         container:
-            image: connectedhomeip/chip-build:0.5.15
+            image: connectedhomeip/chip-build:0.5.18
             options:
                 --privileged --sysctl "net.ipv6.conf.all.disable_ipv6=0
                 net.ipv4.conf.all.forwarding=1 net.ipv6.conf.all.forwarding=1"

.github/workflows/unit_integration_test.yaml

@@ -37,7 +37,7 @@ jobs:
         runs-on: ubuntu-latest
 
         container:
-            image: connectedhomeip/chip-build:0.5.15
+            image: connectedhomeip/chip-build:0.5.18
             volumes:
                 - "/tmp/log_output:/tmp/test_logs"
                 - "/tmp/happy_test_logs:/tmp/happy_test_logs"

.pullapprove.yml

@@ -91,6 +91,14 @@ groups:
             teams: [reviewers-comcast]
         reviews:
             request: 10
+#     shared-reviewers-espressif:
+#         type: optional
+#         conditions:
+#             - files.include('*')
+#         reviewers:
+#             teams: [reviewers-espressif]
+#         reviews:
+#             request: 10
     shared-reviewers-google:
         type: optional
         conditions:

CONTRIBUTING.md

@@ -2,41 +2,41 @@
 
 Want to contribute? Great! First, read this page (including the small print at
 the end). By submitting a pull request, you represent that you have the right to
-license your contribution to the Connectivity Standards Alliance and the community, and agree by
-submitting the patch that your contributions are licensed under the
-[Apache 2.0 license](./LICENSE). Before submitting the pull request, please make
-sure you have tested your changes and that they follow the project guidelines
-for contributing code.
+license your contribution to the Connectivity Standards Alliance and the
+community, and agree by submitting the patch that your contributions are
+licensed under the [Apache 2.0 license](./LICENSE). Before submitting the pull
+request, please make sure you have tested your changes and that they follow the
+project guidelines for contributing code.
 
 # Contributing as an Open Source Contributor
 
 As an open source contributor you can report bugs and request features in the
 [Issue Tracker](https://github.com/project-chip/connectedhomeip/issues), as well
-as contribute bug fixes and features that do not impact Matter
-specification as a pull request. For example: ports of Matter to add APIs
-to alternative programming languages (e.g. Java, JS), hardware ports, or an
-optimized implementation of existing functionality. For features that impact the
-specification, please join Matter work group within the Connectivity Standards Alliance.
-The requirements to become an open source contributor of the
-[Project CHIP Repository](https://github.com/project-chip/connectedhomeip) are:
+as contribute bug fixes and features that do not impact Matter specification as
+a pull request. For example: ports of Matter to add APIs to alternative
+programming languages (e.g. Java, JS), hardware ports, or an optimized
+implementation of existing functionality. For features that impact the
+specification, please join Matter work group within the Connectivity Standards
+Alliance. The requirements to become an open source contributor of the
+[Matter Repository](https://github.com/project-chip/connectedhomeip) are:
 
 -   Agree to the [Code of Conduct](./CODE_OF_CONDUCT.md)
 -   Agree to the [License](./LICENSE)
 -   Have signed the
-    [Zigbee Project CHIP Working Group CLA](https://gist.github.com/clapre/65aa9fc63981da765039e0bb7e8701be)
+    [Matter Working Group CLA](https://gist.github.com/clapre/65aa9fc63981da765039e0bb7e8701be)
 
-# Contributing as a Connectivity Standards Alliance Project CHIP Working Group Member
+# Contributing as a Connectivity Standards Alliance Matter Working Group Member
 
-As a participant of the Connectivity Standards Alliance Project CHIP Working Group, you can
-attend Working Group meetings, propose changes to the Matter
+As a participant of the Connectivity Standards Alliance Matter Working Group,
+you can attend Working Group meetings, propose changes to the Matter
 specification, and contribute code for approved updates to the specification.
 The requirements to become a member of the
-[Project CHIP Repository](https://github.com/project-chip/connectedhomeip) are:
+[Matter Repository](https://github.com/project-chip/connectedhomeip) are:
 
 -   Must be a [Participant member](http://www.zigbeealliance.org/join) or higher
     of the Connectivity Standards Alliance
--   Must be a Project CHIP Working Group member
--   Have signed the Alliance Project CHIP Working Group CLA
+-   Must be a Matter Working Group member
+-   Have signed the Alliance Matter Working Group CLA
 -   Have approval from your company's official approver
 
 # Bugs
@@ -67,15 +67,14 @@ new feature:
 
 # Contributing Code
 
-Project CHIP follows the "Fork-and-Pull" model for accepting contributions.
+Matter follows the "Fork-and-Pull" model for accepting contributions.
 
 ### Initial Setup
 
 Setup your GitHub fork and continuous-integration services:
 
-1. Fork the
-   [Project CHIP repository](https://github.com/project-chip/connectedhomeip) by
-   clicking "Fork" on the web UI.
+1. Fork the [Matter repository](https://github.com/project-chip/connectedhomeip)
+   by clicking "Fork" on the web UI.
 
 2. All contributions must pass all checks and reviews to be accepted.
 
@@ -165,8 +164,8 @@ on occasion.
 
 #### Documentation Best Practices
 
-Project CHIP uses Doxygen to markup (or markdown) all C, C++, Objective C,
-Objective C++, Perl, Python, and Java code. Read our
+Matter uses Doxygen to markup (or markdown) all C, C++, Objective C, Objective
+C++, Perl, Python, and Java code. Read our
 [Doxygen Best Practices, Conventions, and Style](https://github.com/project-chip/connectedhomeip/blob/master/docs/style/DOXYGEN.adoc)
 
 #### Submit Pull Request