All Issues
24,993 verified issues
ECONNRESET at Function.AxiosError.from
Hi there, I was using axios v0.21.4 and constantly receiving ECONNRESET errors throughout the day: [code block] After updating to the latest version (v1.1.3) and some rewrites to use the AbortController instead of CancelToken and an NodeJS-Upgrade (v18) I still receive the EONNRESET error but with some more information: [code block] Further information I send similar requests over and over throughout the day. Some of the requests (axios.get) are handled correctly, some return with [code block] and some lead to the ECONNRESET error above. Is this a problem within my code or a general problem within axios? Axios Version 1.1.3 Node.js Version 18
`npm outdated` suddenly throws a multitude of "Access token expired or revoked. Please try logging in again." notices
Starting yesterday evening, `npm outdated` started throwing lots of `Access token expired or revoked. Please try logging in again.` notices. This seems to happen for every local package in my npm workspaces TurboRepo. Apparently the `outdated` command tries to find newer versions for local packages as well: [code block] Googling this error message gave me literally zero results, so I dug deeper into the npm source code and found out that the message is returned from the registry.npmjs.org server itself as a response header and then logged as a notice: [code block] I suspect there has been a change yesterday on the npm registry servers which now adds this `npm-notice` header to every 404 returned by the npm registry. But it makes me wonder: Why does the outdated command check the registry for local packages in the first place? And does it really make sense to return this error when a package was just not found?
Option to disable foreign keys creation
Issue type: [x] question [ ] bug report [x] feature request [ ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [x] `mysql` / `mariadb` [ ] `oracle` [ ] `postgres` [ ] `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: Is there a way to disable foreign keys creation? I searched a bit and couldn't find it. If not, is there a chance such option can be implemented? Maybe I can give it a try if you point me in the right direction. (:
[Android] Extreme lag after upgrade to 0.39.2 and 0.40.0
Description Updating from 0.36.0 to 0.39.2 and 0.40.0 renders the app unusable after minimal interaction. The javascript thread slowly grinds to a halt until it becomes unresponsive. Native UI, such as scrolling or native animations is unaffected. Problem persists with 0.41.0-rc.0 It works perfectly well with 0.38.0 Reproduction I managed to reproduce this in a freshly installed app with an infinite scroll list containing rows with images. With 0.40.0, the JS driven animation begins to lag after only ~150 items. WIth 0.38.0, animation stays smooth as long as there is no rendering. See attached videos below: 0.38.0 0.40.0 Test app can be found here A relative StackOverflow question. Solution I suspect the new C-based CSS implementation, as that is the only major change from 0.38 to 0.39. Another reason could be a problem with removeClippedSubviews. Additional Information React Native version: 0.39.2 / 0.40.0 Platform: Android * Operating System: MacOS
Expo start tunnel failed to start tunnel
> Jump to _official_ temporary workaround Summary Expected When running `expo start -c --tunnel` it should start up a tunnel Actual I get this error message: [code block] What platform(s) does this occur on? Android, iOS, Web Environment [code block] Minimal reproducible example Simply run the following in a terminal: [code block]
iOS: NetInfo.isConnected returns always false
I am currently running RN 0.28.0... [code block] I would do a PR but I can't code for iOS.
next/image "url" parameter is valid but upstream response is invalid
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) Image optimization (next/image, next/legacy/image) Link to the code that reproduces this issue or a replay of the bug https://github.com/luca-vogels/bug-next-image To Reproduce Run `npm run dev` or `npm run build && npm run start` Describe the Bug When using next with a custom server like express images are not displayed anymore. Default next image uses following route for fetching optimized images: `/_next/image/?url=...&w=...&q=...` However opening this route returns following error: `"url" parameter is valid but upstream response is invalid` Expected Behavior Optimized image is returned Which browser are you using? (if relevant) 115.0.5790.111 How are you deploying your application? (if relevant) npm run start <sub>NEXT-1681</sub>
Ephemeral (single use) runner registrations
Describe the bug When starting a self hosted runner with `./run.cmd --once`, the runner sometimes accepts a second job before shutting down, which causes that second job to fail with the message: [code block] This looks like the same issue recently fixed here: microsoft/azure-pipelines-agent#2728 To Reproduce Steps to reproduce the behavior: 1. Create a repo, enable GitHub Actions, and add a new workflow 1. Configure a new runner on your machine 1. Run the runner with `./run.cmd --once` 1. Queue two runs of your workflow 1. The first job will run and the runner will go offline 1. (Optionally) configure and start a second runner 1. The second job will time out after several minutes with the message: [code block] (where `[runner-name]` is the name of the first runner) 1. Also: trying to remove the first runner with the command `./config.cmd remove --token [token]` will result in the following error until the second job times out: [code block] Expected behavior The second job should run on (and wait for) any new runner that comes online rather than try to run as a second job on the, now offline, original runner. Runner Version and Platform 2.262.1 on Windows Runner and Worker's Diagnostic Logs _diag.zip
Support stream response in browser
Would be useful if `responseType` could be set to `stream` in the browser. Right now, it only works in node.
npm is down
open https://www.npmjs.com/package/@2gis/tiny-map got 503 {"error":"Service Unavailable"} or sometimes > ESOCKETTIMEDOUT > id: 22e8c953-b92e-4626-96c3-66857626c11b also 404's sometimes on packages install upd see current status on https://status.npmjs.org/
Log lines for an active step are inaccessible
Describe the bug When opening the "run" page for an active job you can see: - Gray checkmarks and expandable sections for completed steps and all of their log lines. - Yellow loading animation on any active steps. - Circles for the future steps. The log lines for the active steps will then start streaming in, but the prior lines for that step are not there, and there appears to be no way to see them until the step completes. To Reproduce Steps to reproduce the behavior: 1. Run an action 2. Visit the run page after a few seconds and try to find the log lines for the currently running step that occurred before you loaded the page. Expected behavior All of the log lines that were emit before I loaded the page should be visible, then new ones stream in afterwards.
componentDidReceiveProps Please
I would like to humbly request a componentDidReceiveProps hook, often times I would like to do something on both componentWillMount and componentWillReceiveProps, but because `this.props` hasn't been set yet I am forced to pass props around instead of reading directly from `this.props`. Before New Hook [code block] After New Hook [code block] In this simple example it may seem like a small thing, but often times the passing of props runs deep and instead of conveniently referencing this.props one is forced to plumb the props throughout the component. Please consider adding `componentDidReceiveProps` as a hook to leverage the same code that is leveraged in componentWillMount without forcing both to plumb props throughout the component.
[FEATURE]: Add check support in drizzle-kit
Describe what you want This issue is a part of https://github.com/drizzle-team/drizzle-orm/issues/229
Hot Reloading is not working
- [ x ] I have reviewed the documentation - [ x ] I have searched existing issues - [ x ] I am using the latest React Native version Hot Reloading is not updating the view in Android device even we have made changes. It happens after a Reload triggered from the device. I have tested this issue in v0.55.2, 0.54.0 and 0.53.3. The only version that has hot reload still functioning well is 0.53.3, this problem starts occuring from 0.54.0 Environment OS: Windows 10 Node: 6.11.5 Yarn: 1.3.2 npm: 4.6.1 Watchman: Not Found Xcode: N/A Android Studio: Version 3.0.0.0 AI-171.4443003 Packages: (wanted => installed) react: 16.3.1 => 16.3.1 react-native: 0.55.2 => 0.55.2 Steps to Reproduce 1. Run `react-native init NoHotLoad` 2. Run `react-native run-android` 3. When the project loaded, enable the Hot Reloading 4. Make changes to the App.js, like editing the text. The change should appear in the device. 5. Do Reload on the device 6. Repeat step 4, but the change won't appear at the device. Just a toast of Hot reloading appears. Another scenario: after installing the app to the device, replace step 2 above with `npm start` should also reproduces this problem. Expected Behavior The Hot Reloading should be able to hot-reload all the changes, regardless number of attempts of reload. Actual Behavior The Hot Reloading only works before a Reload action triggerred
[Feature Proposal] - Nested Group Hover
Hi, When creating nav dropdown, I usually just add `group` class to my `<li>` element, and then to my `<ul>` that is child of that `<li>` I add something like `opacity-0 invisible backface-invisible group-hover:opacity-100 group-hover:visible group-hover:backface-visible`. Which works fine, but then if my dropdown will have another dropdown, this won't work. It would be awesome if we could have nested group hover. :)
App keeps refreshing with log: `Server connection lost polling for restart`
Describe the bug In certain situation the app keeps refreshing indefinitely giving this log in console: `server connection lost polling for restart`. I'm using vite 2.4.2 with https, react and typescript. Reproduction I noticed this happen in this 2 situations: 1. Using Brave with a CORS extension enabled on the page (in my case is CORS Unblock). Weirdly using Chrome with the same Chromium version and same extension doesn't cause the problem 2. Running `vite` with the `--host` flag and accessing it with my phone (Safari on iOS 14) via the shared url: `https://192.168.1.xxx:3000`. Removing the https option "solves" the problem on iOS. System Info [code block] Used Package Manager yarn 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 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.
Passing custom props via axios config
Describe the bug We use some custom parameters via axios configuration. They are used in the response interceptor. Sometimes there may be a lot of information there, so the option to pass it through the `headers` or `params` is not suitable for us because of the length limit To Reproduce - Open: https://jsfiddle.net/w2rmhy4c/1/ - Attach axios 0.18 (uncomment line with `axios@0.18.0`) - Run fiddle (console show true) - Attach axios 0.19 (uncomment line with `axios@0.19.0`) - Run fiddle (console show undefined) Expected behavior Custom config parameter passed. Or the ability to use another config option to pass custom data. Environment: - Axios Version 0.18/0.19 Additional context/Screenshots First messages with axios 0.18, second with 0.19 <img width="975" alt="" src="https://user-images.githubusercontent.com/4497128/61464515-0a48e180-a97f-11e9-8806-d14f173ecba7.png">
Migration tool doesn't recognize .scss files
What version of Tailwind CSS are you using? 3.4.17 What build tool (or framework if it abstracts the build tool) are you using? Vite 6, Vue 3, postCSS What version of Node.js are you using? 22 What browser are you using? N/A What operating system are you using? Windows 11 Reproduction URL No repro Describe your issue My project has a .scss file with Tailwindcss declaration, which is in turn imported in the main .ts file. Trying to run migration with `npx @tailwindcss/upgrade@next` returns the following error: │ Searching for CSS files in the current directory and its subdirectories… │ ↳ Cannot find any CSS files that reference Tailwind CSS. │ Before your project can be upgraded you need to create a CSS file that imports Tailwind CSS or uses `@tailwind`. The error disappears if I rename my .scss stylesheet to .css.
[BUG] `npm install` creates unsync `package-lock.json`
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 When I run `npm install`, the generated `package-lock.json` file isn't synchronized with the `package.json` file. The `npm ci` command fails. If I run `npm install` a second time: the `package-lock.json` file is modified (and synchronized). Expected Behavior `npm install` creates a `package-lock.json` file synchronized. Steps To Reproduce - Create `package.json` with this content: [code block] - `npm install` [code block] - `npm ci` [code block] - `cp package-lock.json package-save.json` - `npm install` [code block] - `diff package-lock.json package-save.json` [code block] The directory at the end with the files `package.json`, `package-lock.json`, `package-save.json`, and the directory `node_modules/`: testcase.zip Environment - npm: 10.0.0 - Node.js: v20.5.1 - OS Name: Ubuntu 22.04.3 LTS - System Model Name: Dell Inspiron - npm config: [code block] Related issues / pull request - https://github.com/npm/cli/issues/4859 - https://github.com/npm/cli/issues/5854 - https://github.com/npm/cli/issues/6378 - https://github.com/npm/cli/issues/7793 - https://github.com/npm/cli/issues/7841 - https://github.com/npm/cli/issues/7847 - https://github.com/npm/cli/issues/8669 - https://github.com/npm/cli/issues/8674 - https://github.com/npm/cli/issues/8718 - https://github.com/npm/cli/issues/8725 -
There will be temporary vite.config.js.timestamp files that have not been cleaned up
Describe the bug When I use Ctrl+C to terminate the process of launching vite, I may leave behind the temporary file vite.config.js.timestamp.xxxxx.mjs By checking the code, I found that the problem may be caused by the loadConfigFromBundledFile method in packages/vite/src/node/config.ts, for esm. When the temporary file is written locally and the process ends, this issue will be triggered, mainly when dynamicImport is time-consuming I am considering whether it is possible to check and clean up temporary files every time the loadConfigFromBundledFile method is executed Reproduction https://stackblitz.com/edit/vitejs-vite-rmx6nh?file=index.html&terminal=dev Steps to reproduce _No response_ System Info [code block] Used Package Manager pnpm 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.