All Issues
24,993 verified issues
Preview feature feedback: Prisma tracing (`tracing`)
Please share your feedback about the `tracing` functionality released in v4.2.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.
UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Hi since yesterday I've been running into this error while doing `docker-compose up` Full Error Message [code block] Docker Version Docker for Mac: 1.12.0-a (Build 11213) Machine info MacBook Air (13-inch, Early 2015) Processor: 1.6 GHz i5 Memory: 4GB 1600 MHz DDR3 macOS: Version 10.11.6 (Build 15G1004) Attempts - Everything still works on colleagues' machine, they are using MacBook Pro - Increased Docker CPU from 2 to 3, and 2GB RAM to 3GB, still error - Removed All Docker containers & images, and rebuild everything, still error
Retry logic for OpenAI timeouts
I'm seeing the following error in prod: [code block] It's getting captured in my catch block, so I'm fairly sure the retries aren't happening, unless the first attempt is the one that gets re-thrown or something confusing like that. Is it possible this doesn't meet the criteria for retryable? Could this be addressed using the FailedAttemptHandler interface? I've not set a timeout for the LLM. I'm having a hard time figuring out the default value. [code block]
Support for Asynchronous Virtual
I'd like to express some virtual properties that perform asynchronous work, such as inspecting other Mongoose models. It would be nice if the virtual getters and setters accepted an optional done function that would be invoked after the async work completed.
[Help] Google Drive export example not working
I have the code from the drive export example with the sampleClient and it's producing an error. (node:3593) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'on' of undefined [code block]
Getting ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined
We are getting `Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in langchain\package.json ` It started happening from versions 0.0.13 and up. It works fine for 0.0.12.
Expo Facebook returns cancel with native IOS facebook app on successful login
🐛 Bug Report Environment Expo CLI 2.20.2 environment info: System: OS: macOS 10.14.5 Shell: 5.3 - /bin/zsh Binaries: Node: 12.1.0 - /usr/local/bin/node npm: 6.9.0 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman IDEs: Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild npmPackages: expo: ^33.0.0 => 33.0.7 react: 16.8.3 => 16.8.3 react-native: https://github.com/expo/react-native/archive/sdk-33.0.0.tar.gz => 0.59.8 react-navigation: ^3.11.0 => 3.11.0 npmGlobalPackages: expo-cli: 2.20.2 iOS standalone app Steps to Reproduce 1. Use Facebook.logInWithReadPermissionsAsync to make a facebook login. 2. Choose to log in with the Facebook native app(not in the browser) 3. Press continue to get back to your app. Expected Behavior 3. User should be successfully logged in after getting redirected back to the app Actual Behavior 3. The promise returns type === cancel no matter what the user actually does. *Note: This seems to only happen to some users, but most of the time it does not work. I'd say 1/10 people actually manage to log in the first try. Reproducible Demo In the view I have: <TouchableOpacity onPress={this._handlePressAsync}> <Image source={facebookLogin} style={styles.facebookLogin}/> </TouchableOpacity> The function called: _handlePressAsync = async () => { const {type, token,} = await Facebook.logInWithReadPermission
Cannot open self /usr/bin/docker-compose or archive /usr/bin/docker-compose.pkg
I installed `docker-compose` on my server I reconnect later it said : [code block] I have to reinstall it all the time :/ Thanks for your help!
[BUG] npm install deletes an existing symlinked node_modules directory
Is there an existing issue for this? - [X] I have searched the existing issues Current Behavior If a package contains a node_modules that is symlinked then an npm install will issue the message npm WARN reify Removing non-directory .... and delete the node_modules directory. Expected Behavior A symlinked node_modules directory should be used as is and not recreated - many people symlink node_modules to a local filesystem so that it does not get synced to cloud storage (like Dropbox). I suspect that the npm code is just checking if any existing file object named node_modules is a directory and does not also check to see if the non-directory file object is actually a symlinked directory. Steps To Reproduce cd /tmp mkdir symlinked mkdir z cd z npm init -y ln -s /tmp/symlinked node_modules . npm install lodash Environment - OS: Ubuntu 20.04.1 - Node: 16.7 - npm: 7.21.0
Terraform ignores skip_final_snapshot so it's impossible to delete rds db instance
Hi, I've noticed that terraform (I'm using 0.6.9) ignores skip_final_snapshot argument for RDS DB instance resource that I need to remove: [code block] I'm getting the following error trying to remove DB instance: - aws_db_instance.db_instance: DB Instance FinalSnapshotIdentifier is required when a final snapshot is required Adding final_snapshot_identifier argument doesn't help -- result is the same, terraform fails. tfstate (sensitive data is removed): [code block]
Revert #3002 - set type of data to any
Is your feature request related to a problem? Please describe. Yes. After #3002 was merged, we are now required to set explicit type definitions for every single axios request we make, even if we don't want to, because these would result in an error. Describe the solution you'd like The default type for AxiosResponse#data should be any so that we can modify it if we want, or keep it as is if we don't care about the typings for that specific request Describe alternatives you've considered As suggested in that PR, we could set the type to `any` explicitly, however, many people use typescript-eslint's no-explicit-any rule that prevents us from doing this. I believe everyone should be able to choose what types they wanna work with, because for extremely simple responses from which you only need one or two simple properties you don't always need explicit type declarations Additional context TypeScript's DOM library sets the return type of Body#toJSON to Promise<any>, so we should be following the native approach and not restricting user's options by setting a default that "most users may want", even if most users do not want this.
Bug in IF conditions on inputs for reusable workflows
Problem: When a reusable workflow (called workflow), contains if conditions (based on the input of the job) at job level, there is a observation that the if condition seems to execute and use value globally (causing jobs which are being skipped because of a check). Example > Caller workflow: Simple workflow calling a reusable workflow passing in the github event (PR or push) to the reusable workflow [code block] > Reusable workflow: Workflow with a sequence of job which has conditions based on the input (whether it is a pull_request or a push) [code block] Observation - Job 3 gets the check skipped , even though the condition is valid and matches as Job 2 (Job 3 only depends on success of job 2 and the same `IF` condition as job2. - On removal of the `IF` condition on Job 4 , then Job 3 executes fine . Which implies of some sort of "state" of the IF condition (since there is no relationship between Job 4 and Job 3). The observation of runs can be found in this repository here -> https://github.com/action-foobar/action-testing/actions/runs/1682109402 PS: This was working perfectly fine till 11PM GMT 10th Jan . (as we have a lot of jobs in our org on this setup)
[BUG] Unable to resolve reference $react
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 am attempting to run npm install to create the node_modules folder with nodes and package-lock.json file from the package.json file. When I run npm install it returns this error message "npm ERR! Unable to resolve reference $react". Expected Behavior Since I have react and its version defined in my dependencies, then I expect npm to resolve the reference to react and finish processing my package.json file. Steps To Reproduce 1. In this environment: Windows 10 2. With this config (package.json): [code block] 3. Run 'npm install' 4. See error: "npm ERR! Unable to resolve reference $react" Environment - npm: 8.19.2 - Node.js: 16.18.0 - OS Name: Windows 10 - System Model Name: Dell Precision 7560 - npm config: ; "builtin" config from C:\Program Files\nodejs\node_modules\npm\npmrc prefix = "C:\\Users\\i338909\\AppData\\Roaming\\npm" ; "user" config from C:\Users\i338909\.npmrc http_proxy = "http://bcproxy.hcscint.net:8080" https_proxy = "http://bcproxy.hcscint.net:8080" proxy = "http://bcproxy.hcscint.net:8080/" registry = "http://nexus.fyiblue.com/repository/npm-all/" scripts-prepend-node-path = true strict-ssl = true ; node bin location = C:\Program Files\nodejs\node.exe ; node version = v16.18.0 ; npm local prefix = C:\NMP_TEST\rover-web-app-test ; npm version = 8.19.2 ; cwd = C:\NMP_TEST
docker-compose does not set environment variables
Description of the issue When using `docker-compose up` or `docker-compose run -e ENVIRONMENT_VAR=value`, environment variables are not being applied either through the `-e` command line parameters or from the docker-compose.yml file. The docker-compose.yml file I am using is as follows: [code block] Context information (for bug reports) Output of `docker-compose version` [code block] Output of `docker version` [code block] Output of `docker-compose config` [code block] Steps to reproduce the issue 1. Create a docker-compose.yml file that sets environment variables 2. Run docker-compose up Observed result Environment Variables are not applied Expected result Environment variables should be applied to containers started by docker-compose Stacktrace / full error message [code block] Additional information OS Version: Windows 10 Pro v1909, `docker-compose` install method: Docker Desktop for Windows Installer, followed by manual upgrade of docker-compose (Issue occurred on docker-compose version 1.25.4 which was included with Docker Desktop and with manual upgrade to 1.25.5)
[vite 6.0.9] option server.allowedHosts doesn't take into account "true"
Describe the bug hi, i've recently updated vite to 6.0.9, the main change being the allowedHosts server conf field, it's said in the documentation that if set to true, it will accept any hosts, but even when setting it to true i get the error: Blocked request. This host ("hidden") is not allowed. To allow this host, add "hidden" to `server.allowedHosts` in vite.config.js. (maybe i could be dumb but it really doesn't seem to work) Reproduction google.com Steps to reproduce _No response_ System Info [code block] Used Package Manager npm Logs _No response_ Validations - [x] Follow our Code of Conduct - [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] 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 vuejs/core instead. - [x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. - [x] The provided reproduction is a minimal reproducible example of the bug.
[BUG]: drizzle-kit introspect TypeError: Cannot read properties of undefined (reading 'toLowerCase')
What version of `drizzle-orm` are you using? 0.3.10 What version of `drizzle-kit` are you using? 0.21.2 Describe the Bug ``bun version 1.1.8 [code block] getting this error on bunx drizzle-kit introspect command db schema is here [code block] Expected behavior _No response_ Environment & setup _No response_
Expo build failed / SDK 48
Summary Build failed after update to SDK 48 (from SDK 46). No any errors while application running in development mode. Any help? What platform(s) does this occur on? Android SDK Version 48 Environment System: OS: macOS 13.2.1 Shell: 5.8.1 - /bin/zsh Binaries: Node: 16.16.0 - /usr/local/bin/node Yarn: 1.22.19 - /usr/local/bin/yarn npm: 8.11.0 - /usr/local/bin/npm IDEs: Xcode: /undefined - /usr/bin/xcodebuild npmPackages: @expo/metro-config: ^0.5.2 => 0.5.2 @expo/webpack-config: ^18.0.1 => 18.0.1 expo: ^48.0.0 => 48.0.8 react: 18.2.0 => 18.2.0 react-dom: 18.2.0 => 18.2.0 react-native: 0.71.3 => 0.71.3 react-native-web: ~0.18.11 => 0.18.12 Expo Workflow: managed Minimal reproducible example package.json [code block] Stacktrace (if a crash is involved) [code block]
Tailwind just stops working randomly
What version of Tailwind CSS are you using? 2.1.2 What build tool (or framework if it abstracts the build tool) are you using? Next.js What version of Node.js are you using? 14.16.1 What browser are you using? Chrome What operating system are you using? Mac Reproduction repository N/A Describe your issue From time to time tailwing just stop working, so adding a new class or changing it does not take any effect solution i found is to nuke `.lock` and `node_modules` and do `yarn install` again Has any one else experienced this? Also i have `mode: 'jit',` enabled
com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java:79)
Description Hi, In Android the app randomly crashing with the below error. Got this in firebase crashlytics dashboard and there is no log to debug and reproduce. and We see this crash mostly happens on Samsung devices. Fatal Exception: com.facebook.react.common.JavascriptException TypeError: null is not an object (evaluating 'U.networkType.value'), stack: onValueChange@1368:4730 onPress@954:1602 onPress@229:1700 value@225:7540 value@225:6753 onResponderRelease@225:5556 b@99:1125 S@99:1268 w@99:1322 R@99:1617 M@99:2401 forEach@-1 U@99:2201 <unknown>@99:13818 Pe@99:90199 Re@99:13478 Ie@99:13664 receiveTouches@99:14448 value@40:3544 <unknown>@40:840 value@40:2798 value@40:812 value@-1 Below are the dependencies. "@burstware/react-native-portal": "^1.0.2", "@react-native-community/async-storage": "^1.9.0", "@react-native-community/datetimepicker": "3.0.0", "@react-native-community/geolocation": "^2.0.2", "@react-native-community/masked-view": "^0.1.7", "@react-native-community/netinfo": "^5.9.5", "@react-native-community/progress-bar-android": "^1.0.3", "@react-native-community/progress-view": "@1.1.1", "@react-native-firebase/analytics": "^7.4.2", "@react-native-firebase/app": "^8.3.1", "@react-native-firebase/crashlytics": "^8.3.3", "@react-navigation/bottom-tabs": "5.2.6", "@react-navigation/drawer": "5.0.5", "@react-navigation/material-bottom-tabs": "5.1.7", "@react-navigation/material-top-tabs": "5.1.7", "
Preview feature feedback: `interactiveTransactions`
Please share your feedback about the preview of Interactive Transactions support that was released in v2.29.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 #prisma2 channel in the Prisma Slack.