ERROR  [unhandledRejection] read ECONNRESET

Environment

Operating System: Linux
Node Version:     v18.18.2
Nuxt Version:     3.7.4
CLI Version:      3.9.0
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      app, devtools, modules, css, ui, colorMode, postcss
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
Sorry, I can't share code due to corporate law... I hope you understand. 🙏
Describe the bug
When I am programming for a long time nuxt gives me that server error apparently and it is usually tedious because I have to start everything again
 Vite server hmr 17 files in 10811.276ms

 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:41119  10:57:18 AM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)

Additional context
No response
Logs
Vite server hmr 17 files in 10811.276ms

 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:41119  10:57:18 AM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)

Do you have a custom HMR port? Is 41119 the port your main Nuxt dev server is running on?

I believe this one is extremely difficult to reproduce and perhaps an issue somewhere with the local env setup.
Also no custom HMR port defined this side.
This is one of the reasons I have not reported this myself. Even after completely reinstalling node pnpm this issue still occurs.
However @castrogarciajs  perhaps this will help as a short term workaround
✔ Nitro built in 6575 ms                                                                                nitro 11:52:46 PM
ℹ Vite client warmed up in 14274ms                                                                                11:52:47 PM
(node:80030) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)

 ERROR  [unhandledRejection] connect ETIMEDOUT <IP_ADDRESS>:55605                                                                                11:53:36 PM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)

This port will of course change every time you restart the dev server.
My current workaround is to use http://<IP_ADDRESS>:55605/ which works then without any timeout issues
I think this perhaps relates to layers and directed at more complexed nuxt projects.
With a clean install without any 3rd party modules or plugins this doesn't happen.

Environment

Operating System: Darwin
Node Version:     v18.18.1
Nuxt Version:     3.8.0
CLI Version:      3.9.1
Nitro Version:    2.7.0
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      experimental, debug, dev, alias, runtimeConfig, extends, routeRules, srcDir, modules, sitemap, site, plugins, session, i18n, tailwindcss, typescript, build, vite, app, spaLoadingTemplate
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>unplugin-icons/nuxt<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

I have the same problem. I am using a package named node-rfc which is the core cause of the problem. I believe the issue occurs because of the module has some C++ code bindings and hot reloading it will crash the whole application. In my experience, the http server fully freezes not crashes. It will not respond to anything but it will keep listening the port. I was going to create a new issue when I have the time and I am able to reproduce in a minimal project but saw this and wanted to comment.

Forgot to mention the most important part: Code will work the first time I start the server and it will freeze whenever I make a change and save it.

I was able to reproduce the problem in a minimal project. However, node-rfc module requires a licensed system library named nwrfcsdk which contains bunch of .so Linux library files. If you want, I can open the repository to you guys so you can check it out and try. I am not able to do that on StackBlitz or CodeSandbox because of limitations. (StackBlitz doesn't allow uploading files so I cannot upload nwrfcsdk and on CodeSandbox, I got so much trouble and just couldn't do it.) Just tell me usernames to add to the GitHub repository. If you have time, I can do a screen-sharing session too.
I have tried to add the following in nuxt.config.ts which didn't help:
  vite: {
    optimizeDeps: {
      exclude: ['node-rfc'],
    },
  },

(Another problem is that when I run npm run build and try starting with node .output/server/index.mjs, it will give an error with node-rfc and it gets fixed when I manually copy the node_modules/node-rfc into .output/server/node_modules/node-rfc/.)

@danielroe
Hello,
It is impossible to make a reproduction, because it is an error that happens during development and I cannot capture the exact moment of the error. I just have to close everything again.

I think this happens in projects with db connection, I get the same error sometimes.
Does everyone have a db connection in the project?

@productdevbook I don't think this issue is related to the db connection.
In our headless e-commerce stack we are using nitro connecting through to Laravel
Most of our endpoints use useAsyncData catchall to hit nuxt server routes.
Then we use $fetch to send server-side for example using our custom composable.
This was working up until v3.7.0 so I suspect it has something to do with the Nitro 2.6 update.
import type { H3Event } from 'h3'
import { getCookie } from 'h3'

const baseUrl = process.env.NUXT_APP_HUB_BASE_URL
interface INitroApiOptions {
  event: H3Event
  endpoint: string
  action?: string
  requiresAuth?: boolean
  method?: any
  contentType?: string
  query?: any
}

export default function useNitroApi(options: INitroApiOptions, data?: any): Promise<any> {
  const {
    event,
    endpoint,
    action,
    requiresAuth = false,
    method = 'GET',
    contentType = 'application/json',
    query = {},
  } = options
  const headers: any = {
    Accept: contentType,
    'Language-Locale': getCookie(event, 'i18n_redirected'),
    'Content-Type': contentType,
  }
  if (requiresAuth) {
    headers.Authorization = `Bearer ${getCookie(event, 'token') || ''}`
  }

  const opts: any = {
    method,
    headers,
  }

  if (!['show', 'index', 'destroy'].includes(<string>action)) {
    opts.body = data ? JSON.stringify(data) : undefined
    opts.query = query
  }

  return $fetch(`${baseUrl}${endpoint}`, opts)
}

This was working up until v3.7.0 so I suspect it has something to do with the Nitro 2.6 update.

I also had this error in version 3.7 and I was not interested because I was suspicious of the db. now 3.8 has the same error.

@danielroe Could the issue be due to nitro changing to unjs/httpxy?
This does seem to be around the same date 3.7.0 was released.
https://github.com/unjs/nitro/commit/dd8101f1ee2627f8a1fe4cdb39dbf6884ec52a9e
Also this does seem to be where the error is coming from 👀
https://github.com/unjs/httpxy/blob/1f62fffb141e905a398f55eb34bd75366082ca3c/src/middleware/web-incoming.ts#L122

This was the issue and I have found a solution which works perfectly 😁
Try adding this to your nuxt config. On my side there are no more timeouts even after several refreshes!
nitro: {
  devProxy: {
    host: 'localhost',
  },
},

This was the issue and I have found a solution which works perfectly 😁 Try adding this to your nuxt config. On my side there are no more timeouts even after several refreshes!
nitro: {
  devProxy: {
    host: 'localhost',
  },
},

It doesn't work for me (I get problem every time I update the server-side code, 100% reproducible) :/

@unitythemaker Are you using localhost with a default port?
Your error seems to be related more towards node and perhaps node-rfc
What is your current node version?
@productdevbook @castrogarciajs did my solution work for you guys?

@adam-code-labx My version is 20.9.0, I use default port of nuxt

@adam-code-labx My version is 20.9.0, I use default port of nuxt

Ok and you still get an error after adding this to your nuxt config?
nitro: {
  devProxy: {
    host: 'localhost',
  },
},

@unitythemaker Are you using localhost with a default port? Your error seems to be related more towards node and perhaps node-rfc What is your current node version?
@productdevbook @castrogarciajs did my solution work for you guys?

Yeah probably it is because node-rfc and some complicated thing happening with hmr and it breaks from it. However, I am not sure because this is just a guess.
I normally use custom host and port but error occurs even if I use the default host and port (localhost:3000 for me). I tried with both.
unitythemaker@blazingfast ~/Projects/Other/sap_pentest/sap_pentest/frontend (main)
❯ node -v
v18.17.0
unitythemaker@blazingfast ~/Projects/Other/sap_pentest/sap_pentest/frontend (main)
❯ cat package.json | grep nuxt
  "name": "nuxt-app",
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
    "@nuxt/devtools": "latest",
    "@nuxtjs/eslint-module": "^4.1.0",
    "@nuxtjs/i18n": "8.0.0-rc.4",
    "@nuxtjs/sentry": "^7.5.0",
    "@nuxtjs/tailwindcss": "^6.8.0",
    "@pinia/nuxt": "^0.4.11",
    "nuxt": "^3.8.0",

If you ever wanted to check it out my minimal reproduction, I gave you access at here.

If you ever wanted to check out my minimal reproduction, I gave you access at here.

I recommend you update node js to version 20
@adam-code-labx's recommendation is working for me, maybe that's it

If you ever wanted to check out my minimal reproduction, I gave you access at here.

I recommend you update node js to version 20 @adam-code-labx's recommendation is working for me, maybe that's it

I switched to Node v20 now. It is still the same.

@productdevbook ummm thats strange overriding nitro devProxy should have worked for you 🤔
Can you share your nuxt config. Not sure it will make any difference but you can try directly with <IP_ADDRESS> instead of localhost. Also add it at the end of your config.
export default defineNuxtConfig({
  // ... nuxt config
  nitro: {
    devProxy: {
      host: '<IP_ADDRESS>',
    },
  },
})

@productdevbook ummm thats strange overriding nitro devProxy should have worked for you 🤔 Can you share your nuxt config. Not sure it will make any difference but you can try directly with <IP_ADDRESS> instead of localhost. Also add it at the end of your config.
export default defineNuxtConfig({
  // ... nuxt config
  nitro: {
    devProxy: {
      host: '<IP_ADDRESS>',
    },
  },
})

This seems to have solved it for me. Thank you very much!

ERROR  [unhandledRejection] connect ETIMEDOUT <IP_ADDRESS>:55231                                                                            22:39:02
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1247:16)

Same here,
I upgraded Node to v. 20 and it works better but still:
 ERROR  [unhandledRejection] connect ETIMEDOUT <IP_ADDRESS>:61144   at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)
Could anybody help?

I can confirm this is happening to me as well, Node v20 and Nuxt v3.10.0

@Hibrix-net @max-lf
I was able to reproduce the error on a simple application, it seems the problem is the number of requests<EMAIL_ADDRESS>works fine.
https://github.com/nuxt/cli/issues/335
Are you having the same problem?

@Hibrix-net @max-lf I was able to reproduce the error on a simple application, it seems the problem is the number of requests<EMAIL_ADDRESS>works fine. nuxt/cli#335
Are you having the same problem?

I'm only experiencing the latest part of your error logs e.g.:
`ERROR  [unhandledRejection] connect ETIMEDOUT <IP_ADDRESS>:61574                                                   9:49:52 PM
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)`

@Flashantik it seems like it might be a related issue, but (at least for me) I'm not experiencing any slowdown rendering anything. I get this error pretty much 100% of the time when running dev mode. Sometimes immediately, sometimes after a couple of minutes. It seems to possibly be triggered by saving files/hot reloads, but I can't find any consistent pattern.

I can confirm this is happening to me as well, Node v20 and Nuxt v3.10.0

Same here

@Flashantik it seems like it might be a related issue, but (at least for me) I'm not experiencing any slowdown rendering anything. I get this error pretty much 100% of the time when running dev mode. Sometimes immediately, sometimes after a couple of minutes. It seems to possibly be triggered by saving files/hot reloads, but I can't find any consistent pattern.
Edit: and the error is just the last part of the logs, like @Hibrix-net just posted
I'm able to develop for a little bit (usually only a minute or two), but at some point I'll save a file, trigger a hot reload, and then I get this error:
 ✔ Nitro built in 448 ms

  ERROR  [unhandledRejection] socket hang up

   at connResetException (node:internal/errors:787:14)
   at Socket.socketOnEnd (node:_http_client:519:23)
   at Socket.emit (node:events:526:35)
   at endReadableNT (node:internal/streams/readable:1589:12)
   at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

  ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:61372

   at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)

Same here
- Operating System: Linux
- Node Version:     v18.19.0
- Nuxt Version:     3.10.2
- CLI Version:      3.10.1
- Nitro Version:    2.8.1
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      devtools, modules, plugins, i18n, imports, css, quasar, nitro, routeRules, proxy, app, piniaPersistedstate
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -

I have the same issue.
- Operating System: Darwin
- Node Version:     v20.11.0
- Nuxt Version:     3.10.3
- CLI Version:      3.10.1
- Nitro Version:    2.8.1
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      devtools, modules, css, plugins, app, router, auth, devServer, robots, colorMode, pinia, build, typescript, piniaPersistedstate, hooks, runtimeConfig
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>v-wave/nuxt<EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -

Following error after making changes in dev (yesterday):
 ERROR  [unhandledRejection] socket hang up                                                                                3:21:02 AM

  at connResetException (node:internal/errors:787:14)
  at Socket.socketOnEnd (node:_http_client:519:23)
  at Socket.emit (node:events:530:35)
  at endReadableNT (node:internal/streams/readable:1696:12)
  at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:51689                                                                                3:21:02 AM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)

Today again:
 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:54862                                                                                2:49:53 AM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)

 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:54862                                                                                2:52:22 AM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)

 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:54862                                                                                2:52:22 AM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16) (repeated 3 times)

How i run the project?
HOST=0 NODE_TLS_REJECT_UNAUTHORIZED=0 nuxt dev
  devServer: {
    https: {
      key: './ssl/localhost-key.pem',
      cert: './ssl/localhost.pem'
    }
  },

This does not solve my problem
nitro: {
    devProxy: {
      host: '<IP_ADDRESS>',
    },
  },

Not sure why they seem to ignore this issue...

This if almost certainly not a Nuxt issue. It might be a nitro one.
Would you see if you can reproduce this in pure Nitro (reproduction sandbox), and if so, raise there? 🙏

How am I supposed to fit an entire Nuxt project into a Nitro project to reproduce? Has anyone already created an issue on Nitro?

This if almost certainly not a Nuxt issue. It might be a nitro one.
Would you see if you can reproduce this in pure Nitro (reproduction sandbox), and if so, raise there? 🙏

as I already described this in another issue (https://github.com/nuxt/cli/issues/335), it is unlikely that the problem is only in nitro, since if you install<EMAIL_ADDRESS>the nitro version remains fresh<EMAIL_ADDRESS>however the problem goes away. Perhaps there is a problem with how nuxt interacts with nitro?

In that case it is an issue either in nuxt/cli or in how the cli interacts with nitro.
cc: @pi0

Same here. Mac with node latest v18 and v20. The only workaround I found working is downgrading nitropack to v2.8.1. Thanks for the hint.

Same here. Infinite loop, CPU on 100%. I simply unable to start the project.
Environment:

Windows 10
Node @ v20.10.0
Nuxt @ 3.11.1
Nitro @ 2.9.4

ERROR  [unhandledRejection] read ECONNRESET                                                                                11:48:24

 at TCP.onStreamRead (node:internal/stream_base_commons:217:20)

ERROR  [unhandledRejection] write after end                                                                                11:48:24

 at _write (node:internal/streams/writable:479:11)
 at Writable.write (node:internal/streams/writable:494:10)
...

why is this issue closed if this problem is still relevant?
just upgraded my project to the latest version with node 20.10 and facing the same issue
`
ERROR  [unhandledRejection] read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:217:20)
ERROR  [unhandledRejection] write after end         `

Possible solution found:
After some investigation, I found that the culprit was the app.buildAssetsDir variable set in nuxt.config.ts. Simply removing or commenting out this variable resolved the issue for me.

I have the same issue upgrading nuxt  from 3.10.3 -> 3.11.1 as @realityfilter commented, I downgraded my nitropack to 2.8.1 it's solved my problem.
Version & Config

node : v18.19.1
nuxt:  3.11.1
pnpm: 8.15.5
Nuxt only client mode ssr: false

package.json
{
  ...
   "devDependencies": {
       "nuxt": "3.11.1",
    ....
  },
  "pnpm": {
    "overrides": {
      "nitropack": "2.8.1"
    }
  }
}

Environment:
Nuxt v3.11.1
Nitro v2.9.4
Node v20.11.1
Operating System: Windows 10
SSR: True
I don't know how they are related, but if I don't set the app.buildAssetsDir variable in the Nuxt config file, the error ceases.

I do not have a app.buildAssetsDir set. So in my case this is not the culprit.

I do not have a app.buildAssetsDir set. So in my case this is not the culprit.

Do you have any plugins that may be setting that? In my case, nuxt-electron is setting it.

Same here
Here's my config
"nuxt-electron": "^0.7.0",
"nuxt": "^3.11.1",
"vue": "^3.4.21",

I've tried updating Nitro and Nuxt versions as shared above but no solution worked, and this affecting our entire team which also indicates it's not a local config thing.

It's been months that I'm asking myself the exact same thing...

I created a reproduction repo at this url:
https://github.com/JulienChampagnol/ReproduceNuxtElectronError/tree/main
Couldn't make it to work on stackblitz, probably because of the electron window and security concerns I suppose.
Hope this helps!

Thanks for carving time to reproduce this @JulienChampagnol! 🎖
More of a note, we're not using nuxt-electron and yet we can still reproduce the issue. Based on previous answers, I believe others also have different setups that don't necessarily overlap with Electron, making it seem like a base Nuxt thing.
When researching about it, there seem to be a lot of somewhat related issues:
https://github.com/nuxt/image/issues/1158
https://github.com/nuxt/nuxt/issues/24355
https://github.com/nuxt/cli/issues/338
https://github.com/caoxiemeihao/nuxt-electron/issues/71
https://github.com/nuxt/nuxt/issues/26396

Thanks for carving time to reproduce this @JulienChampagnol! 🎖 More of a note, we're not using nuxt-electron and yet we can still reproduce the issue. Based on previous answers, I believe others also have different setups that don't necessarily overlap with Electron, making it seem like a base Nuxt thing.
When researching about it, there seem to be a lot of somewhat related issues: #26396 #25115 #24355 nuxt/image#1158 nuxt/cli#338 caoxiemeihao/nuxt-electron#71

Yes, this isn't related with nuxt-electron it is a generic Nuxt issue.

cc: @pi0

Thanks for carving time to reproduce this @JulienChampagnol! 🎖 More of a note, we're not using nuxt-electron and yet we can still reproduce the issue. Based on previous answers, I believe others also have different setups that don't necessarily overlap with Electron, making it seem like a base Nuxt thing.
When researching about it, there seem to be a lot of somewhat related issues: #26396 #25115 #24355 nuxt/image#1158 nuxt/cli#338 caoxiemeihao/nuxt-electron#71

Once again, I did a super simple project a few months ago without any customizations or plugins. (https://github.com/Flashantik/nuxt-3.10.-slow-dev-mode)  Just nuxt, vue and vue-router (installed by default).
The only thing there is 3998 super simple components. that output a string and add count to the console.
100% error ERROR [unhandledRejection]   in npm run dev

@danielroe Any news about this?

I'm also still waiting for any news. Issue is still there 😬

same，I get problem every time when i refresh browser, 100% reproducible

same，I get problem every time when i refresh browser, 100% reproducible

Yes, HMR never works for me due to this error. I always refresh manually during development.

@danielroe Sorry for the ping, I'm not sure if the following issue is related to that one, but I'm getting  ERROR  [nitro] [unhandledRejection] XXX is not defined where XXX is a global js library (old article here...), and here are the reproducible steps:
1- Create a new Nuxt (v3.11.2) app
2- Register a global js (e.g. Stripe API):
File: nuxt.config.ts:
...
  app: {
    head: {
      charset: 'utf-8',
      viewport: 'width=device-width, initial-scale=1',
      script: [
        {
            'hid':'stripe',
            'src':'https://js.stripe.com/v3/',
            'defer': true
        }
    ]
    },
  },

3- Interact with the API from a page:
File: app.vue:
<script setup>
let isStripe = () => {
  if (Stripe) {
    return new Stripe('pk_test_TYooMQauvdEDq54NiTphI7jx');
  }
  return false;
};
</script>
<template>
  <div>
    <h1 v-if="isStripe()">ok</h1>
    <h2 v-else>No</h2>
  </div>
</template>

P.S. The app will continue to work while the lib is loading, but looks like Nitro is detecting an error.
Let me know if I had to open a new issue for that case.

@bitsnaps That's not valid code on the server. Wrap it in if (import.meta.client) or check with typeof Stripe or access globalThis.Stripe.

Thanks! I thought ClientOnly was the proper way to check for that, but that's for the client side only, we need some time to get used to write Nuxt on the server!

@danielroe could we just have an update, will you or anyone from the core team look at this anytime soon or should the community find a workaround on their own?
Thanks for your answer.

I'm still having issues with this after upgrading. Really frustrating. First npx nuxi@latest upgrade did not want to upgrade from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>so I manually upgraded using pnpm up nuxt --latest and now this issue 😓
Electron

CLI

pnpm nuxi info
------------------------------
- Operating System: Windows_NT
- Node Version:     v18.15.0
- Nuxt Version:     3.11.2
- CLI Version:      3.11.1
- Nitro Version:    2.9.6
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      ssr, css, modules, ionic, vite, nitro
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -
------------------------------

Same error with Vite:
Nuxt: 3.11.2 (ssr true)
Electron: 30.0.2
Nuxt-electron: 0.7.0
Node: 18.18.2
OS: Windows 11

When researching about it, there seem to be a lot of somewhat related issues:
#24355
#25115
#26396
nuxt/image#1158
nuxt/cli#335
nuxt/cli#338
nuxt/cli#346
caoxiemeihao/nuxt-electron#71
nuxt/cli#231
nuxt/cli#232
nuxt/cli#425

I think most of these issues are related to nuxi -> nuxt cli transition that happened with 3.7.
I have been having good luck staying back with 3.7.3 (not sure if I could go update further by staying on nuxi 3.8.4) by means of the below overrides in my package.json:
  "pnpm": {
    "overrides": {
      "nuxi": "3.8.4"
    }
  },
  "overrides": {
    "nuxi": "3.8.4"
  },

While this is not really the solution to this issue, given the wait, if you could, give it a shot. Obviously, this is a trade-off as this will miss other bug fixes that came in the later releases.

Please note, the following are my observations, thoughts, and speculations.

From my observations, there are two distinct problems at play here, neither of which are directly related to Nuxt itself, but rather to NitroPack or the compiler used for Nitro. I was unable to reproduce these issues by merely updating client-side code. However, the behaviors of Nitro and Nuxt seem to diverge significantly when these bugs occur. In Nitro, the server continues to serve requests as usual but stops reloading, running the pre-bug code. In Nuxt, requests stop receiving responses, and a listener keeps the client alive indefinitely, preventing even the Nuxt starting page from loading.

Problem 1: Race Condition
The race condition issue appears more frequently in larger projects due to the time it takes to build the Nitro server. In a medium-scale project, if you press Ctrl+S on a server-side code multiple times in quick succession (4-5 times within a second), it crashes.
To reproduce this, I created a directory named libraries/ at the project root, added a foo.ts file exporting a function that returns "foo", and created an API endpoint that calls this function. As the library is not auto-imported, I manually imported foo from ~/libraries/foo. I'm unsure if this issue affects auto-imported modules or if it relates to modules at all, but I was able to reproduce it consistently by holding down Ctrl+S.

Problem 2: Incompatible Modules
The second issue occurs when using incompatible modules, such as sharp, which relies on C++ libraries or other non-JS files requiring .so files or additional dependencies. The compiler does not account for these, causing hot module reloading to fail when these libraries are imported.

Additional Observations
There seems to be some server-client interaction between the compiler and the running program to perform HMR or a similar process, though this area is less clear to me. The build server likely encounters a fatal error and crashes, leading to the client receiving a read ECONNRESET error due to the forced disconnection. It then retries the connection and fails with connect ETIMEDOUT <IP_ADDRESS>:<ephemeral port>. For security, the server runs on localhost and uses a randomly selected ephemeral port, probably to allow multiple Nuxt dev servers to run on the same machine.

Collaboration Request
If others could confirm or reject these observations, we can work together to pinpoint the exact issues and potentially develop a solution. Your feedback and insights are crucial for us to tackle this problem collaboratively and effectively. Let's pool our knowledge and efforts to fix this issue.

Why this is important for me?
This issue is becoming increasingly critical for me as our projects grow. Particularly because we use Nuxt UI, which renders pages very slowly for some reason. Adding this crashing problem to the mix makes it nearly unbearable to continue developing our projects beyond a certain point. I literally need to wait around 30 seconds between each server-side change, which significantly hampers our development process.

Thank you for your understanding and cooperation.

I have been maintaining few reliable reproductions for this [unhandledRejection] type errors in the nuxt/cli repo from 3.7.4 onwards.
Please refer to these:
nuxt/cli#231
nuxt/cli#232
nuxt/cli#425
Lately in nuxt/cli#425, I have noticed HMR not establishing a connection at all when a vite plugin is added using the addVitePlugin nuxt kit utility.
As I previously mentioned, all these unhandledRejection E-type errors all surfaced only after the nuxi->nuxt/cli transition. This should have ideally been released in an experimental way,so the community could have test and avoided all these issues instead of pushing it on us. Given the random nature of these errors, even ecosystem ci wouldn't have picked these up.

Thank you @TechAkayy. @pi0 and I have discussed reverting the current behaviour in nuxi.

Perhaps it is not clear for everyone, how to fix this prob temporarily with the latest nuxt version.
"overrides": {
    "nitro": "2.8.1 "
  }

this works perfectly.

I run into this problem with a  mono-repository that I just refactored in multiple layers and it only happens when I change code in the server/ folder (middleware or api) and save it.
 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:63003                                                                                5:14:57 PM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1605:16)

It make developing a nightmare as one has to restart nuxi dev everytime one changes the api.

I ran into this problem with a mono-repository that I just refactored in multiple layers and it only happens when I change code in the server/ folder (middleware or api) and save it.
 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:63003                                                                                5:14:57 PM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1605:16)

