All Issues
24,993 verified issues
Preview feature feedback: Prisma Client Extensions
Please share your feedback about Prisma Client Extensions released in v4.7.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-client channel in the Prisma Slack.
Using await within emit causes payload to be sent to all connected clients
You want to: [x] report a bug [ ] request a feature Current behaviour Using `async/await` to construct payloads results in a race condition and messages potentially being broadcast to all connections. Steps to reproduce Fiddle: https://github.com/tommoor/socket.io-fiddle/tree/async-await-critical-issue TLDR: Using `await` within the payload construction for `emit` will cause the message to be sent to all connections instead of the specific room. eg: [code block] Expected behaviour Data should be sent to the correct room and not leaked to all clients. Setup - OS: All - browser: All - socket.io version: 2.2.0
Deploy stops at "Installing dependencies for custom CloudFormation resources"
I´m using this template https://github.com/msfidelis/serverless-architecture-boilerplate and the issue has only occured with this template so far. Creating new projects from scratch with the sls assistent and deploying works fine. When running sls deploy it processes these 3 steps and then stops [code block] Running deploy with --verbose --force does not change anything and there are literally no additional exceptions or log messages thrown which makes it very hard to find the source of this issue. Serverless v: 1.50.0 OS: Windows 10
[BUG]: drizzle-kit push stuck at "Pulling schema from database..." / not detecting "dialect"
What version of `drizzle-orm` are you using? 0.31.2 What version of `drizzle-kit` are you using? 0.22.8 Describe the Bug I have a setup that connects to a Supabase Postgres database. When I run `npx drizzle-kit push` it hangs at "Pulling schema from database...": When I run `npx drizzle-kit push --verbose` I get this error: [code block]
Error resolving plugin [id: 'com.facebook.react.settings']
Minimal reproducible example https://github.com/BraveEvidence/SampleExpo What platform(s) does this occur on? Android Where did you reproduce the issue? in a development build Summary I created a simple Expo Project using `npx create-expo-app@latest --template blank-typescript`, I need to write native android code so I did following `npx expo install expo-dev-client` `npx expo run:android` `npx create-expo-module@latest --local` I have the necessary Android Setup on my Mac like Android Studio, Java etc When I open the android folder in Android Studio I get following error during gradle sync. I have not written a single line of code [code block] Environment [code block] Expo Doctor Diagnostics [code block]
`supabase.auth.api.getUserByCookie()` doesn't work in Next.JS server-side environment
Bug report Describe the bug `supabase.auth.api.getUserByCookie()` doesn't work in Next.JS server-side environment (`_middleware.ts`) To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: 1. Create a supabase project 2. Create a Next.JS project 3. Create Add following code to `_middleware.ts` [code block] 4. See logs [code block] Expected behavior getUserByCookie() should either work (use `fetch()` internally instead of `XMLHttpRequest`), OR message should be more clear (check the presence of `XMLHttpRequest` in `getUserByCookie()` and throw `Sorry, you shouldn't call this method in server side environment` System information Next version is `12.0.1` Additional context Add any other context about the problem here.
RangeError: Maximum call stack size exceeded
I am just calling `ìo.sockets.emit('hey', data);``and it will crash with``RangeError: Maximum call stack size exceeded``. I use it in other places in my app and it works fine. I am not repeating this (checked with console). The logs say the error is in``socket.io/node_modules/has-binary-data/index.js:46``. I dont know where the problem is. I tried logging `io.sockets` right before using it and it outputs this: [code block] My code is: [code block] JAVASCRIPT if (game.scoreTeamTwo > game.scoreTeamOne && game.scoreTeamTwo > game.scoreTeamThree && game.scoreTeamTwo > game.scoreTeamFour) { game.winner = 2; io.sockets.emit('CTFEnd', game); } //It´s just looking if team 1 won the game and when it does is emits [code block]` and all the other game data [code block]
Incorrect Typescript types on MessageInstance
Issue Summary The `MessageInstance` class looks as if it contains incorrect types for some of its instance properties. Properties such as `errorCode` and `errorMessage` can be nullable according to the documentation so I would think that the type of `errorCode` should be `number | null` rather than simply `number` as it currently is. Props types that seem incorrect: - `errorCode`: should be `number | null` rather than `number` - `errorMessage`: should be `string | null` rather than `string` - `price`: should be `string | null` rather than `string` - `priceUnit`: should be `string | null` rather than `string` - `messagingServiceSid`: should be `string | null` rather than `string` (From the docs: "The SID of the Messaging Service used with the message. The value is null if a Messaging Service was not used.") Code Snippet Compare the type of the instance property `errorCode` here [code block] to the sample JSON response in the documentation: [code block] Exception/Log [code block] Technical details: twilio-node version: `v3.49.0` node version: `12.8.3`
Multiple sockets open after reconnect
I've noticed this both on my socket.io application and someone else's. When a reconnect occurs, it's common for more than one socket within a client to be open, which should never happen. Here's a log I got from my own test application when I had a disconnect/reconnect. *\ Disconnect *\ Reconnecting with delay 1000 Attempts: 1 *\ Reconnecting with delay 2000 Attempts: 2 *\ Connecting with xhr-polling *\ Connecting with xhr-polling *\ Reconnect with transport type xhr-polling Attempts: 2 *\ Connected *\ Connected When this happens, I get duplicate messages sent, one for each connected socket, even though there should only be one. It is confirmed by Firebug that there are, in fact, two sockets from the client connected. My best guess is that this is in the client code, perhaps not closing the first reconnection attempt. Of course, the real question might be why was there a disconnect in the first place?
Model.find() is not returning all documents
With a particular model, I have ~120 documents. When I run model.find({}, function(err, list) {…}); some documents for that model are not returned. If I add a clause to the query, I can make it return certain matching documents that are not returned with an empty query. The problem can also occur when I specify a query parameter that matches many documents (one or two are missing from the returned results). I'm curious if others have experienced this problem and how they fixed it. Is it a mongoose issue, the mongo native module, or mongodb itself? What did others do to fix it? I am running mongoose 1.3.7 and mongodb 1.8.1 on Ubuntu Linux.
11000 E11000 duplicate key error index: dbName.users.$_id_ dup key: { : ObjectId('5469eb08370fea375383e2d3')}
I am trying to save an an array of objects into a db using `db.collection.insert` but I am getting this error: [code block] I've tried dropping the database and reinserting but of no use. Also, no document with such id is present in the collection earlier.
Drive download returning token JSON object
Hello, I'm having a problem downloading from the Drive using this API (v3). The data returned from the API is of the form: [code block] My code is roughly as follows (parts ommited due to confidentiality reasons): [code block] auth is an object created using a derivation of this example: https://developers.google.com/drive/v3/web/quickstart/nodejs#step_3_set_up_the_sample Am I doing something wrong, or has the API changed somehow?
Bug: MobX-like observer pattern doesn't work with Fast Refresh because Hooks don't get detected
React version: 17.0.0 Steps To Reproduce 1. https://codesandbox.io/s/react-refresh-webpack-plugin-rendered-more-hooks-than-during-the-previous-render-issue-ezcrz?file=/src/Comp.js 2. Delete one of the hooks there Link to code example: https://codesandbox.io/s/react-refresh-webpack-plugin-rendered-more-hooks-than-during-the-previous-render-issue-ezcrz?file=/src/Comp.js The current behavior You get "Rendered more hooks than during the previous render" error The expected behavior Should hot reload and re-mount the component. The source of the issue have two parts: 1. react-refresh and the bundler fails to inject signature to the component 2. When no signature apparent, `react-refresh` consider the components as compatible, which is not always true, as in the repro https://github.com/facebook/react/blob/9aca239f11f31109dc1a229aa1571c2bf02f5524/packages/react-refresh/src/ReactFreshRuntime.js#L126-L132 I've filed an issue also for the webpack plugin: https://github.com/pmmmwh/react-refresh-webpack-plugin/issues/266 Mobx related issue: https://github.com/mobxjs/mobx/issues/2668
[JIT]: JIT not working properly. like flex classes (next js)
What version of Tailwind CSS are you using? v2.1.1 What build tool (or framework if it abstracts the build tool) are you using? next.js 10.1.3 What version of Node.js are you using? v14.15.1 What browser are you using? Firefox, Chrome What operating system are you using? macOS Reproduction repository https://github.com/MuttakinHasib/tealeaf Describe your issue JIT not working properly... when i use classs like w-20 or flex classes its not working properly @adamwathan can you check my repo ? is it bug or i missed something ?
[AppCheck] Firestore stops working after leaving the website idle overnight - AppCheck HTTP error 403 (appCheck/fetch-status-error) + infinite loop / high CPU usage
AppCheck problem AppCheck works fine and enforced. However, after leaving the webapp idle for a while (e.g., if I leave the tab open and go to sleep and put the laptop to sleep, then come to work the next day), Firestore stops working (as if it gets disconnected and doesn't reconnect or refresh AppCheck token). Console error observed in production: `@firebase/app-check: FirebaseError: AppCheck: Fetch server returned an HTTP error status. HTTP status: 403. (appCheck/fetch-status-error).` Console error observed on localhost: `zone.js:1061 Unhandled Promise rejection: cancelled ; Zone: <root> ; Task: Promise.then ; Value: cancelled undefined` Environment Angular version: 14.0.2 (latest) Firebase SDK version: 9.8.3 (latest) AngularFire version: 7.4.1 (latest) Firebase Product: AppCheck
[docs] No native ExpoFirebaseCore module found with firebase-recaptcha
[https://docs.expo.io/versions/latest/sdk/firebase-recaptcha/] I followed the steps described in this doc to set up the phone auth but ran into the issue of "ExpoFirebaseCore module not found, are you sure the expo-firebase-core module is linked properly?" I installed the expo-firebase-core package too but still ran into this error. How to fix it?
ETIMEDOUT connecting to AWS Elasticache (non-cluster)
Trying to connect to an AWS Elasticache instance and running in to this problem. Verifying that Redis connection works from EC2 instance; [code block] Connecting like this: [code block] Recieving ETIMEDOUT error when connection through `ioredis`; [code block] Timeouts continue indefinitely like above. Out of ideas with this one so if anyone could help I would really appreciate it.
Prisma Memory Leak when using in NestJS app, reported by Jest
Bug description In our (closed source) project, we added a lot of test for a new feature. That resulted in memory problems in our ci. We found, that Prisma is might be one of the problems. I created a minimal reproduction https://github.com/adrian-goe/prisma-nestjs-memory-leak-repoduction There is one test without using prisma app.controller.spec.ts and one using prisma app-prisma.controller.spec.ts running both test with `node --expose-gc` and `jest --detectLeaks` results in jest finding memory leaks in the test with prisma. It might be possible, that this leaks also happens while running the application, but I didn't test that. It could be possible, that this is a nestJs problem as well, but we ware only be able to reproduce this with Prisma, but no other dependency or module. How to reproduce https://github.com/adrian-goe/prisma-nestjs-memory-leak-repoduction Expected behavior _No response_ Prisma information see https://github.com/adrian-goe/prisma-nestjs-memory-leak-repoduction Environment & setup - OS: [macOS, Windows, Debian] might be more - Database: [PostgreSQL] only tested with postgres - Node.js version: v16.18.0 Prisma Version [code block] In our internal project, this was also an issue with Prisma 4.1.1
Fails to nmake on PostgreSQL 17 RC1 [Windows]
Tried installing pgvector on my new PostgreSQL 17 RC1. It fails to install on Windows when doing nmake: [code block] Works fine using PostgreSQL 16
"synchronize" option removing data from the database
Issue type: [ ] question [] bug report [ ] feature request [ ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [] `mysql` / `mariadb` [ ] `oracle` [ ] `postgres` [ ] `sqlite` [ ] `sqljs` [ ] `react-native` [ ] `expo` TypeORM version: [*] `latest` [ ] `@next` [ ] `0.x.x` (or put your version here) Steps to reproduce or a small repository showing the problem: when i enable "synchronize" option, it constantly changing my database data in very specific table and specific data, its changing the "Accounts" entity, changing the "company" field to empty string and the "active" column to 0 where the id is 1 so my database looks like this: id | company | active 1 | blabla | 1 transformed into this on every change: id | company | active 1 | | 0 This is my account entity: [code block] and this is the ormconfig: [code block]