Error when migrating mariadb database during the latest upgrade to 2.6.9
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
Empieza reproduciendo la migración de docker-compose contra la configuración de MariaDB indicada e inspeccionando la migración fallida Application\Migrations\Version20190806130304. Rastrea por qué la columna language rechaza los datos de las filas existentes; se considera terminado cuando la migración se completa correctamente sin truncamiento.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
I'm unable to login to the wallabag after an update. I ran the database migration command (the one for docker-compose) but I get the following error during the update. Looks like something is unusual about my database that is tripping the migration. Any advice?
[notice] Migrating up to Application\Migrations\Version20230613121354
[notice] Migration Application\Migrations\Version20160401000000 skipped during Execution. Reason: "Database already initialized"
[notice] Migration Application\Migrations\Version20170327194233 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170405182620 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170407200919 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170501115751 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170511115400 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170602075214 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170606155640 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20170824113337 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20171105202000 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20171120163128 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20171125164500 skipped during Execution. Reason: "It seems that you already played this migration."
[notice] Migration Application\Migrations\Version20190619093534 skipped during Execution. Reason: "Migration can only be executed safely on 'sqlite'."
[error] Migration Application\Migrations\Version20190806130304 failed during Execution. Error: "An exception occurred while executing a query: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631"
01:25:22 CRITICAL [console] Error thrown while running command "doctrine:migrations:migrate --env=prod --no-interaction". Message: "An exception occurred while executing a query: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631" ["exception" => Doctrine\DBAL\Exception\DriverException^ { …},"command" => "doctrine:migrations:migrate --env=prod --no-interaction","message" => "An exception occurred while executing a query: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631"]
In ExceptionConverter.php line 117:
An exception occurred while executing a query: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631
In Exception.php line 28:
SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631
In Connection.php line 71:
SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'language' at row 631
Here is my docker-compose:
version: '3'
services:
wallabag:
image: wallabag/wallabag
container_name: wallabag
restart: unless-stopped
environment:
- MYSQL_ROOT_PASSWORD=[rootpassword]
- SYMFONY__ENV__DATABASE_DRIVER=pdo_mysql
- SYMFONY__ENV__DATABASE_HOST=db
- SYMFONY__ENV__DATABASE_PORT=3306
- SYMFONY__ENV__DATABASE_NAME=wallabag
- SYMFONY__ENV__DATABASE_USER=wallabag
- SYMFONY__ENV__DATABASE_PASSWORD=[password]
- SYMFONY__ENV__DATABASE_CHARSET=utf8mb4
- SYMFONY__ENV__DATABASE_TABLE_PREFIX="wallabag_"
- SYMFONY__ENV__MAILER_HOST=127.0.0.1
- SYMFONY__ENV__MAILER_USER=[email_address]
- SYMFONY__ENV__MAILER_PASSWORD=[password]
- SYMFONY__ENV__FROM_EMAIL=wallabag@domain
- SYMFONY__ENV__DOMAIN_NAME=https://myurl
#- SYMFONY__ENV__DOMAIN_NAME=
ports:
- "8090:80"
volumes:
- /home/mford6/config/wallabag/images:/var/www/wallabag/web/assets/images
healthcheck:
test: ["CMD", "wget" ,"--no-verbose", "--tries=1", "--spider", "http://localhost/api/info"]
interval: 1m
timeout: 3s
depends_on:
- db
- redis
db:
image: mariadb:latest
container_name: mariadb
environment:
- MYSQL_ROOT_PASSWORD=[rootpassword]
volumes:
- /home/mford6/config/wallabag/data:/var/lib/mysql
restart: unless-stopped
healthcheck:
#test: ["CMD", "mysqladmin" ,"ping", "-h", "localhost"]
##test: ["CMD", "mariadb-admin" ,"ping", "-h", "localhost", "--password=[password]"]
##interval: 20s
##timeout: 3s
test: ["CMD", "/usr/local/bin/healthcheck.sh" ,"--innodb_initialized"]
- Lenguaje dominante
- Shell
- Estrellas
- 771
- Forks
- 168
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de wallabag/docker
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 3/5 1-2 días Aptitud para principiantes 57/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
-
Awaiting response
Dificultad 4/5 3-5 días Aptitud para principiantes 32/100
Todos los issues de wallabag/docker
Issues similares
-
source:reader type:enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
stephrobert/blog-roadmap#115 ·
-
Python Volcengine provider returns failures instead of raising themPosiblemente ocupada @Ricardo-M-L la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
agent-infra/sandbox#248 ·
-
chore priority:low size:S
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
celo-org/celopedia-skills#98 ·
Los mantenedores suelen responder en 1 día
-
Git for Windows shouldn't be locked on their `.windows.1` versionsPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertogit windows
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
jenkins-infra/packer-images#3179 ·
Los mantenedores suelen responder en 1 día
-
ready-for-pr
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
kunchenguid/firstmate#7679 · 1 comentario ·
Los mantenedores suelen responder en 1 día