All Issues
24,993 verified issues
VS Code Remote SSH drops connection every few minutes on macOS Sonoma
VS Code Remote SSH connections drop every 3–10 minutes with 'Connection to server closed' on macOS Sonoma. The issue started after upgrading macOS. macOS Sonoma introduced more aggressive network connection management that closes idle TCP connections. SSH connections without keepalive packets are silently terminated by the OS networking stack.
Custom max-width for container
I need to tweak max-width for each `.container` breakpoints. In fact, I would prefer to use these: Class | Breakpoint | Properties -- | -- | -- |.container | None | width: 100%; ||sm (640px) | max-width: 600px; ||md (768px) | max-width: 700px; ||lg (1024px) | max-width: 800px; ||xl (1280px) | max-width: 900px; But I couldn't find a way to achieve that using `tailwind.config.js`.
bind mount (volumes) not allowed for files – only directorys
hey, trying to mount a single file (instead of a directory) throws an error: Cannot start container bc0f924401841f2ed92c088cb8089cadad2359126b9f6a3ff15b6cb657835fb0: setup mount namespace bind mounts mounting /etc/eb8/freeIPA/server/etc/krb5.conf into /var/lib/docker/btrfs/subvolumes/bc0f924401841f2ed92c088cb8089cadad2359126b9f6a3ff15b6cb657835fb0/etc/krb5.conf not a directory it's allowed in docker!!! fig.yml [code block]
0.3 generic findOneBy typescript error
Issue Description With the upgrade to the new syntax in 0.3 there is a typescript issue with using `findOneBy` on a generic repro. [code block] Expected Behavior The code above should compile fine, no issues Actual Behavior I get the following typescript error. [code block] - ✖️ Yes, I have the time, and I know how to start. - ✅Yes, I have the time, but I don't know how to start. I would need guidance. - ✖️ No, I don’t have the time, but I can support (using donations) development. - ✖️ No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.
Cannot upload file within FormData
Describe the bug After upgrading from 0.24.0 to 0.25.0 File Form upload breaks. To Reproduce Original working on 0.24.0 code. [code block] This code was working previously, but now backend cannot extract file field. After specifying content type: [code block] I got an error on backend "bad content-type header, no multipart boundary" Expected behavior Seems like previous version of axios (0.24.0) automatically add correct header and also boundary. Or was there any breaking change that I didn't notice? Environment - Axios Version [0.25.0] - Node.js Version [16.0.0] - Additional Library Versions [formidable 2.0.1, React-Native 0.66.4] Additional context/Screenshots Not needed.
CORS Errors after updating to 2.2.0
You want to: [x] report a bug [ ] request a feature Current behaviour Getting lots of CORS errors after the latest update. Steps to reproduce (if the current behaviour is a bug) Repo. See README for instructions. Expected behaviour No CORS errors. Setup - OS: Mac - browser: Chrome 70 - socket.io version: 2.2.0 Other information (e.g. stacktraces, related issues, suggestions how to fix) @davericher made a comment here indicating this. Perhaps he has more details.
[0.75][0.76] HAS FIX - React Native Android Build error - `zip END header not found` - INDIA Only
IMPORTANT > [!IMPORTANT] > The latest official update on this issue is available here Description When i run my react native app in debug mode which is already running without errors using npx react-native run-android command then suddenly it gives gradle build running error like below screenshot and description from today in all pc. My Configurations react-native: 0.76.1 gradle-wrapper version: gradle-8.10.2 [code block] please help me to solve this error!! Steps to reproduce 1. clone reproducer i have given or change configurations given by me in project 2. run yarn android(react-native run-android) 3. gradle plugin error occurs React Native Version 0.76.1 Affected Platforms Runtime - Android, Build - MacOS Output of `npx react-native info` [code block] Stacktrace or Logs [code block] Reproducer https://github.com/kush-scs/reproducer-gradle-build Screenshots and Videos
Using environment vars in job returns in empty strings
I'm trying to build a reusable workflow that dynamically picks the runner depending on the job environment. I'm triggering the job with a workflow dispatch with environment as an input, setting the environment of a job as "environment: ${{ inputs.environment }}" (but even if i hard code the environment it wont work). But the problem I have seems to be a bug with using environment vars at the job level. For example ${{ vars.MY_VAR }} always returns an empty string. Unless I add the variable as a repository variable instead of an environment variable. If I am to echo out ${{ vars.MY_VAR }} inside a step, the variable is there, but not when I'm trying to configure a job. To Reproduce Follow the example from the documentation. https://docs.github.com/en/actions/learn-github-actions/contexts#vars-context Setting a workflow environment variable works fine. But setting for example the job name or runs-on in a job would result in an empty string. Echoing the vars in a step works fine. Expected behavior Using vars.RUNNER (as in the example) would set the runner configured for that environment in the repository settings. Found some similar reports on this but not quite. Have been trying out different workarounds and gone through the documentation a few times now but none will work.
Prisma generate randomly fails on Ubuntu due to missing internal .so `libquery_engine-debian-openssl-1.1.x.so.node`
Bug description Here is my package.json in the root of my repo: [code block] I have two database packages with `prisma-generate` scripts that look like so: [code block] In my GitHub actions, when I run `pnpm install`, I randomly (and only sometimes) get the following error: [code block] How to reproduce See above. Can't consistently reproduce Expected behavior No errors Prisma information See above Environment & setup - OS: `runs-on: ubuntu-latest` from my GH action - Database: PostgreSQL - Node.js version: `18.12.1` Prisma Version [code block]
OpenAI API 429 rate limit despite low request count — TPM limit reached, not RPM
The OpenAI API returns 429 errors even when request count is well below the documented requests-per-minute (RPM) limit. The actual limit being hit is tokens-per-minute (TPM). A single GPT-4o request can consume 4,000+ tokens, so 50 concurrent requests easily exceeds the TPM budget even though only 50 RPM are used. The error message mentions the RPM limit but the real constraint is TPM.
Production websites using Next.js
Hi all, I'm compiling a list of production applications built in Next.js so we can feature them in the 2.0 announcement. Please do share yours :smile: Related to #727 List: - zeit.co - npm - scaleapi - tutorbro - project r - platzi music - skys limo - rainbow.now.sh - upsum news - bigfive.world - open-source.now.sh - ritoplz - goot.now.sh - opencollective - avocode
Intermittent Error: write EPIPE when running stripe client in AWS Lambda
We're using the stripe node client 8.71.0 on an AWS Lambda running node 12.x. A stripe customers.list call is called first thing when the lambda executes. 33% of the time - we get this error on that call. It consistently happens so does not seem to be transient. I did read https://github.com/stripe/stripe-node/issues/650, and setting maxNetworkRetries in stripe to 2 seems to resolve the issue. However it seems that just masks the issue. Is this a stripe issue or AWS Lambda issue? Probably lambda, I submitted a request with AWS. But putting this here in case others run into it. 2020-10-13T12:02:58.032Z c184006d-fe96-490a-9bfe-696b8271769a ERROR StripeConnectionError: An error occurred with our connection to Stripe. at /var/task/node_modules/stripe/lib/StripeResource.js:234:9 at ClientRequest.<anonymous> (/var/task/node_modules/stripe/lib/StripeResource.js:489:67) at ClientRequest.emit (events.js:315:20) at ClientRequest.EventEmitter.emit (domain.js:483:12) at TLSSocket.socketErrorListener (_http_client.js:426:9) at TLSSocket.emit (events.js:315:20) at TLSSocket.EventEmitter.emit (domain.js:483:12) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) { type: 'StripeConnectionError', raw: { message: 'An error occurred with our connection to Stripe.', detail: Error: write EPIPE at WriteWrap.o
Migration generate drops/creates all constraints
Issue type: [ ] question [x ] bug report [ ] feature request [ ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [ ] `mysql` / `mariadb` [ ] `oracle` [x] `postgres` [ ] `sqlite` [ ] `sqljs` [ ] `websql` TypeORM version: [ ] `latest` [x] `@next` [ ] `0.x.x` (or put your version here) On an existing database in PostgreSQL 9.6.2 migration generation wants to drop all unique constraints and create them again. I ran this migration however it wants to do it on the next generate as well. The only thing I can tell(without digging into the code) is that the order in [code block] is backwards on the columns in the SQL statement..
Provide precompiled binaries for NixOS
Original issue https://github.com/prisma/prisma/issues/2305 Read the instructions how to use Prisma with nix
🐞 [BUG] "npm ERR! cb() never called!" or "Exit handler never called"
\Updated\ as of 01/15/2021 Note: Please read this doc-never-called%3F-Exit-handler-never-called%3F-I'm-having-the-same-problem!%22) before filing a new issue.
[BUG] Cannot set property 'peer' of null
Is there an existing issue for this? - [X] I have searched the existing issues This issue exists in the latest npm version - [X] I am using the latest npm Current Behavior I can only hit this particular error in a certain directory with a certain package, but I can reproduce it over several npm versions and it's 100% of the time. There are more examples available in #3711 (the author refuses to reopen the bug even though it is not fixed and people are hitting it!). After having a working npm for years and not changing the config, I just ran into it on npm v8.1.4. Upgraded to v8.5.4 and the problem did not go away. Here's the log with the latest version (8.12.1): [code block] I redacted the user and package name as they are company internals. I use a company artifactory with npm registry. However, this has worked for me before and is working for thousands of our developers as we speak, so I think it's a local problem with my npm. Expected Behavior `npm i <package>` installs the package successfully Steps To Reproduce 1. In this environment... 2. With this config... 3. Run '...' 4. See error... Environment - npm: v8.12.1 - Node.js: v17.2.0 - OS Name: Windows 10 x64 - npm config: [code block]
[BUG]: The inferred type of X cannot be named without a reference to ../../../../../node_modules/drizzle-zod/schema.types.internal.mjs
Report hasn't been filed before. - [X] I have verified that the bug I'm about to report hasn't been filed before. What version of `drizzle-orm` are you using? 0.38.0 What version of `drizzle-kit` are you using? 0.30.0 Other packages drizzle-zod@0.6.0 Describe the Bug Since the latest update, all previously working drizzle-zod functions show a type error. `The inferred type of updateUserProfileSchema cannot be named without a reference to ../../../../../node_modules/drizzle-zod/schema.types.internal.mjs` <img width="1154" alt="image" src="https://github.com/user-attachments/assets/98380270-b2d3-4e8a-9577-fd01b6e9f129"> <img width="1140" alt="image" src="https://github.com/user-attachments/assets/94a9a4e4-466f-4c1d-8945-3932a2a6955b"> Node.js v22.10.0 Bun v1.1.38 Turborepo v2.3.3 Workaround is disabling declaration and declarationMap in tsconfig.json: [code block]
[BUG]: "Please install `postgres`to allow Drizzle ORM to connect to the database" 0.35.0
What version of `drizzle-orm` are you using? 0.35.0 What version of `drizzle-kit` are you using? 0.26.1 Describe the Bug Since updating from 0.34.x to 0.35.0, I'm getting the following error when building my app: [code block] But postgres (postgres-js) is already installed. A sample code that triggers the error for me: [code block] My drizzle.config.json file: [code block] I have cleared the node_modules and my Nuxt output and built everything from scratch, but error is still there. Reverting to 0.34.1 fixes the problem for now. Expected behavior _No response_ Environment & setup - MacBook Pro M1 running MacOS Sequoia - Node 22
MongoDB analytics active user count always 0 when country filter applied
An analytics dashboard shows correct total active user counts but returns 0 when filtering by country. The query uses `{ _id: { $in: userIds }, _id: { $in: countryUserIds } }` — a JavaScript object with two identical `_id` keys. The second key overwrites the first, so only the country filter is applied, but the country user list includes all user types (drivers, admins), not just the user type being counted.
Redis connection pool exhausted: new client created per request in serverless
The application returns 'ECONNREFUSED' or 'max number of clients reached' errors under moderate load. The root cause is creating a new ioredis client inside each API route handler or Lambda function invocation. Each new client opens a fresh TCP connection to Redis. In serverless environments with high concurrency, dozens of connections are opened simultaneously, exhausting the Redis server's client limit.