All Issues
24,993 verified issues
ScrollView: Unsupported top level event "topScroll" dispatched
Is this a bug report? yes Have you read the Contributing Guidelines? yes Environment Environment: OS: macOS Sierra 10.12.6 Node: 8.4.0 npm: 5.3.0 Watchman: 4.7.0 Xcode: Xcode 8.3.3 Build version 8E3004b Android Studio: 2.3 AI-162.4069837 Packages: (wanted => installed) react-native: 0.50.0.rc1 react: 16.0.0 Target Platform: Android (8.0.0) Steps to Reproduce 1. launch a scrollview page which has two Image as child 2. scroll this page 3.show red box: Unsupported top level event "topScroll" dispatched
[Workarounds] Packager unable to resolve module from /Users/node_modules/
There are various issues scattered around the repo related to this issue. Basically what happens is, for some packages, when you try to require `some-module` in a file, for example, [code block] It is unable to resolve the package and the following error appears, [code block] This error message is a symptom of the packager not being able to find `some-module`. It'll walk up the directory tree until it finds `node_modules/some-module`. It just so happens that `/Users` is the last directory to try, hence the weird `/Users/node_modules` directory in the error message (h/t @philikon). Workarounds Currently, the workarounds seem to be, - Delete the `node_modules` folder - `rm -rf node_modules && npm install` - Reset packager cache - `rm -fr $TMPDIR/react-*` or `node_modules/react-native/packager/packager.sh --reset-cache` - Clear watchman watches - `watchman watch-del-all` - Recreate the project from scratch
findById returns no results even with correct ObjectId
Configuration: Mongoose 4.0.5, MongoDb 3.0.4, Node 0.12.4 Issue does not appear on Mongoose 3.8.30 My database has the following data: [code block] I query it with Mongoose using the following syntax: [code block] which returns null for both error and user. Strangely enough Mongoose's debugging shows the following, correct query: [code block] which queried directly on MongoDB finds the expected data: [code block] I tried various alternatives such as directly initializing an ObjectId object or taking an ObjectId from a `find()` result which leads to no results either. As stated above reverting back to Mongoose 3.8 resolves the issue.
Add support for HNSW algo
Currently, it's very slow, please add support for the HNSW algorithm to continue to use pg_vector. I recently came across, pg_embedding, please try to replicate it.
no such file or directory, open '/path/schema.prisma' since 3.1.1
Bug description When I call ` new PrismaClient()`, I get the error [code block] That just happen on 3.1.1 How to reproduce 1. Upgrade prisma to 3.1.1 2. Execute `prisma db push` command 3. Call ` new PrismaClient()` Expected behavior _No response_ Prisma information Environment & setup - OS: Windows(wsl) - Database: SQLite - Node.js version: v14.17.4 Prisma Version [code block]
Future of TypeORM
We are working full-time on TypeORM for almost three years. That’s why we have such a powerful and really amazing ORM. And this time wasn't funded or sponsored by anybody except our core developers - (@pleerock and @AlexMesser). And three years is a huge amount of time and it cost us lot of resources. ----- Open source is free, but if you want a really high-quality open source with a good support, code reviews, new features, performance and bug fixes - our core developers should spend much more time on it. And we all know that time is money. TypeORM is a huge and very complex library. Ideally it requires a few full-time paid developers. Nobody is working full-time for free, you should understand that people have families, kids and they have to live on something. They simply can't be unemployment and work on TypeORM full-time. ----- Again, being a full-time is very important for this project because developing a good orm is a very complex task as it takes a lot of time to maintain it, develop a new features, review pull requests, answer people questions, maintain all this infrastructure. Without being a full-time we loose in all those areas and processes are very slow. To understand scales, I'll provide you an example. In last few months I've got 1000+ github notifications from TypeORM repository. They include github issues and pull requests. Now imagine how much time it requires to: read each issue review its code clone attached repository and test it (if it was atta
React Fire: Modernizing React DOM
------------- For latest status, see an update from June 5th, 2019: https://github.com/facebook/react/issues/13525#issuecomment-499196939 ------------- This year, the React team has mostly been focused on fundamental improvements to React. As this work is getting closer to completion, we're starting to think of what the next major releases of React DOM should look like. There are quite a few known problems, and some of them are hard or impossible to fix without bigger internal changes. We want to undo past mistakes that caused countless follow-up fixes and created much technical debt. We also want to remove some of the abstraction in the event system which has been virtually untouched since the first days of React, and is a source of much complexity and bundle size. We're calling this effort "React Fire". 🔥 React Fire React Fire is an effort to modernize React DOM. Our goal is to make React better aligned with how the DOM works, revisit some controversial past decisions that led to problems, and make React smaller and faster. We want to ship this set of changes in a future React major release because some of them will unfortunately be breaking. Nevertheless, we think they're worth it. And we have more than 50 thousands components at Facebook to keep us honest about our migration strategy. We can't afford to rewrite product code except a few targeted fixes or automated codemods. Strategy There are a few different things that make up our current plan. We might add
How to secure 'io' cookie
I noticed that socket.io (engine.io to be precise) is setting a non-secure session cookie called 'io' on the URL it is invoked. What is the role of this cookie, is it necessary and if so, can it be secured? We force https:// for all locations where socket.io is running, and could easily set this cookie to secure but I cannot find where.
Copy/replace/add left <-> right in compare views
In the compare views, it would be nice to have "Copy to left/right" "Replace left (with right)/right (with left)" "Add above/down left/right" in all* views, i.e. the side-by-side and the unified view (there with other text than "left/right"). Now, I need to select the text and copy-paste it. In the unified view, I even can't select the text from the compared file ("left" file in side-by-side view). A nice UI would be the one as in Meld: Related: #24390 (but only wanted for staging VCS diffs) Blocked by: https://github.com/Microsoft/vscode/issues/4180 ?
Cannot select text from deleted lines diff view
- VSCode Version: 1.3.0-insider - OS Version: OS X 10.11 Steps to Reproduce: 1. Open a file with changes in inline diff mode 2. Try to select the red (deleted) lines (You can't) You can select them normally in the side-by-side. Being able to do so is useful to restore/revert small pieces of code manually by copying and pasting.
Error response data nodejs
Describe the bug ` var axios = require('axios'); var data = JSON.stringify({ "production_status": "", "package_status": [], "extra_status_reason": [], "page": 1, "limit": 1 }); var config = { method: 'post', url: 'https://example.com/', headers: { 'Authorization': 'Bearer token', }, data: { "production_status": "", "package_status": [], "extra_status_reason": [], "page": 1, "limit": 1 } }; axios(config) .then(function (response) { console.log(response.data); }) .catch(function (error) { console.log(error); }); ` When i send API this response I want respose must be json like that To Reproduce _No response_ Code snippet _No response_ Expected behavior _No response_ Axios Version 1.2.0 Adapter Version _No response_ Browser _No response_ Browser Version _No response_ Node.js Version 14.20.1 OS _No response_ Additional Library Versions _No response_ Additional context/Screenshots _No response_
Storing sensitive values in state files
#309 was the first change in Terraform that I could find that moved to store sensitive values in state files, in this case the `password` value for Amazon RDS. This was a bit of a surprise for me, as previously I've been sharing our state files publicly. I can't do that now, and feel pretty nervous about the idea of storing state files in version control at all (and definitely can't put them on github or anything). If Terraform is going to store secrets, then some sort of field-level encryption should be built in as well. In the meantime, I'm going to change things around to use https://github.com/AGWA/git-crypt on sensitive files in my repos.
Vim Style Key binding
There are a few extensions in the marketplace for Vim, however Vim key bindings is still such a hot request in User Voice. Can VS Code / Vim users chime in on what is currently missing?
Implement connection queueing to avoid nodejs connection limits
I sometimes get this error after doing some requests: [code block] Here is the last request I'm recording: [code block]
Proposal: Variadic Kinds -- Give specific types to variadic functions
Variadic Kinds Give Specific Types to Variadic Functions This proposal lets Typescript give types to higher-order functions that take a variable number of parameters. Functions like this include `concat`, `apply`, `curry`, `compose` and almost any decorator that wraps a function. In Javascript, these higher-order functions are expected to accept variadic functionsas arguments. With the ES2015 and ES2017 standards, this use will become even more common as programmers start using spread arguments and rest parameters for both arrays and objects. This proposal addresses these use cases with a single, very general typing strategy based on higher-order kinds. This proposal would completely or partially address several issues, including: 1. #5331 -- Tuples as types for rest ...arguments 2. #4130 -- Compiler incorrectly reports parameter/call target signature mismatch when using the spread operator 3. #4988 -- Tuples should be clonable with Array.prototype.slice() 4. #1773 -- Variadic generics? 5. #3870 -- Rest types in generics for intersection types. 6. #212 -- bind, call and apply are untyped (requires #3694's this-function types). 7. #1024 -- Typed ...rest parameters with generics I'll be updating this proposal on my fork of the Typescript-Handbook: sandersn/TypeScript-Handbook@76f5a75868de3fb1ad4dbed5db437a8ab61a2698 I have an in-progress implementation at sandersn/TypeScript@f3c327aef22f6251532309ba046874133c32f4c7 which currently has the simple parts of the proposal impleme
Popper.js:11 Uncaught TypeError: styled_default is not a function at Popper.js:11:20
Describe the bug I have updated some of my dependencies. I expect to see the address of my code in the error call stack. All I see is this: [code block] I have also reported it to the MUI Team I have also seen that it's been asked here. My problem is that the error does not give us more information. Is it a Vite bug? Is it a bug related to esbuild? Is it a bug of MUI? I literally do not know. Reproduction https://github.com/Nefcanto/MuiPopperBug Steps to reproduce 1. `git clone https://github.com/Nefcanto/MuiPopperBug` 2. `cd MuiPopperBug` 3. `npm install` 4. `npm run dev` 5. Browse and see the error 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] package-lock.json integrity value for git dependencies depends on the architecture (Apple Silicon M1 differs)
Current Behavior: The `package-lock.json` integrity value seems to depend on the OS/architecture. Take the following git dependency which specifies a commit hash: [code block] The integrity value produced is different on these OSes/architectures: - Ubuntu 20.04, and macOS 11.2.3 (Intel): `sha512-DnBTbDDxd9/9mwPehyraeuRTbNEqbWLcAdE3GC1trdBWWwKnkWsaU/X6mVLIKKB/IYWmG+cnL3ihg/Ql/rW5kg==` - macOS 11.2.3 (Apple Silicon): `sha512-T3ZWOM1TT+Ch/splApkEe1HwktWs+n/iHvDvtIGEI+4xuMGHite6mMujuNd8sen49ofLP/PxzprQMSPJK8APww==` Expected Behavior: The integrity value should not be different on Apple Silicon (M1 chip) machines. Steps To Reproduce: Run `npm pack "git+ssh://git@github.com/jhiesey/idb-kv-store.git#109ccad165fd6470e12fd66025da9e4743a46043" ` and inspect the integrity value from an M1 Mac. Node.js was installed from Homebrew using `brew install node` and the `amd64` version was installed. Also... @jhiesey and I dug into this a bit and found that the tarballs fetched from the GitHub CDN are exactly the same on M1 and other architectures, byte-for-byte. Same for the ungzipped tarballs – they are the same byte-for-byte. What differs, though, is the gzipped tarballs (`.tar.gz`) files. Those appear to have substantial differences when viewed in a hex editor. Environment: - OS: Various, see above - Node: v15.11.0 - npm: 7.6.2
Safari dropping web socket connection due to inactivity when page not in focus
You want to: [x] report a bug [ ] request a feature Current behaviour Not sure if this is a known issue (I tried searching but found nothing). Safari for Mac appears to be silently dropping websocket connections due to inactivity/idle if the page/tab is not in focus. Steps to reproduce (if the current behaviour is a bug) Make Safari tab/page not in focus; log websocket events. Expected behaviour Websockets should be kept alive via the heartbeat functionality. Not seeing this behavior in other browsers so unlikely to be my code. Setup - OS: Mac OSX 10.12.4 (16E195) - browser: Safari 10.1 (12603.1.30.0.34) - socket.io version: 1.7.3 Other information (e.g. stacktraces, related issues, suggestions how to fix) Is this possibly some sort of power-saving feature that is overriding/ignoring the heartbeats?
[BUG] <Freezes during npm install>
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 While running the command npm install with the latest version (V10.9.0), the installation pauses and does not proceed further. To resolve this, I have attempted the following steps: 1. Cleared the npm cache using npm cache clean --force. 2. Restarted both my PC and Visual Studio Code. 3. Deleted the package-lock.json file and the node_modules directory. But none of these worked. Expected Behavior Sould have installed the dependencies and created package-lock.json and node_modules. Steps To Reproduce Environment: Using Visual Studio Code with Node.js version 20.13.1. React and TypeScript: The project uses React version 18.2.0 and TypeScript version 5.3.3. Command: When I run npm install, the process appears to be loading continuously without any further progress. Environment - npm: 10.9.0 - Node.js: 20.13.1 - OS Name: Ubuntu 20.04.6 LTS - npm config: `
firebase.messaging.getToken() edgecase when push notification is set back to default (ask)
[REQUIRED] Describe your environment Operating System version: macOS Mojave Version 10.14.6 Browser version: Google Chrome Version 78.0.3904.97 Firebase SDK version: 7.0.0 * Firebase Product: Firebase Cloud Messaging [REQUIRED] Describe the problem The issue I have identified was introduced in version 7.0.0 of the firebase-js-sdk. I do not run into this issue in versions previous to 7.0.0. The issue occurs when a use grants notification permissions, gets a FCM token, then updates the notification permissions in the browser back to Ask (default), reloads the page, grants notification permissions again in Chrome, and get an error when trying to getToken at this point. Note: subsequent calls to getToken don't face this issue. Steps to reproduce: The problem occurs after taking the following steps: - Call Notification.requestPermission() and user grants permissions - Call firebase.messaging.getToken() - Set notification permission in browser back to Ask (default) - Call Notification.requestPermission() and user grants permissions - call firebase.messaging.getToken() - get DELETE https://fcmregistrations.googleapis.com/v1/projects/{project_id}/regis.../{FCM_token} 500 error and this specific error from FCM: "FirebaseError: Messaging: A problem occured while unsubscribing the user from FCM: FirebaseError: Messaging: A problem occured while unsubscribing the user from FCM: Internal error encountered. (messaging/token-unsubscribe-failed). (messaging/token-unsubscribe