Migrate: Error: Error in migration engine. Reason: [/rustc/c7087fe00d2ba919df1d813c040a5d47e43b0fe7/src/libcore/str/mod.rs:1920:47] byte index 1 is out of bounds of ``

Created on 10 Jul 2020  路  9Comments  路  Source: prisma/migrate

Command: prisma migrate save --experimental
Version: 2.2.0
Binary Version: 45c4da4dd3ccd6a322796b228bdf937c7ce884e8
Report: https://prisma-errors.netlify.app/report/8640
OS: x64 darwin 19.5.0

JS Stacktrace:

Error: Error in migration engine.
Reason: [/rustc/c7087fe00d2ba919df1d813c040a5d47e43b0fe7/src/libcore/str/mod.rs:1920:47] byte index 1 is out of bounds of ``

Please create an issue in the migrate repo with
your `schema.prisma` and the prisma command you tried to use 馃檹:
https://github.com/prisma/migrate/issues/new

    at ChildProcess.child.on (/Users/kaisky89/.nvm/versions/node/v10.21.0/lib/node_modules/@prisma/cli/build/index.js:2:2370192)
    at ChildProcess.emit (events.js:198:13)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)

Rust Stacktrace:

[/rustc/c7087fe00d2ba919df1d813c040a5d47e43b0fe7/src/libcore/str/mod.rs:1920:47] byte index 1 is out of bounds of ``
bu1-repro-available kinbug statuneeds-action

Most helpful comment

This is easily reproducible with this specific version of MariaDB.

All 9 comments

@divyenduz did you manage to reproduce that last week? I gave it a quick try, and I can't reproduce the crash.

I was also unable to reproduce this. We have missing migrations in the data collected:
image

So this is hard to reproduce imo. We also can't trace back the report to anyone so we are blind here.

Did you both try it with this specific version of MariaDB?
https://github.com/prisma/prisma/issues/3095#issuecomment-665596987

Nope, I tried it with whatever version I had installed. There is a lot going on this cycle for me, so I will try to find the time to try to reproduce this on the right version of MariaDB, but it's unlikely I will get to it very soon.

This is easily reproducible with this specific version of MariaDB.

This is easily reproducible with this specific version of MariaDB.

This information should be added to the original issue and issue title then.

This information should be added to the original issue and issue title then.

Someone else besides me needs to confirm that. Once that is done, we can change the title

I am unable to reproduce this with this docker image:

# Use root/example as user/password credentials
version: '3.1'

services:

  db:
    image: mariadb:10.1.36
    restart: always
    ports:
      - 3307:3306
    environment:
      MYSQL_ROOT_PASSWORD: root

image

Schema taken from the error report.

Prisma version used:

Environment variables loaded from prisma/.env
@prisma/cli          : 2.5.0-dev.9
Current platform     : darwin
Query Engine         : query-engine 8e4f3a5c140fa60e254d5ca37536c5991960dc7f (at node_modules/@prisma/cli/query-engine-darwin)
Migration Engine     : migration-engine-cli 8e4f3a5c140fa60e254d5ca37536c5991960dc7f (at node_modules/@prisma/cli/migration-engine-darwin)
Introspection Engine : introspection-core 8e4f3a5c140fa60e254d5ca37536c5991960dc7f (at node_modules/@prisma/cli/introspection-engine-darwin)
Format Binary        : prisma-fmt 8e4f3a5c140fa60e254d5ca37536c5991960dc7f (at node_modules/@prisma/cli/prisma-fmt-darwin)

(Edit: Also works fine with 2.4.1)

We recently implemented a fix for default value parsing on MySQL variants. Since then we cannot reproduce this anymore. I am closing this therefore.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

flybayer picture flybayer  路  3Comments

steebchen picture steebchen  路  3Comments

jwld picture jwld  路  3Comments

julien1619 picture julien1619  路  3Comments

ff-anthony-soto picture ff-anthony-soto  路  3Comments