You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey guys! We are considering using nestjs-asyncapi in our company, and we tried to use your library in our nestjs services.
Suddenly, we came across a weird bug which when we run our nestjs app using Node Cluster, it is crashing, and the cause - is the nestjs-asyncapi library.
When it's added - the cluster app is not responding and the nestjs application is not loading. When the dependency doesn't exist - it's working perfectly.
Worth to mention that when using the dependency in an app that is not running on cluster mode, it's working.
Also worth to mention - the node instance is running on k8s cluster! when we use a simple docker or run it locally (even with Node cluster) - it works, but on k8s cluster it doesn't. Very specific specs.
I'm trying to debug it, because it's very weird behaviour which may also be linked to our very specific configuration, but I wonder if someone encountered this issue using this library.
Environment
Nest version: 9.3.10
For Tooling issues:
Node version: 18
Platform: Linux
Running on Kubernetes Cluster
The text was updated successfully, but these errors were encountered:
Describe the bug
Hey guys! We are considering using nestjs-asyncapi in our company, and we tried to use your library in our nestjs services.
Suddenly, we came across a weird bug which when we run our nestjs app using Node Cluster, it is crashing, and the cause - is the nestjs-asyncapi library.
When it's added - the cluster app is not responding and the nestjs application is not loading. When the dependency doesn't exist - it's working perfectly.
Worth to mention that when using the dependency in an app that is not running on cluster mode, it's working.
Also worth to mention - the node instance is running on k8s cluster! when we use a simple docker or run it locally (even with Node cluster) - it works, but on k8s cluster it doesn't. Very specific specs.
To Reproduce
Steps to reproduce the behavior:
I'm trying to debug it, because it's very weird behaviour which may also be linked to our very specific configuration, but I wonder if someone encountered this issue using this library.
Environment
Nest version: 9.3.10
For Tooling issues:
The text was updated successfully, but these errors were encountered: