All Issues
24,993 verified issues
Vercel deployment fails: serverless function exceeds 50MB with Prisma bundled per route
Deploying a Next.js 14 App Router application to Vercel fails because every serverless function that imports Prisma includes the full Prisma query engine binary, pushing each function over the 50MB unzipped limit. Prisma ships multiple platform-specific engine binaries and by default all are bundled. Setting binaryTargets to only rhel-openssl-3.0.x (the Vercel runtime) and using outputFileTracingExcludes reduces the size dramatically.
Prisma migration fails with "relation already exists" after partial run
A Prisma migration fails mid-way through execution (e.g. due to a constraint violation or connection drop). When you attempt to run the migration again, it fails with 'relation already exists' because some tables were created before the failure. The Prisma migrations table marks the migration as 'failed' but does not roll back the partial changes, leaving the database and migration history out of sync.
LLM response contains markdown code fences that break JSON.parse()
When prompting an LLM to return JSON, the model often wraps the output in markdown code fences (```json ... ```) even when explicitly told not to. Passing this raw response to JSON.parse() throws SyntaxError. This happens with GPT-4o, Claude, and Gemini — any model that has been fine-tuned to be "helpful" tends to add markdown formatting.
Chat participant API
We have finalized the Language Model and Chat Participant API 🚀 Thus, you can now publish your extensions to the VS Marketplace. This API is finalized in VS Code Insiders, and will be finalized in VS Code Stable in July. In your package.json, you should set [code block] and VS Code Stable will gracefully handle your extensions and ignore your usage of Language Model and Chat API until the API gets finalized in Stable in July. Full docs https://code.visualstudio.com/api/extension-guides/chat We are excited to see what you build ✨ --- -- Proposal dts: https://github.com/microsoft/vscode/blob/main/src/vscode-dts/vscode.proposed.chatParticipant.d.ts - Sample: https://github.com/microsoft/vscode-extension-samples/tree/main/chat-sample - Docs: https://code.visualstudio.com/api/extension-guides/chat Extension authors can subscribe to this issue to get updates about the proposed chat agent API. There may still be breaking changes coming, and I will post here whenever a breaking change is made. I'm also interested in feedback about how you might use this API. Current TODOs - [x] Need to enable agents to identify sessions uniquely and store state, including across a window reload - [x] Should be able to use `shouldRepopulate` for agents - Maybe this should be the default behavior for agents - [x] `ChatAgentReplyFollowup` should parameterize the agent and slash command names, don't require the agent to include them in the prompt as text - Maybe this goes for variables to
Recent increase in 'No matching activity' errors from `WebBrowser.openBrowserAsync()`
Summary An app in production since August 2020 that launches a web browser using `WebBrowser.openBrowserAsync()` is failing to do so without throwing 'No matching activity' errors on some Android devices, but with an increasing frequency during 2021 so far. It seems to be mostly affecting devices running Android 11 (a full list of device models is available). 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? Android SDK Version (managed workflow only) _No response_ Environment Expo CLI 3.28.5 environment info: System: OS: macOS 10.15.7 Shell: 5.7.1 - /bin/zsh Binaries: Node: 12.19.0 - /usr/local/bin/node npm: 6.14.11 - /usr/local/bin/npm Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2 IDEs: Xcode: 12.4/12D4e - /usr/bin/xcodebuild npmPackages: expo: ^37.0.0 => 37.0.12 react: 16.9.0 => 16.9.0 react-dom: 16.9.0 => 16.9.0 react-native: 0.61.4 => 0.61.4 react-native-web: ^0.11.7 => 0.11.7 react-navigation: ^4.0.10 => 4.4.0 npmGlobalPackages: expo-cli: 3.28.5 Expo Workflow: bare Reproducible demo or steps to reproduce from a blank project [code block] The issue above is occurring with increasing frequency on an app in production on Expo 37. I am aware of `We
Prisma Postgres Adapter with Turborepo does not work
Bug description if I have a `turborepo` monorepo with a `packages/db` folder containing my `prisma` schema, and a `apps/web` application (Next.JS) and I use the updated prisma with `previewFeatures = ["queryCompiler", "driverAdapters"]` I get an error: [code block] it is looking for `query_compiler_bg.wasm` at the `web` application but it should look for the same in the `db` package before you ask if I am creating a new PrismaClient inside the `web` application, I'm not, I'm only creating one prisma client in `db` package and exporting it, which is getting used in all other apps Severity 🚨 Critical: Data loss, app crash, security issue Reproduction Follow your guide to use `prisma` with `turborepo` and update the `index.ts` file to use the "Rust-free" version of Prisma ORM (using the `queryCompiler` and `adapters`), something you guys have mentioned here Expected vs. Actual Behavior let's call prisma with `previewFeatures = ["queryCompiler", "driverAdapters"]` to be `p1` and prisma without `previewFeatures = ["queryCompiler", "driverAdapters"]` to be `p2` I expect `p1` and `p2` to behave the same when I'm using them in a monorepo/turborepo Frequency Consistently reproducible Does this occur in development or production? Both development and production Is this a regression? if I directly use prisma without the `previewFeatures = ["queryCompiler", "driverAdapters"]`, it works Workaround as I said > if I directly use prisma without the `previewFeatures = ["q
"Flutter/Flutter.h not found." on iOS.
Steps to Reproduce Preface: I'm on the flutter `master` channel and have run `upgrade` half an hour ago. I've reinstalled flutter and cocoapods completely before and tried the fixes provided in #15437, #15532 and all other issues on GitHub looking like the problem I have. _ `flutter create --template=plugin -i swift health_stats` `cd health_stats/example` health_stats.zip Logs _Run your application with `flutter run` and attach all the log output._ [code block] _Run `flutter analyze` and attach any output of that command also._ [code block] Flutter Doctor _Paste the output of running `flutter doctor -v` here._ [code block] Additional information Creating and running a normal project works fine: `flutter create regular` `cd regular` `flutter run` [code block] However when adding a dependency like `path_provider`: [code block] and then `flutter packages get`, [code block] `flutter run` produces this: [code block] I did not have `path_provider` version `0.4.0` in my dart packages folder before running the app, so it's a fresh copy. I need to get this working a.s.a.p. since I need to make an app for our company soon.
DeleteResult / UpdateResult not implemented for all Drivers
Issue type: [ ] question [x] bug report [ ] feature request [ ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [ ] `mysql` / `mariadb` [ ] `oracle` [x] `postgres` [ ] `sqlite` [ ] `sqljs` [ ] `react-native` TypeORM version: [ ] `latest` [ ] `@next` [x] `0.2.7` (or put your version here) Steps to reproduce or a small repository showing the problem: 1. invoke `Repository.delete` 2. the returned `DeleteResult` does not include any info at all. Expecting to include the number of affected rows. I'm having trouble with `Repository.delete`: the operation successfully removes the entity from the database, but `DeleteResult` does not contain count of entities deleted, it's just `DeleteResult { raw: [] }`. This occurs with v0.2.7. Also, there doesn't appear to be a tag for version 0.2.7 on GitHub though there's a release on npmjs. Why is that? Why doesn't `DeleteResult` specify a property for the number of rows affected?
Disable New line at then end of file
Prettier 1.18.2 Playground link [code block] Input: [code block] Output: [code block] Expected behavior:
Next.js App Router dynamic [slug] routes return 404 on Vercel after deploy
Dynamic routes like /issue/[slug] and /user/[id] return 404 on Vercel in production even though they work fine locally. The routes exist in the file system and localhost serves them correctly. The issue is Next.js attempting to statically generate these pages at build time when the database isn't available, resulting in 404 fallbacks being deployed.
npm ci ERESOLVE peer dependency conflict after upgrading to Node.js 20
npm ci fails with ERESOLVE on Node.js 20 for a project that installed cleanly on Node.js 18. No changes were made to package.json. npm 10 (shipped with Node.js 20) uses stricter peer dependency resolution by default. Legacy packages with broad peer dependency ranges that were previously ignored now cause hard errors.
JSON-LD support?
I know GraphQL theoretically has no problem fetching data in JSON-LD format, but I'm wondering if there could be more 1st-class support for: - Schema validation - expansion/contraction - @embed, @link etc.
Support generation of signed URL's for S3 access
Support generation of signed URL's for S3 access
Android standalone app crashing on Android X
Hi expo team, I did update SDK yesterday. (35 to 36). Android build does not work on android x versions. The application gives error after splash screen. "Application keep stopping". and no error. I'm just getting unsafe lifecycle methods warning from GridList and Hyperlink packages. I uninstalled and tried these packages, but the problem persists. But there is a detail; The application opens smoothly on first installation. But if you close it through the task manager it won't open again. Expo CLI 3.11.1 environment info: System: OS: macOS 10.15.1 Shell: 5.7.1 - /bin/zsh Binaries: Node: 10.17.0 - /usr/local/opt/node@10/bin/node Yarn: 1.19.1 - /usr/local/bin/yarn npm: 6.11.3 - /usr/local/opt/node@10/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman IDEs: Android Studio: 3.5 AI-191.8026.42.35.5900203 Xcode: 11.1/11A1027 - /usr/bin/xcodebuild npmPackages: expo: ^36.0.0 => 36.0.0 react: 16.9.0 => 16.9.0 react-native: https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz => 0.61.4 react-navigation: ^4.0.10 => 4.0.10 npmGlobalPackages: expo-cli: 3.11.1
[BUG]: `createInsertSchema` from `drizzle-zod@0.6.1` does not infer types correctly but returns `unknown` for every value
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.3 What version of `drizzle-kit` are you using? 0.30.1 Other packages drizzle-zod@0.6.1,zod@3.24.1,typescript@5.7.2 Describe the Bug What is the undesired behavior? When using `createInsertSchema` provided by `drizzle-zod` to build a type-safe schema based on a table definition, it seems that the types are not properly inferred when the resulting schema is used to parse data. The keys in the resulting schema overlap with the table but all values are `unknown` (and optional). _Screenshot_ <img width="791" alt="example" src="https://github.com/user-attachments/assets/80a4a8de-5098-44a7-85a4-624bd95a099a" /> What are the steps to reproduce it? 1. Install packages with the following `package.json`: [code block] 2. Copy the example code from the docs. Slightly edited version below: [code block] 3. Launch editor and inspect types 🤓 What is the desired result? Ideally I'd like the types to be inferred properly "before" and "after" the use of `createInsertSchema` (and similar helpers) from `drizzle-zod` so that I can use the resulting schema (including specificed overwrites) for type-safe parsing of data.
bug: Cannot read properties of undefined (reading 'keyPrefix')
Provide environment information [code block] Describe the bug After upgrading to trpc 11.7.0 from trpc 11.6.0, our Next.js app crashes on the client-side with errror: [code block] Link to reproduction N/A To reproduce Upgrading to trpc 11.7.0 Additional information _No response_ 👨👧👦 Contributing - [ ] 🙋♂️ Yes, I'd be down to file a PR fixing this bug!
Please support python-rsa 4.0
This has been available (stable release) for a month now. Please can you test and bump your requirements? Thank you
Accessing env variables from index.html
Describe the bug I try to insert html tag by environment variable condition and use `vite-plugin-html` for it. But Vite behaviour is weird Reproduction https://github.com/xSorc/test-vite-index-env 1. This code works only in build [code block] During server i have this error [code block] 2. This code works only in dev server [code block] But during build this doesn't work, because Vite replace `process.env` with this: [code block] 3. The only option that works in both server and build is this: [code block] I suppose that first or second variant should works System Info Output of `npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers`: [code block] Used package manager: --- Before submitting the issue, please make sure you do the following - [x] Read the Contributing Guidelines. - [x] Read the docs. - [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. - [x] Provide a description in this issue that describes the bug. - [x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead. - [x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
Axios send the same request twice and ignore the first response, only receives the second response.
Describe the bug axios.post sends duplicate POST request and ignores the first response, only receives the second response. To Reproduce I don't know how to reproduce it since it's occurred. [code block] The submit function above is only called once, while the axios.post() is called twice. I have log for my system, in subject Additional context/Screenshots Expected behavior The request is only sent once. Environment: - Axios Version [e.g. 0.19.0] - OS: [e.g. Android 10; SM-G970U] - Browser [e.g. Chrome] - Browser Version [e.g. 80] - Additional Library Versions [e.g. React 16.8, redux 4.0.1 react-redux 7.1.0 redux-saga 1.0.3 ] Additional context/Screenshots <img width="1021" alt="Screen Shot 2563-03-17 at 12 26 08" src="https://user-images.githubusercontent.com/2849568/76825630-10b09580-684d-11ea-8b4e-2d28b5e5afd3.png"> You will see `request.query.t` for first and second time. it same requested.
Invalid file 'image': unsupported mimetype ('application/octet-stream'). Supported file formats are 'image/png'.
Confirm this is a Node library issue and not an underlying OpenAI API issue - [x] This is an issue with the Node library Describe the bug Since yesterday, a call to the "openai.images.edit" API throws an error: `BadRequestError: 400 Invalid file 'image': unsupported mimetype ('application/octet-stream'). Supported file formats are 'image/png'.` The same API call worked for that last year without this error. To Reproduce Provide to images, and set the filenames to patchFn and maskFn, both files are PNGs. Call the openai.images.edit API with the following code Code snippets [code block] OS macOS 15.4 Node version Node v22.14.0 Library version openai 4.95.0