hm | Object-Relational Mapping library

Your sum object is declared twice. The second declaration overwrites the first, so the keys needed for the first calculator are lost.

change to this, it will work:

the reason you got the previous calculation and the second one after it, is because each time you click on the radio button you create a new event listener to the add button, so when you click it two handlers are running that is why you get 2 alerts. pull the event listener of the add button out, and you will have only one handler for it:

If you are open to using a formula instead of script, I can propose a solution. (In my own practice of decades, I save script for only those times when formulas cannot produce the desired result; this cuts down greatly on potential problems.)

This solution uses information from the script in your post to ascertain that the name of the source sheet is 'gest' and the ranges of data to include in the new report are B:C and E:F.

Create a new sheet and place the following formula in cell A1:

=ArrayFormula({gest!B1:C1, gest!E1:F1; QUERY({gest!B2:C, E2:F},"Select Col1, Col2, SUM(Col3), SUM(Col4) WHERE Col1 Is Not Null GROUP BY Col1, Col2 LABEL SUM(Col3) '', SUM(Col4) ''")})

This single formula will produce all headers and results, and will "keep up" as you add new rows of data in the 'gest' sheet.

A virtual array is formed between the curly brackets { }. This is a way of "sticking together" non-contiguous data in new ways.

The headers are grabbed by the two references preceding the semicolon.

Then a QUERY is formed from the non-header information in the target columns.

In plain English, the Select clause of the QUERY reads "Return four columns: exactly what is in the first requested column and the second requested column followed by the categorized sums from the third and fourth requested columns, separating (i.e., "GROUPing") those sums by each unique pairing from the first two columns." The LABEL section just removes technical headers from the sum columns created (which would otherwise have placed stock headers of 'sum' above each of the summed columns).

Okay I got it!

This guy goes over the required libraries

https://www.youtube.com/watch?v=2IWtEkAHXFI

I was missing swig, and afterwards I was also missing liborc-0.4-dev

They can be installed via:

From the description of the problem, time complexity should be O(n^2). But this part of your code is not O(n^2), in worst case it is O(n^3)

rayon is not a good fit for async because it operates on ordinary non-async functions, and blocks in operations like for_each(). But since you're using async, you could avoid Rayon altogether and just spawn a task for each operation:

char *HM is a char pointer whereas the passed parameter HashMap is a struct node*

There is @JsonUnwrapped annotation for this. Should work like this: