All Issues
24,993 verified issues
useCallback() invalidates too often in practice
This is related to https://github.com/facebook/react/issues/14092, https://github.com/facebook/react/issues/14066, https://github.com/reactjs/rfcs/issues/83, and some other issues. The problem is that we often want to avoid invalidating a callback (e.g. to preserve shallow equality below or to avoid re-subscriptions in the effects). But if it depends on props or state, it's likely it'll invalidate too often. See https://github.com/facebook/react/issues/14092#issuecomment-435907249 for current workarounds. `useReducer` doesn't suffer from this because the reducer is evaluated directly in the render phase. @sebmarkbage had an idea about giving `useCallback` similar semantics but it'll likely require complex implementation work. Seems like we'd have to do _something_ like this though. I'm filing this just to acknowledge the issue exists, and to track further work on this.
Android crash: Fatal Exception: java.lang.RuntimeException java.util.concurrent.ExecutionException: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/android.test.runner.jar", zip file "/system/framewor
2024 Overview: The root of this issue for most all flutter customers is that your app is running on physical android hardware that flutter does not support. The "fix" is to not ship your app to devices where flutter cannot run. For most users this means using gradle to indicate to Google Play that your app can run on a subset of all android supported hardware architectures. Flutter did not include abi filtering in `flutter create` until https://github.com/flutter/flutter/pull/135529/. Add to app flutter customers may not want to add abi filtering and instead may choose to check the hardware before exposing screens using flutter. Original issue: We have seen this crash a number of times in the wild from crashlytics. [code block] [code block] [code block] [code block] Steps to Reproduce I'm unsure exactly how to reproduce as it seems to happen randomly to some users at startup. The only device reported affected in crashlytics: Model:GCE x86 phone - Android 9 Expected results: Actual results: <details> <summary>Logs</summary> [code block] [code block] [code block] </details>
No official way to install the AWS CLI (v2) on Mac M1 (without Rosetta)
Describe the bug There is no package available for M1 Macs for the AWS CLI v2. The only current way to do so is through Homebrew the problems are detailed here - https://roadtoaws.com/2022/02/10/installing-aws-cli-on-apple-silicon/ Expected Behavior Base don the documentation I would assume that I can do this [code block] Current Behavior The only way to install AWS is through Homebrew. This is an unofficial workaround https://roadtoaws.com/2022/02/10/installing-aws-cli-on-apple-silicon/ Reproduction Steps https://roadtoaws.com/2022/02/10/installing-aws-cli-on-apple-silicon/ Possible Solution https://roadtoaws.com/2022/02/10/installing-aws-cli-on-apple-silicon/ or to install Rosetta on a M1 Mac https://support.apple.com/en-il/HT211861 Additional Information/Context _No response_ CLI version used v2 Environment details (OS name and version, etc.) M1 Mac
Error: Cannot get entity metadata for the given alias
Issue type: [x] question [ ] bug report [ ] feature request [ ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [ ] `mysql` / `mariadb` [ ] `oracle` [x] `postgres` [ ] `cockroachdb` [ ] `sqlite` [ ] `sqljs` [ ] `react-native` [ ] `expo` TypeORM version: [x] `latest` [ ] `@next` [ ] `0.x.x` (or put your version here) Steps to reproduce or a small repository showing the problem: Hi. I'm having an issue with retrieving documents from a nested FROM-clause like this: [code block] And get the error `` Cannot get entity metadata for the given alias "alias". `` Also, if I try to add another from: [code block] the query works, but the second FROM doesn't replace the first one, as specified in the docs. How can I do this the right way? Thanks <!-- 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]) !>
[BUG]: jsonb always inserted as a json string when using postgres-js.
What version of `drizzle-orm` are you using? 0.26.5 What version of `drizzle-kit` are you using? 0.18.1 Describe the Bug Inserting an object into a postgres jsonb field with db.insert only inserts a string when using the postgres-js.adapter. Expected behavior With the pg package, an object is inserted using the code below, which is the expected behavior. With the postgres-js package, a string is inserted into the table using the same code. Environment & setup drizzle packages as above, and, "pg": "8.11.0" and "postgres": "3.3.5" schema.ts: import { pgTable, jsonb } from "drizzle-orm/pg-core"; export const logs = pgTable("log", { line: jsonb("line").$type<object>(), }); load.ts: let lines: { line: object }[] = []; let n = 0; for await (const line of rl) { const lineObj = JSON.parse(line); lines.push({ line: lineObj }); if (++n > numLines) { await runFunction(lines); lines = []; n = 0; } } await runFunction(lines); runFunction: async (lines) => { await db.insert(logs).values(lines); }
Error when instance changed that has EBS volume attached
This is the specific error I get from terraform: [code block] We are building out some infrastructure in EC2 using terraform (v0.6.0). I'm currently working out our persistent storage setup. The strategy I'm planning is to have the root volume of every instance be ephemeral, and to move all persistent data to a separate EBS volume (one persistent volume per instance). We want this to be as automated as possible of course. Here is a relevant excerpt from our terraform config: [code block] And mount.sh: [code block] As you can see, this: - Provisions an instance to run Rundeck (http://rundeck.org/) - Provisions an EBS volume based off of a snapshot. The snapshot in this case is just an empty ext4 partition. - Attaches the voulme to the instance - Mounts the volume inside the instance, and then creates some directories to store data in This works fine the first time it's run. But any time we: - make a change to the instance configuration (i.e. change the value of var.aws_ami_rundeck) or - make a change to the provisioner config of the volume attachment resource Terraform then tries to detach the extant volume from the instance, and this task fails every time. I believe this is because you are meant to unmount the ebs volume from inside the instance before detaching the volume. The problem is, I can't work out how to get terraform to unmount the volume inside the instance _before_ trying to detach the volume. It's almost like I need a provisioner to run before the resou
TypeError: Network request failed On Android
Hi Everyone, I found this problem on my React-Native Android App. When I using a fetch to communicate with a working api, this type of error is returned to me. > TypeError: Network request failed I Used the Chrome debbuger and I found this: `TypeError: Network request failed at XMLHttpRequest.xhr.onerror (whatwg-fetch.js:504) at XMLHttpRequest.dispatchEvent (event-target.js:172) at XMLHttpRequest.setReadyState (XMLHttpRequest.js:580) at XMLHttpRequest.__didCompleteResponse (XMLHttpRequest.js:394) at XMLHttpRequest.js:507 at RCTDeviceEventEmitter.emit (EventEmitter.js:181) at MessageQueue.__callFunction (MessageQueue.js:366) at MessageQueue.js:106 at MessageQueue.__guard (MessageQueue.js:314) at MessageQueue.callFunctionReturnFlushedQueue (MessageQueue.js:105)` This is the code that I used: `static creaUtente(identity, FirstName, LastName, FiscalCode , Email) { let formdata = new FormData(); formdata.append('Identity', identity); formdata.append('FirstName', FirstName); formdata.append('LastName', LastName); formdata.append('FiscalCode', FiscalCode); formdata.append('Email', Email); console.log(Configuration.base_url.rest + Configuration.apiRoutes.signUp) console.log(formdata) return new Promise((resolve, reject)=> { fetch('https://linktotheapi.com',{ method: 'POST', headers: { 'Content-Type': 'multipart/form-data', },
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './server.edge' is not defined by "exports"
Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release Provide environment information [code block] Which area(s) of Next.js are affected? (leave empty if unsure) _No response_ Link to the code that reproduces this issue sorry i can't upload because my project contains localhost database connections To Reproduce On my own server.js file, every page of my application in development mode gets the same error, while on my own server.js file in localhost in production mode, I get this error on the pages under [slug]! When I run this with my server.js file I get this error. While it then worked on 13.3.1, it's now broken! What am I missing in my server.js file or what should I do? I got this error in the last 13.3.2-canary.7 and it continued in later versions! Normally, I get this error when I refresh the pages under news-media/[slug] and other pages under news-media/[slug] while opening in production mode. I get this error on every page in development mode!"dev": "next dev", "build": "next build", While "start": "next start" was OK, as I mentioned above on my server.js file, after the "next 13.3.1" version, errors started on server.js both in development and production mode! Here's my run npm commands for my own server.js: "httpsDevelopment": "node --max_old_space_size=8192 server/server.js", "httpsProduction": "next build && node server/server.js production", My server.js file looks like this: [code block] De
Support for module http2?
Hi, I would like to know if Express 5.0 will have support for http2: https://github.com/molnarg/node-http2 I was reading a bit and I noticed that exist a problem with http2 module: https://github.com/molnarg/node-http2/issues/100 I have tested in local and the problem continues: https://github.com/jabrena/CloudFoundryLab/blob/master/Node_HelloWorld_http2_express/index.js It this issue in the roadmap? Does exist another alternative to run a express application with http2? Many thanks in advance. Juan Antonio
Continual “transport close” on client
I've setup socket.io v.1.4.5 w express and I have been unable to trace the reason for unexplainable disconnects on the clients. The reason given by the disconnect event on the client is "transport close." It happens very consistently on some clients. Is there any explanation for a client getting "transport close" disconnects on what seems to be a timed interval? The client reconnects just fine but it causes extreme inconvenience because it happens so frequently. I've tried various settings, like changing the pingInterval, pingTimeout and the port for websockets (I am now using port 80). But no matter what I seem to do, the problem never goes away.
Can't build on Linux ARM -> cannot find module '@tailwindcss/oxide-linux-arm64-gnu'
What version of Tailwind CSS are you using? 4.0.0 What build tool (or framework if it abstracts the build tool) are you using? Vite 6 What version of Node.js are you using? 22.12.0 What browser are you using? Occurs in CLI What operating system are you using? Ubuntu Linux on arm64 Reproduction URL / Describe your issue When running `tsc && vite build` the build fails and gives the following error: [code block]
Terminal: broken text layout
- VSCode Version: Code - Insiders 1.9.0-insider (fcac9b686abe4292e69a774f61c8c4ce17768bf5, 2017-01-31T00:57:46.157Z) - OS Version: Windows_NT ia32 10.0.15019 - Extensions: |Extension|Author|Version| |---|---|---| |vscode-eslint|dbaeumer|1.2.2| |theme-dracula|dracula-theme|1.2.5| |vscode-great-icons|emmanuelbeziat|1.1.38| |Theme-azure|gerane|0.0.2| |theme-material-theme|jprestidge|1.0.1| |vs-color-picker|lihui|0.3.2| |Theme-MaterialKit|ms-vscode|0.1.1| |view-in-browser|qinjia|0.0.4| |ActiveFileInStatusBar|RoscoP|1.0.2| |eval|Stormspirit|0.0.5| |omnipascal|Wosi|0.12.0| --- Steps to Reproduce: 1. running grunt test to run unit testing should produce this output: (here in cmd.exe) Here is what I got in VSCode integrated terminal: Note that the first time I ran it, the layout of the prompt was also broken, instead of the cursor directly following the prompt, like: I was having: (and I could not move the cursor more on the left)
npm publish 404 Not Found - PUT
The nearest issue is #1626 but it's about using npm to get package, and it look solved for most user. Here it's about npm publishing package in CI, and it's not solved for now. Current Behavior: https://framagit.org/1000i100/g1lien/-/jobs/1072053 [code block] Expected Behavior: Successful publish of my package from docker in gitlab-CI with npm_token authentication. (it works yesterday on my laptop with npm login, but not with npm_token in CI). Steps To Reproduce: ex. steps to reproduce the behavior: 1. Fork this : https://framagit.org/1000i100/g1lien 2. change the package name and add your npm token 3. push it with a tag on a gitlab with CI active. It should reproduce the problem. Environment: https://framagit.org/1000i100/g1lien/-/blob/master/.gitlab-ci.yml#L5 https://framagit.org/1000i100/g1lien/-/jobs/1072052#L17 - OS: Docker in gitlab with image: node:current - Node: v14.7.0 - NPM: 6.14.7
Cannot use interpolations in lifecycle attributes
I was wanting to parameterize a boolean resource property with a variable, but it seems this isn't possible. I tried this with `enable_dns_hostnames` on `aws_vpc` too, so it doesn't seem limited to the `prevent_destroy` example below. The example below fails if the variable's default value is unquoted or quoted. Tested with v0.6.0 and v0.6.3. [code block] [code block]
[0.54] Warnings for soon to be deprecated lifecycle methods
Environment Environment: OS: macOS High Sierra 10.13.3 Node: 8.9.3 Yarn: 1.3.2 npm: 5.6.0 Watchman: 4.9.0 Xcode: Xcode 9.2 Build version 9C40b Android Studio: 3.0 AI-171.4443003 Packages: (wanted => installed) react: 16.2.0 => 16.2.0 react-native: 0.54.0 => 0.54.0 Expected Behavior No warnings would appear in debugger console. Actual Behavior Warnings about React soon to be deprecated lifecycle methods are displayed. e.g.: [code block] Steps to Reproduce [code block] With Chrome debugger open.
Overriding the set of values when extending the "ports" option.
The default behavior when extending a service or overriding a whole docker-compose.yml file is to concatenate the sets of values on the multi-value options: ports, expose, external_links, dns and dns_search. The problem appears when for example you have two production hosts both serving on the port 80 and a single machine for development, there is no way of extending or overriding the services for a development environment that avoids the port collision on the host. An example: lets assume there are two servers one is a REST API and the other is a webpage that uses the API, both listen on port 80 on the production host - compose.yml on host A: [code block] - compose.yml on host B: [code block] On a development environment where you want to test this setup you would define: - compose.override.yml on dev for A: [code block] - compose.override.yml on dev for B: [code block] Of course the "ports" option is concatenated with the production and there is no way of running both containers on the same host because both try to bind to port 80. Is there any workaround or yml specific syntax for this use case?
[Feature] add typescript types in this repo
Currently types are located in https://www.npmjs.com/package/@types/ioredis Types ares out of sync with ioredis repo. It would be easier to fix and maintain there.
TypeError: Missing parameter name at 2: https://git.new/pathToRegexpError
Environment information Version: v5.1.0 Platform: Linux 6.8.0-1021-aws 23~22.04.1-Ubuntu SMP Tue Dec 10 16:50:46 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux Node.js version: v16.20.2 Any other relevant information: N/A What steps will reproduce the bug? [code block] then throws error [code block] Temporary Fix Downgrade to 4.21.2 [code block]
Hight number of processes of /next/dist/compiled/jest-worker/processChild.js still alive after next build
Verify canary release - [X] I verified that the issue exists in the latest Next.js canary release Provide environment information Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 22.3.0: Thu Jan 5 20:48:54 PST 2023; root:xnu-8792.81.2~2/RELEASE_ARM64_T6000 Binaries: Node: 18.13.0 npm: 8.19.3 Yarn: 1.22.19 pnpm: 7.26.2 Relevant packages: next: 12.0.9 react: 17.0.2 react-dom: 17.0.2 Which area(s) of Next.js are affected? (leave empty if unsure) CLI (create-next-app) Link to the code that reproduces this issue https://github.com/vercel/next.js/files/10565355/reproduce.zip To Reproduce reproduce.zip <img width="1492" alt="image" src="https://user-images.githubusercontent.com/3240259/216242566-6f87ae6e-e369-405f-9fca-e525e051797d.png"> This problem can reproduce above next@12.0.9, but 12.0.8 was all right. Or remove `getInitialProps` in `_app.tsx ` was all right above next@12.0.9. [code block] Describe the Bug Hight number of processes of /next/dist/compiled/jest-worker/processChild.js still alive after next build Expected Behavior Kill all child processes. Which browser are you using? (if relevant) _No response_ How are you deploying your application? (if relevant) _No response_ <sub>NEXT-1348</sub>
Next13 caching fetched data even with the 'revalidate = 0' route segment
Verify canary release - [x] I verified that the issue exists in the latest Next.js canary release Provide environment information [code block] Which area(s) of Next.js are affected? (leave empty if unsure) App directory (appDir: true), Data fetching (gS(S)P, getInitialProps) Link to the code that reproduces this issue or a replay of the bug https://github.com/EvandrooViegas/outsystem-angola To Reproduce 1. clone my repo 2. run `npm install` in the root of the cloned repo 3. run `npm run dev` Describe the Bug Next13 seems to be caching the data coming from supabase even with the `revalidate = 0` route segment. Expected Behavior Get the freshest data in every page request Which browser are you using? (if relevant) chrome How are you deploying your application? (if relevant) _No response_