Bug description
Report ID: 11391
I've installed Prisma in a repo and tried running introspect, but I'm being met with the following error
yarn run v1.22.5
$ cross-env DEBUG="*" yarn prisma introspect
$ G:\Code\Projects\NewValkyrja\Valkyrja.web\node_modules\.bin\prisma introspect
Environment variables loaded from prisma\.env
Introspecting based on datasource defined in prisma\schema.prisma …
IntrospectionEngine:rpc starting introspection engine with binary: G:\Code\Projects\NewValkyrja\Valkyrja.web\node_modules\@prisma\cli\introspection-engine-windows.exe +0ms
IntrospectionEngine:rpc SENDING RPC CALL {"id":1,"jsonrpc":"2.0","method":"introspect","params":[{"schema":"// This is your Prisma schema file,\n// learn more about it in the docs: https://pris.ly/d/prisma-schema\n\ndatasource db {\n provider = \"mysql\"\n url = env(\"DATABASE_URL\")\n}\n\ngenerator client {\n provider = \"prisma-client-js\"\n}\n"}]} +11ms
IntrospectionEngine:stderr {"is_panic":true,"message":"[src\\libcore\\str\\mod.rs:2200:5] begin <= end (1 <= 0) when slicing `1`","backtrace":" 0: <unknown>\n 1: <unknown>\n 2: <unknown>\n 3: <unknown>\n 4: <unknown>\n 5: <unknown>\n 6: <unknown>\n 7: <unknown>\n 8: <unknown>\n 9: <unknown>\n 10: <unknown>\n 11: <unknown>\n 12: <unknown>\n 13: <unknown>\n 14: <unknown>\n 15: <unknown>\n 16: <unknown>\n 17: <unknown>\n 18: <unknown>\n 19: <unknown>\n 20: <unknown>\n 21: <unknown>\n 22: <unknown>\n 23: <unknown>\n 24: <unknown>\n 25: <unknown>\n 26: <unknown>\n 27: <unknown>\n 28: <unknown>\n 29: <unknown>\n 30: <unknown>\n 31: <unknown>\n 32: <unknown>\n 33: <unknown>\n 34: BaseThreadInitThunk\n 35: RtlUserThreadStart\n"} +0ms
Oops, an unexpected error occured!
[src\libcore\str\mod.rs:2200:5] begin <= end (1 <= 0) when slicing `1`
How to reproduce
- Run
prisma introspect
- See error
Expected behavior
Introspection works
Prisma information
I've setup prisma.schema as follows
datasource db {
provider = "mysql"
url = env("DATABASE_URL")
}
generator client {
provider = "prisma-client-js"
}
with env
DATABASE_URL="mysql://root@localhost:3306/valkyrja"
Environment & setup
- OS: Windows 10 Pro Version 10.0.19041 Build 19041
- Database: MariaDB 10.5.5
- Node.js version: v12.14.1
- Prisma version:
$ prisma version
Environment variables loaded from prisma\.env
@prisma/cli : 2.7.1
Current platform : windows
Query Engine : query-engine 5c2ad460cf4fe8c9330e6640b266c046542c8b6a (at node_modules\@prisma\cli\query-engine-windows.exe)
Migration Engine : migration-engine-cli 5c2ad460cf4fe8c9330e6640b266c046542c8b6a (at node_modules\@prisma\cli\migration-engine-windows.exe)
Introspection Engine : introspection-core 5c2ad460cf4fe8c9330e6640b266c046542c8b6a (at node_modules\@prisma\cli\introspection-engine-windows.exe)
Format Binary : prisma-fmt 5c2ad460cf4fe8c9330e6640b266c046542c8b6a (at node_modules\@prisma\cli\prisma-fmt-windows.exe)
Studio : 0.288.0
Done in 1.10s.
Bug description
Report ID: 11391
I've installed Prisma in a repo and tried running introspect, but I'm being met with the following error
How to reproduce
prisma introspectExpected behavior
Introspection works
Prisma information
I've setup
prisma.schemaas followswith env
Environment & setup