Highlights
- 3 discussions answered
Pinned
571 contributions in the last year
Contribution activity
June 2022
Created 6 commits in 2 repositories
Created a pull request in prisma/prisma that received 12 comments
chore: drop Node.js 12 and modernize the toolchain
Stop testing on Node.js 12, start testing on Node.js 18 (i.e., test on Node.js 14, 16, and 18). Before the changes: After the changes: Update…
+86
−103
•
12
comments
Opened 3 other pull requests in 3 repositories
prisma/ecosystem-tests
1
open
prisma/prisma
1
open
prisma/engines-wrapper
1
open
Reviewed 14 pull requests in 2 repositories
prisma/prisma
12 pull requests
- test(client): Opt Out Of Providers
- fix(client): allow prisma.empty to $executeRaw
- fix(engine-core): Fix race conditon during panic in BinaryEngine
- fix dev version detect (failing ecosystem tests)
- test/refactor(client): add missing helpers
- fix(engine-core): Correctly report panics within LibraryEngine
- chore(*): polishing upstream work on the data proxy [DPGA, 5]
- chore(test): Add scaffolding for new functional tests
-
chore(cli, client): check that
prisma://cannot be used with unsupported commands [DPGA, 4] - chore(client, cli): implement --data-proxy [DPGA, 1]
- chore(client): fix isolated data proxy issues [DPGA, 3]
- chore(client): split the runtime into two [DPGA, 2]
prisma/ecosystem-tests
2 pull requests
Created an issue in prisma/prisma that received 2 comments
Triggering a panic makes the client unusable if the exception is handled in user code
See this comment: #10586 (comment) I can reproduce that the client becomes unusable after the panic if I catch the error in user code outside Prism…
2
comments