thread 'tokio-runtime-worker' panicked at 'not yet implemented'
See original GitHub issueBug description
thread 'tokio-runtime-worker' panicked at 'not yet implemented', query-engine\connectors\mongodb-query-connector\src\logger.rs:160:31
stack backtrace:
0: 0x7ffcdc31e4af - napi_register_module_v1
1: 0x7ffcdc33fe7a - rust_eh_personality
2: 0x7ffcdc315bd8 - napi_register_module_v1
3: 0x7ffcdc3212db - napi_register_module_v1
4: 0x7ffcdc320dd4 - napi_register_module_v1
5: 0x7ffcdb1a0a30 - <unknown>
6: 0x7ffcdc321896 - napi_register_module_v1
7: 0x7ffcdc32166f - napi_register_module_v1
8: 0x7ffcdc31edf7 - napi_register_module_v1
9: 0x7ffcdc321399 - napi_register_module_v1
10: 0x7ffcdc4cf3a0 - rust_eh_personality
11: 0x7ffcdc4cf2ec - rust_eh_personality
12: 0x7ffcdb675623 - napi_register_module_v1
13: 0x7ffcdb674a40 - napi_register_module_v1
14: 0x7ffcdb6757a4 - napi_register_module_v1
15: 0x7ffcdb55eb40 - napi_register_module_v1
16: 0x7ffcdb5c24f5 - napi_register_module_v1
17: 0x7ffcdb2be665 - napi_register_module_v1
18: 0x7ffcdb2e72f1 - napi_register_module_v1
19: 0x7ffcdb2e2dd0 - napi_register_module_v1
20: 0x7ffcdb2facb6 - napi_register_module_v1
21: 0x7ffcdb13e9cb - <unknown>
22: 0x7ffcdb125ce6 - <unknown>
23: 0x7ffcdb15836a - <unknown>
24: 0x7ffcdb135575 - <unknown>
25: 0x7ffcdb12b7f1 - <unknown>
26: 0x7ffcdb12485f - <unknown>
27: 0x7ffcdb131af3 - <unknown>
28: 0x7ffcdb158fe2 - <unknown>
29: 0x7ffcdb14540b - <unknown>
30: 0x7ffcdb1f6a76 - napi_register_module_v1
31: 0x7ffcdb0dd746 - <unknown>
32: 0x7ffcdb0d31ae - <unknown>
33: 0x7ffcdc20c4cf - napi_register_module_v1
34: 0x7ffcdc211e97 - napi_register_module_v1
35: 0x7ffcdc210c7f - napi_register_module_v1
36: 0x7ffcdc2183d8 - napi_register_module_v1
37: 0x7ffcdc21066a - napi_register_module_v1
38: 0x7ffcdc222d6f - napi_register_module_v1
39: 0x7ffcdc216444 - napi_register_module_v1
40: 0x7ffcdc20cae6 - napi_register_module_v1
41: 0x7ffcdc21b440 - napi_register_module_v1
42: 0x7ffcdc227816 - napi_register_module_v1
43: 0x7ffcdc219745 - napi_register_module_v1
44: 0x7ffcdc2172e3 - napi_register_module_v1
45: 0x7ffcdc32b8dc - napi_register_module_v1
46: 0x7ffd3c8f7034 - BaseThreadInitThunk
47: 0x7ffd3cec2651 - RtlUserThreadStart
F:\_RaccoonsCode\Konan\node_modules\@prisma\client\runtime\index.js:45582
throw new PrismaClientUnknownRequestError(message, this.client._clientVersion);
^
PrismaClientUnknownRequestError:
Invalid `prisma.user.create()` invocation in
F:\_RaccoonsCode\Konan\test.ts:6:33
3
4 (async () => {
5 console.log(await prisma.$connect());
→ 6 console.log(await prisma.user.create(
not yet implemented
at Object.request (F:\_RaccoonsCode\Konan\node_modules\@prisma\client\runtime\index.js:45582:15)
at async PrismaClient._request (F:\_RaccoonsCode\Konan\node_modules\@prisma\client\runtime\index.js:46405:18) {
clientVersion: '3.12.0'
}
error Command failed with exit code 1.
How to reproduce
import { PrismaClient } from '@prisma/client';
import 'dotenv/config';
const prisma = new PrismaClient();
(async () => {
console.log(await prisma.$connect());
console.log(await prisma.user.create({
data: {
id: '1',
},
}));
})();
Expected behavior
No response
Prisma information
// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema
generator client {
provider = "prisma-client-js"
}
datasource db {
provider = "mongodb"
url = env("DATABASE_URL")
}
model User {
ObjectId String @id @default(auto()) @map("_id") @db.ObjectId
createdAt DateTime @default(now()) @db.Timestamp
id String @unique
premium DateTime? @db.Timestamp
guilds Guild[]
backups Backup[]
}
model Guild {
ObjectId String @id @default(auto()) @map("_id") @db.ObjectId
createdAt DateTime @default(now()) @db.Timestamp
id String @unique
User User @relation(fields: [userId], references: [id], onDelete: Cascade, onUpdate: Cascade)
userId String
backups Backup[]
}
model Backup {
ObjectId String @id @default(auto()) @map("_id") @db.ObjectId
createdAt DateTime @default(now()) @db.Timestamp
id String @unique
data Json
premium Boolean?
Guild Guild @relation(fields: [guildId], references: [id], onDelete: Cascade, onUpdate: Cascade)
guildId String
User User @relation(fields: [userId], references: [id], onDelete: Cascade, onUpdate: Cascade)
userId String
}
Environment & setup
- OS: Windows 10
- Database: MongoDB
- Node.js version: 16.14.0
Prisma Version
prisma : 3.12.0
@prisma/client : 3.12.0
Current platform : windows
Query Engine (Node-API) : libquery-engine 22b822189f46ef0dc5c5b503368d1bee01213980 (at node_modules\@prisma\engines\query_engine-windows.dll.node)
Migration Engine : migration-engine-cli 22b822189f46ef0dc5c5b503368d1bee01213980 (at node_modules\@prisma\engines\migration-engine-windows.exe)Introspection Engine : introspection-core 22b822189f46ef0dc5c5b503368d1bee01213980 (at node_modules\@prisma\engines\introspection-engine-windows.exe)
Format Binary : prisma-fmt 22b822189f46ef0dc5c5b503368d1bee01213980 (at node_modules\@prisma\engines\prisma-fmt-windows.exe)
Default Engines Hash : 22b822189f46ef0dc5c5b503368d1bee01213980
Studio : 0.459.0
Issue Analytics
- State:
- Created a year ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Thread 'tokio-runtime-worker' - help - Rust Users Forum
Why I'm getting this bug on the tokio runtime? thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: ...
Read more >Why do I get "panicked at 'not currently running on the Tokio ...
It looks like Elasticsearch's crate is using Tokio internally, so you must use it too to match their assumptions.
Read more >Runtime in tokio::runtime - Rust - Docs.rs
The Tokio runtime implements Sync and Send to allow you to wrap it in a Arc . Most fn take &self to allow...
Read more >Thread 'tokio-runtime-worker' panicked - Radicle Community
thread 'tokio-runtime-worker' panicked at 'error binding to 0.0.0.0:80: error creating server listener: Permission denied (os error 13)', ...
Read more >Thread 'tokio-runtime-worker' panicked at 'Storage root must ...
try and purge-chain and re-sync from scratch. make sure you have bumped your spec_version after upgrading. if in doubt, use --execution Wasm to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The solution I found is using version 3.10.0 of the prisma and @prisma/client packages
In the next 24 hours.
If you need to continue in the meantime, you can use the
prisma@dev
and@prisma/client@dev
packages temporarily.