text:
Mariadb data persists beyond deleting image

Hello,
I'm using mariadb and wanted to load a fresh DB from prod. I expected docker-compose stop mariadb and docker-compose rm mariadb to delete the complete container including database. I've delete an mariadb-related image manually.
On rebuilding, I expected the createdb.sql to be loaded as initially. But the original data remains. Seems like it's stored elsewhere. Is this expected? If so, how would one clear the DB?
Cheers!

Hi @spekulatius, you should delete the volume, not the image

Hi @spekulatius, you should delete the volume, not the image

Shouldn't the volume be removed with the container @soufiene-slimi ?

Shouldn't the volume be removed with the container @soufiene-slimi ?

Not named volumes

Not named volumes

ah okay - that's something I wasn't aware of. I expected them to be deleted with the container.

ah okay - that's something I wasn't aware of. I expected them to be deleted with the container.

I've delete the container, the image and volume. The new database is still not imported. I feel like I'm missing something here...

I've delete the container, the image and volume. The new database is still not imported. I feel like I'm missing something here...

@spekulatius can you provide the output of this command docker volume ls ?

@spekulatius can you provide the output of this command docker volume ls ?

I shutdown the service, deleted the image and volume and restarted it:
✔ /var/www/dev.project.com/laradock [master|✔]
18:41 $ docker-compose stop mariadb nginx workspace redis
Stopping laradock_nginx_1     ... done
Stopping laradock_workspace_1 ... done
Stopping laradock_mariadb_1   ... done
Stopping laradock_redis_1     ... done
✔ /var/www/dev.project.com/laradock [master|✔]
18:52 $ docker-compose rm mariadb nginx workspace redis
Going to remove laradock_nginx_1, laradock_workspace_1, laradock_mariadb_1, laradock_redis_1
Are you sure? [yN] y
Removing laradock_nginx_1     ... done
Removing laradock_workspace_1 ... done
Removing laradock_mariadb_1   ... done
Removing laradock_redis_1     ... done
✔ /var/www/dev.project.com/laradock [master|✔]
18:52 $ docker volume ls | grep lara
local               laradock_adminer
local               laradock_aerospike
local               laradock_caddy
local               laradock_cassandra
local               laradock_confluence
local               laradock_docker-in-docker
local               laradock_elasticsearch
local               laradock_graylog
local               laradock_mariadb
local               laradock_meilisearch
local               laradock_memcached
local               laradock_minio
local               laradock_mongo
local               laradock_mosquitto
local               laradock_mssql
local               laradock_mysql
local               laradock_neo4j
local               laradock_percona
local               laradock_phpmyadmin
local               laradock_postgres
local               laradock_react
local               laradock_redis
local               laradock_rethinkdb
local               laradock_sonarqube
✔ /var/www/dev.project.com/laradock [master|✔]
18:52 $ docker volume rm laradock_mariadb
laradock_mariadb
✔ /var/www/dev.project.com/laradock [master|✔]
18:52 $ docker volume ls | grep lara
local               laradock_adminer
local               laradock_aerospike
local               laradock_caddy
local               laradock_cassandra
local               laradock_confluence
local               laradock_docker-in-docker
local               laradock_elasticsearch
local               laradock_graylog
local               laradock_meilisearch
local               laradock_memcached
local               laradock_minio
local               laradock_mongo
local               laradock_mosquitto
local               laradock_mssql
local               laradock_mysql
local               laradock_neo4j
local               laradock_percona
local               laradock_phpmyadmin
local               laradock_postgres
local               laradock_react
local               laradock_redis
local               laradock_rethinkdb
local               laradock_sonarqube
✔ /var/www/dev.project.com/laradock [master|✔]
18:52 $ docker image rm laradock_mariadb:latest
Untagged: laradock_mariadb:latest
Deleted: sha256:18b0d16703d523b2ab6a367ad6db18a61b6f9439610421a869cbe8456bc92705
Deleted: sha256:23c890ccd1fd6fa9fa2765ae82cc59a2bbd76417b9a0ff89bdb0dce6216641d5
Deleted: sha256:a6b8958c8de80fb5341d7dd0f85efcb52563d9f3271d2e38bb5b8983ee91ecd0
Deleted: sha256:9eaae7041d6cd048b2560ed1784d439219528635417c8393dc458854318301dd
Deleted: sha256:1f00ae4a629aecbd0c1c935f9c316bad50e01ab9355e799b8bd6d21059547e2a
Deleted: sha256:6610127be249eebf578b2139f14d0e49eb39124f36eaa0c9de917184e7cb6e89
Deleted: sha256:bdb86a8d89876da4a017093ef4ce829fd90bad37cf07f1a35afcaa1bf6bf2402
Deleted: sha256:49c1b8a5827ec9ac883e70d8e52afc196bf320551bd8d105c398e80f43b81d07
Deleted: sha256:f941eb5338ccd70c14d31eb823b753f7a721d9217181e30e41376465a1fbb8e2
Deleted: sha256:64e498153a437e40efe848450fb1aeb81a51e2483d4113b3d8099f3b08d8e23a
Deleted: sha256:aed7215b6e741fa63db62b2a4ae5fad108f2de5fba3a9d3782f464efc437c728
✔ /var/www/dev.project.com/laradock [master|✔]
18:53 $ docker-compose up -d mariadb nginx redis workspace
Creating volume "laradock_mariadb" with local driver
Building mariadb
Step 1/10 : ARG MARIADB_VERSION=latest
Step 2/10 : FROM mariadb:${MARIADB_VERSION}
 ---> 3a348a04a815
Step 3/10 : LABEL maintainer="Mahmoud Zalt <mahmoud@zalt.me>"
 ---> Running in 6d2197d87689
Removing intermediate container 6d2197d87689
 ---> fbd36eec6365
Step 4/10 : ARG TZ=UTC
 ---> Running in 90661bbcf062
Removing intermediate container 90661bbcf062
 ---> 95a97af7d51f
Step 5/10 : ENV TZ ${TZ}
 ---> Running in c9ccf617114b
Removing intermediate container c9ccf617114b
 ---> f121e50b90d0
Step 6/10 : RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone && chown -R mysql:root /var/lib/mysql/
 ---> Running in 5c94edc7c480
Removing intermediate container 5c94edc7c480
 ---> ba26fbbf774d
Step 7/10 : COPY my.cnf /etc/mysql/conf.d/my.cnf
 ---> 098dfad20a0b
Step 8/10 : RUN chmod -R 644 /etc/mysql/conf.d/my.cnf
 ---> Running in f1b721ff0a14
Removing intermediate container f1b721ff0a14
 ---> 9f678ee90465
Step 9/10 : CMD ["mysqld"]
 ---> Running in 5670a02a25e9
Removing intermediate container 5670a02a25e9
 ---> f741d637fa60
Step 10/10 : EXPOSE 3306
 ---> Running in 69c602992e8f
Removing intermediate container 69c602992e8f
 ---> c985d9f1c8a3

Successfully built c985d9f1c8a3
Successfully tagged laradock_mariadb:latest
WARNING: Image for service mariadb was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
laradock_docker-in-docker_1 is up-to-date
Creating laradock_redis_1     ... done
Creating laradock_mariadb_1   ... done
Creating laradock_workspace_1 ... done
Recreating laradock_php-fpm_1 ... done
Creating laradock_nginx_1     ... done
✔ /var/www/dev.project.com/laradock [master|✔]
18:54 $

I shutdown the service, deleted the image and volume and restarted it:
✔ /var/www/dev.project.com/laradock [master|✔]
18:41 $ docker-compose stop mariadb nginx workspace redis
Stopping laradock_nginx_1     ... done
Stopping laradock_workspace_1 ... done
Stopping laradock_mariadb_1   ... done
Stopping laradock_redis_1     ... done
✔ /var/www/dev.project.com/laradock [master|✔]
18:52 $ docker-compose rm mariadb nginx workspace redis
Going to remove laradock_nginx_1, laradock_workspace_1, laradock_mariadb_1, laradock_redis_1
Are you sure? [yN] y
Removing laradock_nginx_1     ... done
Removing laradock_workspace_1 ... done
Removing laradock_mariadb_1   ... done
Removing laradock_redis_1     ... done
✔ /var/www/dev.project.com/laradock [master|✔]
18:52 $ docker volume ls | grep lara
local               laradock_adminer
local               laradock_aerospike
local               laradock_caddy
local               laradock_cassandra
local               laradock_confluence
local               laradock_docker-in-docker
local               laradock_elasticsearch
local               laradock_graylog
local               laradock_mariadb
local               laradock_meilisearch
local               laradock_memcached
local               laradock_minio
local               laradock_mongo
local               laradock_mosquitto
local               laradock_mssql
local               laradock_mysql
local               laradock_neo4j
local               laradock_percona
local               laradock_phpmyadmin
local               laradock_postgres
local               laradock_react
local               laradock_redis
local               laradock_rethinkdb
local               laradock_sonarqube
✔ /var/www/dev.project.com/laradock [master|✔]
18:52 $ docker volume rm laradock_mariadb
laradock_mariadb
✔ /var/www/dev.project.com/laradock [master|✔]
18:52 $ docker volume ls | grep lara
local               laradock_adminer
local               laradock_aerospike
local               laradock_caddy
local               laradock_cassandra
local               laradock_confluence
local               laradock_docker-in-docker
local               laradock_elasticsearch
local               laradock_graylog
local               laradock_meilisearch
local               laradock_memcached
local               laradock_minio
local               laradock_mongo
local               laradock_mosquitto
local               laradock_mssql
local               laradock_mysql
local               laradock_neo4j
local               laradock_percona
local               laradock_phpmyadmin
local               laradock_postgres
local               laradock_react
local               laradock_redis
local               laradock_rethinkdb
local               laradock_sonarqube
✔ /var/www/dev.project.com/laradock [master|✔]
18:52 $ docker image rm laradock_mariadb:latest
Untagged: laradock_mariadb:latest
Deleted: sha256:18b0d16703d523b2ab6a367ad6db18a61b6f9439610421a869cbe8456bc92705
Deleted: sha256:23c890ccd1fd6fa9fa2765ae82cc59a2bbd76417b9a0ff89bdb0dce6216641d5
Deleted: sha256:a6b8958c8de80fb5341d7dd0f85efcb52563d9f3271d2e38bb5b8983ee91ecd0
Deleted: sha256:9eaae7041d6cd048b2560ed1784d439219528635417c8393dc458854318301dd
Deleted: sha256:1f00ae4a629aecbd0c1c935f9c316bad50e01ab9355e799b8bd6d21059547e2a
Deleted: sha256:6610127be249eebf578b2139f14d0e49eb39124f36eaa0c9de917184e7cb6e89
Deleted: sha256:bdb86a8d89876da4a017093ef4ce829fd90bad37cf07f1a35afcaa1bf6bf2402
Deleted: sha256:49c1b8a5827ec9ac883e70d8e52afc196bf320551bd8d105c398e80f43b81d07
Deleted: sha256:f941eb5338ccd70c14d31eb823b753f7a721d9217181e30e41376465a1fbb8e2
Deleted: sha256:64e498153a437e40efe848450fb1aeb81a51e2483d4113b3d8099f3b08d8e23a
Deleted: sha256:aed7215b6e741fa63db62b2a4ae5fad108f2de5fba3a9d3782f464efc437c728
✔ /var/www/dev.project.com/laradock [master|✔]
18:53 $ docker-compose up -d mariadb nginx redis workspace
Creating volume "laradock_mariadb" with local driver
Building mariadb
Step 1/10 : ARG MARIADB_VERSION=latest
Step 2/10 : FROM mariadb:${MARIADB_VERSION}
 ---> 3a348a04a815
Step 3/10 : LABEL maintainer="Mahmoud Zalt <mahmoud@zalt.me>"
 ---> Running in 6d2197d87689
Removing intermediate container 6d2197d87689
 ---> fbd36eec6365
Step 4/10 : ARG TZ=UTC
 ---> Running in 90661bbcf062
Removing intermediate container 90661bbcf062
 ---> 95a97af7d51f
Step 5/10 : ENV TZ ${TZ}
 ---> Running in c9ccf617114b
Removing intermediate container c9ccf617114b
 ---> f121e50b90d0
Step 6/10 : RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone && chown -R mysql:root /var/lib/mysql/
 ---> Running in 5c94edc7c480
Removing intermediate container 5c94edc7c480
 ---> ba26fbbf774d
Step 7/10 : COPY my.cnf /etc/mysql/conf.d/my.cnf
 ---> 098dfad20a0b
Step 8/10 : RUN chmod -R 644 /etc/mysql/conf.d/my.cnf
 ---> Running in f1b721ff0a14
Removing intermediate container f1b721ff0a14
 ---> 9f678ee90465
Step 9/10 : CMD ["mysqld"]
 ---> Running in 5670a02a25e9
Removing intermediate container 5670a02a25e9
 ---> f741d637fa60
Step 10/10 : EXPOSE 3306
 ---> Running in 69c602992e8f
Removing intermediate container 69c602992e8f
 ---> c985d9f1c8a3

Successfully built c985d9f1c8a3
Successfully tagged laradock_mariadb:latest
WARNING: Image for service mariadb was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
laradock_docker-in-docker_1 is up-to-date
Creating laradock_redis_1     ... done
Creating laradock_mariadb_1   ... done
Creating laradock_workspace_1 ... done
Recreating laradock_php-fpm_1 ... done
Creating laradock_nginx_1     ... done
✔ /var/www/dev.project.com/laradock [master|✔]
18:54 $

@spekulatius what about docker image inspect laradock_mariadb ?

@spekulatius what about docker image inspect laradock_mariadb ?

[
    {
        "Id": "sha256:c985d9f1c8a3359bc8385789cf6203af06f8a5268962cef028a512177f22eeca",
        "RepoTags": [
            "laradock_mariadb:latest"
        ],
        "RepoDigests": [],
        "Parent": "sha256:f741d637fa606ccc402d366dec06d8c4aafabdf425a9d97cfcaa5cebd9f48a38",
        "Comment": "",
        "Created": "2021-01-21T14:53:56.478137368Z",
        "Container": "69c602992e8fa7fab6be739e592e1d930f0c81f682dc548ae21bc4336ce81f65",
        "ContainerConfig": {
            "Hostname": "69c602992e8f",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "3306/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "GOSU_VERSION=1.12",
                "GPG_KEYS=177F4010FE56CA3336300305F1656F24C74CD1D8",
                "MARIADB_MAJOR=10.5",
                "MARIADB_VERSION=1:10.5.8+maria~focal",
                "TZ=UTC"
            ],
            "Cmd": [
                "/bin/sh",
                "-c",
                "#(nop) ",
                "EXPOSE 3306"
            ],
            "Image": "sha256:f741d637fa606ccc402d366dec06d8c4aafabdf425a9d97cfcaa5cebd9f48a38",
            "Volumes": {
                "/var/lib/mysql": {}
            },
            "WorkingDir": "",
            "Entrypoint": [
                "docker-entrypoint.sh"
            ],
            "OnBuild": null,
            "Labels": {
                "maintainer": "Mahmoud Zalt <mahmoud@zalt.me>"
            }
        },
        "DockerVersion": "19.03.9",
        "Author": "",
        "Config": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "3306/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "GOSU_VERSION=1.12",
                "GPG_KEYS=177F4010FE56CA3336300305F1656F24C74CD1D8",
                "MARIADB_MAJOR=10.5",
                "MARIADB_VERSION=1:10.5.8+maria~focal",
                "TZ=UTC"
            ],
            "Cmd": [
                "mysqld"
            ],
            "Image": "sha256:f741d637fa606ccc402d366dec06d8c4aafabdf425a9d97cfcaa5cebd9f48a38",
            "Volumes": {
                "/var/lib/mysql": {}
            },
            "WorkingDir": "",
            "Entrypoint": [
                "docker-entrypoint.sh"
            ],
            "OnBuild": null,
            "Labels": {
                "maintainer": "Mahmoud Zalt <mahmoud@zalt.me>"
            }
        },
        "Architecture": "amd64",
        "Os": "linux",
        "Size": 406514967,
        "VirtualSize": 406514967,
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/cd0f836d39a4e2e86550e903751cebee989ae94d9a72b1c60d29f98fd4108203/diff:/var/lib/docker/overlay2/52c3a2d20478d65724d676d3c71bf69b1e71e9832bcfd9f7297f25e26482730a/diff:/var/lib/docker/overlay2/9752ca527118072ec88527ad3f973a6c55bad07927102ec41e05d427ed66fd0d/diff:/var/lib/docker/overlay2/91c9d9439cea30115afa0f079fb58f47926a6160e58606acd66efe7f2c0a31a7/diff:/var/lib/docker/overlay2/77d5be5403421cda18120a2d97394dd8c19a05a719e5d4025497c9a86264e432/diff:/var/lib/docker/overlay2/abaaac528fde372094ca45df9478fa1015d4bb65296c413b9a5e09561d5939d6/diff:/var/lib/docker/overlay2/6b9696580df2639ecbf78f520a5357e7d20754dbf897dc26e05f5faa50e9edd1/diff:/var/lib/docker/overlay2/69fb3d3fe7e6365295ec3b509f824c2b893dcf2d93015dcb7378b2dcc70fc9b2/diff:/var/lib/docker/overlay2/d78ab6290b3e76d51d07f224e136a7bb2e63ac23374dd72a41d9770232eda7ea/diff:/var/lib/docker/overlay2/4557c171bbe8efc487626b84d46004ddb39ee2da44371dd90c43670d0fd5d50f/diff:/var/lib/docker/overlay2/413ea396b692e0bb804c01bfccbe8cc5c6681cbe3a0434df3207216489dbc456/diff:/var/lib/docker/overlay2/06873580eea13d107f35dc6bbc5237f7f8d53b9eb5dfc45323267ea25c2d8147/diff:/var/lib/docker/overlay2/94cd9686dd3539c72336a848625ca3b755603f790285df622728191ec8ec7d3a/diff:/var/lib/docker/overlay2/8ce67bfa3c7223fb3e9039644d8968bc2ee477027717d3caa2c2de500ca045f3/diff",
                "MergedDir": "/var/lib/docker/overlay2/1b5af01cfa43db24e7004388d2ae2cdffc0a8a6ba155b5db185ec5e2de5b8af3/merged",
                "UpperDir": "/var/lib/docker/overlay2/1b5af01cfa43db24e7004388d2ae2cdffc0a8a6ba155b5db185ec5e2de5b8af3/diff",
                "WorkDir": "/var/lib/docker/overlay2/1b5af01cfa43db24e7004388d2ae2cdffc0a8a6ba155b5db185ec5e2de5b8af3/work"
            },
            "Name": "overlay2"
        },
        "RootFS": {
            "Type": "layers",
            "Layers": [
                "sha256:bacd3af13903e13a43fe87b6944acd1ff21024132aad6e74b4452d984fb1a99a",
                "sha256:9069f84dbbe96d4c50a656a05bbe6b6892722b0d1116a8f7fd9d274f4e991bf6",
                "sha256:f6253634dc78da2f2e3bee9c8063593f880dc35d701307f30f65553e0f50c18c",
                "sha256:ff068d14a6b3b1244cc7fe27503441e2cb6cbb3853df669b80e23c7558ebb309",
                "sha256:d0a26c9ee0b533ab7cfbd14d4353e2ff50b6b49ec9d42564f3fc2ba2e882b8ec",
                "sha256:c5245e85fcc3612dfd75a0b25d8a3af21cb7a8f79a4fb2724a016ccf40994ede",
                "sha256:9e46a4bfb2263d365b68a611e0b370225294992d6d4cbcdef17fa3b55463ee76",
                "sha256:d897753904d883e1f7a2dea45915531766e3473efaa66c7a111cc43af22413a8",
                "sha256:d556dd0afed8b8b235993cab52d3b8320a8a1f7efb60d6c8c002cbabae7b5feb",
                "sha256:b52018619114ae11cbfab7a993728849448f2628c1b5c598598889123849e65c",
                "sha256:5c2e6ea2fe34173fe862dffd66e4ea9bde29e7469d0f0a6a48f02da04983a2ac",
                "sha256:86e20c7da3da482d6e584c25a99d20177d70c88c14acc4782f74c880320097c0",
                "sha256:8c18a720b1c9f749156d46cd72db55c504a1305c3bf9b4b273b93eb9f7a08a08",
                "sha256:26c5764518cd237e36217bbb7dc5030efa418fee398dfb8c0e879067fcf39353",
                "sha256:865cf92c56a6d55d560fc38a21fdf8006074be1216513bfffb0468c7a453db82"
            ]
        },
        "Metadata": {
            "LastTagTime": "2021-01-21T18:53:56.911235993+04:00"
        }
    }
]

[
    {
        "Id": "sha256:c985d9f1c8a3359bc8385789cf6203af06f8a5268962cef028a512177f22eeca",
        "RepoTags": [
            "laradock_mariadb:latest"
        ],
        "RepoDigests": [],
        "Parent": "sha256:f741d637fa606ccc402d366dec06d8c4aafabdf425a9d97cfcaa5cebd9f48a38",
        "Comment": "",
        "Created": "2021-01-21T14:53:56.478137368Z",
        "Container": "69c602992e8fa7fab6be739e592e1d930f0c81f682dc548ae21bc4336ce81f65",
        "ContainerConfig": {
            "Hostname": "69c602992e8f",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "3306/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "GOSU_VERSION=1.12",
                "GPG_KEYS=177F4010FE56CA3336300305F1656F24C74CD1D8",
                "MARIADB_MAJOR=10.5",
                "MARIADB_VERSION=1:10.5.8+maria~focal",
                "TZ=UTC"
            ],
            "Cmd": [
                "/bin/sh",
                "-c",
                "#(nop) ",
                "EXPOSE 3306"
            ],
            "Image": "sha256:f741d637fa606ccc402d366dec06d8c4aafabdf425a9d97cfcaa5cebd9f48a38",
            "Volumes": {
                "/var/lib/mysql": {}
            },
            "WorkingDir": "",
            "Entrypoint": [
                "docker-entrypoint.sh"
            ],
            "OnBuild": null,
            "Labels": {
                "maintainer": "Mahmoud Zalt <mahmoud@zalt.me>"
            }
        },
        "DockerVersion": "19.03.9",
        "Author": "",
        "Config": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "3306/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "GOSU_VERSION=1.12",
                "GPG_KEYS=177F4010FE56CA3336300305F1656F24C74CD1D8",
                "MARIADB_MAJOR=10.5",
                "MARIADB_VERSION=1:10.5.8+maria~focal",
                "TZ=UTC"
            ],
            "Cmd": [
                "mysqld"
            ],
            "Image": "sha256:f741d637fa606ccc402d366dec06d8c4aafabdf425a9d97cfcaa5cebd9f48a38",
            "Volumes": {
                "/var/lib/mysql": {}
            },
            "WorkingDir": "",
            "Entrypoint": [
                "docker-entrypoint.sh"
            ],
            "OnBuild": null,
            "Labels": {
                "maintainer": "Mahmoud Zalt <mahmoud@zalt.me>"
            }
        },
        "Architecture": "amd64",
        "Os": "linux",
        "Size": 406514967,
        "VirtualSize": 406514967,
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/cd0f836d39a4e2e86550e903751cebee989ae94d9a72b1c60d29f98fd4108203/diff:/var/lib/docker/overlay2/52c3a2d20478d65724d676d3c71bf69b1e71e9832bcfd9f7297f25e26482730a/diff:/var/lib/docker/overlay2/9752ca527118072ec88527ad3f973a6c55bad07927102ec41e05d427ed66fd0d/diff:/var/lib/docker/overlay2/91c9d9439cea30115afa0f079fb58f47926a6160e58606acd66efe7f2c0a31a7/diff:/var/lib/docker/overlay2/77d5be5403421cda18120a2d97394dd8c19a05a719e5d4025497c9a86264e432/diff:/var/lib/docker/overlay2/abaaac528fde372094ca45df9478fa1015d4bb65296c413b9a5e09561d5939d6/diff:/var/lib/docker/overlay2/6b9696580df2639ecbf78f520a5357e7d20754dbf897dc26e05f5faa50e9edd1/diff:/var/lib/docker/overlay2/69fb3d3fe7e6365295ec3b509f824c2b893dcf2d93015dcb7378b2dcc70fc9b2/diff:/var/lib/docker/overlay2/d78ab6290b3e76d51d07f224e136a7bb2e63ac23374dd72a41d9770232eda7ea/diff:/var/lib/docker/overlay2/4557c171bbe8efc487626b84d46004ddb39ee2da44371dd90c43670d0fd5d50f/diff:/var/lib/docker/overlay2/413ea396b692e0bb804c01bfccbe8cc5c6681cbe3a0434df3207216489dbc456/diff:/var/lib/docker/overlay2/06873580eea13d107f35dc6bbc5237f7f8d53b9eb5dfc45323267ea25c2d8147/diff:/var/lib/docker/overlay2/94cd9686dd3539c72336a848625ca3b755603f790285df622728191ec8ec7d3a/diff:/var/lib/docker/overlay2/8ce67bfa3c7223fb3e9039644d8968bc2ee477027717d3caa2c2de500ca045f3/diff",
                "MergedDir": "/var/lib/docker/overlay2/1b5af01cfa43db24e7004388d2ae2cdffc0a8a6ba155b5db185ec5e2de5b8af3/merged",
                "UpperDir": "/var/lib/docker/overlay2/1b5af01cfa43db24e7004388d2ae2cdffc0a8a6ba155b5db185ec5e2de5b8af3/diff",
                "WorkDir": "/var/lib/docker/overlay2/1b5af01cfa43db24e7004388d2ae2cdffc0a8a6ba155b5db185ec5e2de5b8af3/work"
            },
            "Name": "overlay2"
        },
        "RootFS": {
            "Type": "layers",
            "Layers": [
                "sha256:bacd3af13903e13a43fe87b6944acd1ff21024132aad6e74b4452d984fb1a99a",
                "sha256:9069f84dbbe96d4c50a656a05bbe6b6892722b0d1116a8f7fd9d274f4e991bf6",
                "sha256:f6253634dc78da2f2e3bee9c8063593f880dc35d701307f30f65553e0f50c18c",
                "sha256:ff068d14a6b3b1244cc7fe27503441e2cb6cbb3853df669b80e23c7558ebb309",
                "sha256:d0a26c9ee0b533ab7cfbd14d4353e2ff50b6b49ec9d42564f3fc2ba2e882b8ec",
                "sha256:c5245e85fcc3612dfd75a0b25d8a3af21cb7a8f79a4fb2724a016ccf40994ede",
                "sha256:9e46a4bfb2263d365b68a611e0b370225294992d6d4cbcdef17fa3b55463ee76",
                "sha256:d897753904d883e1f7a2dea45915531766e3473efaa66c7a111cc43af22413a8",
                "sha256:d556dd0afed8b8b235993cab52d3b8320a8a1f7efb60d6c8c002cbabae7b5feb",
                "sha256:b52018619114ae11cbfab7a993728849448f2628c1b5c598598889123849e65c",
                "sha256:5c2e6ea2fe34173fe862dffd66e4ea9bde29e7469d0f0a6a48f02da04983a2ac",
                "sha256:86e20c7da3da482d6e584c25a99d20177d70c88c14acc4782f74c880320097c0",
                "sha256:8c18a720b1c9f749156d46cd72db55c504a1305c3bf9b4b273b93eb9f7a08a08",
                "sha256:26c5764518cd237e36217bbb7dc5030efa418fee398dfb8c0e879067fcf39353",
                "sha256:865cf92c56a6d55d560fc38a21fdf8006074be1216513bfffb0468c7a453db82"
            ]
        },
        "Metadata": {
            "LastTagTime": "2021-01-21T18:53:56.911235993+04:00"
        }
    }
]

Hi @spekulatius, as described in the createdb.sql file:
### this SQL script is autorun when mariadb container start and **$DATA_PATH_HOST/mariadb** not exist.
###
### if your $DATA_PATH_HOST/mariadb is exists and you do not want to delete it, you can run by manual execution:
###
###     docker-compose exec mariadb bash
###     mysql -u root -p < /docker-entrypoint-initdb.d/createdb.sql

seems like the problem is that the $DATA_PATH_HOST/mariadb exists somewhere, as a quick fix, try to start the PHPMyAdmin container and do what you want to do there, or follow the comment and execute the file manually.
I'll check where the $DATA_PATH_HOST/mariadb is persisting exactly to fix this issue.
Best Soufiene,

Hi @spekulatius, as described in the createdb.sql file:
### this SQL script is autorun when mariadb container start and **$DATA_PATH_HOST/mariadb** not exist.
###
### if your $DATA_PATH_HOST/mariadb is exists and you do not want to delete it, you can run by manual execution:
###
###     docker-compose exec mariadb bash
###     mysql -u root -p < /docker-entrypoint-initdb.d/createdb.sql

seems like the problem is that the $DATA_PATH_HOST/mariadb exists somewhere, as a quick fix, try to start the PHPMyAdmin container and do what you want to do there, or follow the comment and execute the file manually.
I'll check where the $DATA_PATH_HOST/mariadb is persisting exactly to fix this issue.
Best Soufiene,

HI @spekulatius, the data is persisting under ~/.laradock/data/mariadb, try to run sudo rm -rf ~/.laradock/data/mariadb and this should solve your problem 😀

HI @spekulatius, the data is persisting under ~/.laradock/data/mariadb, try to run sudo rm -rf ~/.laradock/data/mariadb and this should solve your problem 😀

Yaaay! That worked! Thank you! Closing thanks to @soufiene-slimi!

Yaaay! That worked! Thank you! Closing thanks to @soufiene-slimi!

authors: soufiene-slimi spekulatius

repo: laradock/laradock


text:
Upgrade to Stripe 4.1.1

There has been some issues when working with cashier 7.0.

ErrorException in CurlClient.php line 250:
Unexpected error communicating with Stripe. If this problem persists, let us know at support@stripe.com.
(Network error [errno 35]: Unsupported SSL protocol version)

After contacting support@stripe.com, I upgraded my apache to 2.4.8, my php to 5.6.8 and my openssl to 1.0.1f afterwhich the error persisted. Support then asked me to upgrade my stripe to stripe 4.1.1. I but cashier uses 3.0 which caused my composer to break.
My workaround was to place the latest copy of stripe in the vendors folder of my app and it works perfectly but this would cause issues when I run an update. It would be great to have this integrated into the next release for cashier.

Any word on getting this upgraded? Composer is now listing this as extremely outdated as Stripe is now on v4.3.0.

source: gharchive/issue

authors: ellisio jideokus

repo: laravel/cashier

license: mit

license_type: permissive

license_source: bigquery


text:
allow setting of / or move location of bootstrap/cache

right now, we need to make /storage AND boostrap/cache folders writable for usage by the framework.
This is fine (a little annoying) for none distributed applications, but when building something for others to consume this is just added complexity which isnt really desired.
I know the config/services cache has moved a few times already, but doesnt it make sense to just have 1 writeable folder for the framework?
theres two parts to this issue:

can i request a method to "set" the config cache path on the application class so i can update it in the bootstrap/app.php file (without needing to extend the class) before the apps passed to a kernel.
as a proposal for v5.3 can i suggest the current /boostrap/cache/* files are moved to /storage/bootstrap/* for consistency. this would mean only 1 folder needs write permissions, simpler and more secure.

We already moved them out of there for consistency.

This is useful when deploying with zero-downtime.

Isn't still using it under bootstrap/cache folder? I also come up to this situation when my app is only readable state and have to move out of from app root.
https://github.com/laravel/framework/blob/eb3b472ae8032c2832fb7476f0319ad62aca8ace/src/Illuminate/Foundation/Application.php#L857

confirmed, its still under bootstrap/cache in 5.3 and 5.4 versions

If you symlink then weird things seem to happen as well.

I hate to drag-up an old issue, but seems to me it was erroneously closed in the first place, given this statement "We already moved them out of there for consistency." doesn't seem to be correct? Certainly my Laravel 8 install still needs to write to bootstrap/cache.
Am currently looking at what I need to override to be able to move that, as it's a non-starter for me.
It's pretty poor form to be writing files to an application directory IMO, so would prefer to be able to shift this to something in the /var directory or some other more appropriate place.
At the very least all writeable directories should be located in the one subdirectory structure, surely (like the storage one you also default to being within the application code's directory structure)?
I guess it's fine to default to having writeable dirs in an application directory (not really, but hey, it is what it is), but it'd be great to be able to move it when server security policies are such that "code directories are read only".

authors: GrahamCampbell adamcameron hlorofos joeyhub leemason winminsoe

repo: laravel/framework

license: MIT

license_source: github-api


text:
Accept cost parameter or fail BcryptHasher

In PHP, password_hash() and crypt() accept cost parameter.
In Laravel, I did
$hash = bcrypt($password, ['cost' => 11]);
$hash is $2y$10$... so the cost is 10.
Security related functions should be robust, please throw an exception if cost is passed or accept cost parameter in addiction to rounds parameter, in BcryptHasher:
    public function make($value, array $options = [])
    {
        $cost = isset($options['rounds']) ? $options['rounds'] : $this->rounds;

        $hash = password_hash($value, PASSWORD_BCRYPT, ['cost' => $cost]);

        if ($hash === false) {
            throw new RuntimeException('Bcrypt hashing not supported.');
        }

        return $hash;
    }

Anyway, this should throw an exception if any unknown parameter is passed. Typo example:
bcrypt($password, ['round'=>11]);
Anyway2, the meaning rounds = 10 in context of bcrypt implies pretty low security, as bcrypt in practice does hundreds or thousands of rounds (2^cost where cost is between 4 and 31, but cost default is in this year 10, so 1024 rounds).
Anyway3, rounds is specification (bad) and cost is abstraction (good).
Ideally, accept cost parameter and deprecate the rounds parameter, later remove the rounds parameter and always throw an exception when unknown parameter is passed.

rounds is different from the PHP option name, and sounds like it's linear, whereas this cost option is in fact exponential or so.
On the other hand, changing the option name would be a breaking change, and supporting multiple names for the same option doesn't seem to be a good idea.

I'd tend to agree with this proposal:

accept cost parameter and deprecate the rounds parameter, later remove the rounds parameter

Unsure about this part:

throw an exception when unknown parameter is passed

It would be user-friendly, but complicating the codebase

Yes, the rounds should be definitely changed, because people think this is the iterations of bcrypt algo.
But the bcrypt algo is iterated from 16 up to 2147483648 times (2^cost where cost is in 4..31).

authors: misog vlakoff


text:
FileNotFoundException, The file  "./." does not exist

it work on my localhost, but not on live server

what should i do.?

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!


text:
app()->runningInConsole() returns true when invoked inside of a queued job ?

Laravel Version: 7.30.3
PHP Version: 7.4.14

Description:
I noticed that app()->runningInConsole() returns true when being checked inside of a queued job. I did not expect this behaviour. I extend the ConsoleOutput class so that it gives me colourful feedback when running manually via the CLI and otherwise logs the feedback to the log file when not run in the CLI. I was surprised to see that queued jobs (redis queue driver) are considered as being run on the CLI. Not sure if this is a bug or intended. If intended, is there a way to detect whether code is being run manually on the CLI vs being run inside of a queued job
Steps To Reproduce:
Inside a controller function
    public function jobTest()
    {
        logger()->debug(sprintf('JobController - Running in console? %s', app()->runningInConsole())); // returns false

        dispatch(new \App\Jobs\JobTest());
    }

<?php

namespace App\Jobs;

use Illuminate\Bus\Queueable;
use Illuminate\Queue\SerializesModels;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Foundation\Bus\Dispatchable;

class JobTest implements ShouldQueue
{
    use Dispatchable;
    use InteractsWithQueue;
    use Queueable;
    use SerializesModels;

    public function handle()
    {
        logger()->debug(sprintf('JobTest - Running in console? %s', app()->runningInConsole())); // returns true ?!
    }
}

Hey there,
Unfortunately we don't support this version anymore. Please check out our support policy on which versions we are currently supporting. Can you please try to upgrade to the latest version and see if your problem persists? We'll help you out and re-open this issue if so.
Thanks!

Hey there,
Unfortunately we don't support this version anymore. Please check out our support policy on which versions we are currently supporting. Can you please try to upgrade to the latest version and see if your problem persists? We'll help you out and re-open this issue if so.
Thanks!


text:
[5.3] Add '.' by default for 'as' on route

Related issue:
laravel/internals#181 and #15058
This change adds '.' by default when creating the name of a route so instead of using it like this:
Route::group([
    'as' => 'admin.', // the trailing dot makes me think this is unintended
    'prefix' => 'admin'
], function () {
    Route::resource('users', 'UserController');
});

You can now use it like this:
Route::group([
    'as' => 'admin',
    'prefix' => 'admin'
], function () {
    Route::resource('users', 'UserController');
});

Since prefix is not appending a name to the route name anymore people are using the 'as' to achieve this.
Added a trim function so if you are using the old version with an . at the final of the 'as' parameter it will remove it not breaking existing code base.

Is . standardised? I use / in several applications.

This is definetly a breaking change so if we are to merge this it should go into 5.4 :)

Sure, but it still assumes I use a period when I don't necessarily want to, making it opinionated.

@mikerockett Its kinda a standard, if you need to use nested resources for example:
Route::resource('project.member', 'ProjectMemberController');

The  i guess you'll have tu use th . as it explodes it to created a nested resource route, in this case /project/{id}/member and etc.
So you could
Route::group(['as' => 'admin'], function() {
Route::resource('project.member', 'ProjectMemberController');
});

@fernandobandeira - I see, so from that stand-point it is somewhat. I don't use resource routes, so didn't pick up on that. That said, if it is standardised, then does the framework specifically convert other separators to dots in the case of as? If not, it should so that this PR works as intended.

Breaking change.

@taylorotwell
Well also i'd like to comment this, retired from the docs as a statement of why this should be merged:

Resource Route Names No Longer Affected By Prefixes

Alternatively, you may change the prefix option on your route group to the as option:

Route::group(['as' => 'admin'], function () {
//
});

This is actually a wrong statement you can't simply change your 'prefix' to 'as' because 'prefix' adds the '.' meanwhile the 'as' doesn't and this change of behavior is not clear anywhere in the upgrade guide.
Using prefix you would get admin.projects.members meanwhile as adminprojects.members So if this is not merged at least the docs should state the change of behavior.

source: gharchive/pull-request

authors: fernandobandeira mikerockett morloderex taylorotwell


text:
Add methods redirect and view

Add these two methods signatures in registrar contract

@diegosm Adding methods to an interface is a breaking change, and should go to the master branch.

Can't change this on a point release.

authors: diegosm m1guelpf taylorotwell


text:
[5.8] update gitattibutes

update gitattibutes with SECURITY.md

#28635

[…] I also didn't add this to the .gitattributes file because I believe it always has value to be cloned along with the source code.

@bonzai thanks

authors: TBlindaruk bonzai


text:
function for print whole words from strings

Feel free to add this to your own app.

authors: GeorgiNiagulov driesvints


text:
[9.x] Type hint

following from https://github.com/laravel/framework/pull/34224
do people override the default Request object without extending from the default? I can't imagine so, but maybe that was the reason this wasn't originally typed?

I don't see a big reason to change this.


text:
[8.x] Bump Symfony to 5.4

This bumps Symfony to the latest minor version which will be the last iteration of the 5.x series. Doing this will allow us to remove the versioning workaround in our builds and so we can use the latest features of Symfony 5.4 in Laravel 8.

This seams reasonable. Going forward, the 5.4.x series will be only one (from 5.x) to get bug and security fixes, and it is (mostly) BC with all 5.x, so I don't see why anyone would object to us doing this. :shipit:

authors: GrahamCampbell driesvints


text:
Add temporaryDownloadUrl method to FilesystemAdapter

For an implementation using Azure Blob Storage, we needed a way to create a temporary URL that triggers a download. Temporary URLs and file downloads are supported in Laravel filesystems, but this doesn't work out of the box for Azure Blob Storage.
As you can see in the macro below, a content_disposition option is required to generate the download URL. The content disposition is used when generating the shared access signature in the URL.
I found out that there's already a temporaryUploadUrl method for S3 drivers, which could also be useful for an Azure Blob Storage adapter.
Adding a temporaryDownloadUrl method seems to make sense to me.
public function temporaryDownloadUrl(): callable
{
    return function (string $path, DateTimeInterface $expiration, ?string $filename = null, array $options = []): string {

        $filename = str_replace('%', '', Str::ascii($filename ?? basename($path)));

        $options = array_merge([
            'content_disposition' => HeaderUtils::makeDisposition(HeaderUtils::DISPOSITION_ATTACHMENT, $filename),
        ], $options);

        return $this->temporaryUrl($path, $expiration, $options);
    };
}

The Storage facade is macroable so you could macro this into your own application. Or share the Azure driver as a package?

@taylorotwell
Fair enough, that's exactly what we did, our own package with the method added as a mixin.
Just for the sake of argument, why is temporaryUploadUrl in there, given it is only supported for the S3 driver?

authors: shineability taylorotwell


text:
[10.x] Add dependency resolver attributes

Premise of this PR
This PR adds the ability to have an implementation decide where to get dependencies from without explicit binding.
I often use the container for container to resolve services/actions etc in my code to have IoC but
find e.g. giving config values to those classes cumbersome, especially if all other dependencies
can be resolved by the container itself except one (api key for example).
An alternative would be contextual binding, but I personally don't like having references to parameters
that my IDE doesn't understand. Renaming it would probably break the code unless you search for it.
Of course having automated tests would prevent mistakes like that to a certain extend, but I often
mock my dependencies instead of letting them resolve.
This issue was addressed by https://github.com/laravel/framework/pull/46530 but very specific to config.
This PR attempts to provide a more generic solution.
Examples
Before 1:
<?php

namespace App\Providers;

use App\ApiClient;
use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    public function register(): void
    {
        $this->app->bind(ApiClient::class, function () {
            return new ApiClient(
                key: config('services.api.key'),
            );
        });
    }
}

<?php

namespace App;

class ApiClient
{
    public function __construct(
        private readonly string $key,
    ) {
        //
    }
}

Before 2:
<?php

namespace App\Providers;

use App\ApiClient;
use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    public function register(): void
    {
        $this->app->when(ApiClient::class)
            ->needs('$key')
            ->giveConfig('services.api.key');
    }
}

<?php

namespace App;

class ApiClient
{
    public function __construct(
        private readonly string $key,
    ) {
        //
    }
}

After:
No binding needed
<?php

namespace App;

use Illuminate\Config\Attributes\InjectFromConfig;

class ApiClient
{
    public function __construct(
        #[InjectFromConfig('services.api.key')]
        private readonly string $key,
    ) {
        //
    }
}

Benchmarks
My main concern with adding this would be performance due to the usage of reflection, this was
actually not that bad in my opinion. Here are a few test cases, feel free to suggest more scenarios.
Tested on a 2023 M2 MacBook Air 16GB
Test 1:
$container = new Container();

Benchmark::dd(function () use ($container) {
    $container->make(ContainerConcreteStub::class);
}, 100);

Before: 0.001ms
After: 0.002ms
Test 2:
$container = new Container();

Benchmark::dd(function () use ($container) {
    $container->make(ContainerDefaultValueStub::class);
}, 100);

Before: 0.004ms
After: 0.005ms
Test 3:
$container = new Container();

$container->bind(IContainerContractStub::class, ContainerImplementationStub::class);

Benchmark::dd(function () use ($container) {
    $container->make(ContainerNestedDependentStub::class);
}, 100);

Before: 0.007ms
After: 0.007ms
Breaking changes
As far as I can tell this does not break existing code.
Final thoughts
The performance was my main concern like I pointed out earlier. I however also don't know if this is
"too much" for the container, I have always seen the container as fairly straight forward and I think
this feature might lean more toward the "syntactic sugar"-side.
It might be worth it to add a setting to enable or disable this for people who which to avoid the
performance penalty caused by reflection. This will probably have to be set quite early in the
framework lifecycle to guaranty consistent results, not too sure.
Feel free to give feedback. Thanks

Don't totally hate the idea, but not sure I want to take it on right now. 👍


text:
[11.x] Add component view instance caching

This PR will add a view instance caching support to components and prevent creating new view instances on each render resulting in increasing +20% performance rendering components.
Benchmarks:
Before the view instance caching:

After the view instance caching:

With the merge of other recent performance improvement PRs I'm actually not seeing any meaningful performance benefit from this PR anymore. Can you re-run your tests with latest code in 11.x? Mark as ready for review if you want me to take another look or after you comment.

@taylorotwell
This PR is not needed anymore.
But my closed PR (#51141) still can improve performance.
Without in-memory cache support for Blade:

With in-memory cache support for Blade:

@taylorotwell
This PR can cause side effect issues as it caches view data.
web.php:
Route::get('/', function () {
    return view('home');
});

home.blade.php:
<x-sample param1="Hello" />

<x-sample param1="Hello" param2="World" />

<x-sample param1="Hello" />

sample.blade.php:
@if (isset($param1))

Param 1: {{ $param1 }}

@else

Param 1 is not set

@endif

@if (isset($param2))

Param 2: {{ $param2 }}

@else

Param 2 is not set

@endif

Output:

Fixed the reuse data issue and this PR still can improve performance while using View::compose.
Without view instance caching:

With view instance caching:

Causing other side effects, closing the PR.


text:
Add functionality to the framework to customize service providers loading process

Add ability to the framework to optionally alter service providers loading process by providing custom providerRepository and adding more control to the Application's register and bootProvider methods.
This is second part of the solution, please refer to the PR in laravel/octane.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!

authors: taylorotwell tornike


text:
Trying to access array offset on value of type null

Pulse Version
v1.0.0-beta11
Laravel Version
v10.42.0
PHP Version
8.2
Livewire Version
v3.4.2
Database Driver & Version
MySQL 8.0.30
Description
As soon as I add:
    'recorders' => [
    ]

In the pulse.php config file. I get this error:
Trying to access array offset on value of type null
Steps To Reproduce

Open pulse.php config file
Add recorders' => []
You should be getting an error.

I'm using the default configuration for Pulse same for the Pulse dashboard

Hi @jean-mathieu-myevent, may I ask why you're adding that?
I assume the error appears when loading the dashboard, which would be because the cards can't load their configuration.

Hi @jean-mathieu-myevent, may I ask why you're adding that?
I assume the error appears when loading the dashboard, which would be because the cards can't load their configuration.

Initially I was trying to implement this:
https://github.com/maantje/pulse-database
But as soon as I added it in the recorders array it was given this error. So when attempting to debug, I noticed by just adding the array even while being empty it would give that error.

This issue only arises on the dashboard when you are using cards that do not have their recorders registered.
I would recommend making sure all cards you reference in your dashboard have their appropriate recorders added.

repo: laravel/pulse


text:
✨ Adding flywayDB

Resolves https://github.com/laravel/homestead/issues/618

This has been released in the new base box: https://github.com/laravel/settler/releases/tag/v3.1.0

repo: laravel/settler


text:
using jasmine-reporters with the accessibility plugin

Hi,
This is connected to http://stackoverflow.com/questions/29913799/report-accessibility-plugin-results
I want to use the jasmine-reporters plugin to create a report on protractor and the accessibility plugin.
As i understand this does not work out of the box and i have to process the json output. This is because the plugin events are not emitted.
Is there a way to use jasmine-reporters in any way to make the parsing  of the json file. Maybe to use it somehow as post processor?
Thanks,
David

Hi David. As Poijted out in the answer on that SO article, the primary problem here is that the plugin does not emit Jasmine events, so jasmine-reporters (or other custom Jasmine reporters) doesn't receive anything to react to.
Jasmine-reporters Is only designed to work in within a Jasmine environment and responding to those events, and does not have the ability to post process arbitrary files and output XML. You can certainly use jasmine-reporters as an example of what properties you may want to include in your XML, but you may be better off writing a custom xslt to convert your JSON or finding some other tool designed for that purpose.
If you do roll your own, the Junit schema definition is available on GitHub, which you can reference to ensure you write a valid junit-style XML. https://github.com/windyroad/JUnit-Schema

Thanks for your quick response,
David

authors: bloveridge david-gang

repo: larrymyers/jasmine-reporters


text:
Update sts to 2.13.29

Updates software.amazon.awssdk:sts from 2.13.21 to 2.13.29.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk", artifactId = "sts" } ]

labels: library-update, semver-patch

Codecov Report

Merging #351 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #351   +/-   ##
=======================================
  Coverage   46.26%   46.26%
=======================================
  Files          24       24
  Lines         281      281
=======================================
  Hits          130      130
  Misses        151      151

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a12252d...69442fd. Read the comment docs.

authors: codecov-commenter scala-steward


text:
Breadcrumbs not loading for root path until user visits a nested route

Hello,
I'm having an issue where the breadcrumbs will not render for the root path the first time a user visits my app until that user visits a nested route. Once the user visits a nested route, the crumbs will load on the root path. I have display_single_fragment: true in my layout file. The issue can't be replicated by clearing the cache. It can only be replicated by restarting the server or visiting the app from a different machine. It appears to happen regardless of which browser I use.
Thanks!

Greetings,
You can add this line under breadcrumbs call
breadcrumb :root unless breadcrumbs.links.any?

Hi @danielbonnell, if you are still having this issue could you please provide some more information about your environment? E.g. Rails and Gretel version, your config/breadcrumbs.rb file, and relevant lines from your routes.rb file?
Thanks!

@WilHall I had this issue on a pet project I was working on but I haven't touched it since last February and likely won't do anything with it again. The source for the project is here if you're still interested.

authors: WilHall danielbonnell mmatviyiv

repo: lassebunk/gretel


text:
add a web endpoint that processes a SAML token

Deleted!!

Deleted!!

repo: lastpass/saml-sdk-java


text:
推荐使用，这个demo支持20+平台分享和登录QQ、微信、微博、Facebook、twitter、line、instgram等等

https://github.com/MobClub/ShareSDK-for-Android

你们开源我就用。

repo: laughfly/RxSocialLib


text:
Update RustCrypto crates

Updates all RustCrypto dependencies depending on digest 0.9 to the latest versions depending on digest 0.10
Opening as draft, waiting for RSA 0.6.0 to be released (depends on: https://github.com/RustCrypto/RSA/pull/135)

I think this is ready to be merged. The rsa prerelease is just to debug https://github.com/RustCrypto/RSA/issues/146, but there shouldn't be any breaking API changes in the final 0.6.0

Hmm, that issue is closed now but there's still no rsa 0.6.0 release?

I've asked in https://github.com/RustCrypto/RSA/issues/137#issuecomment-1089709692

A new version of rsa has been published

authors: abonander paolobarbolini

repo: launchbadge/sqlx


text:
Directives/components cannot have digits in the name

e.g. "foo-123-bar" fails to match the required pattern: /^[a-z][a-zA-Z]*$/

Fixed in commit 9194e867e3b92460881acdd736d6a52cd1c6b239.

repo: laurence-myers/tcat


text:
Cannot implicitly convert type UnityEngine.Coroutine' to Coroutine'

Hey Laurenth,
sorry to bother but I get this error when importing the LevelLightmapData-script into my project:
Assets/LevelLightmapData.cs(73,38): error CS0029: Cannot implicitly convert type UnityEngine.Coroutine' to Coroutine'
Any idea why this is? Didn't change a thing and in a fresh testproject it is working, too.
I am working on 2018.2.2f1
Thank you in advance for any help and best,
Friedemann

My bad!!
Had a script that I used to test called "Coroutines" in my project :P
Hard to be a noob...
Can you delete this, laurenth? Sorry!!
Best, Friedemann

Ok, no problem :)

authors: BANZBOWINKEL laurenth-unity

repo: laurenth-unity/lightmap-switching-tool


text:
[Docs] List supported operations for the Meshery adapter for Linkerd

Current State:
The operations supported by the adapter for Linkerd are not listed in its documentation.
Desired State:
Under the heading Sample Applications and include a list of the supported operations, with a small explanation for each. The operations can be found listed here; (lines 37-64). Look out for the following line: opType: meshes.OpCategory_SAMPLE_APPLICATION. This means that the operation listed is a sample application.

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

Hey, I'd like to work on this issue

Thanks for jumping in here @lolyparty. Sure. Go ahead!

I'm to add a list of supported operations with their names right? Also can I get a link to where I can read on the operations. Thanks  @chandrashritii

I'm to add a list of supported operations with their names right? Also can I get a link to where I can read on the operations. Thanks @chandrashritii

@lolyparty see the link in the Desired State section in the issue description.

I'm to add a list of supported operations with their names right? Also, can I get a link to where I can read on the operations? Thanks @chandrashritii

@lolyparty see the link in the Desired State section in the issue description.

Ok thank you

@lolyparty you will want to try building the site with Ruby 2.6.7. You might want to use RVM (https://rvm.io) as a tool to help install different versions of Ruby.

@lolyparty you will want to try building the site with Ruby 2.6.7. You might want to use RVM (https://rvm.io) as a tool to help install different versions of Ruby.

Ok, thank you. I'll try that.

authors: chandrashritii leecalcote lolyparty


text:
[Fix CI] Add Label Commenter

Notes for Reviewers
This PR fixes #66

[x] Yes, I signed my commits.

Thank you, @sandramsc 🙂

authors: leecalcote sandramsc


text:
Vue 2.0

@kcalliauw  do you have any plans on update this bootstrap project to use the version 2.0 of vue and the other components?

@gpassarelli
I have been trying to upgrade to vue 2....  but I am pretty stuck on the bootstrap.js file... specifically on the render part .. I am getting a blank screen. @kcalliauw made a sick little app here but a bit difficult to modify.
`const App = Vue.extend(require('./compiled/app.vue'))
new App(router).$mount('#app')
// blank screen
//new Vue(Vue.util.extend({router}, App)).$mount('#app');
// still need to fix this....
//router.start(App, '#app')
//window.router = router
`
Other than that I believe I have the routes working. In tandem I am working on the webpack version, trying to get that to @kcalliauw style working example

can you push the v0.12 version ? I can't find it

authors: boussou gpassarelli iannazzi


text:
更新2.9.4之后部分电脑input聚焦有问题，input.focus();失效了

议题条件

[X] 我确认已查看官方使用文档：https://layui.dev ，但没有找到相关解决方案。
[X] 我确认已在 Issues 中搜索过类似的问题，但没有找到相关解决方案。
[X] 我已仔细阅读： 🍀 Layui Issue 贡献指南

议题类型
疑是 BUG
使用版本
2.9.4
问题描述
更新2.9.4之后部分电脑input自动聚焦有问题，input.focus();失效了
业务代码
const $shop_input= $("#shop_input");
$shop_input.focus();

截图补充
No response
浏览器
Chrome 121.0.6167.86（正式版本） （64 位）
演示地址
No response
友好承诺

[X] 我承诺将本着相互尊重、理解和友善的态度进行交流，共同维护 Layui 良好的社区氛围。

已有类似的 Issue，不要重复提。

repo: layui/layui


text:
About rectification in stage 2

Hi, thanks for the code!
I was wondering why in stage 2 the loss weight lambda-kl-target is set to 0.
From my understanding, the rectification is done by using this term.
Thanks in advance.

The lambda-kl-target term is 0 because it is only used in stage 1 when minimizing the discrepancy between the two classifiers.

repo: layumi/Seg-Uncertainty


text:
Scraperobject Italy tested

In your data.csv https://coronadatascraper.com/#data.csv
city	county	state	country	population	lat	long	url	cases	deaths	recovered	active	tested	growthFactor	date
from detailed file for Italy: https://github.com/pcm-dpc/COVID-19/blob/master/dati-regioni/dpc-covid19-ita-regioni.csv
You have these column headings:
data > date
stato > country
codice_regione
denominazione_regione > state
lat
long
ricoverati_con_sintomi (in hospital)
terapia_intensiva (ICU)
totale_ospedalizzati (total in hospital= in hospital+ICU)
isolamento_domiciliare (home isolation/quarantine)
totale_attualmente_positivi > active (total in hospital+home isolation)
nuovi_attualmente_positivi (new day active)
dimessi_guariti > recovered
deceduti > deaths
totale_casi > cases
tamponi > tested
So you can add tested column too that is really a key number (in Italy we have really low numbers of tested).
If someone can find Spain, Germany, UK tested/tampon csv would be great.

Can you please rebase from the latest master? It looks like you're working off a pretty old commit.

In https://raw.githubusercontent.com/pcm-dpc/COVID-19/master/dati-regioni/dpc-covid19-ita-regioni.csv
data,stato,codice_regione,denominazione_regione,lat,long,ricoverati_con_sintomi,terapia_intensiva,totale_ospedalizzati,isolamento_domiciliare,totale_attualmente_positivi,nuovi_attualmente_positivi,dimessi_guariti,deceduti,totale_casi,tamponi,note_it,note_en
tamponi > tested

The intent is good on this PR, but it badly needs a re-base. Can you redo it against the current master?

Dear Larry
First time here, sorry!
I tried doing so:
https://github.com/lazd/coronadatascraper/commit/072b936510c55a6e6d5944d70e54db32cd94a998#r38078934
Il giorno gio 26 mar 2020 alle ore 20:57 Larry Davis <
notifications@github.com> ha scritto:

The intent is good on this PR, but it badly needs a re-base. Can you redo
it against the current master?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lazd/coronadatascraper/pull/344#issuecomment-604652709,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO4VCPZTMGY72YW7RU6VN63RJOXS3ANCNFSM4LTLWKXA
.

--
also known as aledettaaLe

Ok I get it! I will make the change to include tested as tamponi and set the commit author to you.
Grazie mille!

authors: aledettaale lazd

repo: lazd/coronadatascraper


text:
Connecting multiple EV chargers

Describe the bug
If I connect only one charger everything works. After connecting the second charger, the diagnostic data will remain, but all data from all sensors will disappear.
Screenshots

LOG report:
2024-06-13 07:11:40.863 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_export_register not found.
2024-06-13 07:11:40.864 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_rpm not found.
2024-06-13 07:11:40.865 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_import_interval not found.
2024-06-13 07:11:40.866 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_export_interval not found.
2024-06-13 07:11:40.866 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_factor not found.
2024-06-13 07:11:40.866 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_import_register not found.
2024-06-13 07:11:40.867 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_reactive_import not found.
2024-06-13 07:11:40.868 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_reactive_export not found.
2024-06-13 07:11:40.888 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'ocpp' at custom_components/ocpp/api.py, line 1005: await self.hass.async_create_task(super()._handle_call(msg)) (offender: /usr/local/lib/python3.12/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.12/site-packages/ocpp/charge_point.py", line 238, in start
await self.route_message(message)
File "/usr/local/lib/python3.12/site-packages/ocpp/charge_point.py", line 261, in route_message
await self._handle_call(msg)
File "/config/custom_components/ocpp/api.py", line 1005, in _handle_call
await self.hass.async_create_task(super()._handle_call(msg))
2024-06-13 07:11:40.890 INFO (MainThread) [ocpp] Wallbox_1: send [3,"1415483299",{}]
2024-06-13 07:11:40.899 INFO (MainThread) [ocpp] Wallbox_1: receive message [2,"1754391931","StatusNotification",{"info": "","vendorId": "com.wallbox","vendorErrorCode": "","connectorId": 1,"errorCode": "NoError","status": "Available","timestamp": "2024-06-13T05:11:40Z"}]
2024-06-13 07:11:40.900 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_export_register not found.
2024-06-13 07:11:40.901 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_rpm not found.
2024-06-13 07:11:40.902 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_import_interval not found.
2024-06-13 07:11:40.902 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_export_interval not found.
2024-06-13 07:11:40.902 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_factor not found.
2024-06-13 07:11:40.903 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_import_register not found.
2024-06-13 07:11:40.903 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_reactive_import not found.
2024-06-13 07:11:40.903 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_reactive_export not found.
2024-06-13 07:11:40.908 INFO (MainThread) [ocpp] Wallbox_1: send [3,"1754391931",{}]
2024-06-13 07:11:41.727 ERROR (MainThread) [custom_components.hacs]  No manifest.json file found 'custom_components/None/manifest.json'
2024-06-13 07:11:42.776 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'ocpp' at custom_components/ocpp/api.py, line 571: resp = await self.call(req) (offender: /usr/local/lib/python3.12/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/ocpp/api.py", line 459, in post_connect
await self.get_supported_features()
File "/config/custom_components/ocpp/api.py", line 571, in get_supported_features
resp = await self.call(req)
2024-06-13 07:11:42.781 INFO (MainThread) [ocpp] Wallbox_1: send [2,"4dbb86a5-69be-4f15-a88f-bf0a1525aab0","GetConfiguration",{"key":["SupportedFeatureProfiles"]}]
2024-06-13 07:11:42.879 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"4dbb86a5-69be-4f15-a88f-bf0a1525aab0",{"unknownKey": [],"configurationKey": [{"readonly": true,"key": "SupportedFeatureProfiles","value": "Core,FirmwareManagement,LocalAuthListManagement,Reservation,SmartCharging,RemoteTrigger"} ]}]
2024-06-13 07:11:42.902 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'ocpp' at custom_components/ocpp/api.py, line 571: resp = await self.call(req) (offender: /usr/local/lib/python3.12/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/ocpp/api.py", line 459, in post_connect
await self.get_supported_features()
File "/config/custom_components/ocpp/api.py", line 571, in get_supported_features
resp = await self.call(req)
2024-06-13 07:11:42.908 INFO (MainThread) [ocpp] Wallbox_1: send [2,"ddb6f396-906e-464b-a7b8-ae04db7318fe","GetConfiguration",{"key":["NumberOfConnectors"]}]
2024-06-13 07:11:43.012 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"ddb6f396-906e-464b-a7b8-ae04db7318fe",{"unknownKey": [],"configurationKey": [{"readonly": true,"key": "NumberOfConnectors","value": "1"} ]}]
2024-06-13 07:11:43.016 INFO (MainThread) [ocpp] Wallbox_1: send [2,"c20f325f-0d28-4fd3-b7ef-b341d07f9836","GetConfiguration",{"key":["HeartbeatInterval"]}]
2024-06-13 07:11:43.092 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"c20f325f-0d28-4fd3-b7ef-b341d07f9836",{"unknownKey": [],"configurationKey": [{"readonly": false,"key": "HeartbeatInterval","value": "3600"} ]}]
2024-06-13 07:11:43.114 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'ocpp' at custom_components/ocpp/api.py, line 474: resp = await self.call(req) (offender: /usr/local/lib/python3.12/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/ocpp/api.py", line 474, in post_connect
resp = await self.call(req)
2024-06-13 07:11:43.118 INFO (MainThread) [ocpp] Wallbox_1: send [2,"4a182100-1bb6-4a11-8ef5-e4019e455a4b","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Current.Export"}]
2024-06-13 07:11:43.246 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"4a182100-1bb6-4a11-8ef5-e4019e455a4b",{"status": "Accepted"}]
2024-06-13 07:11:43.270 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'ocpp' at custom_components/ocpp/api.py, line 474: resp = await self.call(req) (offender: /usr/local/lib/python3.12/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/ocpp/api.py", line 474, in post_connect
resp = await self.call(req)
2024-06-13 07:11:43.281 INFO (MainThread) [ocpp] Wallbox_1: send [2,"44b69f5a-f11c-4632-aeee-1ce30b7ea475","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Current.Import"}]
2024-06-13 07:11:43.348 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"44b69f5a-f11c-4632-aeee-1ce30b7ea475",{"status": "Accepted"}]
2024-06-13 07:11:43.349 INFO (MainThread) [ocpp] Wallbox_1: send [2,"945a74a6-177c-497d-9bdb-96723e722bfc","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Current.Offered"}]
2024-06-13 07:11:43.379 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"945a74a6-177c-497d-9bdb-96723e722bfc",{"status": "Accepted"}]
2024-06-13 07:11:43.379 INFO (MainThread) [ocpp] Wallbox_1: send [2,"0e272f53-33e4-4c0f-a0a0-5b8b7e67ed26","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Energy.Active.Export.Interval"}]
2024-06-13 07:11:43.496 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"0e272f53-33e4-4c0f-a0a0-5b8b7e67ed26",{"status": "Accepted"}]
2024-06-13 07:11:43.500 INFO (MainThread) [ocpp] Wallbox_1: send [2,"43ef1d6f-e9cc-4c34-8c73-e1e1a0e7b7ec","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Energy.Active.Export.Register"}]
2024-06-13 07:11:43.780 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"43ef1d6f-e9cc-4c34-8c73-e1e1a0e7b7ec",{"status": "Accepted"}]
2024-06-13 07:11:43.784 INFO (MainThread) [ocpp] Wallbox_1: send [2,"978cfe56-bc2f-4396-9d98-4f4e81ec47e9","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Energy.Active.Import.Interval"}]
2024-06-13 07:11:43.969 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"978cfe56-bc2f-4396-9d98-4f4e81ec47e9",{"status": "Accepted"}]
2024-06-13 07:11:43.971 INFO (MainThread) [ocpp] Wallbox_1: send [2,"c29c83ad-7086-40ba-b1c8-b2f1cc8ca3c2","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Energy.Active.Import.Register"}]
2024-06-13 07:11:43.991 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"c29c83ad-7086-40ba-b1c8-b2f1cc8ca3c2",{"status": "Accepted"}]
2024-06-13 07:11:43.994 INFO (MainThread) [ocpp] Wallbox_1: send [2,"f2822b92-38e4-4208-869b-60e587c50d80","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Frequency"}]
2024-06-13 07:11:44.025 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"f2822b92-38e4-4208-869b-60e587c50d80",{"status": "Accepted"}]
2024-06-13 07:11:44.032 INFO (MainThread) [ocpp] Wallbox_1: send [2,"2ebfb43f-f517-4a69-a53d-4cfdc3e90f31","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Power.Active.Export"}]
2024-06-13 07:11:44.211 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"2ebfb43f-f517-4a69-a53d-4cfdc3e90f31",{"status": "Accepted"}]
2024-06-13 07:11:44.214 INFO (MainThread) [ocpp] Wallbox_1: send [2,"fbd839b9-c0dd-4c88-9c6e-9b433108f404","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Power.Active.Import"}]
2024-06-13 07:11:44.389 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"fbd839b9-c0dd-4c88-9c6e-9b433108f404",{"status": "Accepted"}]
2024-06-13 07:11:44.391 INFO (MainThread) [ocpp] Wallbox_1: send [2,"7b48faf1-0ea0-4811-9ba6-dbf16ae07c24","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Power.Offered"}]
2024-06-13 07:11:44.430 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"7b48faf1-0ea0-4811-9ba6-dbf16ae07c24",{"status": "Accepted"}]
2024-06-13 07:11:44.434 INFO (MainThread) [ocpp] Wallbox_1: send [2,"7fe851c8-670a-4634-9641-3be166da76ee","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"SoC"}]
2024-06-13 07:11:44.594 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"7fe851c8-670a-4634-9641-3be166da76ee",{"status": "Accepted"}]
2024-06-13 07:11:44.596 INFO (MainThread) [ocpp] Wallbox_1: send [2,"5c1479dc-c75c-48b5-943c-f4644b7a2543","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Temperature"}]
2024-06-13 07:11:44.633 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"5c1479dc-c75c-48b5-943c-f4644b7a2543",{"status": "Accepted"}]
2024-06-13 07:11:44.638 INFO (MainThread) [ocpp] Wallbox_1: send [2,"d90eebef-7b55-45e7-a0a2-7aa3fccc9faa","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Voltage"}]
2024-06-13 07:11:44.803 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"d90eebef-7b55-45e7-a0a2-7aa3fccc9faa",{"status": "Accepted"}]
2024-06-13 07:11:44.805 INFO (MainThread) [ocpp] Wallbox_1: send [2,"c213ec29-2100-412d-8927-9909a746ca47","GetConfiguration",{"key":["MeterValuesSampledData"]}]
2024-06-13 07:11:44.827 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"c213ec29-2100-412d-8927-9909a746ca47",{"unknownKey": [],"configurationKey": [{"readonly": false,"key": "MeterValuesSampledData","value": "Voltage"} ]}]
2024-06-13 07:11:44.828 INFO (MainThread) [ocpp] Wallbox_1: send [2,"df7af11c-f3d7-4325-ac89-d10d42696265","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Current.Export,Current.Import,Current.Offered,Energy.Active.Export.Interval,Energy.Active.Export.Register,Energy.Active.Import.Interval,Energy.Active.Import.Register,Frequency,Power.Active.Export,Power.Active.Import,Power.Offered,SoC,Temperature,Voltage"}]
2024-06-13 07:11:45.008 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"df7af11c-f3d7-4325-ac89-d10d42696265",{"status": "Accepted"}]
2024-06-13 07:11:45.009 INFO (MainThread) [ocpp] Wallbox_1: send [2,"a320117d-3d0b-4b54-8eb8-8e5cdfca51a8","GetConfiguration",{"key":["MeterValueSampleInterval"]}]
2024-06-13 07:11:45.031 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"a320117d-3d0b-4b54-8eb8-8e5cdfca51a8",{"unknownKey": [],"configurationKey": [{"readonly": false,"key": "MeterValueSampleInterval","value": "60"} ]}]
2024-06-13 07:11:45.032 INFO (MainThread) [ocpp] Wallbox_1: send [2,"86c1708f-6ae6-4792-9bb0-289a9d0f35a0","GetConfiguration",{"key":["ClockAlignedDataInterval"]}]
2024-06-13 07:11:45.053 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"86c1708f-6ae6-4792-9bb0-289a9d0f35a0",{"unknownKey": [],"configurationKey": [{"readonly": false,"key": "ClockAlignedDataInterval","value": "900"} ]}]
2024-06-13 07:11:45.057 INFO (MainThread) [ocpp] Wallbox_1: send [2,"e69aa474-4ee7-4768-8466-2b8878ab567e","GetConfiguration",{"key":["WebSocketPingInterval"]}]
2024-06-13 07:11:45.251 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"e69aa474-4ee7-4768-8466-2b8878ab567e",{"unknownKey": [],"configurationKey": [{"readonly": true,"key": "WebSocketPingInterval","value": "60"} ]}]
2024-06-13 07:11:45.314 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'ocpp' at custom_components/ocpp/api.py, line 745: resp = await self.call(req) (offender: /usr/local/lib/python3.12/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/ocpp/api.py", line 560, in post_connect
await self.set_availability()
File "/config/custom_components/ocpp/api.py", line 745, in set_availability
resp = await self.call(req)
2024-06-13 07:11:45.322 INFO (MainThread) [ocpp] Wallbox_1: send [2,"13a5ee77-4816-4e8b-916b-777510a179b1","ChangeAvailability",{"connectorId":0,"type":"Operative"}]
2024-06-13 07:11:45.669 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"13a5ee77-4816-4e8b-916b-777510a179b1",{"status": "Accepted"}]
2024-06-13 07:11:45.687 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'ocpp' at custom_components/ocpp/api.py, line 745: resp = await self.call(req) (offender: /usr/local/lib/python3.12/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/ocpp/api.py", line 560, in post_connect
await self.set_availability()
File "/config/custom_components/ocpp/api.py", line 745, in set_availability
resp = await self.call(req)
2024-06-13 07:11:45.700 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'ocpp' at custom_components/ocpp/api.py, line 607: resp = await self.call(req) (offender: /usr/local/lib/python3.12/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/ocpp/api.py", line 563, in post_connect
await self.trigger_boot_notification()
File "/config/custom_components/ocpp/api.py", line 607, in trigger_boot_notification
resp = await self.call(req)
2024-06-13 07:11:45.703 INFO (MainThread) [ocpp] Wallbox_1: send [2,"4ef70412-4ce7-4636-8ab5-627f910e4430","TriggerMessage",{"requestedMessage":"BootNotification"}]
2024-06-13 07:11:46.892 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"4ef70412-4ce7-4636-8ab5-627f910e4430",{"status": "Accepted"}]
2024-06-13 07:11:46.916 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'ocpp' at custom_components/ocpp/api.py, line 607: resp = await self.call(req) (offender: /usr/local/lib/python3.12/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/ocpp/api.py", line 563, in post_connect
await self.trigger_boot_notification()
File "/config/custom_components/ocpp/api.py", line 607, in trigger_boot_notification
resp = await self.call(req)
2024-06-13 07:11:46.920 INFO (MainThread) [ocpp] Wallbox_1: send [2,"c5eabf6b-d7f8-4450-bc22-4b1f4873c194","TriggerMessage",{"requestedMessage":"StatusNotification","connectorId":0}]
2024-06-13 07:11:46.987 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"c5eabf6b-d7f8-4450-bc22-4b1f4873c194",{"status": "Accepted"}]
2024-06-13 07:11:46.988 INFO (MainThread) [ocpp] Wallbox_1: send [2,"69a8d277-a3c1-4444-8067-44903f0bff4d","TriggerMessage",{"requestedMessage":"StatusNotification","connectorId":1}]
2024-06-13 07:11:47.084 INFO (MainThread) [ocpp] Wallbox_1: receive message [2,"1738601311","BootNotification",{"chargePointSerialNumber": "797587","chargePointVendor": "Wall Box Chargers","meterType": "Internal NON compliant","meterSerialNumber": "","chargePointModel": "PLP1-0-2-3","iccid": "","chargeBoxSerialNumber": "797587","firmwareVersion": "6.4.14","imsi": ""}]
2024-06-13 07:11:47.135 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'ocpp' at custom_components/ocpp/api.py, line 1005: await self.hass.async_create_task(super()._handle_call(msg)) (offender: /usr/local/lib/python3.12/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.12/site-packages/ocpp/charge_point.py", line 238, in start
await self.route_message(message)
File "/usr/local/lib/python3.12/site-packages/ocpp/charge_point.py", line 261, in route_message
await self._handle_call(msg)
File "/config/custom_components/ocpp/api.py", line 1005, in _handle_call
await self.hass.async_create_task(super()._handle_call(msg))
2024-06-13 07:11:47.139 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_export_register not found.
2024-06-13 07:11:47.140 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_rpm not found.
2024-06-13 07:11:47.140 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_import_interval not found.
2024-06-13 07:11:47.141 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_export_interval not found.
2024-06-13 07:11:47.141 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_factor not found.
2024-06-13 07:11:47.141 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_import_register not found.
2024-06-13 07:11:47.143 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_reactive_import not found.
2024-06-13 07:11:47.143 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_reactive_export not found.
2024-06-13 07:11:47.161 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'ocpp' at custom_components/ocpp/api.py, line 1005: await self.hass.async_create_task(super()._handle_call(msg)) (offender: /usr/local/lib/python3.12/site-packages/ocpp/messages.py, line 164: with open(path, "r", encoding="utf-8-sig") as f:), please create a bug report at https://github.com/lbbrhzn/ocpp/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.12/site-packages/ocpp/charge_point.py", line 238, in start
await self.route_message(message)
File "/usr/local/lib/python3.12/site-packages/ocpp/charge_point.py", line 261, in route_message
await self._handle_call(msg)
File "/config/custom_components/ocpp/api.py", line 1005, in _handle_call
await self.hass.async_create_task(super()._handle_call(msg))
2024-06-13 07:11:47.163 INFO (MainThread) [ocpp] Wallbox_1: send [3,"1738601311",{"currentTime":"2024-06-13T05:11:47Z","interval":3600,"status":"Accepted"}]
2024-06-13 07:11:47.166 INFO (MainThread) [ocpp] Wallbox_1: receive message [3,"69a8d277-a3c1-4444-8067-44903f0bff4d",{"status": "Accepted"}]
2024-06-13 07:11:48.175 INFO (MainThread) [ocpp] Wallbox_1: receive message [2,"604781483","StatusNotification",{"info": "","vendorId": "com.wallbox","vendorErrorCode": "","connectorId": 1,"errorCode": "NoError","status": "Available","timestamp": "2024-06-13T05:11:47Z"}]
2024-06-13 07:11:48.177 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_export_register not found.
2024-06-13 07:11:48.180 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_rpm not found.
2024-06-13 07:11:48.182 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_import_interval not found.
2024-06-13 07:11:48.183 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_export_interval not found.
2024-06-13 07:11:48.183 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_factor not found.
2024-06-13 07:11:48.185 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_energy_reactive_import_register not found.
2024-06-13 07:11:48.188 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_reactive_import not found.
2024-06-13 07:11:48.188 WARNING (MainThread) [homeassistant.helpers.entity_component] Forced update failed. Entity sensor.charger_1_power_reactive_export not found.
2024-06-13 07:11:48.202 INFO (MainThread) [ocpp] Wallbox_1: send [3,"604781483",{}]
**Desktop

OS: Windows 10
Browser Chrome
Version  125.0.6422.113 (Oficiální sestavení) (64bitový)

Adding information:
EV charger:

Multiple chargers are not currently supported :(

I have same problem, plaese this multiple chargers feature will be available sometime in the future?

same situation here, integration worked so well i bought another charger!
much work involved to add this capability?

I am in process of installing chargers at home, and installed the first charger yesterday. Was happy to see that it mostly works. Today I plan on installing the second charger, but now discovered this topic 😅
Has anyone looked into what it would take to get two chargers working? @lbbrhzn do you know if there are limitations for supporting multiple chargers or was just not considered when implementing as you probably just had one charger to work with?

Hi Tom,There is a branch for supporting multiple chargers using a single server instance, but it still needs some work.Meanwhile, you can just install one server for each charger. Just use a different port for each one and it will work fine.Verstuurd vanaf mijn iPhoneOp 20 okt 2024 om 08:41 heeft Tom Välja @.***> het volgende geschreven:
I am in process of installing chargers at home, and installed the first charger yesterday. Was happy to see that it mostly works. Today I plan on installing the second charger, but now discovered this topic 😅
Has anyone looked into what it would take to get two chargers working? @lbbrhzn do you know if there are limitations for supporting multiple chargers or was just not considered when implementing as you probably just had one charger to work with?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Multiple chargers of the sale brand does not work… at least not for Wallbox even if you use différent ports On 20 Oct 2024, at 12:03, lbbrhzn @.> wrote:
Hi Tom,There is a branch for supporting multiple chargers using a single server instance, but it still needs some work.Meanwhile, you can just install one server for each charger. Just use a different port for each one and it will work fine.Verstuurd vanaf mijn iPhoneOp 20 okt 2024 om 08:41 heeft Tom Välja @.> het volgende geschreven:
I am in process of installing chargers at home, and installed the first charger yesterday. Was happy to see that it mostly works. Today I plan on installing the second charger, but now discovered this topic 😅
Has anyone looked into what it would take to get two chargers working? @lbbrhzn do you know if there are limitations for supporting multiple chargers or was just not considered when implementing as you probably just had one charger to work with?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Hi Tom,There is a branch for supporting multiple chargers using a single server instance, but it still needs some work.Meanwhile, you can just install one server for each charger. Just use a different port for each one and it will work fine.Verstuurd vanaf mijn iPhoneOp 20 okt 2024 om 08:41 heeft Tom Välja @.> het volgende geschreven: I am in process of installing chargers at home, and installed the first charger yesterday. Was happy to see that it mostly works. Today I plan on installing the second charger, but now discovered this topic 😅 Has anyone looked into what it would take to get two chargers working? @lbbrhzn do you know if there are limitations for supporting multiple chargers or was just not considered when implementing as you probably just had one charger to work with? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>

Hi.
It doesn't seems to be working for the set_charge_rate service, as both services are registered under opp.set_charge_rate

authors: VendisFronek anon145 lbbrhzn lightheaded npinguin puhycz rbb-dev sandersr

repo: lbbrhzn/ocpp


text:
create youtube sync FAQ

Please provide feedback / make edits as needed

Hey @tzarebczan, in the 'Minimum requirements' paragraph, the second sentence should probably reference the number of views/videos again to keep things clear.  So 'If it does not, please use one of the other' should probably be 'If your channel does not meet these requirements, please use...'.

authors: tzarebczan wilsonk