How to contribute?

[hgy59]

While working on a solution for matter-js/python-matter-server#1102 I faced some issues

I already have a working solution in a branch on my fork https://github.com/hgy59/chip-wheels/tree/feature-custom-config-data-path

Here are some fixes that I would like to create dedicated PRs for

• to build the wheels for aarch64 I had to choose a different runner (ubuntu-22.04-arm) since ARM64 isn't available anymore
• under ubuntu 22.04 the latest supported version of pygobject is 3.50.0 to create the controller library
• on my fork the build job did not run, since the container is created only when the Docker file was updated (my solution was to force the creation of the docker image when it does not exist)
• the shared library is not stripped yet and enlarges the created wheel unnecessarily

Finally I would like to support custom config data folders by definition of an environment variable.
The config folders are already patched to /data. This works well within docker containers.
But for a standalone installation (i.e. installation with python virtual env) we must not use hard coded paths.
I will hold back such a PR until I get feedback that the python-matter-server really works on Synology Diskstation devices.
But the common issues in the list above should be fixed anyway.

[agners]

How to contribute?

Generally, just by creating a PR. If it doesn't interfere with the main goal and if it doesn't make things unnecessarily complex for our use case, I am happy to merge PR which target other use cases as well.

• to build the wheels for aarch64 I had to choose a different runner (ubuntu-22.04-arm) since ARM64 isn't available anymore

Yeah that is a reasonable change. I've created a PR for it with #122 and #123.

• under ubuntu 22.04 the latest supported version of pygobject is 3.50.0 to create the controller library

We target Debian 12 explicitly, that is why we create our own build container, since that is the preferred glibc based Distribution for Home Assistant. If you want to target Ubuntu, Ubuntu 24.04 is probably the better choice as this is the version upstream CHIP build containers are using.

• on my fork the build job did not run, since the container is created only when the Docker file was updated (my solution was to force the creation of the docker image when it does not exist)

Ugh yeah, I guess ideally we add a check if the container exists, and if not trigger a build just as if the Dockerfile changed. Feel free to create a PR to address this.

• the shared library is not stripped yet and enlarges the created wheel unnecessarily

Yes, and that is done on purpose. We've seen crashes in the SDK in the past, and we attach the debugger when enabling beta mode in our add-on (see home-assistant/addons#3348). This makes it possible to fix actual bugs in the SDK. The size difference isn't all that relevant in nowadays world.