It makes developing a nightmare as one has to restart nuxi dev everytime one changes the api.
Is there a way to debug this?

npx nuxi@latest upgrade

Still getting the problem even with npx nuxi@latest upgrade.
Each time I save a /server/api/*.ts file:
Nuxi version: 3.12.0
Nuxt version: 3.12.3
logs

ERROR  [unhandledRejection] socket hang up                                                                                11:49:45 AM

  at Socket.socketOnEnd (node:_http_client:526:23)
  at Socket.emit (node:events:532:35)
  at endReadableNT (node:internal/streams/readable:1696:12)
  at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:57197                                                            11:50:11 AM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)

Hi again, I fixed it with disabling all prerender:
export default defineNuxtConfig({
	...
	routeRules: {
		"/": { prerender: false },
		"/api/search.json": { prerender: false },
		"/docs": { redirect: "/docs/getting-started", prerender: false },
	},
	...
});

I ran into this problem with a mono-repository that I just refactored in multiple layers and it only happens when I change code in the server/ folder (middleware or api) and save it.
 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:63003                                                                                5:14:57 PM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1605:16)

It makes developing a nightmare as one has to restart nuxi dev everytime one changes the api.
Is there a way to debug this?

https://github.com/nuxt/cli/issues/335#issuecomment-2036387675
now i found only 2 solutions.

use<EMAIL_ADDRESS>- last version without bug
use bun instead node

Well, we are still waiting for the next version. I really hope that this will be fixed in nuxt@4

I ran into this problem with a mono-repository that I just refactored in multiple layers and it only happens when I change code in the server/ folder (middleware or api) and save it.
 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:63003                                                                                5:14:57 PM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1605:16)

It makes developing a nightmare as one has to restart nuxi dev everytime one changes the api.
Is there a way to debug this?

nuxt/cli#335 (comment)
now i found only 2 solutions.

use<EMAIL_ADDRESS>- last version without bug
use bun instead node

Well, we are still waiting for the next version. I really hope that this will be fixed in nuxt@4

For me the issue was fixed with https://github.com/nuxt/content/issues/2691

I ran into this problem with a mono-repository that I just refactored in multiple layers and it only happens when I change code in the server/ folder (middleware or api) and save it.
 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:63003                                                                                5:14:57 PM

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1605:16)

It makes developing a nightmare as one has to restart nuxi dev everytime one changes the api.
Is there a way to debug this?

nuxt/cli#335 (comment)
now i found only 2 solutions.

use<EMAIL_ADDRESS>- last version without bug
use bun instead node

Well, we are still waiting for the next version. I really hope that this will be fixed in nuxt@4

how would you use bun instead of node

@shai-raz , install it and then run bun --bun run dev
PS: If you plan to use @supabase/nuxt, be aware that bun has a bug with it and doesn't work (link)

@shai-raz , install it and then run bun --bun run dev PS: If you plan to use @supabase/nuxt, be aware that bun has a bug with it and doesn't work (link)
Somehow, I don't have the problem on AMD CPU laptops; it only occurs on Intel ones.

Thanks, that actually makes it work, which is amazing:))
But now there's another issue that nuxt devtools won't work :<

We are also facing this issue in a monorepo with a payload cms backend, a nuxt frontend and a nuxt module for components.  Nothing overly complicated, but half the time the frontend simply won’t work.
None of the workarounds posted here seem to have any impact.
We are getting all sorts of errors, at random times. Sometimes after navigating, sometimes after a hard refresh. It’s basically impossible to work on the project at all in this state.

I’d be happy to give the Nuxt team access to our repo and help set up a local environment to reproduce the problems we are facing. @danielroe @pi0 please let me know if this would be of interest!

One source of the problems we are facing is an icon component that pulls in a large icon library with import.meta.glob. I'm guessing nuxt is not able to handle this amount of async components while in dev mode.
<template>
  <icon-component class="icon-renderer" />
</template>

<script lang="ts" setup>
import { defineAsyncComponent, type ComponentPublicInstance } from 'vue'
import { filename } from 'pathe/utils'

interface IconRenderer {
  name: string
  weight?: 400 | 500
}

const props = withDefaults(defineProps<IconRenderer>(), {
  weight: 400,
})

const IconComponent = defineAsyncComponent({
  loader: async () => {
    const glob = import.meta.glob<{ default: ComponentPublicInstance }>(
      `../assets/icons/*-(400|500).svg`,
      {
        eager: true,
      }
    )

    const icons = Object.fromEntries(
      Object.entries(glob).map(([key, value]) => [filename(key), value.default])
    )

    const name = `${props.name}-${props.weight}`
    const icon = icons[name]

    return icon
  },
})
</script>

Same issue,
With node 18.18, 20.17 and 22.70
and ussing npm run dev, yarn run dev and bun run dev

Same here, still facing this constantly after roughly 3-4 code changes and reloads

@manniL Hello Alexander, I wanted to ask if this issue is already solved?

Just sharing what my problem was, it might be something entirely different for you: I was running Nuxt in dev mode, but the connection was being passed through Caddy as a reverse proxy (to have a local domain with SSL). Caddy (and Nginx too, for that matter) was defaulting to HTTP 2, but Nuxt/Nitro/h2 only supports HTTP 1.1 which. So when running in dev mode, the sheer number of modules being requested overloaded the HTTP 1.1 connection which is limited to a small number of concurrent requests while HTTP 2 is handling this differently. So I configured Caddy to only use HTTP 1.1 and it works.

I do nothing special, but with intellij, Chrome, Typescript and Vue Language Services running, my 16GB memory is used up almost entirely.
Maybe that's related but I'd expect a different error in this case

Just sharing what my problem was, it might be something entirely different for you: I was running Nuxt in dev mode, but the connection was being passed through Caddy as a reverse proxy (to have a local domain with SSL). Caddy (and Nginx too, for that matter) was defaulting to HTTP 2, but Nuxt/Nitro/h2 only supports HTTP 1.1 which. So when running in dev mode, the sheer number of modules being requested overloaded the HTTP 1.1 connection which is limited to a small number of concurrent requests while HTTP 2 is handling this differently. So I configured Caddy to only use HTTP 1.1 and it works.

I'm on HTTP 1.1 and still having issues.

Hello, I've also had this problem for 2 months, it's really annoying to have to delete .nuxt and restart my server 50 times a day every time I change things in the server part of Nuxt.
Having said that, I love developing with Nuxt, thank you so much for all the work you've done on this Framework.
Here's the error I get a lot:
FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal
----- Native stack trace -----

 1: 0x102f70b18 node::OnFatalError(char const*, char const*) [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
 2: 0x1030fa5d4 v8::api_internal::ToLocalEmpty() [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
 3: 0x102f92f5c node::(anonymous namespace)::Parser::Proxy<int (node::(anonymous namespace)::Parser::*)(), &node::(anonymous namespace)::Parser::on_message_begin()>::Raw(llhttp__internal_s*) [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
 4: 0x103e94de8 llhttp__internal__run [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
 5: 0x103e94c80 llhttp__internal_execute [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
 6: 0x102f9291c node::(anonymous namespace)::Parser::Execute(char const*, unsigned long) [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
 7: 0x102f92764 node::(anonymous namespace)::Parser::OnStreamRead(long, uv_buf_t const&) [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
 8: 0x103042964 node::LibuvStreamWrap::OnUvRead(long, uv_buf_t const*) [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
 9: 0x103043098 node::LibuvStreamWrap::ReadStart()::$_1::__invoke(uv_stream_s*, long, uv_buf_t const*) [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
10: 0x10394e44c uv__stream_io [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
11: 0x103955d50 uv__io_poll [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
12: 0x10394423c uv_run [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
13: 0x102e9d6f0 node::SpinEventLoopInternal(node::Environment*) [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
14: 0x103026b60 node::worker::Worker::Run() [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
15: 0x103029db8 node::worker::Worker::StartThread(v8::FunctionCallbackInfo<v8::Value> const&)::$_3::__invoke(void*) [/Users/redacted/.nvm/versions/node/v20.15.0/bin/node]
16: 0x191a6f2e4 _pthread_start [/usr/lib/system/libsystem_pthread.dylib]
17: 0x191a6a0fc thread_start [/usr/lib/system/libsystem_pthread.dylib]

 ERROR  [unhandledRejection] socket hang up                                                                                21:12:52

  at Socket.socketOnEnd (node:_http_client:524:23)
  at Socket.emit (node:events:531:35)
  at endReadableNT (node:internal/streams/readable:1696:12)
  at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:64865                                                                                21:12:52

  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1606:16)

I'm having the same error. it's making me go nuts....

Same here with Nuxt 3.13.2

@warflash could the workaround available label be removed? The error is still there, and based on the folks coming here so frequently, it seems that doesn't work for most people. I didn't work on our project, at least.

This is indeed an extremely annoying bug which have been with us for almost a year now. I've tried all the workarounds, and so far no luck. Including the errors mentioned already, I also get some other seemingly related errors messages:
#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0x16fbae2a8
----- Native stack trace -----
 1: 0x10511ab88 node::NodePlatform::GetStackTracePrinter()::$_3::__invoke() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 2: 0x1061d2274 V8_Fatal(char const*, ...) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 3: 0x10577c1c0 v8::internal::InstructionStreamMap::~InstructionStreamMap() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 4: 0x105765074 v8::internal::CpuProfiler::~CpuProfiler() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 5: 0x10526e954 v8::CpuProfiler::Dispose() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 6: 0x10aae2ecc FreeAddonData(napi_env__*, void*, void*<EMAIL_ADDRESS> 7: 0x105085018 void napi_env__::CallIntoModule<void node_napi_env__::CallFinalizer<true>(void (*)(napi_env__*, void*, void*), void*, void*)::'lambda'(napi_env__*)&, void node_napi_env__::CallbackIntoModule<true, void node_napi_env__::CallFinalizer<true>(void (*)(napi_env__*, void*, void*), void*, void*)::'lambda'(napi_env__*)>(void node_napi_env__::CallFinalizer<true>(void (*)(napi_env__*, void*, void*), void*, void*)::'lambda'(napi_env__*)&&)::'lambda'(napi_env__*, v8::Local<v8::Value>)>(void node_napi_env__::CallFinalizer<true>(void (*)(napi_env__*, void*, void*), void*, void*)::'lambda'(napi_env__*)&, void node_napi_env__::CallFinalizer<true>(void (*)(napi_env__*, void*, void*), void*, void*)::'lambda'(napi_env__*)&&) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 8: 0x10508103c node_napi_env__::CallFinalizer(void (*)(napi_env__*, void*, void*), void*, void*) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 9: 0x105066644 non-virtual thunk to v8impl::RefBase::Finalize() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
10: 0x105080e24 node_napi_env__::DeleteMe() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
11: 0x10500bb10 node::CleanupQueue::Drain() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
12: 0x105058024 node::Environment::RunCleanup() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
13: 0x104fe5028 node::FreeEnvironment(node::Environment*) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
14: 0x10516e2f8 node::worker::Worker::Run() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
15: 0x105171838 node::worker::Worker::StartThread(v8::FunctionCallbackInfo<v8::Value> const&)::$_3::__invoke(void*) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
16: 0x182489034 _pthread_start [/usr/lib/system/libsystem_pthread.dylib]
17: 0x182483e3c thread_start [/usr/lib/system/libsystem_pthread.dylib]
 ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:56115                                                                                10:04:33 AM
  at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)

#
# Fatal error in , line 0
# Check failed: node->IsInUse().
#
#
#
#FailureMessage Object: 0x17a54e258
----- Native stack trace -----
 1: 0x1027feb88 node::NodePlatform::GetStackTracePrinter()::$_3::__invoke() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 2: 0x1038b6274 V8_Fatal(char const*, ...) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 3: 0x102a990fc v8::internal::GlobalHandles::NodeSpace<v8::internal::GlobalHandles::Node>::Release(v8::internal::GlobalHandles::Node*) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 4: 0x102e68f5c v8::internal::WeakCodeRegistry::Clear() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 5: 0x102e49224 v8::internal::CpuProfiler::DisableLogging() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 6: 0x102e49074 v8::internal::CpuProfiler::~CpuProfiler() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 7: 0x102952954 v8::CpuProfiler::Dispose() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 8: 0x10841eecc FreeAddonData(napi_env__*, void*, void*<EMAIL_ADDRESS> 9: 0x102769018 void napi_env__::CallIntoModule<void node_napi_env__::CallFinalizer<true>(void (*)(napi_env__*, void*, void*), void*, void*)::'lambda'(napi_env__*)&, void node_napi_env__::CallbackIntoModule<true, void node_napi_env__::CallFinalizer<true>(void (*)(napi_env__*, void*, void*), void*, void*)::'lambda'(napi_env__*)>(void node_napi_env__::CallFinalizer<true>(void (*)(napi_env__*, void*, void*), void*, void*)::'lambda'(napi_env__*)&&)::'lambda'(napi_env__*, v8::Local<v8::Value>)>(void node_napi_env__::CallFinalizer<true>(void (*)(napi_env__*, void*, void*), void*, void*)::'lambda'(napi_env__*)&, void node_napi_env__::CallFinalizer<true>(void (*)(napi_env__*, void*, void*), void*, void*)::'lambda'(napi_env__*)&&) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
10: 0x10276503c node_napi_env__::CallFinalizer(void (*)(napi_env__*, void*, void*), void*, void*) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
11: 0x10274a644 non-virtual thunk to v8impl::RefBase::Finalize() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
12: 0x102764e24 node_napi_env__::DeleteMe() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
13: 0x1026efb10 node::CleanupQueue::Drain() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
14: 0x10273c024 node::Environment::RunCleanup() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
15: 0x1026c9028 node::FreeEnvironment(node::Environment*) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
16: 0x1028522f8 node::worker::Worker::Run() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
17: 0x102855838 node::worker::Worker::StartThread(v8::FunctionCallbackInfo<v8::Value> const&)::$_3::__invoke(void*) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
18: 0x182489034 _pthread_start [/usr/lib/system/libsystem_pthread.dylib]
19: 0x182483e3c thread_start [/usr/lib/system/libsystem_pthread.dylib]

  #  /Users/jbh/.nvm/versions/node/v20.17.0/bin/node[71714]: void node::AsyncWrap::EmitTraceEventDestroy() at ../src/async_wrap.cc:560
  #  Assertion failed: "Unreachable code reached" __VA_OPT__(": ")

----- Native stack trace -----

 1: 0x10064b0d4 node::Assert(node::AssertionInfo const&) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 2: 0x101b4b2f8 node::AsyncWrap::EmitTraceEventDestroy() (.cold.1) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 3: 0x10058ae88 node::AsyncWrap::~AsyncWrap() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 4: 0x100588e28 node::AsyncWrap::~AsyncWrap() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 5: 0x10064eda8 node::fs::FileHandle::~FileHandle() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 6: 0x100949cbc v8::internal::GlobalHandles::InvokeFirstPassWeakCallbacks() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 7: 0x1009a8eb0 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 8: 0x1009a6dc0 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
 9: 0x1009b0534 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
10: 0x1009be2c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
11: 0x1006ad234 node::PerIsolatePlatformData::RunForegroundTask(std::__1::unique_ptr<v8::Task, std::__1::default_delete<v8::Task>>) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
12: 0x1006abf8c node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
13: 0x10101f550 uv__async_io [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
14: 0x101031628 uv__io_poll [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
15: 0x10101fb14 uv_run [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
16: 0x1005756f0 node::SpinEventLoopInternal(node::Environment*) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
17: 0x100702278 node::worker::Worker::Run() [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
18: 0x100705838 node::worker::Worker::StartThread(v8::FunctionCallbackInfo<v8::Value> const&)::$_3::__invoke(void*) [/Users/jbh/.nvm/versions/node/v20.17.0/bin/node]
19: 0x182489034 _pthread_start [/usr/lib/system/libsystem_pthread.dylib]
20: 0x182483e3c thread_start [/usr/lib/system/libsystem_pthread.dylib]

Nuxt 3.14.159, node 20.17.0

It may just be an chokidar issue and not Nuxt related. But overall it seems a lot of people have it, and it's not really addressed right now.
See  https://github.com/paulmillr/chokidar/issues/1237
I wonder why Mayne people do not have this issue?
Is it related to the OS, Windows Version, or Node? Is something else interfering?
Is it our setup?

Hi, i have same problem , every thing was working good .... until err shows up on projuct that im working on , even after i created a new nuxt projuct and install node v20 lts and delete every thing / cache .. stil facing same ERR
Nuxt 3.14.159 with Nitro 2.10.4

I have this error since day one of my project which was about 3 months ago. I tried with a complete minimum app in docker container. Sometimes I can get this to work, but usually when I go back to project I am blocked with this bug. Already wasted few days for this issue. Tried latest version of nuxt and older ones too. Currently using 3.12.1 because it was working once but now its not (maybe I was just lucky).
Its really annoying. I think its a Nitro problem and might be related to incorrect/missing cleaning up in Docker environment?

It is actually an issua that will be resolved faster the more reproduction example codes you send.

I prepared minimal code with newest with these dependencies using nuxi init:
https://github.com/poziminski/nuxt-bug-reproduction
Latest versions in package.json:
{
    "nuxt": "^3.14.1592",
    "vue": "latest",
    "vue-router": "latest"
  }

It is a docker-compose-dev.yml config + 2 services:

nginx
web (nuxt 3 app)

Nginx lets me access app via http://localhost/web/
To run:
docker-compose -f docker-compose-dev.yml up --force-recreate
Worth noticing is that running project locally (without Docker) works fine.
My setup: Macbook M2 + Macos 14.4.1 (23E224)
nuxt_bug_reproduction-web-1    | [nitro] ✔ Nuxt Nitro server built in 600 ms
nuxt_bug_reproduction-web-1    | ℹ Vite client warmed up in 1ms
nuxt_bug_reproduction-web-1    | ℹ Vite server warmed up in 629ms
nuxt_bug_reproduction-web-1    |
nuxt_bug_reproduction-web-1    |  ERROR  [unhandledRejection] socket hang up
nuxt_bug_reproduction-web-1    |
nuxt_bug_reproduction-web-1    |   at connResetException (node:internal/errors:720:14)
nuxt_bug_reproduction-web-1    |   at Socket.socketOnEnd (node:_http_client:525:23)
nuxt_bug_reproduction-web-1    |   at Socket.emit (node:events:529:35)
nuxt_bug_reproduction-web-1    |   at endReadableNT (node:internal/streams/readable:1400:12)
nuxt_bug_reproduction-web-1    |   at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
nuxt_bug_reproduction-web-1    |
nuxt_bug_reproduction-web-1    |
nuxt_bug_reproduction-web-1    |
nuxt_bug_reproduction-web-1    |  ERROR  [unhandledRejection] connect ECONNREFUSED <IP_ADDRESS>:44719
nuxt_bug_reproduction-web-1    |
nuxt_bug_reproduction-web-1    |   at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)

Maybe the issue is related to the way nitro stores its workers data? in nitro.json

I have recently started facing this issue

Here are the versions I am using:

Node v22.12.0
Nuxt v3.14.1592
Nuxt Content v2.13.4
No docker, No external db. Just a static website with markdown and json data being fetched from nuxt-content.

I solved the problem and now I have it working just fine. Just in case it helps someone, I'll leave my project package.json
{
    "name": "nuxt-app",
    "private": true,
    "type": "module",
    "scripts": {
        "build": "nuxt build",
        "dev": "nvm use; nuxt dev",
        "generate": "nuxt generate",
        "preview": "nuxt preview",
        "postinstall": "nuxt prepare",
        "lint": "eslint . --fix"
    },
    "devDependencies": {
        "@nuxt/content": "npm:@nuxt/content-edge@latest",
        "@nuxt/devtools": "latest",
        "@nuxt/eslint": "^0.3.13",
        "@nuxt/types": "^2.18.1",
        "@nuxtjs/i18n": "^8.3.1",
        "@pinia-plugin-persistedstate/nuxt": "^1.2.1",
        "@types/busboy": "^1.5.4",
        "@types/multer": "^1.4.11",
        "@types/nodemailer": "^6.4.16",
        "eslint": "^9.4.0",
        "eslint-plugin-prettier": "^5.1.3",
        "nuxt": "^3.11.1",
        "prettier": "^3.3.0",
        "sequelize-cli": "^6.6.2",
        "ts-node": "^10.9.2",
        "vue": "^3.3.4",
        "vue-router": "^4.2.5"
    },
    "dependencies": {
        "@mdi/font": "^7.4.47",
        "@types/bcrypt": "^5.0.2",
        "@types/express": "^4.17.21",
        "@types/jsonwebtoken": "^9.0.6",
        "@vue-email/components": "^0.0.21",
        "@vue-email/html": "^0.0.3",
        "@vue-email/render": "^0.0.9",
        "bcrypt": "^5.1.1",
        "buffer": "^6.0.3",
        "busboy": "^1.6.0",
        "cloudinary": "^2.2.0",
        "connect": "^3.7.0",
        "date-fns": "^3.6.0",
        "jsonwebtoken": "^9.0.2",
        "mercadopago": "^2.0.15",
        "multer": "^1.4.5-lts.1",
        "mysql2": "^3.10.3",
        "nodemailer": "^6.9.16",
        "nuxi": "^3.11.1",
        "pg-hstore": "^2.3.4",
        "pinia": "^2.1.7",
        "pinia-plugin-persistedstate": "^3.2.1",
        "sass": "^1.77.2",
        "sequelize": "^6.37.3",
        "sequelize-auto-migrations": "^1.0.3",
        "slugify": "^1.6.6",
        "vuetify": "^3.7.3"
    }
}

it works.

the issue on our end seems to be a segmentation fault when terminating the worker. If I comment out the following line in nitropack/dist/core/index.mjs the error doesn't occur anymore:
https://github.com/nitrojs/nitro/blob/f982f99fbab57d3bfc51d155f5fff73c7ab2a4ec/src/core/dev-server/server.ts#L94


 Add Legacy water colors for water, flowing water, and underwater fog

Legacy Console Edition used water colors from Bedrock Edition, not Java Edition. The Environmental Water pack I released repackages these colors in the OptiFine/Colormatic format, but it is not ideal because you have to use a lookup table to match biome ID to name.
You could look in the Console Aspects Updated Textures biomes_client, which stores each biome water color in hex, but Bedrock uses old (pre-1.13) biome names, so there may be slight confusion (for example, "mega_taiga" is now "old_growth_pine_taiga" on Java).

This one might be important since BedrockWaters which had water colors is known to have issues with resources reloading.

Added in 1.3

Added in 1.3


Get selected images

Hello, MWPhotoBrowser is  a wonderful framework.but in some case, it has something to improve.such as, when I selected some images, how to get the seleted image object in main viewcontroller?? I didn't find any convionince method, can you provide a solution ....

Hello, MWPhotoBrowser is a wonderful framework.but in some case, it has something to improve.such as, when I selected some images, how to get the seleted image object in main viewcontroller?? I didn't find any convionince method, can you provide a solution ....

@suqiang @JaydeepPatel   I've also met the same problem.....Have you found any solutions, please?

I used anthoer one.

Fine....I've just found a closed issue here. Just past it here in case anyone need.

https://github.com/pjk1129/JKImagePicker

I'm not sure if this is what you are asking, but if you need to access the UIImage in a MWPhoto object (as in #421), you can call the protocol method underlyingImage which is defined in MWPhotoProtocol.h.
Here's how I do it in my MWPhotoBrowser delegate. _avatars is an NSArray of MWPhoto objects, and I pass the selected image to RSKImageCropViewController.
- (void)photoBrowser:(MWPhotoBrowser *)photoBrowser actionButtonPressedForPhotoAtIndex:(NSUInteger)index {
    MWPhoto * mwPhoto = [_avatars objectAtIndex:index];
    RSKImageCropViewController *cropVC = [[RSKImageCropViewController alloc] initWithImage:[mwPhoto underlyingImage]];
    cropVC.view.backgroundColor = [UIColor blackColor];
    cropVC.delegate = self;

    [self.navigationController pushViewController:cropVC animated:YES];
}

@eliburke Thanks for your suggestion. I did check the underlyingImage method, but it returned me the original image. I want to use the thumbnails as preview showed in my collectionview. Here's my code, and please tell me if you've got a better idea. :)
- (NSMutableArray *)thumbsFowCollectionView:(NSArray *)assets selections:(NSArray *)selections
{
    if (assets.count != selections.count) return nil;

    NSMutableArray *result = [NSMutableArray array];

    for (int i = 0; i < selections.count; i++) {
        if ([selections[i] boolValue]) {
            UIImage *img = [self getAssetThumbnail:assets[i]];
            [result addObject:img];
        }
    }
    return result;
}

- (UIImage *)getAssetThumbnail:(PHAsset *)asset
{
    PHImageManager *imgManager = [PHImageManager defaultManager];
    PHImageRequestOptions *option = [[PHImageRequestOptions alloc] init];
    option.synchronous = YES;
    UIImage *thumbnail = [[UIImage alloc] init];
    __block UIImage *weakImg = thumbnail;
    [imgManager requestImageForAsset:asset targetSize:CGSizeMake(100, 100) contentMode:PHImageContentModeAspectFit options:option resultHandler:^(UIImage * _Nullable result, NSDictionary * _Nullable info) {
        weakImg = result;
    }];

    return weakImg;
}

And I get _thumbsArray in photoBrowserDidFinishModalPresentation: like this.
- (void)photoBrowserDidFinishModalPresentation:(MWPhotoBrowser *)photoBrowser {
    // If we subscribe to this method we must dismiss the view controller ourselves
    NSLog(@"Did finish modal presentation");
    _thumbsForCV = [self thumbsFowCollectionView:_assets selections:_selections];

    NSLog(@"-------_thumbsForCV:  %@",_thumbsForCV);
    [self dismissViewControllerAnimated:YES completion:NULL];

    [_thumbCollectionView reloadData];
}

thanks..no my best try,sorry.
p.j.radadiya
On Wed, May 11, 2016 at 8:41 AM, Calios<EMAIL_ADDRESS>wrote:

@eliburke https://github.com/eliburke Thanks for your suggestion. I did
check the underlyingImage method, but it returned me the original image.
I want to use the thumbnails as preview showed in my collectionview. Here's
my code, and please tell me if you've got a better idea. :)

(NSMutableArray *)thumbsFowCollectionView:(NSArray *)assets selections:(NSArray *)selections
{
if (assets.count != selections.count) return nil;
NSMutableArray *result = [NSMutableArray array];
for (int i = 0; i < selections.count; i++) {
if ([selections[i] boolValue]) {
UIImage *img = [self getAssetThumbnail:assets[i]];
[result addObject:img];
}
}
return result;
}

(UIImage *)getAssetThumbnail:(PHAsset *)asset
{
PHImageManager *imgManager = [PHImageManager defaultManager];
PHImageRequestOptions *option = [[PHImageRequestOptions alloc] init];
option.synchronous = YES;
UIImage *thumbnail = [[UIImage alloc] init];
__block UIImage *weakImg = thumbnail;
[imgManager requestImageForAsset:asset targetSize:CGSizeMake(100, 100) contentMode:PHImageContentModeAspectFit options:option resultHandler:^(UIImage * _Nullable result, NSDictionary * _Nullable info) {
weakImg = result;
}];
return weakImg;
}

And I get _thumbsArray in photoBrowserDidFinishModalPresentation: like
this.

(void)photoBrowserDidFinishModalPresentation:(MWPhotoBrowser *)photoBrowser {
// If we subscribe to this method we must dismiss the view controller ourselves
NSLog(@"Did finish modal presentation");
_thumbsForCV = [self thumbsFowCollectionView:_assets selections:_selections];
NSLog(@"-------_thumbsForCV:  %@",_thumbsForCV);
[self dismissViewControllerAnimated:YES completion:NULL];
[_thumbCollectionView reloadData];
}

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/mwaterfall/MWPhotoBrowser/issues/429#issuecomment-218350843

@CaliosD I'm not certain I understand what you want.

Are you trying to provide thumbnails for MWPhotoBrowser? There is a delegate:
- (id <MWPhoto>)photoBrowser:(MWPhotoBrowser *)photoBrowser thumbPhotoAtIndex:(NSUInteger)index;
Capture all the thumbnails MWPhotoBrowser creates? If you subclass MWPhotoBrowser and import "MWPhotoBrowserPrivate.h" I am pretty sure you can write a method to return the private variable _thumbPhotos.

@eliburke Thanks for your attention first. :)

I want to transfer thumbnails of MWPHotoBrowser to UIImage, which I can show in my custom collectionview. For example, in controller A, I tap the "add" button, and push to MWPhotoBrowser to select images, realize its delegate - (void)photoBrowser:(MWPhotoBrowser *)photoBrowser photoAtIndex:(NSUInteger)index selectedChanged:(BOOL)selected and save the selections. Then tap the "done" button in MWPhotoBrowser and back to controller A. Now I want to show the images that are just selected. So, this is my use case.
I've updated the logic a little and it works fine for me at present. :)


Please add Typescript Type Definition supports

This components are awesome, I'm develop tuya cloud based home control app with react native typescript, I hope this awesome kit can use in typescript. thank you

This matter is under planning, thank you for submitting your proposal.

check 2.0.0-rc.6


action_on_self_use?

I'm asking if we could get a bi entity action when an entity interacts with the entity with the power as opposed to if the player interacts with an entity if this is not already a thing.

Added in the form of ActionOnBeingUsedPower


Add distinct() method

User can do $db->distinct()->select(...) to do a distinct selection (add DISTINCT to the query).
Used code from the post by @darre4nbrown in issue #113.
This simple to use and a crucial feature for interacting with a database.

:+1:

:+1:
You should reset distinct mode after executing a query, however.

I like this feature.
I am thinking about if I provide code $medoo->distinct()->count('account', 'age'), what SQL should be generated.
SELECT DISTINCT COUNT("age") FROM "account"

or
SELECT COUNT(DISTINCT "age") FROM "account"

@SyuTingSong it should be SELECT DISTINCT... since no specific column is given. An overload like $medoo->distinct('age')->... for specifying a specific the distinct column(s) would be great.

@Sebb767 I merged @sargunster's work to my fork. And I implement auto-reset and SELECT COUNT(DISTINCT "age") FROM "account" additionally.
I guess distinct($column) is inconsistent with medoo's column function way (e.g. COUNT, MAX, MIN, AVG...). The distinct method is more likely a decorator.
You can review my code in commit b7eea7ef6f223da800e52198a1098cdf4f21e036 . Since my fork has merged some others' pull-requests which catfan ignored. I won't create new pull-request here.
Feel free to use and discuss my code.

:+1:

:thumbsup:

this would be great

Upvoted.

+1

@SyuTingSong any plan for implementing this? I am really looking forward to this method.

Missing this piece

Seems like this project is no longer maintained, closing this old PR to clear my queue.


Publish Dockerfile to GitHub Container Registry

Feature Request
Publish the Dockerfile that is in .devcontainer/Dockerfile to the GitHub Container Registry (GHCR).
Make sure to turn on caching, and schedule a no-cached run so packages are up to date.
Description
Publishing the Dockerfile to the GHCR will allow us to tell users to run docker run algorithm-archivists/aaa-langs -v $pwd:/root (or something similar) to be able to use any of the languages that the algorithm archive supports.
This will enable reviewers to run languages that they potentially do not have installed. Additionally, it will allow us to run our automated testing for Scons (#906) with all languages in our pipelines.

For Algorithm Archive Developers

[x] This feature can be added to the Master Overview (if it cannot be, explain why in a comment below -- lack of technical expertise, not relevant to the scope of this project, too ambitious)
[x] There is a timeline for when this feature can be implemented
[x] The feature has been added to the Master Overview
[x] The feature has been implemented (#938)

Closed in #938


Conflict with android.support.v7.app.AlertDialog

Hi all and thank you for your work.
I use android.support.v7.app.AlertDialog in my application.
It want not compile when I add compile 'com.github.paolorotolo:appintro:4.1.0 to my app gradle.
the error is:
Error:Failed to resolve: com.android.support:appcompat-v7:24.2.1
crdlt.

Issue template ignored....closing.

If you wish to have this reopened, please follow the template, and print full errors.


Specify v0.2 tag for google-github-actions/setup-gcloud

Specify the version tag v0.2v0.2.1 instead of the master for google-github-actions/setup-gcloud,
because the current master has a breaking change.
Signed-off-by: Masayuki Ishii<EMAIL_ADDRESS>

It seems that v0.2 is maintained as a branch and it is currently pointing to the
same commit as v0.2.1.  Why don't we use v0.2?
https://github.com/google-github-actions/setup-gcloud/tags

@ymmt2005
Thank you. I fixed the tag.


Asakatsu - Yoga and Exercising

Starting a new challenge! I am going to exercise and do yoga regularly.

Let's start together and keep each other accountable, Avie Chan! we got this🔥🔥🔥🔥


Batch update

Analyse validate on blur too

Validation debounce should be optional and have a prop to define the time to wait


An extra +1 is added when not necessary for Agent.Connect()

For numbers that aren't already prefixed with a +, the streams api seems to automatically prepend the us country code +1 to the phone number. For example - when calling agent.connect from the agent API with the phone number endpoint,<PHONE_NUMBER>, the call is made to +11123456789. Is there any way around this?

Normalise the number on your end before hitting the agent.connect action. Give this lib a go: https://www.npmjs.com/package/libphonenumber-js


Some ideas  ( out of office, config script, push mail )

Perhaps a nice feature to have is an out of office feature.
And a simple script you can run in the terminal to manage the account creation, editing , removal out of office. Although both are minor I would love to contribute to this repo and have thought of writing such a solution myself for a non dockerized mailserver setup I currently run in production. ( but plan to move to the base of this docker solution )
Auto responders would be nice:
https://www.howtoforge.com/how-to-set-up-a-postfix-autoresponder-with-autoresponse
Probably overkill:
https://www.mnxsolutions.com/scripts/postfix-dovecot-user-admin-script.html
Push email to clients:
http://mishmashmoo.com.au/blog/?p=208

I close this issue and wait for PR if someone wants to add some new features without doing something overkill.


Improve documentation navigation

Before undergoing a substantial to docs or the codebase, please open up an issue to make sure it's a desired change.

I'd like to improve the navigation in these ways:

If the user clicks on Read the docs on the homepage, he/she will be redirect to https://blocks-ui.com/docs. I'd like to redirect to https://blocks-ui.com/getting-started/ as the starting point for the documentation.
Highlight the currently active page in the side navigation.
Add proper WIP description to the pages missing content.
Add prev/next navigation to the pages at the  bottom. (Helps to get to the next docs page - especially on mobile.)

Would that be okay?

That would be great @donaldpipowitch!


All Platforms Exporting Error

Godot version
3.3.4 stable
System information
Windows 10
Issue description
Whenever I try to export any project at all, it gives me an error, and the file it creates (aside from the pack file) is empty. I've tried to reinstall godot and the export templates again and again, but it seems to not work. I also don't have another device to use godot on, so I'm not sure if this is just my specific device.
The error that keeps repeating in the console when exporting:
drivers/windows/file_access_windows.cpp:315 - Condition "fwrite(p_src, 1, p_length, f) != (size_t)p_length" is true.
Steps to reproduce
I'm not really sure how to reproduce the issue, as it seems to stem from my actual device. It seems to happen on any project I have.
Minimal reproduction project
No response

Maybe you have too little free space left? Did you try to export to another disk (e.g. D: instead of C:)?

Godot 3.3.4 cannot export PCK files larger than 2 GB, but Godot 3.4rc can.

Maybe you have too little free space left? Did you try to export to another disk (e.g. D: instead of C:)?
Yeah, I've tried exporting to both disks (which both have a few gigs free), and it still doesn't work

Godot 3.3.4 cannot export PCK files larger than 2 GB, but Godot 3.4rc can.
From what I can see, the pck files aren't larger than 2gb, so that can't be it

Also, make sure to export to a directory where you have write access (so, not Program Files).
Yeah, this is the part which is making me confused. I'm exporting to my desktop, so there's no way that I don't have write access to it

@aidanabat Do you use any third-party antivirus programs (i.e. anything else than Windows Defender)? Maybe it's interfering with Godot's export process.

@aidanabat Do you use any third-party antivirus programs (i.e. anything else than Windows Defender)? Maybe it's interfering with Godot's export process.
Ooh! I turned off malwarebytes and it didn't show the fwrite error anymore, but the exported exe is still 0kb, while the pck is the only one with an actual size. Not sure if that itself is related to this problem, but I thought it was worth mentioning

From what I know the exported exe file is unchanged between projects - it's the exact exe file copied from export template folder, just renamed. Can you check if the file in the export template folder also has a size of zero?

Also, I've found a case before with the same error: https://godotengine.org/qa/88028/exporting-game-windows-results-empty-and-unusable-exe-file
Maybe some of tricks from there would solve the problem for you?

Also, I've found a case before with the same error: https://godotengine.org/qa/88028/exporting-game-windows-results-empty-and-unusable-exe-file
Maybe some of tricks from there would solve the problem for you?

Thanks for the link -- Sadly, none of it seemed to work for me.

From what I know the exported exe file is unchanged between projects - it's the exact exe file copied from export template folder, just renamed. Can you check if the file in the export template folder also has a size of zero?

Hmm, from looking inside the export templates folder, I found out that the templates for windows were all 0kb, but for the other platforms, it was normal. I guess that explains why I can't export for windows, but that still sadly doesn't explain why it won't work for other platforms.

I found out that the templates for windows were all 0kb, but for the other platforms, it was normal.

It sounds like your antivirus removed them or put them in quarantine? Try to white-list the folder in the antivirus or to turn off the antivirus. And then reinstall templates


fix module chunk loading

What kind of change does this PR introduce?
bugfix

Did you add tests for your changes?
no

Does this PR introduce a breaking change?
no

What needs to be documented once your changes are merged?
nothing

Thanks


Euler connector

Euler Connector
Closes #237
Functions Added:

deposit
withdraw
borrow
repay
eTransfer
dTranfer
mint
burn
approveDebt
swap
enterMarket
exitMarket

Testcases-

Connector deployed at - 0xb12bA67bac0A287d8C0634f2C6e5CEd833e1896d


Merge to publish.

Docs Build status updates of commit 107d582:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/build-office-365-solutions.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Delete readme.txt

Or add something like this.
To compile your first program you need to run next command to your terminal.
$ clang helloworld.c -o helloworld
OR
$ gcc helloworld.c -o helloworld
To execute your program you need to run next command to your terminal.
$ ./helloworld


package: specfile

Provides a simplified version of the spec file and makefile included in osbuild-composer. Vendors existing dependencies, and enables CI (dependabot) to bump those.

A high level question/suggestion - can we just not include the vendor/ dir but instead make downloading/creating it part of the "make rpm" makefile? I would really like to try to avoid adding 1 million LoC if we can :)

The vendor directory needs to be part of our 'source distribution' which currently is a git checkout :)

Close in favor of #15.


How to get notifications/events about new wallet transactions?

Is there a way to get notifications/events about wallet transactions via websockets?
The new API does not seem to mention anything about this.
P.S: I’m using the version 0.11.0
Thanks in advanced.

Hey!
Indeed, there's no support for websockets event in the new API. Best you can do is to poll the API regularly for transactions.
There's no plan to support this in the near future (a.k.a next release).


Fixed Azure Redis Checkpoint Store Samples Issue

Fixes #40921

API change check
API changes are not detected in this pull request.

@sandeep-sen, @josefree, @ronniegeraghty, @jsquire and @ahsonkhan Could you help review this PR? Thanks a lot.


Automated Package Upgrade

:tada: This PR is included in version 26.0.46 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Pass out more semantic info via visualization events

When implementing the first SeedLang+Unity demo I found that the client code would require more semantic info for every visualization event. Here are some examples:

For the AssignmentEvent, the only thing client can get is the name of the variable. How can the client code know the variable counter is in the global scope or the local function scope? How can the client code tell if the variable counter is a function parameter?

For the BinaryEvent, the client code can get the left value and the right value, but how can the client code know if the left value is retrieved from a local variable counter?

... ...
This issue is kind of related to the topic of the semantic tokens that are to be highlighted in the code editor. Probably for every visualizer event, we need to pass out an EventContext  object to the visualizer. The EventContext may contain:

The corresponding source code.
The semantic parse result of the corresponding source code.
The relationship (if SeedLang Runtime can figure out) between the semantic tokens in the source code and the event parameters such as left value, right value, variable name, etc.

Just some random thoughs.

Adding an opcode VISNOTIFY is good for the running performance of the bytecode. It requires that the code must be re-compiled every time the user updates the visualizer registry (e.g., adding a new visualizer or deleting an existing visualizer) - this is acceptable I guess.

As for the way how to manage the event info structure, doesn't it look like the management of the debugging info in the compiler/debugger toolchain? For example, can SeedLang's compiler define, generate and store a separate Visualization Infomation Section in parallel with the bytecode section into the output? The format of the Visualization Infomation Section can be a significantly simplified version of any one of the popular Debugging Info formats. for example (at least we can take them as references when designing XXXEventInfo structures):
1 DWARF format
2 STABS format
3 Microsoft PDB format


Color not changing to White

After the #118 disaster of it messing the site up because LOCALLY and in the website were different, I have not fixed the issue more or less, but the color is not changing back to white in the toggle, it's only Matte Black and Dark Blue, @vikasganiga05 please can you make the main background as white?

@namyakhan the issue didn't get fixed.

Sorry, it was a deploy issue. It got fixed, but you changed the color back to what it was originally, I wanted it Matte Black lol


Add cichy dataset.

For https://github.com/mne-tools/mne-python/pull/3552

Current coverage is 86.27% (diff: 84.21%)

Merging #3772 into master will decrease coverage by 0.12%

@@             master      #3772   diff @@
==========================================
  Files           343        345     +2
  Lines         60996      61015    +19
  Methods           0          0
  Messages          0          0
  Branches       9325       9325
==========================================
- Hits          52702      52642    -60
- Misses         5590       5671    +81
+ Partials       2704       2702     -2

Powered by Codecov. Last update 7afb903...4c97fe4

by looking at the data I realize there is 92 categories not 96...
also it's only 1 run.
@kingjr is it good enough to make a convincing example?

also it's only 1 run. @kingjr is it good enough to make a convincing example?

Well, from what I recall, the data for one subject isn't super clear; it's mainly face versus rest. But what alternative do we have? Many people ask me about RSA in MNE, it would be great to have an example..

I agree but I am thinking that maybe packaging all the runs is the correct
thing to do even if it's "big data"...

I'm for that, but I'm not sure we should package it as an example then.
it'd be closer to something alike MNE-HCP no?
On 17 November 2016 at 11:05, Alexandre Gramfort<EMAIL_ADDRESS>wrote:

I agree but I am thinking that maybe packaging all the runs is the correct
thing to do even if it's "big data"...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3772#issuecomment-261288342,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEp7DAnafyQY6SphQ83GMf7oTlcMZQloks5q_HtPgaJpZM4K0-aE
.

I'm for that, but I'm not sure we should package it as an example then.
it'd be closer to something alike MNE-HCP no?

I think we should package it but if it breaks the build of circle ci
we could make an example that does not start with plot_ so it's not
run when building the doc.
We need an RSA example in MNE.
An idea would be to look if we can make the data smaller eg package
downsampled data or maybe just the Epochs ...
any thought?

Now all the runs and the trigger file are included.

worked fine but I think that while you're at it you should add the T1.nii.gz and the visual_stimuli.mat file (maybe converted to a simpler .mat or .npy file of shape (92, n_rows, n_cols)

you should add the T1.nii.gz and the visual_stimuli.mat

Included. There's also the csv stimuli file.

thx @jaeilepp


PHP version: Not installed

I ran every test succesfull with php.cmd alias but when importing path of php.cmd into PHPStorm that's said : PHP version not installed.

Do you have installed latest Creator's update?
Bash.exe had iessue with piping stdout.

Same issue here. php.cmd just works fine, but php version not found error in phpStorm 2017.1.4

Download manually Creator's update - worked for me.

Thanks, that did the truck.
I thought since creator update is out a while and I do all updates automatically, I already had the update.


scrollable-tab-view with flatlist can stuck the emulator and then you can not tap anything!

You can test by write a demo.

same problem. When call async method inside componentWillMount, it stuck and cannot rerender the flatlist item.


MINOR: Add 2 minute timeout to KTableKTableLeftJoinTest

According to KAFKA-7933, this test sometimes takes over
an hour. We add a 2 minute timeout to fail faster until
we find the problem. Another benefit is that we now
collect logs when a test fails (since ed3071231).
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Do you think it's worth to collect periodic stack dumps as well? (Might be a bit bigger effort though)

retest this please

@ijuma With https://github.com/apache/kafka/pull/6292, do we still need this?

@ijuma We resolved https://issues.apache.org/jira/browse/KAFKA-7933 -- do we still need this PR?

Let's close it.


Added Punctuation and Clarified Information

I added a period to help make the article appear cleaner, as well as some further information with an already-established link to help clarify what the link tells the reader.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

I'm looking for some help

@METALMAN01 If you need help with how to contribute visit https://gitter.im/FreeCodeCamp/Contributors.  If you need help with understanding/writing some code visit the FCC forum.


tmpfile docs incorrectly state the file location

tmpfile() famously creates files in the system root on some versions of Windows and/or MSVC, which fails if the user does not have permission to do that. This is somewhat documented here with mention of "The temporary file is created in the root directory" and "This example requires administrative privileges to run on Windows Vista".
However, I see that with Windows 11 and MSVC 17 (v143) the temp file is now in %temp%. It would be good to clarify:

Which variables matter - OS or compiler?
Which of these write to the system root, and which use %temp%?

That way we can decide whether this function must be avoided (to support older OSes/compilers) or is now safe to use (security notwithstanding).

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 414314a8-bd8d-99fc-1f6c-5df80b3cc1e3
Version Independent ID: ee91da15-7833-1638-7745-a0d8ee2329b0
Content: tmpfile
Content Source: docs/c-runtime-library/reference/tmpfile.md
Product: visual-cpp
Technology: cpp-ucrt
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

Good point, @maxim-zhao. I will add this to my work list.

Moved this issue to an internal work item tracking system because we are moving away from using GitHub issues to track C++ doc work.


release: Prepare for releasing v1.0.1

Ⅰ. Describe what this PR did
Update controller version to v1.0.1
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #367 (04dc4e0) into main (80d6ecf) will increase coverage by 0.16%.
The diff coverage is 50.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #367      +/-   ##
==========================================
+ Coverage   41.57%   41.73%   +0.16%
==========================================
  Files          44       44
  Lines        5879     5877       -2
==========================================
+ Hits         2444     2453       +9
+ Misses       3262     3251      -11
  Partials      173      173

Impacted Files
Coverage Δ

pkg/ingress/kube/ingressv1/status.go
0.00% <0.00%> (ø)

pkg/ingress/kube/ingress/status.go
14.06% <100.00%> (-1.33%)
:arrow_down:

... and 1 file with indirect coverage changes


refactor.extract should respect project's semicolon policy

I don't use semicolon as line separator in my project. I have "semi": [2, "never"] in rules section in my esling.json. refactor.extract.constant works but adds a redundant semicolon at the end of the extracted line (same for the other refactor.extract actions I believe).
I would be great if refactor.extract could respect eslint.json rules.

Duplicate of https://github.com/Microsoft/TypeScript/issues/18780


spotify: <IP_ADDRESS>1.g9d720389-21 -> <IP_ADDRESS>7.g9bd02c2d-26

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

This update seems needed only because upstream keeps just the latest package, so the previous can not be retrieved.

As this causes build fails in older releases that worked until now, I guess this should be backported.

Could you submit a pull request for the branch of your release after confirming that it works?


How to watch & build when working with different structure ?

I'm trying to build a figma plugin out of my web app (nextjs, tailwind), with goal of reusing most of my components.
-- src
-- common
-- core
-- plugins
    -- figma
        --  build
        --  src
        -- manifest.json
-- package.json

My package.json
  "scripts": {
    "dev": "next",
    "build": "GENERATE_SOURCEMAP=false next build",
    "start": "next start",

    "plugin-build": "npm run plugin-build:css && npm run plugin-build:js",
    "plugin-build:css": "tailwindcss --input ./plugins/figma/src/styles/input.css --output ./plugins/figma/src/styles/output.css",
    "plugin-build:js": "build-figma-plugin --typecheck --minify -o ./plugins/figma",
    "plugin-watch": "npm run plugin-build:css && concurrently npm:plugin-watch:css npm:plugin-watch:js",
    "plugin-watch:css": "tailwindcss --input ./plugins/figma/src/styles/input.css --output ./plugins/figma/src/styles/output.css --watch",
    "plugin-watch:js": "build-figma-plugin --watch -o ./plugins/figma"
  },

I presume my issue would be resolved if I could specify the watch directory (same for typecheck). But I don't see that option in arguments.
So, back to my question.  How can I watch & build when working with different structures?

The build-figma-plugin CLI doesn’t currently support specifying the directory to build or watch. You’d need to cd into the appropriate directory before running it.
The concurrently npm module might be relevant for your use case. See the plugins/preact-tailwindcss template.


How to achieve UE registration and PDU procedures using Packet Rusher

Hello
I am planning to use packet rusher  that involves triggering 5G core procedures such as registration, PDU connection, deregistration, and handover using Packet Rusher. Specifically, I need to:
Trigger 100 registration instances.
Trigger 30 PDU connection instances.
Trigger 50 deregistration instances.
Trigger 20 combined registration and PDU connection instances.
Trigger 10 handover procedures.
Amf load testing
For my setup, I am using the Radiant Open5G Core Helm chart to deploy Open5GCore on Kubernetes and also using the PacketRusher Helm chart to deploy Packet Rusher. Could you please provide guidance or examples on how to achieve these using Packet Rusher? Any documentation and  detailed steps would be greatly appreciated.
Thank you!

Hi Good evening,
I am deploying PacketRusher in Kubernetes and successfully launching it with a single UE. However, when I run PacketRusher with the command ./packetrusher --config config.yml amf-load-loop -n 20 -t 20, it crashes. You can find the crash log in the provided file.
packet_rusher_amf_load_test.txt
Additionally, I attempted to launch multiple UEs using ./packetrusher --config config.yml multi-ue -n 1 -d true -t true, but I encountered the following issue:
PDU address received: <IP_ADDRESS>
time="2024-07-24T15:01:22Z" level=info msg="[UE][GTP] Interface for UE<PHONE_NUMBER> has not been created. Tunnel has been disabled."
Even when I tried launching with a single UE in multi-ue, I still faced the same problem. Could you please help me resolve this issue?
packet_rusher_multi_ue.txt
I also tried running packet rusher with --multi-ue-pdu -n 5 --tr 60000 --td 60000 --npdu 1 -l true . but I didn't observer de registration and re registration of UE's
packet_rusher_multi_ue_pdu.txt
could you please help me to debug these issues. Thanks in advance
Best Regards
Kiran


Delete app endpoint and wired up buttons

What
Allows superuser to delete apps in the UI
How to review

check out, run, log in
create an app
visit /apps, then either
click "Delete app" in the table, or
click through to the app page and click "Delete app" at the bottom of the page
see that the app has been deleted

Look good to me 👍
Only two things to node are:

I'd rename the param to just :id from :app_id for consistency
we could probably write some tests


Add border to text boxes

Hi there,
It would be nice if test boxes will have automatic borders capability. i find myself struggling to add squares and group behind text all the time :)
other then that - this is an awesome product and I use it almost daily.
Thanks you!

I think the better idea would be, to be able to lock the text to the center of any shape. That way you can do more things and playing with backgrounds, paddings, shapes, etc..

Implementing this would make this issue obsolete.

Yeah something like that, but sticky notes it's a different thing.. we don't want those to be exported or printed.

We'll pass on this one, as it will require the text element to have extra properties to change the border color, possibly the background color and other ones that are not related to the text it self but to the background box of it..

Can you at least leave this issue open, because with this feature you can easily format text with optional boxes and so on by copy and paste the style? This is very useful to have, especially if you're doing text-heavy brainstorming sessions and try to maintain some visual structure by quickly formatting some text.

How about the option of reacting to a double-click on a shape by creating a text box with centered text right in the middle of the shape?

We're already doing that when you dblclick in the vicinity of the center, but I guess we can make also it center the text when dblclicking on the element itself.

In case of filled shapes, we can center the text when clicking on the fill also.
Note that you can also do this today by selecting a shape and pressing enter instead of dblclick.

In terms of single-clicking with a text tool, I guess it should retain current behavior even if you click on a shape?

@dwelle You're right, and I must have used that feature unconsciously a few times :-) What is missing though is then to group the text and the shape, because the most frequent action that follows the double click and the typing is a repositioning of the shape....at which point one finds that the text is left behind. Makes sense?


Enable/Disable instance API question

Hello,
Could you please explain next situation:
Consider sequence of api calls
PUT /eureka/v2/apps/appname/instanceid/status?value=OUT_OF_SERVICE - to temporary remove service out of service
DELETE /eureka/v2/apps/appname/instanceid/status?value=OUT_OF_SERVICE - to remove previous override
Will next heartbeat put instance into UP status? Or delete request should contain value=UP to make it happen?
PUT /eureka/v2/apps/appname/instanceid?status=UP&lastDirtyTimestamp=... - heartbeat
Thank you for your time!

Hi @kirillsablin , the next heartbeat will put the instance into either UP or DOWN, depending on what the registered healthcheck to the eureka-client is (if none, it should be UP).


Add --no-color option to crystal spec subcommand

I added --no-color option to spec subcommand.  This is already discussed at #1587.

Now spec subcommand ignores options which starts with --.  This implementation is OK?

+1 for use_colors

@luislavena @kirbyfan64 @jhass
I renamed color to use_colors.

Looks good, could you squash your commits together?
git remote add upstream https://github.com/manastech/crystal.git
git fetch upstream
git checkout spec-no-color
git rebase -i upstream/master
# Leave the first commit at pick, choose squash or fix for the others.
# If there are any conflicts git will inform you about that, resolve them for
# example with git mergetool or manually and with git add, then run
# git rebase --continue, again  watch the output since that might happen for
# each commit.
git log # Look at the updated commit history
git status # should report you're back on your branch
# We need to force push since a rebase edits the commits, effectively
# creating new ones. This is okay to do in a feature branch, the pull
# request will update.
git push -f origin spec-no-color # Assuming you cloned from your fork

Hint: You can also edit your last commit with git commit --amend, since that also effectively creates a new commit, you to need to force push afterwards and again you should only do it in feature branches.

@jhass
Squashed!

Thanks!


#2724- Fix of close method invokation in ActionableNotification close…

… button action
Closes https://github.com/carbon-design-system/carbon-components-angular/issues/2724
When the user will click on close button of ActionableNotification , then the function was not invoked which user defined in html file against close method.
After this Fix- The function will be invoked.
Changelog
New
The close function will be invoked on clicking of close button of ActionableNotification.

Hi @nipun005 ,
I think it is not valid solution, ActionableNotification extends BaseNotification where
@Output() close: EventEmitter = new EventEmitter(); is defined.
In my Issue I described that 'My onNotificationClose() method is beeing properly invoked on 'x' click.. The issue is that notification is not dissapearing on 'x' click.

Closing this as functionality exists using dynamic notifications.


Catalogsource cannot be created via private docker registry

Bug Report

What did you do?
A clear and concise description of the steps you took (or insert a code snippet).
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: my-operators
  namespace: openshift-marketplace
spec:
  displayName: My Operators
  sourceType: grpc
  image: my/catalog-test:0.0.1

If I push the image my/catalog-test:0.0.1 to a private registry, then there is no place to enable me to set a imagepullsecrets for this image, and this will cause the catalogsource deploy failed.
What did you expect to see?
A clear and concise description of what you expected to happen (or insert a code snippet).
What did you see instead? Under which circumstances?
A clear and concise description of what you expected to happen (or insert a code snippet).
Environment

operator-lifecycle-manager version:

Kubernetes version information:

Kubernetes cluster kind:

Possible Solution

Additional context
Add any other context about the problem here.

Can any expert show some comments for this? Thanks!

Take a look at #1294

I'm stumbling on this as well with OLM v 0.16.1 in a plain vanilla kind cluster & operator-sdk v 1.0.1.
In my case I declared a CatalogSource like this:
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: cloudcar-catalog
  namespace: foo
spec:
  displayName: Cloudcar Operators
  sourceType: grpc
  publisher: cloudcar
  image: us.icr.io/ca-sci/cloudcar-operators-index:latest
  secrets:
    - registry-read
  updateStrategy:
    registryPoll:
      interval: 10m

assuming that the pre-existing registry-read pull secret in the foo namespace would be used to pull the index image from my private registry.  Instead the image pulls failed with events like this:
Failed to pull image "us.icr.io/ca-sci/cloudcar-operators-index:latest": rpc error: code = Unknown desc = failed to pull and unpack image "us.icr.io/ca-sci/cloudcar-operators-index:latest": failed to resolve reference "us.icr.io/ca-sci/cloudcar-operators-index:latest": failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized

Once I added the registry-read secret to the default service account in the foo namespace the index image was successfully pulled.
I don't know if this is the right solution (or if its even recommended practice?). After reading https://github.com/operator-framework/operator-lifecycle-manager/issues/1294#issuecomment-587146658 it looks like there may be use cases where using the secrets element in CatalogSource are _not_recommended?
I dug around in the catalog operator code to see if I could find how the catalog pods are created when a CatalogSource is added to a namespace and found this:
https://github.com/operator-framework/operator-lifecycle-manager/blob/6d26c16166b232561132985e1132fce4b4d36532/pkg/controller/registry/reconciler/reconciler.go#L94-L154
It doesn't appear that an imagePullSecrets stanza is added to the container in the catalog pod.  Is it possible that this is an oversight?
Am I misunderstanding the intent behind the secrets element in the CatalogSource custom resource?

It doesn't appear that an imagePullSecrets stanza is added to the container in the catalog pod. Is it possible that this is an oversight?
Am I misunderstanding the intent behind the secrets element in the CatalogSource custom resource?

Based on https://github.com/operator-framework/operator-lifecycle-manager/issues/1536#issuecomment-632054329 it looks like pulling catalog images from private repos is not currently supported.


Dropping basic node modules like Gulp, Bower, etc.

A little bit of Angular, Gulp, Bower, Bootstrap, yadda yadda.

:+1: