Upgrading problem

Dear Community
I am new to Docker and Teslamate and have tried to upgrade for the first time as described on docs.teslamate.org/docs/upgrading.
The upgrade worked but in the terminal the process is still running and I don't know how to proceed. Thanks for your help!

pi@raspberrypi:~/teslamate $ docker-compose up
Recreating teslamate_teslamate_1 ...
Recreating teslamate_teslamate_1 ... done
Recreating teslamate_mosquitto_1 ... done
Recreating teslamate_grafana_1   ... done
Attaching to teslamate_database_1, teslamate_grafana_1, teslamate_mosquitto_1, teslamate_teslamate_1
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Starting Grafana" logger=server version=6.7.4 commit=8e44bbc5f5 branch=HEAD compiled=2020-05-26T17:35:38+0000
mosquitto_1  |<PHONE_NUMBER>: mosquitto version 1.6.10 starting
mosquitto_1  |<PHONE_NUMBER>: Config loaded from /mosquitto/config/mosquitto.conf.
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config loaded from" logger=settings file=/usr/share/grafana/conf/defaults.ini
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config loaded from" logger=settings file=/etc/grafana/grafana.ini
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.data=/var/lib/grafana"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.logs=/var/log/grafana"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.plugins=/var/lib/grafana-plugins"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.provisioning=/etc/grafana/provisioning"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.log.mode=console"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_DATA=/var/lib/grafana"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_LOGS=/var/log/grafana"
mosquitto_1  |<PHONE_NUMBER>: Opening ipv4 listen socket on port 1883.
mosquitto_1  |<PHONE_NUMBER>: Opening ipv6 listen socket on port 1883.
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PLUGINS=/var/lib/grafana-plugins"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PROVISIONING=/etc/grafana/provisioning"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_ANALYTICS_REPORTING_ENABLED=FALSE"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ADMIN_USER=admin"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ADMIN_PASSWORD=********"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_DISABLE_GRAVATAR=true"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ALLOW_EMBEDDING=true"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_USERS_ALLOW_SIGN_UP=false"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_AUTH_ANONYMOUS_ENABLED=true"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_AUTH_BASIC_ENABLED=false"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Path Home" logger=settings path=/usr/share/grafana
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Path Data" logger=settings path=/var/lib/grafana
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Path Logs" logger=settings path=/var/log/grafana
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Path Plugins" logger=settings path=/var/lib/grafana-plugins
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Path Provisioning" logger=settings path=/etc/grafana/provisioning
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="App mode production" logger=settings
database_1   | The files belonging to this database system will be owned by user "postgres".
database_1   | This user must also own the server process.
database_1   |
database_1   | The database cluster will be initialized with locale "en_US.utf8".
database_1   | The default database encoding has accordingly been set to "UTF8".
database_1   | The default text search configuration will be set to "english".
database_1   |
database_1   | Data page checksums are disabled.
database_1   |
database_1   | fixing permissions on existing directory /var/lib/postgresql/data ... ok
database_1   | creating subdirectories ... ok
database_1   | selecting dynamic shared memory implementation ... posix
database_1   | selecting default max_connections ... 100
database_1   | selecting default shared_buffers ... 128MB
database_1   | selecting default time zone ... Etc/UTC
database_1   | creating configuration files ... ok
database_1   | running bootstrap script ... ok
database_1   | performing post-bootstrap initialization ... ok
database_1   | syncing data to disk ... ok
database_1   |
database_1   |
database_1   | Success. You can now start the database server using:
database_1   |
database_1   |     pg_ctl -D /var/lib/postgresql/data -l logfile start
database_1   |
database_1   | initdb: warning: enabling "trust" authentication for local connections
database_1   | You can change this by editing pg_hba.conf or using the option -A, or
database_1   | --auth-local and --auth-host, the next time you run initdb.
database_1   | waiting for server to start....2020-05-26 08:17:11.024 UTC [46] LOG:  starting PostgreSQL 12.3 (Debian 12.3-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
database_1   | 2020-05-26 08:17:11.034 UTC [46] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
database_1   | 2020-05-26 08:17:11.092 UTC [47] LOG:  database system was shut down at 2020-05-26 08:17:07 UTC
database_1   | 2020-05-26 08:17:11.111 UTC [46] LOG:  database system is ready to accept connections
database_1   |  done
database_1   | server started
database_1   | CREATE DATABASE
database_1   |
database_1   |
database_1   | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/
database_1   |
database_1   | 2020-05-26 08:17:12.156 UTC [46] LOG:  received fast shutdown request
database_1   | waiting for server to shut down....2020-05-26 08:17:12.184 UTC [46] LOG:  aborting any active transactions
database_1   | 2020-05-26 08:17:12.189 UTC [46] LOG:  background worker "logical replication launcher" (PID 53) exited with exit code 1
database_1   | 2020-05-26 08:17:12.194 UTC [48] LOG:  shutting down
database_1   | 2020-05-26 08:17:12.276 UTC [46] LOG:  database system is shut down
database_1   |  done
database_1   | server stopped
database_1   |
database_1   | PostgreSQL init process complete; ready for start up.
database_1   |
database_1   | 2020-05-26 08:17:12.442 UTC [1] LOG:  starting PostgreSQL 12.3 (Debian 12.3-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
database_1   | 2020-05-26 08:17:12.442 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
database_1   | 2020-05-26 08:17:12.442 UTC [1] LOG:  listening on IPv6 address "::", port 5432
database_1   | 2020-05-26 08:17:12.450 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
database_1   | 2020-05-26 08:17:12.501 UTC [64] LOG:  database system was shut down at 2020-05-26 08:17:12 UTC
database_1   | 2020-05-26 08:17:12.520 UTC [1] LOG:  database system is ready to accept connections
database_1   | 2020-05-26 08:24:19.976 UTC [1] LOG:  received smart shutdown request
database_1   | 2020-05-26 08:24:19.992 UTC [1] LOG:  background worker "logical replication launcher" (PID 70) exited with exit code 1
database_1   | 2020-05-26 08:24:25.051 UTC [65] LOG:  shutting down
database_1   | 2020-05-26 08:24:25.099 UTC [1] LOG:  database system is shut down
database_1   |
database_1   | PostgreSQL Database directory appears to contain a database; Skipping initialization
database_1   |
database_1   | 2020-05-26 08:24:46.599 UTC [1] LOG:  starting PostgreSQL 12.3 (Debian 12.3-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
database_1   | 2020-05-26 08:24:46.602 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
database_1   | 2020-05-26 08:24:46.602 UTC [1] LOG:  listening on IPv6 address "::", port 5432
database_1   | 2020-05-26 08:24:46.610 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
database_1   | 2020-05-26 08:24:46.667 UTC [25] LOG:  database system was shut down at 2020-05-26 08:24:25 UTC
database_1   | 2020-05-26 08:24:46.716 UTC [1] LOG:  database system is ready to accept connections
database_1   | 2020-05-26 08:56:15.496 UTC [1] LOG:  received smart shutdown request
database_1   | 2020-05-26 08:56:15.511 UTC [1] LOG:  background worker "logical replication launcher" (PID 31) exited with exit code 1
database_1   | 2020-05-26 08:56:20.604 UTC [26] LOG:  shutting down
database_1   | 2020-05-26 08:56:20.641 UTC [1] LOG:  database system is shut down
database_1   |
database_1   | PostgreSQL Database directory appears to contain a database; Skipping initialization
database_1   |
database_1   | 2020-05-26 08:56:42.157 UTC [1] LOG:  starting PostgreSQL 12.3 (Debian 12.3-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
database_1   | 2020-05-26 08:56:42.160 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
database_1   | 2020-05-26 08:56:42.160 UTC [1] LOG:  listening on IPv6 address "::", port 5432
database_1   | 2020-05-26 08:56:42.167 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
database_1   | 2020-05-26 08:56:42.223 UTC [25] LOG:  database system was shut down at 2020-05-26 08:56:20 UTC
database_1   | 2020-05-26 08:56:42.275 UTC [1] LOG:  database system is ready to accept connections
database_1   | 2020-05-26 15:32:51.708 UTC [845] ERROR:  division by zero
database_1   | 2020-05-26 15:32:51.708 UTC [845] STATEMENT:  WITH first_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2019-05-26T15:32:51.701Z' AND '2020-05-26T15:32:51.702Z'
database_1   | 		ORDER BY date ASC
database_1   | 		LIMIT 1
database_1   | 	),
database_1   | 	last_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2019-05-26T15:32:51.701Z' AND '2020-05-26T15:32:51.702Z'
database_1   | 		ORDER BY date DESC
database_1   | 		LIMIT 1
database_1   | 	)
database_1   | 	SELECT
database_1   | 		convert_km(((SELECT odometer FROM last_position) - (SELECT odometer	FROM first_position)) /
database_1   | 		EXTRACT(days FROM (SELECT date FROM last_position) - (SELECT date	FROM first_position)) *
database_1   | 		(365/12), 'km');
database_1   | 2020-05-26 15:32:52.354 UTC [846] ERROR:  division by zero
database_1   | 2020-05-26 15:32:52.354 UTC [846] STATEMENT:  WITH first_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2019-05-26T15:32:52.347Z' AND '2020-05-26T15:32:52.348Z'
database_1   | 		ORDER BY date ASC
database_1   | 		LIMIT 1
database_1   | 	),
database_1   | 	last_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2019-05-26T15:32:52.347Z' AND '2020-05-26T15:32:52.348Z'
database_1   | 		ORDER BY date DESC
database_1   | 		LIMIT 1
database_1   | 	)
database_1   | 	SELECT
database_1   | 		convert_km(((SELECT odometer FROM last_position) - (SELECT odometer	FROM first_position)) /
database_1   | 		EXTRACT(days FROM (SELECT date FROM last_position) - (SELECT date	FROM first_position)) *
database_1   | 		365, 'km');
database_1   | 2020-05-26 17:21:59.081 UTC [1] LOG:  received smart shutdown request
database_1   | 2020-05-26 17:21:59.095 UTC [1] LOG:  background worker "logical replication launcher" (PID 31) exited with exit code 1
database_1   | 2020-05-26 17:21:59.255 UTC [26] LOG:  shutting down
database_1   | 2020-05-26 17:21:59.303 UTC [1] LOG:  database system is shut down
database_1   |
database_1   | PostgreSQL Database directory appears to contain a database; Skipping initialization
database_1   |
database_1   | 2020-05-26 17:22:26.156 UTC [1] LOG:  starting PostgreSQL 12.3 (Debian 12.3-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
database_1   | 2020-05-26 17:22:26.159 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
database_1   | 2020-05-26 17:22:26.159 UTC [1] LOG:  listening on IPv6 address "::", port 5432
database_1   | 2020-05-26 17:22:26.167 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
database_1   | 2020-05-26 17:22:26.222 UTC [26] LOG:  database system was shut down at 2020-05-26 17:21:59 UTC
database_1   | 2020-05-26 17:22:26.270 UTC [1] LOG:  database system is ready to accept connections
database_1   | 2020-05-26 17:26:47.052 UTC [62] ERROR:  division by zero
database_1   | 2020-05-26 17:26:47.052 UTC [62] STATEMENT:  WITH first_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2019-05-26T17:26:47.088Z' AND '2020-05-26T17:26:47.088Z'
database_1   | 		ORDER BY date ASC
database_1   | 		LIMIT 1
database_1   | 	),
database_1   | 	last_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2019-05-26T17:26:47.088Z' AND '2020-05-26T17:26:47.088Z'
database_1   | 		ORDER BY date DESC
database_1   | 		LIMIT 1
database_1   | 	)
database_1   | 	SELECT
database_1   | 		convert_km(((SELECT odometer FROM last_position) - (SELECT odometer	FROM first_position)) /
database_1   | 		EXTRACT(days FROM (SELECT date FROM last_position) - (SELECT date	FROM first_position)) *
database_1   | 		365, 'km');
database_1   | 2020-05-26 17:26:47.052 UTC [60] ERROR:  division by zero
database_1   | 2020-05-26 17:26:47.052 UTC [60] STATEMENT:  WITH first_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2019-05-26T17:26:47.087Z' AND '2020-05-26T17:26:47.087Z'
database_1   | 		ORDER BY date ASC
database_1   | 		LIMIT 1
database_1   | 	),
database_1   | 	last_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2019-05-26T17:26:47.087Z' AND '2020-05-26T17:26:47.087Z'
database_1   | 		ORDER BY date DESC
database_1   | 		LIMIT 1
database_1   | 	)
database_1   | 	SELECT
database_1   | 		convert_km(((SELECT odometer FROM last_position) - (SELECT odometer	FROM first_position)) /
database_1   | 		EXTRACT(days FROM (SELECT date FROM last_position) - (SELECT date	FROM first_position)) *
database_1   | 		(365/12), 'km');
database_1   | 2020-05-28 14:41:21.757 UTC [5553] ERROR:  division by zero
database_1   | 2020-05-28 14:41:21.757 UTC [5553] STATEMENT:  WITH first_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2020-05-28T02:41:21.675Z' AND '2020-05-28T14:41:21.675Z'
database_1   | 		ORDER BY date ASC
database_1   | 		LIMIT 1
database_1   | 	),
database_1   | 	last_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing SqlStore" logger=server
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2020-05-28T02:41:21.675Z' AND '2020-05-28T14:41:21.675Z'
database_1   | 		ORDER BY date DESC
database_1   | 		LIMIT 1
database_1   | 	)
database_1   | 	SELECT
database_1   | 		convert_km(((SELECT odometer FROM last_position) - (SELECT odometer	FROM first_position)) /
database_1   | 		EXTRACT(days FROM (SELECT date FROM last_position) - (SELECT date	FROM first_position)) *
database_1   | 		(365/12), 'km');
database_1   | 2020-05-28 14:41:21.766 UTC [5553] ERROR:  division by zero
database_1   | 2020-05-28 14:41:21.766 UTC [5553] STATEMENT:  WITH first_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2020-05-28T02:41:21.675Z' AND '2020-05-28T14:41:21.675Z'
database_1   | 		ORDER BY date ASC
database_1   | 		LIMIT 1
database_1   | 	),
database_1   | 	last_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2020-05-28T02:41:21.675Z' AND '2020-05-28T14:41:21.675Z'
database_1   | 		ORDER BY date DESC
database_1   | 		LIMIT 1
database_1   | 	)
database_1   | 	SELECT
database_1   | 		convert_km(((SELECT odometer FROM last_position) - (SELECT odometer	FROM first_position)) /
database_1   | 		EXTRACT(days FROM (SELECT date FROM last_position) - (SELECT date	FROM first_position)) *
database_1   | 		365, 'km');
database_1   | 2020-05-28 14:41:25.435 UTC [5553] ERROR:  division by zero
database_1   | 2020-05-28 14:41:25.435 UTC [5553] STATEMENT:  WITH first_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2020-05-27T14:41:25.359Z' AND '2020-05-28T14:41:25.359Z'
database_1   | 		ORDER BY date ASC
database_1   | 		LIMIT 1
database_1   | 	),
database_1   | 	last_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2020-05-27T14:41:25.359Z' AND '2020-05-28T14:41:25.359Z'
database_1   | 		ORDER BY date DESC
database_1   | 		LIMIT 1
database_1   | 	)
database_1   | 	SELECT
database_1   | 		convert_km(((SELECT odometer FROM last_position) - (SELECT odometer	FROM first_position)) /
database_1   | 		EXTRACT(days FROM (SELECT date FROM last_position) - (SELECT date	FROM first_position)) *
database_1   | 		365, 'km');
database_1   | 2020-05-28 14:41:25.440 UTC [5558] ERROR:  division by zero
database_1   | 2020-05-28 14:41:25.440 UTC [5558] STATEMENT:  WITH first_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2020-05-27T14:41:25.359Z' AND '2020-05-28T14:41:25.359Z'
database_1   | 		ORDER BY date ASC
database_1   | 		LIMIT 1
database_1   | 	),
database_1   | 	last_position AS (
database_1   | 		SELECT date, odometer
database_1   | 		FROM positions
database_1   | 		WHERE car_id = '1' AND date BETWEEN '2020-05-27T14:41:25.359Z' AND '2020-05-28T14:41:25.359Z'
database_1   | 		ORDER BY date DESC
database_1   | 		LIMIT 1
database_1   | 	)
database_1   | 	SELECT
database_1   | 		convert_km(((SELECT odometer FROM last_position) - (SELECT odometer	FROM first_position)) /
database_1   | 		EXTRACT(days FROM (SELECT date FROM last_position) - (SELECT date	FROM first_position)) *
database_1   | 		(365/12), 'km');
database_1   | 2020-05-29 06:13:21.445 UTC [1] LOG:  received smart shutdown request
database_1   | 2020-05-29 06:13:21.459 UTC [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
database_1   | 2020-05-29 06:13:26.537 UTC [27] LOG:  shutting down
database_1   | 2020-05-29 06:13:26.595 UTC [1] LOG:  database system is shut down
database_1   |
database_1   | PostgreSQL Database directory appears to contain a database; Skipping initialization
database_1   |
database_1   | 2020-05-29 06:13:48.230 UTC [1] LOG:  starting PostgreSQL 12.3 (Debian 12.3-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
database_1   | 2020-05-29 06:13:48.233 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
database_1   | 2020-05-29 06:13:48.233 UTC [1] LOG:  listening on IPv6 address "::", port 5432
database_1   | 2020-05-29 06:13:48.240 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
database_1   | 2020-05-29 06:13:48.304 UTC [26] LOG:  database system was shut down at 2020-05-29 06:13:26 UTC
database_1   | 2020-05-29 06:13:48.359 UTC [1] LOG:  database system is ready to accept connections
database_1   | 2020-06-04 18:15:14.458 UTC [1] LOG:  received smart shutdown request
database_1   | 2020-06-04 18:15:14.471 UTC [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
database_1   | 2020-06-04 18:15:19.509 UTC [27] LOG:  shutting down
database_1   | 2020-06-04 18:15:19.568 UTC [1] LOG:  database system is shut down
database_1   |
database_1   | PostgreSQL Database directory appears to contain a database; Skipping initialization
database_1   |
database_1   | 2020-06-04 18:15:41.225 UTC [1] LOG:  starting PostgreSQL 12.3 (Debian 12.3-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
database_1   | 2020-06-04 18:15:41.228 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
database_1   | 2020-06-04 18:15:41.229 UTC [1] LOG:  listening on IPv6 address "::", port 5432
database_1   | 2020-06-04 18:15:41.236 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
database_1   | 2020-06-04 18:15:41.297 UTC [25] LOG:  database system was shut down at 2020-06-04 18:15:19 UTC
database_1   | 2020-06-04 18:15:41.349 UTC [1] LOG:  database system is ready to accept connections
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Connecting to DB" logger=sqlstore dbtype=sqlite3
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Starting DB migration" logger=migrator
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing HTTPServer" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing BackendPluginManager" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing PluginManager" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Starting plugin search" logger=plugins
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Registering plugin" logger=plugins name="Pie Chart"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Registering plugin" logger=plugins name="Map Panel"
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Registering plugin" logger=plugins name=Discrete
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Registering plugin" logger=plugins name=TrackMap
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing HooksService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing OSSLicensingService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing InternalMetricsService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing RemoteCache" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing RenderingService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing AlertEngine" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing QuotaService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing ServerLockService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing UserAuthTokenService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing DatasourceCacheService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing LoginService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing SearchService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing TracingService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing UsageStatsService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing CleanUpService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing NotificationService" logger=server
grafana_1    | t=2020-06-04T18:41:27+0000 lvl=info msg="Initializing provisioningServiceImpl" logger=server
grafana_1    | t=2020-06-04T18:41:28+0000 lvl=info msg="Backend rendering via phantomJS" logger=rendering renderer=phantomJS
grafana_1    | t=2020-06-04T18:41:28+0000 lvl=warn msg="phantomJS is deprecated and will be removed in a future release. You should consider migrating from phantomJS to grafana-image-renderer plugin. Read more at https://grafana.com/docs/grafana/latest/administration/image_rendering/" logger=rendering renderer=phantomJS
grafana_1    | t=2020-06-04T18:41:28+0000 lvl=info msg="Initializing Stream Manager"
grafana_1    | t=2020-06-04T18:41:28+0000 lvl=info msg="HTTP Server Listen" logger=http.server address=[::]:3000 protocol=http subUrl= socket=
teslamate_1  | 18:41:42.523 [info] Already up
teslamate_1  | 18:42:01.318 [info] Version: 1.19.4
teslamate_1  | 18:42:02.727 [info] Refreshed api tokens
teslamate_1  | 18:42:02.727 [info] Scheduling token refresh in 40d
teslamate_1  | 18:42:02.773 [info] Running TeslaMateWeb.Endpoint with cowboy 2.7.0 at :::4000 (http)
teslamate_1  | 18:42:02.778 [info] Access TeslaMateWeb.Endpoint at http://localhost
teslamate_1  | 18:42:03.035 [info] Starting logger for 'Knight who say Ni'
mosquitto_1  |<PHONE_NUMBER>: New connection from <IP_ADDRESS> on port 1883.
mosquitto_1  |<PHONE_NUMBER>: New client connected from <IP_ADDRESS> as TESLAMATE_302E3833353 (p2, c1, k60).
teslamate_1  | 18:42:03.054 [info] MQTT connection has been established
teslamate_1  | 18:42:04.923 [info] tzdata release in place is from a file last modified Wed, 11 Sep 2019 19:35:17 GMT. Release file on server was last modified Fri, 24 Apr 2020 04:15:20 GMT.
teslamate_1  | 18:42:07.138 car_id=1 [info] Start / :asleep
teslamate_1  | 18:42:10.312 [info] Tzdata has updated the release from 2019c to 2020a
teslamate_1  | 18:43:31.858 [info] GET /
teslamate_1  | 18:43:31.913 [info] Sent 200 in 54ms
teslamate_1  | 18:43:35.554 [info] GET /settings
teslamate_1  | 18:43:35.604 [info] Sent 200 in 49ms
teslamate_1  | 18:43:41.388 [info] GET /
teslamate_1  | 18:43:41.406 [info] Sent 200 in 17ms
teslamate_1  | 18:43:41.428 [info] GET /
teslamate_1  | 18:43:41.444 [info] Sent 200 in 14ms
teslamate_1  | 18:46:45.391 [info] GET /
teslamate_1  | 18:46:45.405 [info] Sent 200 in 13ms
teslamate_1  | 19:09:52.797 [info] GET /settings
teslamate_1  | 19:09:52.840 [info] Sent 200 in 42ms
teslamate_1  | 19:14:25.920 [info] GET /geo-fences
teslamate_1  | 19:14:25.944 [info] Sent 200 in 23ms
teslamate_1  | 19:14:28.280 [info] GET /geo-fences/7/edit
teslamate_1  | 19:14:28.290 [info] Sent 200 in 9ms
teslamate_1  | 19:14:42.051 [info] GET /settings
teslamate_1  | 19:14:42.062 [info] Sent 200 in 10ms
teslamate_1  | 19:14:47.547 [info] GET /settings
teslamate_1  | 19:14:47.585 [info] Sent 200 in 37ms
teslamate_1  | 19:14:49.125 [info] GET /
teslamate_1  | 19:14:49.142 [info] Sent 200 in 16ms
teslamate_1  | 19:14:49.162 [info] GET /
teslamate_1  | 19:14:49.179 [info] Sent 200 in 17ms
teslamate_1  | 19:14:51.002 [info] GET /geo-fences
teslamate_1  | 19:14:51.025 [info] Sent 200 in 22ms
teslamate_1  | 19:14:52.969 [info] GET /geo-fences/7/edit
teslamate_1  | 19:14:52.976 [info] Sent 200 in 7ms
teslamate_1  | 19:30:29.909 [info] GET /
teslamate_1  | 19:30:29.924 [info] Sent 200 in 14ms
teslamate_1  | 19:30:29.947 [info] GET /
teslamate_1  | 19:30:29.962 [info] Sent 200 in 15ms
teslamate_1  | 19:30:34.349 [info] GET /settings
teslamate_1  | 19:30:34.377 [info] Sent 200 in 27ms
^CGracefully stopping... (press Ctrl+C again to force)
Stopping teslamate_teslamate_1   ... done
Stopping teslamate_mosquitto_1   ... done
Stopping teslamate_grafana_1     ... done
Stopping teslamate_database_1    ... done
pi@raspberrypi:~/teslamate $ docker-compose up
Starting teslamate_database_1  ... done
Starting teslamate_teslamate_1 ... done
Starting teslamate_grafana_1   ... done
Starting teslamate_mosquitto_1 ... done
Attaching to teslamate_database_1, teslamate_mosquitto_1, teslamate_teslamate_1, teslamate_grafana_1
database_1   |
database_1   | PostgreSQL Database directory appears to contain a database; Skipping initialization
database_1   |
mosquitto_1  |<PHONE_NUMBER>: mosquitto version 1.6.10 starting
mosquitto_1  |<PHONE_NUMBER>: Config loaded from /mosquitto/config/mosquitto.conf.
database_1   | 2020-06-04 19:37:16.286 UTC [1] LOG:  starting PostgreSQL 12.3 (Debian 12.3-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
database_1   | 2020-06-04 19:37:16.320 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
database_1   | 2020-06-04 19:37:16.321 UTC [1] LOG:  listening on IPv6 address "::", port 5432
database_1   | 2020-06-04 19:37:16.332 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
database_1   | 2020-06-04 19:37:16.431 UTC [25] LOG:  database system was shut down at 2020-06-04 19:36:49 UTC
mosquitto_1  |<PHONE_NUMBER>: Opening ipv4 listen socket on port 1883.
mosquitto_1  |<PHONE_NUMBER>: Opening ipv6 listen socket on port 1883.
database_1   | 2020-06-04 19:37:16.452 UTC [1] LOG:  database system is ready to accept connections
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Starting Grafana" logger=server version=6.7.4 commit=8e44bbc5f5 branch=HEAD compiled=2020-05-26T17:35:38+0000
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config loaded from" logger=settings file=/usr/share/grafana/conf/defaults.ini
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config loaded from" logger=settings file=/etc/grafana/grafana.ini
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.data=/var/lib/grafana"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.logs=/var/log/grafana"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.plugins=/var/lib/grafana-plugins"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.provisioning=/etc/grafana/provisioning"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.log.mode=console"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_DATA=/var/lib/grafana"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_LOGS=/var/log/grafana"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PLUGINS=/var/lib/grafana-plugins"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PROVISIONING=/etc/grafana/provisioning"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_ANALYTICS_REPORTING_ENABLED=FALSE"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ADMIN_USER=admin"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ADMIN_PASSWORD=*********"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_DISABLE_GRAVATAR=true"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ALLOW_EMBEDDING=true"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_USERS_ALLOW_SIGN_UP=false"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_AUTH_ANONYMOUS_ENABLED=true"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_AUTH_BASIC_ENABLED=false"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Path Home" logger=settings path=/usr/share/grafana
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Path Data" logger=settings path=/var/lib/grafana
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Path Logs" logger=settings path=/var/log/grafana
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Path Plugins" logger=settings path=/var/lib/grafana-plugins
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Path Provisioning" logger=settings path=/etc/grafana/provisioning
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="App mode production" logger=settings
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing SqlStore" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Connecting to DB" logger=sqlstore dbtype=sqlite3
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Starting DB migration" logger=migrator
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing HTTPServer" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing BackendPluginManager" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing PluginManager" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Starting plugin search" logger=plugins
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Registering plugin" logger=plugins name="Pie Chart"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Registering plugin" logger=plugins name="Map Panel"
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Registering plugin" logger=plugins name=Discrete
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Registering plugin" logger=plugins name=TrackMap
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing HooksService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing OSSLicensingService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing InternalMetricsService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing RemoteCache" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing RenderingService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing AlertEngine" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing QuotaService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing ServerLockService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing UserAuthTokenService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing DatasourceCacheService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing LoginService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing SearchService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing TracingService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing UsageStatsService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing CleanUpService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing NotificationService" logger=server
grafana_1    | t=2020-06-04T19:37:16+0000 lvl=info msg="Initializing provisioningServiceImpl" logger=server
grafana_1    | t=2020-06-04T19:37:17+0000 lvl=info msg="Backend rendering via phantomJS" logger=rendering renderer=phantomJS
grafana_1    | t=2020-06-04T19:37:17+0000 lvl=warn msg="phantomJS is deprecated and will be removed in a future release. You should consider migrating from phantomJS to grafana-image-renderer plugin. Read more at https://grafana.com/docs/grafana/latest/administration/image_rendering/" logger=rendering renderer=phantomJS
grafana_1    | t=2020-06-04T19:37:17+0000 lvl=info msg="Initializing Stream Manager"
grafana_1    | t=2020-06-04T19:37:17+0000 lvl=info msg="HTTP Server Listen" logger=http.server address=[::]:3000 protocol=http subUrl= socket=
teslamate_1  | 19:37:21.931 [info] Already up
teslamate_1  | 19:37:40.802 [info] Version: 1.19.4
teslamate_1  | 19:37:42.162 [info] Refreshed api tokens
teslamate_1  | 19:37:42.163 [info] Scheduling token refresh in 40d
teslamate_1  | 19:37:42.208 [info] Running TeslaMateWeb.Endpoint with cowboy 2.7.0 at :::4000 (http)
teslamate_1  | 19:37:42.213 [info] Access TeslaMateWeb.Endpoint at http://localhost
teslamate_1  | 19:37:42.444 [info] Starting logger for 'Knight who say Ni'
mosquitto_1  |<PHONE_NUMBER>: New connection from <IP_ADDRESS> on port 1883.
mosquitto_1  |<PHONE_NUMBER>: New client connected from <IP_ADDRESS> as TESLAMATE_302E3134303 (p2, c1, k60).
teslamate_1  | 19:37:42.467 [info] MQTT connection has been established
teslamate_1  | 19:37:43.370 car_id=1 [info] Start / :asleep
teslamate_1  | 19:38:03.241 [info] GET /settings
teslamate_1  | 19:38:03.350 [info] Sent 200 in 108ms
teslamate_1  | 19:38:11.586 [info] GET /settings
teslamate_1  | 19:38:11.635 [info] Sent 200 in 49ms
teslamate_1  | 19:38:12.622 [info] GET /
teslamate_1  | 19:38:12.639 [info] Sent 200 in 16ms
teslamate_1  | 19:38:12.663 [info] GET /
teslamate_1  | 19:38:12.676 [info] Sent 200 in 12ms

Ctrl+C will shut down the containers and detach you from them as well.
In the future, use docker-compose up -d to automatically detach so you can run it in the background.

Hi @KnightwhosayNi777 - I would kill that (Ctrl + C should do it). When you run that again, use the "-d" option which runs the container in the background and detached. If there are errors those won't show up in the console, and I always suggest to go and login and see if teslamate is running as expected.
I just upgraded one of my instances:

I stopped with Ctrl+C and then ran sudo docker-compose up -d. Works great, thanks a lot!
Does it need the sudo? In the TeslaMate documentation the commands are without sudo.

I stopped with Ctrl+C and then ran sudo docker-compose up -d. Works great, thanks a lot!
Does it need the sudo? In the TeslaMate documentation the commands are without sudo.

If it works without sudo you don't need sudo.
To run docker you just need to be part of the docker group.


Update sensor.py

Added sensors for "iavblq_3p" and "iavblq" used for load balancing applications.

Nice! Could you add a test for each of the sensors as well? There is one which tests all ehub sensors where you can add those two sensors. Just run pytest in the root-folder to see the results as well as test coverage.

Nice! Could you add a test for each of the sensors as well? There is one which tests all ehub sensors where you can add those two sensors. Just run pytest in the root-folder to see the results as well as test coverage.

I tried to add the tests and data for the new sensors but I have not been able to run the tests my self.

Superseded by #58


error happens when cargo install b3sum

Hi , I am trying to install blake3
when executing "cargo install b3sum", an error happens and the log looks:
...
cargo:warning=c/blake3_avx512_x86-64_unix.S:2517: Error: operand type mismatch for `vpxord'
cargo:warning=c/blake3_avx512_x86-64_unix.S:2518: Error: operand type mismatch for `vprord'
cargo:warning=c/blake3_avx512_x86-64_unix.S:2521: Error: operand type mismatch for `vpxord'
cargo:warning=c/blake3_avx512_x86-64_unix.S:2522: Error: operand type mismatch for `vprord'
cargo:warning=c/blake3_avx512_x86-64_unix.S:2524: Error: operand type mismatch for `vpxord'
cargo:warning=c/blake3_avx512_x86-64_unix.S:2525: Error: operand type mismatch for `vprord'

error occurred: Command "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-Wall" "-Wextra" "-std=c11" "-mavx512f" "-mavx512vl" "-o" "/tmp/cargo-install5M7wG7/release/build/blake3-40c61925e7999996/out/c/blake3_avx512_x86-64_unix.o" "-c" "c/blake3_avx512_x86-64_unix.S" with args "cc" did not execute successfully (status code exit code: 1).

Seems the compiler tries to use AVX512 feature in the compiling, while my CPU does not support AVX 512 (Intel Xeon E5 2680

What's the version of your C compiler and/or binutils?

This function in build.rs should be detecting whether your compiler supports AVX-512 flags, and disabling our AVX-512 code if not. If you have time, could you help us figure out what it's doing in your case? I've pushed a branch called avx512_debug which fills that function with debug prints. Could you run it something like this, and tell us what you see:
git clone https://github.com/BLAKE3-team/BLAKE3
cd BLAKE3/b3sum
git checkout avx512_debug
cargo build

What's the version of your C compiler and/or binutils?

Using gcc version 5.5.0

This function in build.rs should be detecting whether your compiler supports AVX-512 flags, and disabling our AVX-512 code if not. If you have time, could you help us figure out what it's doing in your case? I've pushed a branch called avx512_debug which fills that function with debug prints. Could you try building it with some commands like these, and tell us what you see:
git clone https://github.com/BLAKE3-team/BLAKE3
cd BLAKE3/b3sum
git checkout avx512_debug
cargo build

Thanks I will try it later and report what happens

This function in build.rs should be detecting whether your compiler supports AVX-512 flags, and disabling our AVX-512 code if not. If you have time, could you help us figure out what it's doing in your case? I've pushed a branch called avx512_debug which fills that function with debug prints. Could you try building it with some commands like these, and tell us what you see:
git clone https://github.com/BLAKE3-team/BLAKE3
cd BLAKE3/b3sum
git checkout avx512_debug
cargo build

cargo:warning=c/blake3_avx512_x86-64_unix.S:2522: Error: operand type mismatch for `vprord'
 cargo:warning=c/blake3_avx512_x86-64_unix.S:2524: Error: operand type mismatch for `vpxord'
 cargo:warning=c/blake3_avx512_x86-64_unix.S:2525: Error: operand type mismatch for `vprord'
 exit code: 1

 --- stderr
 [build.rs:88] is_windows_msvc() = false
 [build.rs:95] build.is_flag_supported("-mavx512f") = Ok(
     true,
 )
 [build.rs:96] build.is_flag_supported("-mavx512vl") = Ok(
     true,
 )
 [build.rs:100] support_result = Ok(
     true,
 )
 [build.rs:101] YesAVX512 = YesAVX512

 error occurred: Command "cc" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-Wall" "-Wextra" "-std=c11" "-mavx512f" "-mavx512vl" "-o" "/home/dell-07/blake3/BLAKE3-avx512_debug/target/debug/build/blake3-9eeb7062f782522d/out/c/blake3_avx512_x86-64_unix.o" "-c" "c/blake3_avx512_x86-64_unix.S" with args "cc" did not execute successfully (status code exit code: 1).

I'm almost certain that this is caused by an old binutils version. What's the output of as -v /dev/null?

This is what happens with binutils 2.24, which is from 2014 and (as far as I can tell) is used in Ubuntu 14.04:
$ ./binutils-2.24/gas/as-new --64 blake3_avx512_x86-64_unix.s 2>&1 | tail -3
blake3_avx512_x86-64_unix.S:2522: Error: operand type mismatch for `vprord'
blake3_avx512_x86-64_unix.S:2524: Error: operand type mismatch for `vpxord'
blake3_avx512_x86-64_unix.S:2525: Error: operand type mismatch for `vprord'

Binutils 2.24 happens to be the last version that did not supposed AVX-512 instructions.

This is what happens with binutils 2.24, which is from 2013 and (as far as I can tell) is used in Ubuntu 14.04:
$ ./binutils-2.24/gas/as-new --64 blake3_avx512_x86-64_unix.s 2>&1 | tail -3
blake3_avx512_x86-64_unix.S:2522: Error: operand type mismatch for `vprord'
blake3_avx512_x86-64_unix.S:2524: Error: operand type mismatch for `vpxord'
blake3_avx512_x86-64_unix.S:2525: Error: operand type mismatch for `vprord'

Binutils 2.24 happens to be the last version that did not support AVX-512 instructions.

Yes, the compiling is done in Ubuntu 14.04. I will update the OS and try later.


Bug: Fix abort timeout in waitForVideosToBeWritten

This PR fixes abortTime value in waitForVideosToBeWritten and waitForVideosToExist causing script waiting approx 54 years before exit
Please see diff and implementation of waitForVideosToBeWritten for details.
Steps to Reporduce:

Set saveAllVideos = false
Run tests. If any of tests are success - process stucks in infinite loop

@christian-bromann could you please take a look of this one-liner PR when you get a chance?

Can we update line 303 since this will resolve always true now.

True, my bad. Fixed at https://github.com/webdriverio-community/wdio-video-reporter/commit/7a6a6538bd72bd6c5d2f8eb3af4933bc474666d1


Something went wrong error while trying to start training

usage: train_dreambooth.py [-h] --pretrained_model_name_or_path
                           PRETRAINED_MODEL_NAME_OR_PATH [--revision REVISION]
                           [--tokenizer_name TOKENIZER_NAME]
                           --instance_data_dir INSTANCE_DATA_DIR
                           [--class_data_dir CLASS_DATA_DIR] --instance_prompt
                           INSTANCE_PROMPT [--class_prompt CLASS_PROMPT]
                           [--with_prior_preservation]
                           [--prior_loss_weight PRIOR_LOSS_WEIGHT]
                           [--num_class_images NUM_CLASS_IMAGES]
                           [--output_dir OUTPUT_DIR] [--seed SEED]
                           [--resolution RESOLUTION] [--center_crop]
                           [--train_text_encoder]
                           [--train_batch_size TRAIN_BATCH_SIZE]
                           [--sample_batch_size SAMPLE_BATCH_SIZE]
                           [--num_train_epochs NUM_TRAIN_EPOCHS]
                           [--max_train_steps MAX_TRAIN_STEPS]
                           [--save_steps SAVE_STEPS]
                           [--gradient_accumulation_steps GRADIENT_ACCUMULATION_STEPS]
                           [--gradient_checkpointing]
                           [--learning_rate LEARNING_RATE] [--scale_lr]
                           [--lr_scheduler LR_SCHEDULER]
                           [--lr_warmup_steps LR_WARMUP_STEPS]
                           [--use_8bit_adam] [--adam_beta1 ADAM_BETA1]
                           [--adam_beta2 ADAM_BETA2]
                           [--adam_weight_decay ADAM_WEIGHT_DECAY]
                           [--adam_epsilon ADAM_EPSILON]
                           [--max_grad_norm MAX_GRAD_NORM] [--push_to_hub]
                           [--hub_token HUB_TOKEN]
                           [--hub_model_id HUB_MODEL_ID]
                           [--logging_dir LOGGING_DIR]
                           [--mixed_precision {no,fp16,bf16}]
                           [--local_rank LOCAL_RANK]
train_dreambooth.py: error: unrecognized arguments: --image_captions_filename --save_starting_step=3000 --stop_text_encoder_training=10 --save_n_steps=3000 --Session_dir=/content/gdrive/MyDrive/Fast-Dreambooth/Sessions/gtest
Traceback (most recent call last):
  File "/usr/local/bin/accelerate", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.7/dist-packages/accelerate/commands/accelerate_cli.py", line 43, in main
    args.func(args)
  File "/usr/local/lib/python3.7/dist-packages/accelerate/commands/launch.py", line 837, in launch_command
    simple_launcher(args)
  File "/usr/local/lib/python3.7/dist-packages/accelerate/commands/launch.py", line 354, in simple_launcher
    raise subprocess.CalledProcessError(returncode=process.returncode, cmd=cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3', '/content/diffusers/examples/dreambooth/train_dreambooth.py', '--image_captions_filename', '--save_starting_step=3000', '--stop_text_encoder_training=10', '--save_n_steps=3000', '--Session_dir=/content/gdrive/MyDrive/Fast-Dreambooth/Sessions/gtest', '--pretrained_model_name_or_path=/content/stable-diffusion-v1-5', '--instance_data_dir=/content/gdrive/MyDrive/Fast-Dreambooth/Sessions/gtest/instance_images', '--output_dir=/content/models/gtest', '--instance_prompt=', '--seed=682980', '--resolution=512', '--mixed_precision=fp16', '--train_batch_size=1', '--gradient_accumulation_steps=1', '--use_8bit_adam', '--learning_rate=2e-6', '--lr_scheduler=polynomial', '--lr_warmup_steps=0', '--max_train_steps=15000']' returned non-zero exit status 2.
Something went wrong

Error while running start training cell, please help

TheLastBen reset his Diffusers repo 20 hours ago, and now this repo and all the collab books are no longer functioning.

TheLastBen reset his Diffusers repo 20 hours ago, and now this repo and all the collab books are no longer functioning.

the current diffusers branch us "updt" not the "main" one

TheLastBen reset his Diffusers repo 20 hours ago, and now this repo and all the collab books are no longer functioning.

the current diffusers branch us "updt" not the "main" one, the reason of the temporary down is because google switched to python 3.8, but now everything is fixed

Thanks for everything, bro. You've done a great job! Your modifications to Shivam diffusers are amazing!

Using python 3.8 but it still doesn't work for me ; statut 1 btw

@Mariiexe use the latest colab and use the new method colab

@TheLastBen It works now, thanks !


TypeScript has doubled in size since v2.0.0 - now 35 MB

Search Terms: install size mb
Expected behavior:
I expected typescript to be relatively small since it has zero dependencies so there is no additional bloat from package.json or README.md files included with dependencies.
<EMAIL_ADDRESS>is about 17 MB, not too bad.
Actual behavior:
<EMAIL_ADDRESS>is about 35 MB - double the size in about 2 years.
I realize that there are no stated goals of install size, however it is worth considering because...how is TypeScript getting so big so fast? 😕
This might inhibit new users from coming on board when their code base might be a few kB with plain JS and adding TS would make it 35 MB.
Steps to reproduce
mkdir ts2.0
cd ts2.0
npm init -y
npm install --save-dev<EMAIL_ADDRESS>cd ..
mkdir ts2.9
cd ts2.9
npm init -y
npm install --save-dev<EMAIL_ADDRESS>cd ..
du -sh ts2.0 # 17M
du -sh ts2.9 # 35M

I agree - installs should be definitely be fast! But also keep in mind that 2 years is a long time, so we've done a lot outside of what was in 2.0 (e.g. infrastructure for our emit pipeline).
The TypeScript package's lib folder contains the following:

4.85MB of lib.*.d.ts files
0.87MB of .d.ts files relating to our API
2.20MB of localized versions of error messages used by the --locale flag

Then we have something like 24.8MB of .js files (this is all me trusting Windows Explorer btw 😃).
But you're right, on an individual basis, tsc.js from 2.0 is about half of what we're producing now. This is exacerbated by the fact that the compiler's core code (e.g. type-checker etc.) are duplicated between outputs like tsc.js and typescript.js. So if the core compiler increased by 1.44MB, I believe we'd see something like a 7.2MB increase. If we used modules, we'd be able to share each file and avoid this duplication.

@DanielRosenwasser Thanks for the quick and detailed response!
The installs are pretty fast which is why it caught me off guard.
I noticed typescript is about the same size as webpack-cli but installs much faster, likely due to the fact that there are zero dependencies (I didn't measure install times and I'm not sure if npm caches results anyway).

If we used modules, we'd be able to share each file and avoid this duplication.

By modules, you mean ES6 Modules? Something that node.js doesn't support yet?
I know that @jdalton wrote esm which might be worth including a few additional kB from the esm dependency if you can drastically decrease the output size.
I'm not sure how much collaboration there is between the TS team and the Chakra team or even if this is achievable.

Oops, totally invalid results. Didn't realize NPM changed behavior and started saving to package.json by default!

I have been doing some comparisons of popular tools in similar categories and I happen to really like TypeScript so I thought I would make note of it.
You can see some of the comparisons I've done here: https://github.com/styfle/packagephobia#demo

That being said, what is the quote "If we used modules, we'd be able to share each file and avoid this duplication" mean? Is this achievable in a TS 3.0.0 or some future release?

We have a change to reorganize the library in https://github.com/Microsoft/TypeScript/pull/15780. this should allow us to remove all duplication in the lib files. that said, I expect the lib file to increase in the next release as we are working on updating it and adding comments, so that might end up being a wash.
We should be able to remove some 6 MBs by combining the two targets tsserverlibarary.js and typescriptservices.js. this a breaking change, so we will have to phase it on two releases or so (i.e. combine the contents of the two files in one, but keep both copies in one release, then remove one copy in the next release.).
We can always minify our output. we have not had a reason to do this in the past.

That being said, what is the quote "If we used modules, we'd be able to share each file and avoid this duplication" mean? Is this achievable in a TS 3.0.0 or some future release?

it is something we want to do, but no plans for the short term. that is where the majority of savings would come from. if we use modules, we should be able to cut the non-library part to 7 MBs or so.

That being said, what is the quote "If we used modules, we'd be able to share each file and avoid this duplication" mean?

For context, today we don't use modules; each file in the Typescript compiler uses namespaces in the global scope, and is concatenated at the end.

We can always minify our output. we have not had a reason to do this in the past.

For a Node project, I don't think this is worth it unless it'd just be about stripping out whitespace.

Thanks for all the information, I appreciate the dialog 👍
I would like to point out that the latest<EMAIL_ADDRESS>has just doubled again
...now 76.8 MB! 😮
The spike was introduced in<EMAIL_ADDRESS>Is this worrisome? At what point is TypeScript too big? 😕

@mhegazy is the case of those files wrong in our npmignore? All we did was start to publish on 'nix.

the .d.ts files indicate a change in the build process, we should not be building tsc.d.ts in the first place.

lib\diagnosticmessages.generated.json should not be there either.

the *.map file means that debug=true was not set when the build was triggered.

looks like we are explictlly setting setDebugMode in the build.

nevermind, we set it to run the tests, and not for the publishing..

looks like the rouge files were added in #23844

<EMAIL_ADDRESS>was just published, and we are back to 35 MB.

Thanks, I confirmed
Also, I created #24282 to display this info in the README so it's more visible.

Also happened again in<EMAIL_ADDRESS>

version
install size

3.1.0-dev.20180717

3.1.0-dev.20180721

Surely this must be a bug, right?

@weswigham can u take a look.


Implement consul 0.5.1 ACL upsert

This should clean out a lot of our ACL code. 0.5.1 is scheduled for release the week of 5/12/2015.
https://github.com/hashicorp/consul/pull/909

[x] upgrade packages to consul 0.5.1
[x] upgrade cluster to consul 0.5.1
[x] Replace our ACL creation and detection code with UUID generation in security-setup.

PR https://github.com/CiscoCloud/microservices-infrastructure/pull/270

#270 has been merged, closing


rbac Implementation

Is there any we can manage admins and other roles via the user interface? I know that we can make use of the rbca feature but will it compatible with your code and if so how can we implement it?

I hope to see your implementation soon!! Keep up the great work

I hope to see your implementation soon!! Keep up the great work

@mve-it-solutions I have implemented yii2-admin but I still can't allow other users to have access to the admin page of yii2-user. I still have to do it via the program. Do you have a way of implementing it? I have created a role admin and I want the user with this role to have access to the admin page of yii2-user. Please Help


Error building wheel for rustpython_ast (pyo3)

I cloned the repository, entered the ast-pyo3 directory, and ran pyproject-build:
% pyproject-build
* Creating venv isolated environment...
* Installing packages in isolated environment... (maturin>=0.15,<0.16)
* Getting build dependencies for sdist...
* Building sdist...
Running `maturin pep517 write-sdist --sdist-directory /media/data/dev/griffe/rustpython_parser/ast-pyo3/dist`
🍹 Building a mixed python/rust project
🔗 Found pyo3 bindings
🐍 Found CPython 3.11 at /tmp/build-env-m11693t3/bin/python3
📡 Using build options features from pyproject.toml
📦 Built source distribution to /media/data/dev/griffe/rustpython_parser/ast-pyo3/dist/rustpython_ast-0.0.1.tar.gz
rustpython_ast-0.0.1.tar.gz
* Building wheel from sdist
* Creating venv isolated environment...
* Installing packages in isolated environment... (maturin>=0.15,<0.16)
* Getting build dependencies for wheel...
* Building wheel...
Running `maturin pep517 build-wheel -i /tmp/build-env-ra719lal/bin/python --compatibility off`
🍹 Building a mixed python/rust project
🔗 Found pyo3 bindings
🐍 Found CPython 3.11 at /tmp/build-env-ra719lal/bin/python
📡 Using build options features from pyproject.toml
   Compiling autocfg v1.1.0
   Compiling libc v0.2.153
   Compiling proc-macro2 v1.0.79
   Compiling cfg-if v1.0.0
   Compiling unicode-ident v1.0.12
   Compiling target-lexicon v0.12.14
   Compiling version_check v0.9.4
   Compiling once_cell v1.19.0
   Compiling ppv-lite86 v0.2.17
   Compiling ahash v0.8.11
   Compiling siphasher v0.3.11
   Compiling num-traits v0.2.18
   Compiling phf_shared v0.11.2
   Compiling libm v0.2.8
   Compiling zerocopy v0.7.32
   Compiling syn v1.0.109
   Compiling pyo3-build-config v0.19.2
   Compiling getrandom v0.2.12
   Compiling quote v1.0.35
   Compiling rand_core v0.6.4
   Compiling either v1.10.0
   Compiling hashbrown v0.14.3
   Compiling rand_chacha v0.3.1
   Compiling itertools v0.11.0
   Compiling rand v0.8.5
   Compiling ryu v1.0.17
   Compiling phf_generator v0.11.2
   Compiling phf_codegen v0.11.2
   Compiling unicode-width v0.1.11
   Compiling crunchy v0.2.2
   Compiling getopts v0.2.21
   Compiling malachite-base v0.4.5
   Compiling num-integer v0.1.46
   Compiling num-bigint v0.4.4
   Compiling anyhow v1.0.81
   Compiling log v0.4.21
   Compiling tiny-keccak v2.0.2
   Compiling paste v1.0.14
   Compiling unicode_names2_generator v1.2.2
   Compiling pyo3-ffi v0.19.2
   Compiling syn v2.0.53
   Compiling lock_api v0.4.11
   Compiling parking_lot_core v0.9.9
   Compiling unic-char-range v0.9.0
   Compiling unic-common v0.9.0
   Compiling memchr v2.7.1
   Compiling Inflector v0.11.4
   Compiling convert_case v0.4.0
   Compiling unicode_names2 v1.2.2
   Compiling rustpython-parser-vendored v0.3.1 (/tmp/build-via-sdist-_6kryhu2/rustpython_ast-0.0.1/local_dependencies/rustpython-parser-vendored)
   Compiling unic-ucd-version v0.9.0
   Compiling unic-char-property v0.9.0
   Compiling memoffset v0.9.0
   Compiling smallvec v1.13.2
   Compiling scopeguard v1.2.0
   Compiling derive_more v0.99.17
   Compiling rustpython-parser v0.3.1 (/tmp/build-via-sdist-_6kryhu2/rustpython_ast-0.0.1/local_dependencies/rustpython-parser)
   Compiling phf v0.11.2
   Compiling pyo3-macros-backend v0.19.2
   Compiling pyo3 v0.19.2
   Compiling malachite-nz v0.4.5
   Compiling is-macro v0.3.5
   Compiling static_assertions v1.1.0
   Compiling rustpython-parser-core v0.3.1 (/tmp/build-via-sdist-_6kryhu2/rustpython_ast-0.0.1/local_dependencies/rustpython-parser-core)
   Compiling parking_lot v0.12.1
   Compiling pyo3-macros v0.19.2
   Compiling unic-emoji-char v0.9.0
   Compiling unic-ucd-ident v0.9.0
   Compiling num-complex v0.4.5
   Compiling unindent v0.1.11
   Compiling lalrpop-util v0.20.2
   Compiling indoc v1.0.9
   Compiling rustc-hash v1.1.0
   Compiling malachite-q v0.4.5
   Compiling malachite v0.4.5
   Compiling malachite-bigint v0.2.0
   Compiling rustpython-ast v0.3.1 (/tmp/build-via-sdist-_6kryhu2/rustpython_ast-0.0.1/local_dependencies/rustpython-ast)
error[E0252]: the name `bigint` is defined multiple times
  --> local_dependencies/rustpython-ast/src/lib.rs:28:9
   |
26 | pub use malachite_bigint as bigint;
   |         -------------------------- previous import of the module `bigint` here
27 | #[cfg(feature = "num-bigint")]
28 | pub use num_bigint as bigint;
   |         ^^^^^^^^^^^^^^^^^^^^ `bigint` reimported here
   |
   = note: `bigint` must be defined only once in the type namespace of this module
help: you can use `as` to change the binding name of the import
   |
28 | pub use num_bigint as other_bigint;
   |         ~~~~~~~~~~~~~~~~~~~~~~~~~~

warning: unused import: `num_bigint as bigint`
  --> local_dependencies/rustpython-ast/src/lib.rs:28:9
   |
28 | pub use num_bigint as bigint;
   |         ^^^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(unused_imports)]` on by default

For more information about this error, try `rustc --explain E0252`.
warning: `rustpython-ast` (lib) generated 1 warning
error: could not compile `rustpython-ast` (lib) due to 1 previous error; 1 warning emitted
warning: build failed, waiting for other jobs to finish...
💥 maturin failed
  Caused by: Failed to build a native library through cargo
  Caused by: Cargo build finished with "exit status: 101": `PYO3_ENVIRONMENT_SIGNATURE="cpython-3.11-64bit" PYO3_PYTHON="/tmp/build-env-ra719lal/bin/python" PYTHON_SYS_EXECUTABLE="/tmp/build-env-ra719lal/bin/python" "cargo" "rustc" "--features" "pyo3/extension-module" "--message-format" "json-render-diagnostics" "--manifest-path" "/tmp/build-via-sdist-_6kryhu2/rustpython_ast-0.0.1/Cargo.toml" "--release" "--lib"`
Error: command ['maturin', 'pep517', 'build-wheel', '-i', '/tmp/build-env-ra719lal/bin/python', '--compatibility', 'off'] returned non-zero exit status 1

ERROR Backend subprocess exited when trying to invoke build_wheel

Any hint on how to fix that :slightly_smiling_face:?
As to why I'm trying to build it, well, I'd like to try it in a project of mine to see how well it performs and how much work it would need to use it instead of Python's ast.
Quick question by the way: it builds an Abstract Syntax Tree and not a Concrete Syntax Tree right?

Hi, welcome to ast pyo3 support. I usually built it with maturin, like maturin develop for dev version.
I am not very familiar with this ecosystem. Is pyo3 projects usually expected to be built with pyproject-build?

Weirdly enough if I use this command with maturin 1.5.1 directly, it works...
% maturin pep517 build-wheel --compatibility off
⚠  Warning: You specified maturin >=0.15, <0.16 in pyproject.toml under `build-system.requires`, but the current maturin version is 1.5.1
🍹 Building a mixed python/rust project
🔗 Found pyo3 bindings
🐍 Found CPython 3.11 at /home/pawamoy/.basher-packages/pyenv/pyenv/versions/3.11.5/bin/python3
📡 Using build options features from pyproject.toml
   Compiling rustpython-ast-pyo3 v0.0.1 (/media/data/dev/rustpython-parser/ast-pyo3)
    Finished release [optimized] target(s) in 7.03s
📦 Built wheel for CPython 3.11 to /media/data/dev/rustpython-parser/target/wheels/rustpython_ast-0.0.1-cp311-cp311-linux_x86_64.whl
/media/data/dev/rustpython-parser/target/wheels/rustpython_ast-0.0.1-cp311-cp311-linux_x86_64.whl

This crate now placed in https://github.com/RustPython/rustpython-ast-pyo3
This issue seems to be happened with parsers default bigint feature malachite. I fixed this issue in the new repository.

Thanks @youknowone, I'll try the new repository and report back :slightly_smiling_face:

Yay that worked! Thanks a lot!


algorithms_globals

Hello,
i am not being able to import algorithms_globals.
Any suggestions??

What version of qiskit do you have installed? What is the error you are getting - is it from code here or from your own code? Please provide more information.

The name is algorithm_globals not algorithms_globals. The installed qiskit-terra should be 0.17.0.
from qiskit.utils import algorithm_globals

Closing as answered. If however you still have an issue with this not working then feel free to re-open this, providing information and a small code sample etc

The issue was resolved. Thanks alot.
On Tue, Apr 13, 2021, 8:53 PM Steve Wood @.***> wrote:

Closing as answered. If however you still have an issue with this not
working then feel free to re-open this, providing information and a small
code sample etc
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Qiskit/qiskit-machine-learning/issues/39#issuecomment-818845988,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASAJKIOR2HA7LI4FES6ZAVTTIRSG5ANCNFSM42SUV5VA
.


Legend visible for non visible datasets when using min/max

Expected behavior
When I create a bar chart with multiple datasets, but limit the dataset by the x-axis min/max the legend of non visible items should not be visible, see for example https://stackblitz.com/edit/eng-1358-2-chartjs?file=index.ts
Current behavior
When I create a bar chart with multiple datasets, but limit the dataset by the x-axis min/max the legend of non visible items is visible, see for example https://stackblitz.com/edit/eng-1358-2-chartjs?file=index.ts
Reproducible sample
https://stackblitz.com/edit/eng-1358-2-chartjs?file=index.ts
Optional extra steps/info to reproduce
No response
Possible solution
No response
Context
No response
chart.js version
4.2.1
Browser name and version
Chrome 111
Link to your project
https://stackblitz.com/edit/eng-1358-2-chartjs?file=index.ts

You can use a custom generateLabels function for this
https://stackblitz.com/edit/eng-1358-2-chartjs-1fjhkk?file=index.ts


Expand the example with an Http dependant service

There seems to be a total lack of (working) examples on the internet on how to test a service which depends on Http. Since I guess 90% of the services depend on it, it would be a bit more of a real world example.
It would be awesome if it could be added to this repository, and the article on the website.

I'm want to make a "Part 2" of the article with updated examples and some advanced topics about testing.
Not sure when I can have it finished, because I'm pretty busy, but I will write one eventually.


feat: Support for multiple descriptions in TableMetadata

I changed TableMetadata to be able to hold multiple descriptions.
The problem we encountered was that adding programmatic descriptions will override the is_view field and for that reason we are losing information about views when adding programmatic descriptions.
Now that TableMetadata can hold multiple descriptions we can enrich the TableMetadata in a custom transformer and add the needed programatic descriptions without building extra table nodes.
For now I just created this as a PR Draft to get some feedback and discuss further.

hey, I don't quite get why is_view will get override? Also not sure how you get a programmatic description, but oftentimes it will get it through different sources which require different extractor for a different source.

also as long as table key is the same, it won't create a new table node right? For example at Lyft, we have the following cases:
source1 -> table1 with prog_desc_source1
source2 -> table1 with prog_desc_source2
we have one job per each source.

@feng-tao The is_view info is overridden with the following approach:
Lets say that I already imported my bigquery table metadata with the bigquery metadata extractor.
Now I have a csv file with a programmatic description that I want to add.
database,cluster,schema,name,description,tags,description_source
bigquery,test_project,test_schema,test_name,"content","tag","programmatic_source_field"

The csv file is missing is_view data that will default to False when the TableMetadata object is created
To load the data i create a Job with a CsvExtractor where
'extractor.csv.model_class':  ‘databuilder.models.table_metadata.TableMetadata’,

The new Table node will be published and the is_view field overridden. Maybe you are using publisher.neo4j.neo4j_create_only_nodes to mitigate this?
What are you thought on the scenario described above?

The second part is that I in some cases would like to do one or more programmatic field enrichment from a transformer.
A such transformer could look like this:
class ProgrammaticDescriptionEnricher(Transformer):

    def init(self, conf: ConfigTree) -> None:
        self.session = requests.Session()
        self.baseurl = 'http://custom-service:5000'

    def transform(self, record: Any) -> Any:
        tags = []
        desc = self._get_programmatic_description(record)
        if desc is not None:
            record.descriptions.append(desc)
        tags.append("team_b")
        if desc and len(desc._text) > 700:
            tags.append("team_b_long")
        record.tags += TableMetadata.format_tags(tags)
        return record

    def get_scope(self) -> str:
        return 'transformer.programmatic.markdown'

    def _get_programmatic_description(self, record):
        path = '/'.join([record.database, record.cluster,
                         record.schema, record.name])

        try:
            resp = self.session.get(f'{self.baseurl}/{path}')
            resp.raise_for_status()
            return DescriptionMetadata.create_description_metadata(
                text=resp.text,
                source="programmatic_description")
        except Exception:
            return None

The changes in this PR would allow for such transformers.

@feng-tao The is_view info is overridden with the following approach:
Lets say that I already imported my bigquery table metadata with the bigquery metadata extractor.
Now I have a csv file with a programmatic description that I want to add.
database,cluster,schema,name,description,tags,description_source
bigquery,test_project,test_schema,test_name,"content","tag","programmatic_source_field"

The csv file is missing is_view column/data that will default to False when the TableMetadata object is created
To load the data I create a Job with a CsvExtractor where
'extractor.csv.model_class':  ‘databuilder.models.table_metadata.TableMetadata’,

The new Table node will be published and the is_view field overridden. Maybe you are using publisher.neo4j.neo4j_create_only_nodes to mitigate this?
What are you thought on the scenario described above?
The second part is that I in some cases would like to do one or more programmatic field enrichment from a transformer.
A such transformer could look like this:
class ProgrammaticDescriptionEnricher(Transformer):

    def init(self, conf: ConfigTree) -> None:
        self.session = requests.Session()
        self.baseurl = 'http://custom-service:5000'

    def transform(self, record: Any) -> Any:
        tags = []
        desc = self._get_programmatic_description(record)
        if desc is not None:
            record.descriptions.append(desc)
        tags.append("team_b")
        if desc and len(desc._text) > 700:
            tags.append("team_b_long")
        record.tags += TableMetadata.format_tags(tags)
        return record

    def get_scope(self) -> str:
        return 'transformer.programmatic.markdown'

    def _get_programmatic_description(self, record):
        path = '/'.join([record.database, record.cluster,
                         record.schema, record.name])

        try:
            resp = self.session.get(f'{self.baseurl}/{path}')
            resp.raise_for_status()
            return DescriptionMetadata.create_description_metadata(
                text=resp.text,
                source="programmatic_description")
        except Exception:
            return None

The changes in this PR would allow for such transformers.

For the 1st part, why not change the csv to include the is_view information:
database,cluster,schema,name,description,tags,description_source,is_view
bigquery,test_project,test_schema,test_name,"content","tag","programmatic_source_field",True
?

@feng-tao sure if I had is_view data on the programmatic description source I would add it. But It is not normal to have that info when injecting programmatic descriptions from 3 party sources.

sorry for the late, seems reasonable. the change seems to be backward compatible?

@feng-tao I have found a way around this issue in my current code so I do not need it as of now. Still, it might be a good PR to merge if others are in the same position as I was. @Spacerat gave a thumbs up. Is it something you need.
I am good both going forward or closing until others have the same issue. @feng-tao what do you suggest?
If going forward is what we want to do I will make the PR ready for merge start next week.

let's revisit the ticket after then. Also if we merge https://github.com/amundsen-io/amundsendatabuilder/pull/396 , do we still need this pr?

@brunsgaard yep, I gave a thumbs up because I also have a use-case for multiple descriptions. We do have it working right now be emitting multiple TableMetadata objects, but it's awkward.
For me the reason it's awkward is that we have:

An Extractor which emits multiple TableMetadata objects per table (for multiple description support). The "main" object includes most of the metadata, and then additional TableMetadata objects just have the same identity and different descriptions, and no other data
Transforms which operate on those TableMetadata objects.

We ran into a bug, because we had written a transformer which produced tags based on column metadata, but forgotten that the extractor produces multiple metadata objects (with the latter not having any columns in it). That left us with a few options:

Emit all metadata in each copy of the TableMetadata object (seems kind of ugly?)
Write transformers to take into account the potential for multiple TableMetadata for the same table (awkward)
Run two separate ETL jobs, one for each kind of metadata (doubles the amount of work done)

We went with option 2 for now, but I think either this would be an improvement. However, I actually think an even better option could be to decouple descriptions from tables completely, and make TableDescription a primary model as part of the API. (but maybe that's already possible? I should look into it again)

I think we should close this PR when #396 is merged.

@brunsgaard why close this due to #396 ? Although I did use #369 as a part of a workaround for not having multiple table descriptions, I do feel like there needs to be better first class support for it. That being said, I'm ambivalent on whether I'd do it like this, versus a new public TableDescription model.

@brunsgaard why close this due to #396 ? Although I did use #369 as a part of a workaround for not having multiple table descriptions, I do feel like there needs to be better first class support for it. That being said, I'm ambivalent on whether I'd do it like this, versus a new public TableDescription model.

Heads-up: we're now in a code-freeze period as part of the monorepo transition. If you can get this landed in the next few days, I'll cleanly transfer it over to the new repo. If not, it'll need to be manually re-opened.


Failed to poll WAN IPv4 from router error (connect: connection refused)

Hey guys, my service stopped in the last days producing this error message:
cloudflare-dns-update    | 2024/07/26 20:21:13 WARN Failed to poll WAN IPv4 from router error="Post "http://fritz.box:49000/igdupnp/control/WANIPConn1\": dial tcp <IP_ADDRESS>:49000: connect: connection refused"
If I try to open the main fritzbox page from the server or from within the docker container (i.e. Login), I get a 404 error message. If I try the very same command from my Laptop, everything works.
I'm pretty sure that I had some similar issue a couple of years ago, when the fritzbox blocked my servers IP address. I just can't find anything on that and especially not how to unblock it.
Any ideas, thanks a lot!
P.S.: Restarted the container and the box, no change

The is a block list in
Internet > Filter > Listen > IP-Sperrlisten
Maybe that's the issue. I've never seen this issue before so I can't help much beyond that.

Closing this as this seems more on a configuration / network issue that I can't help with much more. It's not locked so anyone can still comment, but I want the issues to be nice and tidy.


Pause re-planning for x seconds when dynamic obstacle detected

Dear Christoph,
I was thinking of implementing a feature that would allow for the following feature:
Dynamic Obstacle get's in the path of the robot. Robot slows down and ultimately stops and waits for X seconds. After x seconds, if the obstacle hasn't moved away, the robot replans the path.
So essentially instead of an immediate re-planning, I would like to add some lag, since in many instances, the dynamic obstacle will move out of the way by itself and a dynamic re-planning with the other dynamic obstacle also re-planning course will lead to many re-plannings...
What are your thoughts on this? Where and how would you start with such a change?

Hi, I do not think the new version of teb_local_planner can solve the issue you given；Do you Continue to follow up on this issue?

Hi, has this feature been added/updated? How do I implement this?


Prevent isAuthenticated for non-compatible tokens

Updated isAuthenticated = false for non-compatible tokens

This does not solve any problem. The only thing I see you did here is combine 2 if statements into one, unless I am missing something?
Anyway, there was an open issue #590 which caused an error when you have a token that looks like a JWT, with 3 parts separated by dot, but is not a valid JWT. I submitted a fix in https://github.com/sahat/satellizer/commit/66beb2da5ccdc8dd1ab343b285b3fed8c9bcb340.

@sahat, it's not only 2 statements combination, but also return false, if not token.split('.').length === 3, since getPayload will fail anyway for not JWT compatible tokens. Please check it.

It is undesirable to return false if a token does not have 3 parts. If you are using implicit grant, where you just use access_token directly, it may or may not have 3 parts, and will likely fail isAuthenticated() check. There was a similar issue a few months ago where isAuthenticated() was failing because a token was not a valid JWT with 3 parts. Your PR will re-introduce that problem for those people that are not using storing JWT in local storage.
You did bring up a good point about getPayload(), however. That function should fail gracefully by returning undefined or null if token is not a valid JWT.


Implements #813 - Add option to panic in test.NewNullLogger

Add a field in Logger for Exit implementation which defaults to Exit().
This can be used in NullLogger() to replace calls to os.Exit() with panic()

Hi @caalberts, thanks for your contribution. There is something important which needs to be changed in order to be backward compatible if we want to merge this PR in a v1 release.
With this implementation, the static declaration of a logger like
log = &Logger{
      Out: os.Stderr,
      Formatter: new(JSONFormatter),
      Hooks: make(LevelHooks),
      Level: logrus.DebugLevel,
}

will be broken and execute a null pointer upon a Fatal call.
We could add instead a method Exit on Logger object which will then check the value of the Exit field and call appropriatly the default method if nil.

Yeah I see what you mean. I can see how having a Exit method on the logger object will keep backward compatibility.
To keep the handlers executed, this Exit method will execute handlers before the final exit, be it os.exit() or panic().
We still need to keep logrus.Exit function around though, because it is exported.

@dgsb Let me know if these changes are ok

@caalberts thanks for your contribution


.NET newest or standard

Do we need to update SukiUI to .net 8 or stuck with .net standard. Most developers seem to be using Avalonia based on .net 6-8 nowadays.
.net standard was the necessary cross-platform solution version prior to .net 5, and I'm not sure if there's still a need to use that version, although most class libraries still use it for compatibility.

Its probably a good idea, to follow somewhat closely the .NET versions supported by avalonia itself. Or in this case Avalonia for Desktop

It is indeed better to stay with .NET Standard 2.0.
But I had another non related thought about the version name, that maybe for next release we could jump directly to "11.1" to match AvaloniaUI version.


Confusing API of route.action

Current routing API as below is quite misleading, because React users think route.action accepts React Component, but actually doesn't.
const toplevelRoutes = Rocon.Path()
  .route("foo", (route) => route.action(() =>
This is foo
));

Suggestion
there's several options to solve this.

Add note to the Document on this page.
AFAIK, this behavior isn't mentioned nor warned in the document.
Or if it is, it should be more emphasized.
Add another API that will accept React Component.
Make route.action accept React Component
I'm not sure these options are possible since this library is designed not only for React.
Though adding some React friendly wrapper API that'll accept it and make React users use that API will be enough.
Detect it is React Component or not before or during runtime before react warns it
I don't think this is possible

@hikarinotomadoi
Thank you for reporting this!
We fixed this in v1.2.2. With that version, you can pass a React component as action.


Update BusinessProcessFlowAction.cs

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)

Description
The same class name "BusinessProcessFlowNextStageUCI" was creating ambiguous issues.
Changed the class name to "BusinessProcessFlowActionUCI" as the file name.
#1158 Previous Pull Request

Any update?


not found 'go' in openblockchain/baseimage

[root@luv fabric]# docker run --rm  openblockchain/baseimage:0.0.9 go
exec: "go": executable file not found in $PATH
docker: Error response from daemon: Container command not found or does not exist..

I'm not sure that the GOPATH in in $PATH in the base image. It is configured during the vagrant up process at https://github.com/hyperledger/fabric/blob/master/devenv/installGolang.sh#L37
@muralisrini Is this something the Go chaincode base image requires?

@ckeyer :  go is in "openblockchain/image" ...

Do you need go in 0.0.9 for any particular reason or are you just checking ?

thanks


[stable/chartmuseum] Fix README.md

What this PR does / why we need it:
Fix README.md
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

/lgtm


Downloaded files have random names!

It is possible to modify and improve this script to download videos from twitter with regular names like userID, tweet ID etc., for example: The filename pattern looks so: [twitter] {author}—{YYYY.MM.DD}—{id}—{filename}.{extension}.
This will be very helpful to make downloaded files well organised and save time, and it would make this tool more attractive and useful.

Hello! Thanks for your feedback - This will be definetely be considered.
I will think about a way to name the files that is short and conveniant.
I will hit you back soon!

Hello, I've implemented the current format:
TweetDL-${username}-${tweetId}.${extension};

Please drop me your feedback! If good, I will push an update soon.

Hello, I have replaced the dashes (-) with underscores (_). I've also fixed some extra stuff and I pushed the 1.0.4 update with file names. Please let me know how it goes!
You should receive an popup telling you to update soon.

Hello, I've noticed a strange underscore at the end of the filenames, I will resolve that now.

 I do find the magic you have done and updated for this tool, it really works well now!! Every video I download from Twitter has its name with userID, tweetID, thank you very much!!!!

I also got some good ideas to improve this tool which will make it Awesome, I do really hope I can contribute my efforts and work to your script, but I do not have a well-built and developed coding knowledge and skills like you, so I will try to use Copilot to assist

Hello, I've noticed a strange underscore at the end of the filenames, I will resolve that now. EDIT: Resolved with version 1.0.6

I will share my ideas to you here soon later

Hello and thank you for the kind words and support, I really appreciate it!
Side note, if you like this script and want something like that for YouTube, check out my brand new script: https://github.com/realcoloride/YoutubeDL
If you wish to suggest anything or report a problem, feel free to open an new issue.
If you feel like this issue has been resolved to you, feel free to close this issue.


Potential security issue in src/reflection.cpp: Unchecked return from initialization function

 What is a Conditionally Uninitialized Variable?  The return value of a function that is potentially used to initialize a local variable is not checked. Therefore, reading the local variable may result in undefined behavior.
2 instances of this defect were found in the following locations:
Instance 1
File : src/reflection.cpp
Function: $StringToNumber@N@flatbuffers
https://github.com/sagpant/flatbuffers/blob/cc44a4442716601600aa50fb8a42abd55294212c/src/reflection.cpp#L61
Code extract:
          reinterpret_cast<const String *>(ReadScalar<uoffset_t>(data) + data);
      if (s) {
        double d;
        StringToNumber(s->c_str(), &d); <------ HERE
        return d;
      } else {

How can I fix it?
Correct reference usage found in src/code_generators.cpp at line 186.
https://github.com/sagpant/flatbuffers/blob/cc44a4442716601600aa50fb8a42abd55294212c/src/code_generators.cpp#L186
Code extract:
    const FieldDef &field) const {
  const auto &constant = field.value.constant;
  T v;
  auto done = StringToNumber(constant.c_str(), &v); <------ HERE
  FLATBUFFERS_ASSERT(done);
  if (done) {

Instance 2
File : src/reflection.cpp
Function: $StringToNumber@N@flatbuffers
https://github.com/sagpant/flatbuffers/blob/cc44a4442716601600aa50fb8a42abd55294212c/src/reflection.cpp#L160
Code extract:
    case reflection::Float:
    case reflection::Double: {
      double d;
      StringToNumber(val, &d); <------ HERE
      SetAnyValueF(type, data, d);
      break;

How can I fix it?
Correct reference usage found in src/code_generators.cpp at line 186.
https://github.com/sagpant/flatbuffers/blob/cc44a4442716601600aa50fb8a42abd55294212c/src/code_generators.cpp#L186
Code extract:
    const FieldDef &field) const {
  const auto &constant = field.value.constant;
  T v;
  auto done = StringToNumber(constant.c_str(), &v); <------ HERE
  FLATBUFFERS_ASSERT(done);
  if (done) {

lgtm


Implement throttling

My provider has stiff brute force protections in place that this library easily bumps into. Anyway to implement some built in throttling? As a comparison, Pywikipediabot automatically slows things down.
Here is the type of policy I'm bumping into (which may be common across many providers):

An IP gets blocked for ten minutes if it accesses wp-login.php or xmlrpc.php more than 20 times in one minute.
If there are three such blocks in a three hour period, the IP is permanently blocked.

It appears that every call() is a new connection to xmlrpc.php, hence a mark against the threshold. If there was a way to count, and then if it hits 10 calls, automatically sleep for a minute.
Thoughts?

This could probably be implemented as a custom Transport implementation, but we should start by figuring out how it would work at a conceptual level.
From code that is consuming this library, what would the expected API or behavior be? That the whole thread gets put to sleep for minutes/hours after you hit a configurable throttle level? Or should it throw an exception and let the consumer figure out how it wants to wait (e.g., put a followup task in a message queue, or spawn another thread/process, or ...)?
Do you have links to documentation for pywikipediabot or other libraries that implement similar behavior?

This is what I wrote to implement a find-and-replace (slightly redacted):
#!/usr/bin/env python

import re

from wordpress_xmlrpc import Client
from wordpress_xmlrpc.methods import posts

from difflib import Differ
from pprint import pprint

import time

def process(client, post):
	#print "Analyzing %s..." % post
	if '<old>' in post.content:
		print "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
		print "!!! '%s' contains the pattern you seek!" % post.title
		update = re.sub('<old>', '<new>', post.content)
		print "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
		print "BEFORE: %s" % post.content
		print "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
		print "AFTER: %s" % update
		print "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"
		post.content = update
		if client.call(posts.EditPost(post.id, post)):
			print "!!!! SUCCESS!!!"
		print
	else:
		print "___ '%s' does NOT contain the pattern you seek" % post.title
		print

client = Client('<website>/xmlrpc.php', 'username', 'password')

offset = 0
increment = 10
while True:
	articles = client.call(posts.GetPosts({'number': increment, 'offset': offset}))
	if len(articles) == 0:
		break  # no more posts returned
	for article in articles:
		process(client, article)
	offset = offset + increment
	time.sleep(2) // <--- turns out, this wasn't enough throttling!

A link to up-to-date pywikibot (formerly pywikipediabot) is here =>
https://github.com/wikimedia/pywikibot-core/blob/master/pywikibot/throttle.py
Essentially, it encapsulates a lock. The lock is acquired, a timer to sleep run, and then the lock is released. I think the idea of routing any/all calls to ServerProxy through the throttle would then let you plugin different strategies. Perhaps default is to NOT throttle (backwards compatibility) at first. But...config options would let you plug in a policy, like counting and timing, to avoid exceeding an effective SLA?