Olen

I made a quick-fix by modifying the Posten Delivery Days sensor to filter out the Invalid dates: ``` value_template: "{{ value_json.nextDeliveryDays | reject('==', 'Invalid date') | list }}" ``` The...

Meldte det inn til posten kundeservice også. De skulle ta det videre.

There is an issue with the use of urllib.parse: ``` >>> address="fd00:1:2:3" >>> result = urllib.parse.urlsplit('//' + address) >>> result.hostname 'fd00' ``` ``` >>> address="[fd00:1:2:3]" >>> result = urllib.parse.urlsplit('//' +...

The rpm requires python3.11. Is the srpm available, so I can rebuild it locally?

I was able to rebuild it, but I think it was the old version... The changes from the PR is not in the sources I get from that srpm

I rebuilt it using the source here instead. I think the issue comes from here: https://github.com/flaktack/systemd-resolved-docker/blob/43e9877f9ac0813d1b7aeed5e6d9b62277401a09/src/systemd_resolved_docker/utils.py#L26 Which again is called from here: https://github.com/flaktack/systemd-resolved-docker/blob/43e9877f9ac0813d1b7aeed5e6d9b62277401a09/src/systemd_resolved_docker/cli.py#L60

The problem is that `parse_ip_port` is called from `parse_listen_address`. https://github.com/flaktack/systemd-resolved-docker/blob/353cc031ce279741dc717719ac6a21c2468b45de/src/systemd_resolved_docker/utils.py#L28-L30 And `parse_listen_address` is used both for the systemd_resolved_listen_address (which contains a port): https://github.com/flaktack/systemd-resolved-docker/blob/353cc031ce279741dc717719ac6a21c2468b45de/src/systemd_resolved_docker/cli.py#L57-L58 And for the docker_listen_addresses, in which `docker_gateway`...

Great, thanks

I only got the error once, just now after upgrading to 2024.6.3, so it could be something else.

Could it make sense to split the ingredient-fied into two parts - amount/volume/whatever and ingredient? This would allow for simpler parsing of the amount-field, and you would avoid all the...