workerpool | Offload tasks to a pool of workers on node.js | Reactive Programming library

I'm working in a reacjs based app and i wanted to add firebase to store simple data, so i followed some firebase tutorials because i wasn't familiar with it. However, when i tried my code after setting up firebase i got like 43 different errors in my console. Now i managed to get rid of most of them (problems with polyfill) but i can't get around the last of them.

I get this errors, it seems that the problem has to do with worker_threads but i don't know where they came from and how to solve it, i saw some tutorials on node workers but i still don't understand what kind of data i have to pass or how to set it up.

I am using Fiber to develop a backend. I have a map that is a global variable that holds the socket connections. When I use the global variable from the same package, no problem here, everything works fine. But, when I try to use the sockets from a route function, I am getting the error below.

I tried to use mutex.lock but no luck.

I checked the code, the socket is not nil in my sendToAll method but it becomes nil in the helper method( inside the lib: github.com/fasthttp/websocket.(*Conn).WriteMessage )

Any advice is welcome.

Thanks.

I'm unable to create an azurerm_monitor_metric_alert. I'd need it to monitor the Deadlettered Messages of a Service Bus. I'm using Terraform 1.0.11 on Linux and azurerm v2.88.1.

The error I'm getting is this:

I have 2 kubernetes clusters in the IBM cloud, one has 2 Nodes, the other one 4.

The one that has 4 Nodes is working properly but at the other one I had to temporarily remove the worker nodes due to monetary reasons (shouldn't be payed while being idle).

When I reactivated the two nodes, everything seemed to start up fine and as long as I don't try to interact with Pods it still looks fine on the surface, no messages about inavailability or critical health status. OK, I deleted two obsolete Namespaces which got stuck in the Terminating state, but I could resolve that issue by restarting a cluster node (don't exactly know anymore which one it was).

When everything looked ok, I tried to access the kubernetes dashboard (everything done before was on IBM management level or in the command line) but surprisingly I found it unreachable with an error page in the browser stating:

503: Service Unavailable

There was a small JSON message at the bottom of that page, which said:

I'm creating worker_threads in node and I'm collecting them to custom WorkerPool. All workers are unique, because they have unique worker.threadId. My app have ability to terminate specific worker -- I have terminateById() method in WorkerPool.

So if you have one node.js instance -- everything is all right. But if you're trying to use docker-swarm or Kubernetes -- you will have n amount of different WorkerPool instances. So, for example, you have created some workers in one node instance and now you're trying to terminate one -- it means you have some request with threadId(or other unique data to identify worker). For example your load balancer have chosen to use another node instance for this request, in this instance you have no workers.

At first I thought, that I can change unique index for worker to something like userId+ThreadId and then store it in redis for example. But then I haven't found any info about something like Worker.findByThreadID(). Then what can I do in situation, when you have multiple node instances?

UPDATE: I have found some info about sticky sessions in load balancers. That means, that using cookies we can stick specific user to specific node instance, but this in my case this stickiness has to be active until worker is terminated. It can last for days

I am writing a program that concurrently reads word by word from a text file to compute the occurrences using channels and worker pool pattern

The program works in the following flow:

1. Read a text file (readText function)
2. readText function sends each word to the word channel
3. Each goroutine executes countWord function that counts word in a map
4. Each goroutine returns a map and the worker function passes the Result value of struct to the resultC channel
5. Test function creates a map based on the result values coming from the resultC channel
6. Print the map created from step 5

The program works, but when I try to put fmt.Println(0) to see the process as shown below

I'm playing with some code for learning purposes and I am getting a race condition on its execution when using the -race flag and I want to understand why. The code starts a fixed set of goroutines that act as workers consuming tasks from a channel, there is no fixed number of tasks, as long as the channel receives tasks the workers must keep working.

I'm getting a race condition when calling the WaitGroup functions. From what I understand (taking a look at the data race report) the race condition happens when the first wg.Add call is executed by one of the spawned goroutines and the main routine calls wg.Wait at the same time. Is that correct? If it is, it means that I must always execute calls to Add on the main routine to avoid this kind of race on the resource? But, that also would mean that I need to know how many tasks the workers will need to handle in advance, which kinds of sucks if I need that the code handles any number of tasks that may come once the workers are running...

The code:

We are using Google Cloud Build as CI/CD tool and we use private pools to be able to connect to our database using private IPs.

Since 08/27 our builds using private pools are stuck in Queued and are never executed ou fail due to timeout, they just hang there until we cancel them.

We have already tried without success:

• Change the worker pool to another region (from southamerica-east1 to us-central1);

• Recreate the worker pool with different configurations;

• Recreate all triggers and connections.

Removing the worker pool configuration (running the build in global) executed the build.

cloudbuild.yaml:

I am very new to golang and for the most part have no idea what im doing so far. I tried to run a simple find() query to get all documents from my databse and I cant seem to get it to work i keep getting this error