All Issues
24,993 verified issues
"'node_modules/@prisma/client' has no exported member 'PrismaClient'." when using symlinks
error TS2305: Module '"../../node_modules/@prisma/client"' has no exported member 'PrismaClient'. import { PrismaClient } from '@prisma/client'; How to reproduce create a schema e.g. [code block] 1. Change DB name in prisma.schema to `dev-database.db` 2. `npm run prisma:migrate` 3. `npm run prisma;generate` all of these command are there in package.json script [code block] It was still referring to old database name. and I am not able to run any queries from code. I manually deleted node_modules/.prisma directory. again followed steps 2 and 3 Now I started seeing this problem: `error TS2305: Module '"../../node_modules/@prisma/client"' has no exported member 'PrismaClient'. import { PrismaClient } from '@prisma/client';` I checked the @prisma/client, .prisma directories present inside node_modules Expected behaviour 1.) after `prisma generate` new changes should automatically reflect in prisma client 2.) Should be able to import and use prisma client. Prisma information Environment & setup - OS: Debian Ubuntu 20.04 LTS - Database: SQLite - Prisma version: @prisma/cli : 2.0.0-beta.6 Current platform : debian-openssl-1.1.x - Node.js version: v14.2.0
Output collision when deploying a split service into the same bucket
Due to #9313, the name of the bucket where the deployment occurred is being exported by default. If a service is divided into multiple files deploying to the same bucket, the default outputs are gonna conflict with each other. <details> <summary><code>serverless_A.yml</code></summary> [code block] </details> <details> <summary><code>serverless_B.yml</code></summary> [code block] </details> <b>Installed version</b> [code block]
BackgroundFetch not running
Environment [code block] app's target - iOS, Standalone Steps to Reproduce 1. Allow background fetch in app.json [code block] 2. define a task in App.js [code block] 3. register task at some point of the apps running [code block] 4. set minimum interval for task in seconds `BackgroundFetch.setMinimumIntervalAsync(60);` Expected Behavior App should periodically call my server to log that the background task is running Actual Behavior Never see the background task run, although i do see the logs that show the background task was registered. The logging service i use has been used to show when location background task has run so this logging service should log if the task runs My main question is has anyone seen background fetch run? if so have i just configured it wrong?
Preview feature feedback: Prisma Migrate
Please share your feedback about the new Preview version of Prisma Migrate that was released in v2.13.0 in this issue. - If you encounter a bug, please open a bug report in this repo. - If the feature is working well for you, please share this in a comment below or leave a 👍 on this issue. If you have any questions, don't hesitate to ask them in the `#prisma-migrate` channel in the Prisma Slack.
unexplained disconnect 'transport end' after upgrading
After adding a dependency to my package.json today I removed my node_modules and ran npm_install. I didn't specify any version number for socket.io so I guess it picked up the latest. After I did that I noticed that within ? a minute or so of starting up my application, my socket would be disconnected and I see a 'transport end' info message in the node.js console output. I having socket.io set for websockets only. I am on Chrome 13 on Linux. I went into package.json and set it at 0.8.7, ran npm install again, and now I am not seeing disconnects anymore. Hopefully I wasn't just confused about something. I did go back and repeat the steps and had the same result. Sorry I don't have more specific information.
Default uWebSocket Engine in 2.0.1 causing 100% CPU spin on server
I want to: [x] report a bug [ ] request a feature Current behaviour Version 2.0.1 exhibits a problem for me when using the default engine: uWebSockets, pushing the Node.js server process into 100% CPU Steps to reproduce (if the current behaviour is a bug) I get the problem consistently if I have an application running in the browser with a web-socket connection in place. I then reload the application in the browser (which forces the old socket to be removed and a new one put in place). At this point the server goes into a spinning loop, eating 100% of the CPU. Replacing the engine with "ws" fixes the issue. Setup - OS: Ubuntu 16.04 - browser: Chrome 57 - socket.io version: 2.0.1 Other information (e.g. stacktraces, related issues, suggestions how to fix) Here's what node debug reports when I pause during 100% CPU utilisation: ubuntu@ip-172-30-1-57:~/qewd$ node debug localhost:7000 connecting to localhost:7000 ... ok debug> pause break in node_modules/uws/uws.js:8 6 const DEFAULT_PAYLOAD_LIMIT = 16777216; 7 > 8 function noop() {} 9 10 function abortConnection(socket, code, name) { debug> It appears to be stuck in a loop calling this function
Feedback on v16.0.0-rc.1
Can you please test your lib/project against https://github.com/graphql/graphql-js/releases/tag/v16.0.0-rc.1 and leave feedback on this issue.
ECR get-login-password for docker login yields 400 bad request
Confirm by changing [ ] to [x] below to ensure that it's a bug: - [x] I've gone though the User Guide and the API reference - [x] I've searched for previous similar issues and didn't find any solution Describe the bug I want to login into ECR in us-west-2, because I would like to pull the aws-iam-authenticator image, ie `docker pull 602401143452.dkr.ecr.us-west-2.amazonaws.com/amazon/aws-iam-authenticator:v0.5.0-alpine-3.7`. The docker login instructions on the release page are out of date. I followed the instructions in the AWS CLI get-login-password, but I get HTTP error code 400 back from the server. SDK version number [code block] Platform/OS/Hardware/Device What are you running the cli on? [code block] To Reproduce (observed behavior) [code block] Expected behavior I should be logged in, but I am not Logs/output [code block] Additional context I have found that I can successfully docker login to region us-east-1, but I cannot login to us-west-2. I need to login to us-west-2, so I can pull `602401143452.dkr.ecr.us-west-2.amazonaws.com/amazon/aws-iam-authenticator:v0.5.0-alpine-3.7`. I looked over the status of ECR for us-west-2 and it's not reporting any issues.
@prisma/engines weights 113 MB and causes maximum size limit error on Vercel
Bug description When I try to deploy a Next.js + GraphQL + Prisma application on Vercel I receive an error about exceeding the lambda function limit. [code block] Full log here: https://gist.github.com/talentlessguy/74f58664cd5af05407037be15b3b25a1 How to reproduce 1. Create a new Next.js project with these files: https://gist.github.com/talentlessguy/9cac915be4fa6a1ea911c7f0ead5fa2b Expected behavior I expected a Next.js app to build and launch as it usually does (it did run fine 1-2 weeks ago) Prisma information Schema: https://gist.github.com/talentlessguy/9cac915be4fa6a1ea911c7f0ead5fa2b#file-graphql_schema-ts Environment & setup - OS: Vercel Linux runtime - Database: PostgreSQL - Node.js version: 14.16 - Prisma version: 2.22.0 [code block]
[BUG] Fix IPv6 records for npm
Is there an existing issue for this? - [X] I have searched the existing issues - - #4085 (probably the same) This issue exists in the latest npm version - [X] I am using the latest npm Current Behavior I'm trying to install `natural` package, but npm freezes in `sill idealTree buildDeps` (Not the same behavior as #3257, so I suppose it's another bug). After some minutes it returns `ETIMEDOUT`. Expected Behavior npm should install the package (it's also unable to update npm itself). Steps To Reproduce 1. Start a empty project 2. Run `npm i [any package]` 4. See error similar to this: [code block] Environment - npm: `7.19.1` (OK), `8.0.0` (Not OK), `8.1.4` (Not OK), `8.3.0` (Not OK) - Node: `17.0.1`, `17.2.0` (npm `8.1.4`) - OS: Ubuntu 21.10 - platform: Intel X64 Notebook - npm config: [code block]
[unimodules][android][notifications] Event listener can miss `emit()` calls made soon after app launch
🐛 Bug Report Summary of Issue If you call `Notifications.addResponseReceivedListener` in `useEffect` for example, the listener will not be triggered when opening an app from a completely killed state via a notification. This can also be demonstrated by adding a timeout to `componentDidMount` as shown here. Without 1 second timeout- events come through; with 1 second timeout- event's do not come through. I should note that the emit method is getting called in this case. Environment - output of `expo diagnostics` & the platform(s) you're targeting Reproducible Demo https://snack.expo.io/@charliecruzan/push-notifications Steps to Reproduce Need to run the app as a published experience or standalone app (or bare debug build) to see the behavior. Press "show notification" and kill the app, tap the notification, observe that response listener isn't triggered. Workaround The workaround (and possibly long-term solution) is to add the listener outside of any component, then it works as expected (presumably bc of how much sooner it's getting called?). I changed the docs to suggest this so fewer people run into this issue
s3 sync/ls issues UnicodeWarning in Windows environment
What steps will reproduce the problem? 1. Log in to Windows(default language is non English(confirmed on Japanese)) 2. Run `aws s3 ls s3:://bucketname/ What is the expected output? What do you see instead? You will encounter `UnicodeWarning` as follows; [code block] What version of the product are you using? [code block] Additional information below. This is not a bug of aws-cli per se and is already reported to python-dateutils. https://bugs.launchpad.net/dateutil/+bug/1227221 But you encounter this warning every time you issue s3 commands, so it's a bit annoying.(`awscli` users are not always (Python) developers, right?) Working around this warning would be appreciated. (When releasing `awscli`, suppressing warning with `python -W ignore::UnicodeWarning` is one option) FYI, this warning also appears in #95(Which occurred in `argparse` module)
tailwind 3 doesn't work with storybook/webpack setup
I'm using macOS, Chrome v96, Node.js 16 I created a github repository with this exact issue - https://github.com/sachinmour/tailwind-issue Basically just do `yarn` and `yarn storybook` and you'll see storybook loaded correctly. change package.json to use tailwind `^3.0.0` and run `yarn` and `yarn storybook` again and you'll see no tailwind is loaded inside storybook.
Allow System Prompt Within Messages As Opposed to Top Level Argument
Most LLM providers (including OpenAI sdk) support "system" as a role within the `messages` argument. allowing `messages` to support this would make it much easier for developers to switch/use your models.
LeanDocument Type doesn't include _id or id
*Do you want to request a feature or report a bug? Report a bug What is the current behavior? I believe that the types defined here are incorrect: https://github.com/Automattic/mongoose/blob/c22152c5a95c5ce9ed688d96b37b05c7df6be1ec/types/index.d.ts#L2261-L2267 This says that `LeanDocuments` (that is documents returned from `.toObject()` or when using the `lean` option don't have the `_id` or `id` fields. I don't think this is correct. This issue only presented itself in version 6.3.2 and wasn't present in 6.3.1 If the current behavior is a bug, please provide the steps to reproduce. [code block] What is the expected behavior? `_id` and `id` are present on LeanDocuments (I think...) What are the versions of Node.js, Mongoose and MongoDB you are using? Note that "latest" is not a version.* Node.js: v16.15.0 TypeScript: v4.6.2 mongoose: v6.3.2
Functions not working with streaming
Describe the bug I have streaming working well with this library. I am trying to add a call to a function, but the response does not include the required arguments. The model recognizes that it wants to use the function, and the part.choices[0].finish_reason contains the value of "function_call" But the function name nor the argument is included in the response. Here is what is in the part.choices: choices: [ { index: 0, delta: {}, finish_reason: 'function_call' } ] I was expecting to see the function name and the args in delta. To Reproduce 1. Create a function 2. Define the function as part of the chat.completions.create command 3. Set stream: true on the command 4. Loop through the chunks 5. When the function is requested by the model, the name and args are not included in the chunk. Code snippets _No response_ OS Linux Node version Node v18.12.1 Library version openai-node 4.0.0-beta.1
Introspection fails to generate `@relation` for many-to-many relation in MySQL
Newer reproduction here: https://github.com/prisma/prisma/issues/14668#issuecomment-1755468605 --- Bug description Introspection (`db pull`) fails to generate `@relation` for relations between tables, that are using compound keys. How to reproduce 1. Create schema from SQL bellow 2. run `npx prisma db pull` 3. See error in relation between tables Expected behavior The resulting schema should create `@relation` with the correct fields. Generated: [code block] Correct: [code block] Prisma information [code block] Environment & setup - OS: Windows - Database: MySQL - Node.js version: v16.13.2 Prisma Version [code block] Extracted from https://github.com/prisma/prisma/issues/14648#issuecomment-1205224365
Error when trying to connect to db.
Prerequisites - [x] I have written a descriptive issue title Mongoose version 6.6.0 Node.js version 18.x MongoDB version 5.0.12 Operating system Windows Operating system version (i.e. 20.04, 11.3, 10) 10 Issue So when I try to connect to my db I have an error [code block] link that I use to connect is [code block] And yes, I have a correct username and password. My IP is allowed too.
HNSWLib-node not found when using in a AWS Lambda function
I recently made a simple Typescript function to create a VectorStore using HNSWLib-node. It saves the vector store in a folder and then, in another script file, I load and execute a RetrievalQAChain using OpenAI. Everything was working fine until I decided to put that in a AWS Lambda Function. My package.json has the following dependencies: [code block] Also, I double checked and the hnswlib-node folder is inside "node_modules" folder in my lambda function folder. However, I keep getting the following error (from CloudWatch Logs): [code block] Also, this error is not thrown on importing HNSWLib, but only in the following line of code: [code block] This is my import: `const { HNSWLib } = require("langchain/vectorstores/hnswlib")` It seems I'm not the only one with this problem. See this post Tried this and didn't work. Expeted behavior: code would be executed properly, just like when executed on my local machine. Actual behavior: the error pasted above.
Upgrading to expo@44.0.0 breaks iOS build of amazon-cognito-identity-js
Summary I use `amazon-cognito-identity-js@5.1.0` in my project as well as `expo`. I tried upgrading to `expo@44.0.0`, but the iOS build then fails with a lot of errors, e.g: [code block]` Build log is attached: expo-44-build-error.txt This build error does not occur with `expo@43.0.3` Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare! bare What platform(s) does this occur on? iOS SDK Version (managed workflow only) _No response_ Environment [code block]` Reproducible demo I created a minimal reproducer here: https://github.com/schiller-manuel/expo-issue The project was created using these steps: 1. `npx react-native init ExpoIssue --template react-native-template-typescript` 2. `npm install amazon-cognito-identity-js && npx pod-install` 3. `npx install-expo-modules` Run `npm run ios` to reproduce the build errors.