All Issues
24,993 verified issues
Max connections per IP
Hi, we want to use the node-http-proxy in combination with express. Our setup ist the following: Main server: - express listening on port 443 - node-http-proxy listening on port 84 and forwards to 443 Proxy server - node-http-proxy listeing on port 443 and forwards to main server port 84 or another tomcat server Clients - clients connect to proxy server - depending on the url, they are routed to main server or tomcat server - if routet to main server the connection is kept open for about 30 seconds (long-polling) Everything works fine if our clients connect directly to the main server. If they connect over the proxy server we can have 5 request and nothing else happens until those requests are closed. We have to be able to connect a minimum of 500 clients by long polling. Any way we can manage this? Thanks for your help.
Type DeepPartial issue when used with generics
Issue type: [ x ] question [ x ] bug report [ ] feature request [ ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [ ] `mysql` / `mariadb` [ ] `oracle` [ ] `postgres` [ ] `sqlite` [ ] `sqljs` [ ] `react-native` [ ] `expo` TypeORM version: [ x ] `latest` [ x ] `@next` [ x ] `0.x.x` (or put your version here) Steps to reproduce or a small repository showing the problem: [code block] Typescript is giving me error on entity.createdAt, entity.updatedAt , entity.savedBy. [ts] Type 'Date' is not assignable to type 'DeepPartial<E["createdAt"]>'. But if I change the DeepPartial type from: export declare type DeepPartial<T> = { [P in keyof T]?: DeepPartial<T[P]> }; to export declare type DeepPartial<T> = { [P in keyof T]?: DeepPartial<T[P]> | T[P] }; the error disappears. Could we change the DeepPartial type ? Regards Hugo <!-- To answer those questions you need to put "x" inside the square brackets, for example: [x] `mysql` [ ] `postgres` Also, please format your code properly (by taking code blocks into [code block]) !>
Expo-Facebook login won't redirect back to Expo Client app when using login with Facebook app
🐛 Bug Report Environment Expo CLI 3.9.0 environment info: System: OS: macOS 10.14.5 Shell: 3.2.57 - /bin/bash Binaries: Node: 12.13.1 - ~/.nvm/versions/node/v12.13.1/bin/node Yarn: 1.19.2 - ~/.yarn/bin/yarn npm: 6.12.1 - ~/.nvm/versions/node/v12.13.1/bin/npm IDEs: Xcode: 11.0/11M337n - /usr/bin/xcodebuild npmPackages: expo: ^35.0.0 => 35.0.1 react: 16.8.3 => 16.8.3 react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8 react-navigation: ^4.0.10 => 4.0.10 npmGlobalPackages: expo-cli: 3.9.0 Expo Client on iOS device Steps to Reproduce I recently tried to add login with Facebook to my application. I just copied the logIn function from here `https://docs.expo.io/versions/v35.0.0/sdk/facebook/` When I run my app via Expo Client, and execute the logIn function it 1) Redirects me to a page asking if I want to use the Facebook app for login or use phone or email 2) If I use phone or email login works perfectly fine 3) If I select `Use Facebook App` it takes me to the Facebook app, it says `You have previously logged into [MY_APP] and then I press `Continue` a white screen shows up with the `Cancel` button on the top left. It never goes back to my app and never resolves this function `logInWithReadPermissionsAsync`. Expected Behavior It should have gone back to the Expo Client app where my app was running and it should have resolved the promise and return
HNSW + Filter inconsistent result issue (based on HNSW index used vs unused)
Postgres gives inconsistent result count when it uses the HNSW index vs index not being used. I am using PGVector HNSW USING hnsw (embedding vector_cosine_ops) WITH (m='16', ef_construction='32'); IFacing an issue with the below sample query WITH filtered_opportunities AS (SELECT sf.notice_id FROM opportunity_filter sf WHERE sf.full_parent_path_name IN ('ABC SERVICE') //and has_related_award=true // line 2 ) SELECT sv.notice_id FROM semantic_vector sv JOIN filtered_opportunities fo ON fo.notice_id = sv.notice_id ORDER BY sv.embedding <=> cast('[-0.5078125]’) limit 200 From the above query, It gives me a result count of 30 by having one filter condition, if I add another AND condition (uncomment line 2) it is giving me 200 records (ideally adding more where condition should reduce the resultset). The difference in above is, with the first query, it uses HNSW index, so postgres fetches 1000 records from vector table & then apply filter on top of it which reduces the resultset, in the second query postgres doesn't uses HNSW index, so it fetches more records while applying the filter at same time. This is a major issue in our application, where the filters behaves differently based on HNSW index used/not used. Is this is a Postgres bug? any way to solve this?
SSL Connection Error
I am just testing out creating a https server with express. Note that I am using 3.0.0beta2 version of express. The summary is that I can't seem to get ssl working with express. I get this error: Unable to make a secure connection to the server. This may be a problem with the server or it may be requiring a client authentication certificate that you don't have. First I thought maybe there is a problem with my certs, so I recreated them and same thing happened. Then I created a https server without express and everything worked. I have tried all that I can think of, maybe someone here can provide some insight into this issue. I uploaded my repo here (https://github.com/sharonjl/ssltest) so you can clone and test it out yourself; contains a dummy certificate as well! The repo contains an express generated app, can be run by executing app.js. And a single file named app2.js, which has the non-express implementation of a https server.
first request is always slow
Hello, I am having an issue where the first request to any domain which is handled by the proxy appears to take 2-3 seconds to load before it actually does. This was all running on a dedicated server, so I tried it out locally and had the same issue, so I set it up locally on another pc (for sanity sake) and the issue is still happening. This is the code I am using: > var proxy = require("http-proxy"); > > proxy.createServer({ > hostnameOnly: true, > router: { > "admin.local": "localhost:8081", > "web.local": "localhost:8080" > } > }).listen(80); Seems to be happening on every version of node I have tested with (0.6.6, 0.6) Is this a known issue with 0.6 compatibility, is this a known performance tradeoff when proxying like this? Have I done something silly? I am not sure! Some clarity as to why this issue might be happening and would be great. Thanks! edit: The platforms I have tested this with are (osx 10.6, 10.7 and freebsd 8.2)
pg-vector not using hnsw indexes
Help me!!! I created the index using hnsw, but I can't use the index for even the simplest query My system info: [code block] My Table Structure: [code block] My query sql: [code block] Analyse result: [code block] From explain result, I can see that the index is not being used. Any idea what I am doing wrong @ankane
npm default install command always runs if binding.gyp exists, and package install script is ignored
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 1. use npm 7 or 8 2. package.json contains install script 3. project root directory contains binding.gyp 4. npm install results in default npm install command `node-gyp rebuild` running instead of the install script in package.json It works correctly with npm 6. Expected Behavior Expect it to behave as documented: > If there is a binding.gyp file in the root of your package and you haven't defined your own install or preinstall scripts, npm will default the install command to compile using node-gyp via node-gyp rebuild I assume this means: > If there is a binding.gyp file in the root of your package and you have defined your own install or preinstall scripts, npm will run your install and preinstall scripts and not default the install command to compile using node-gyp via node-gyp rebuild Steps To Reproduce 1. Create new directory with new package.json that has no dependencies 2. See canvas has binding.gyp and an install script in package.json. 3. npm i canvas@latest -S --verbose 4. "install": "node-pre-gyp install --fallback-to-build --update-binary", in canvas package.json is NOt run but should be 5. `npm info run canvas@2.9.3 install node_modules/canvas node-gyp rebuild` is run but should NOT be 6. Behaves the same if canvas is added as a dependency in package.json and run `npm install` [code
upsert across HTTP requests has a race condition
Bug description Situation: I have a model with a unique string. At the beginning I have an empty database. I want to create or update an object of the model with upsert and check if the object exists by searching for the unique string. If I call several upserts with the same unique string at the same time, I expect it to be created once and then updated if necessary. But it is created once and then the error occurs: Unique constraint failed on the fields. [code block] How to reproduce Expected behavior I expect it to be created once and then updated the just created object, instead of crashing. Prisma information [code block] Environment & setup - OS: Mac OS, - Database: PostgreSQL - Node.js version: v13.3.0 - Prisma version: 2.3.0 [code block]
Stuck on `Creating an optimized production build` forever when development server is running
Verify canary release - [x] I verified that the issue exists in Next.js canary release Provide environment information Operating System: Platform: win32 Arch: x64 Version: Windows 10 Pro Binaries: Node: 16.13.0 npm: N/A Yarn: N/A pnpm: 6.24.0-1 Relevant packages: next: 12.1.4 react: 17.0.2 react-dom: 17.0.2 What browser are you using? (if relevant) _No response_ How are you deploying your application? (if relevant) _No response_ Describe the Bug I had my development server running in the background without me remembering and I wanted to build my app using `next build`, that's what I've got: [code block] And I was stuck for 30 minutes on `info - Creating an optimized production build` without any indication of anything being wrong, I noticed that the development server was running, after I've shut it down and ran `next build` again It compiled successfully. Expected Behavior - Run `next build` to compile the app for production even when I'm running the development server. OR - Notify me that the development server is running and needs to be shut down before running `next build`, that's in case running `next build` when `next` is running isn't possible. Link to reproduction https://github.com/YassinEldeeb/Next.js-starter To Reproduce 1. Run `next` for the development server. 2. Then run `next build` while the development server is running. Note: It's not specific to the repository lin
Firebase on React Native should import AsyncStorage from @react-native-community/async-storage
Describe your environment Operating System version: React Native 0.59 Browser version: iOS, Android Firebase SDK version: 6.1.0 Firebase Product: auth Describe the problem When using Firebase on React Native, it uses AsyncStorage from `react-native` under the hood to store the authentication session across app restarts. Starting from RN0.59 AsyncStorage is deprecated from `react-native` and moved into its own package `react-native-async-storage`. Steps to reproduce: Add Firebase to React Native app and observe how at the startup there's a warning: [code block] Relevant Code: https://github.com/firebase/firebase-js-sdk/blob/96ab56bac05ccaf506ed3a02ccad5ff7e01a07d0/packages/app/index.rn.ts#L27
TypeError: Cannot read property 'databaseName' of undefined
Issue type: [x] bug report Database system/driver: [x] `mssql` TypeORM version: [x] `latest` Steps to reproduce or a small repository showing the problem: Here is a repo with the bug: https://github.com/victorschinaider/typeorm-bug I think `pagination`+ `embedded orderBy`+ `subquery` + `leftJoinAndSelect` combination is giving me the problem.
Secrets fail to set the `uid`, `gid` and `mode` specified in `docker-compose.yml`
Description Docker secrets specified using the long syntax for the `docker-compose.yml` file fail to set the specified `uid`, `gid` and `mode`. Also, from the docs, the default value of the `uid` and `gid` fields should be the user that runs the container however the value remains whatever was set on the host machine. Steps to reproduce the issue: 1. Create a `Dockerfile` [code block] 2. Create a `docker-compose.yml` [code block] 3. Create a text file for secrets (`somefile.txt`) [code block] 4. Run the service `docker compose run secrets-tester` Describe the results you received: Received Output: [code block] Describe the results you expected: Expected Output: [code block] Additional information you deem important (e.g. issue happens only occasionally): Same behavior is observed in these cases: 1. Without creating the `tester` user 2. With same `source` and `target` names for the file in `docker-compose.yml` 3. Using the `uid` and `gid` for `root` 4. Using random values for `uid` and `gid` 5. Different values for `mode` Output of `docker compose version`: [code block] Output of `docker info`: [code block] Additional environment details:
KeyboardAvoidingView does not work on standalone app [Android].
Hello. I have taken this code from a premium theme that i bought. [code block] Its a chat View, it works perfect on Expo testing, but as soon as I build APK standalone it does not work, the keyboard will cover the whole screen. I have tried react-native-keyboard-aware-scroll-view but in order to use its needed to detach the app. I have searched the whole internet. I'm the only one suffering from this issue?
preflight button reset in v3 inconsistent with v2
What version of Tailwind CSS are you using? For example: v3.0.6 What build tool (or framework if it abstracts the build tool) are you using? postcss: 8.3.11 webpack: 5.65.0 What version of Node.js are you using? v14.16.1 What browser are you using? Chrome What operating system are you using? macOS Reproduction URL https://play.tailwindcss.com/AJDoBTeOhx Describe your issue https://github.com/tailwindlabs/tailwindcss/pull/5358 removes the dependency on `modern-normalize`, and then inlines and consolidates it with preflight. During this consolidation it appears as: [code block] was merged with: [code block] Resulting in [code block]` Since `[type='button']`, `[type='reset']`, `[type='submit']` have high specificity simple `background-color` and `background-image` styles included before tailwind are being overridden. This did not occur in v2 when the rules were separate. (I recognize this is not best practices but I am working in a legacy app.) I would be happy to open a PR that breaks apart the rules restoring v2 behavior (if that is desired): [code block]
Axios doesn't work with Android (emulator) raising a Network Error
I'n new with React Native, and I was playing around with components and http ajax request, and all went fine with iOs emulator, until I thought to test on Android emulator. This is my Http class: [code block] This is the error I'm getting from the post request, using login() function I created using axios.post() NOTE: - I'm using the latest version of Axios ^0.16.2 - My AndroidManifest.xml contains: [code block] - The APIs are under VPN, as I wrote all works fine with iOs emulator but doesn't with the Android one.
Feature Request: Allow Unique in Array Schema Definition
The following page states currently supported Schema types: http://mongoosejs.com/docs/schematypes.html One feature that would be nice is for Mongoose to enforce uniqueness in Arrays, which could guarantee unique values in an array in Mongoose, like the $addToSet functionality in the Mongo database query language. Current Issue I can only define an array to hold a list of values, which allows multiple instances of the same value. The following code example demonstrates the issue. var schema = mongoose.Schema({ friends : [{type : mongoose.Schema.Types.ObjectId, ref : 'User' }] }) model = new mongoose.model('User') model['friends'].push(ObjectId('12345')) model['friends'].push(ObjectId('12345')) model.save() Mongo document now looks like: {friends:[ObjectId('12345'),ObjectId('12345')]} Suggested Fix Enhance the schema model to allow unique attribute for an array, which internally uses the Set() object in Mongoose. Then once save() is called, mongoose will convert the set to an array and use the "$addToSet" mongodb operator that will ensure values are unique in the array. Something like the following code snippet would be desired: var schema = mongoose.Schema({ friends : [{type : mongoose.Schema.Types.ObjectId, ref : 'User', unique: true }] }) model = new mongoose.model('User') model['friends'].push(ObjectId('12345')) model['friends'].push(ObjectId('12345')) model.save() Mongo document now looks like: {friends:[ObjectId('12345')]} Current Method Currently it is
Very long re-rendering times in 0.71.3
For the latest update on this situation, please refer to this comment. ---- Description I have a complex calendar component in my app. I previously ran it on 0.66.5, where it was really fast, but after upgrading to 0.71.3, performance dropped drastically, to the point that it is unusable. The problem is most obvious on ios, but also appears on Android. I used to react devtools in flipper to measure the re-render times. On ios in 0.66.5, the component re-rendered in about 7ms, on 0.71.3 it took nearly 400ms. On android the 0.66.5 took about 10ms, 0.71.3 took about 30ms. The app uses dayjs and Flashlist, but performance was the same when switching to regular Flatlist. React Native Version 0.71.3 Output of `npx react-native info` System: OS: macOS 13.0.1 CPU: (8) arm64 Apple M1 Memory: 139.16 MB / 16.00 GB Shell: 3.3.1 - /opt/homebrew/Cellar/fish/3.3.1/bin/fish Binaries: Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.0/bin/yarn npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm Watchman: 2022.01.17.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.11.2 - /opt/homebrew/lib/ruby/gems/3.0.0/bin/pod SDKs: iOS SDK: Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1 Android SDK: API Levels: 29, 30, 33 Build Tools: 29.0.2, 30.0.2, 30.0.3, 33.0.0 System Images: android-30 | Google APIs Intel x86 Atom, android-S | Google APIs AR
PyYAML requires python-dev dependency
Hi, It seems the latest release of `awscli` requires PyYAML as its dependency. I noticed that this dependency breaks my CI test in Ubuntu 14.04. It returned the following error: [code block] I'm wondering, is it possible to use `awscli` via `pip install awscli` without adding extra `python-dev` dependency? Or if it's required to use extra dependency, I think it's a good idea to put it in the documentation. Thank you!
npm ERR! Cannot set properties of null (setting 'dev')
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 `npm install` does not work if try to install one workspace to another STR: - `mkdir foo && cd ./foo` - `npm init -y` - `npm init -y -w ./pkg-a` - `npm init -y -w ./pkg-b` - `npm install ./pkg-a -w pkg-b` AR: `npm ERR! Cannot set properties of null (setting 'dev')` ER: Behaviour similar to `cd ./pkg-b && npm install ../pkg-a` Expected Behavior _No response_ Steps To Reproduce _No response_ Environment - npm: 8.1.0 - Node: v16.13.0 - OS: macOS 12.0.1 - platform: Darwin arm64 [code block]