baron | Native scroll with custom scrollbar | Frontend Framework library

You can use:

The cause of the error is that you are calling sheet too many times, and each call is a request which takes time to process and ultimately leads to the timeout. The easy sounding solution is reduce the calls of sheet.getRange() and sheet.setValue() and sheet.getName() etc… so that you ideally do them once per each sheet you are working on. A simple example would be as follows, where everything is done once (except the api call, which ideally should also be done using a bulk api).

You can split the Name column then use transform function on the resulting array to get first letter of each element:

Because of tolerances any integer variable can be slightly non-integer. This is normal and also happens with linear solvers.

Please read my comments marked as // CHANGE HERE.

You changed your category variable value that you defined earlier from user input inside your for loop. To fix it, rename the category variable to something else eg category_row inside the for loop.

you need to add an "order" column to get expected result. Here is a solution with row_number.

Make it as simple as possible and do not store the information from different loops in these bunch of lists, try to store them in one dict:

The C# code uses Rijndael with a block size of 256 bits (see comments), a static IV (see comments) and returns only the ciphertext (i.e. without prepended IV).
The Go code applies AES with by definition a block size of 128 bits, a randomly generated IV (the static IV in the code is ignored) and returns the concatenation of IV and ciphertext.

AES is a subset of Rijndael. Rijndael defines different block sizes and key sizes between 128 and 256 bits in 32 bit steps, see here. For AES only the block size 128 bits is defined and the key sizes 128, 192 and 256 bits. Note that the standard is AES and not Rijndael, so AES should be preferred over Rijndael (many libraries do not even implement Rijndael, but AES instead).

A static IV is insecure. Key/IV pairs must not repeat for security reasons. Therefore, in general, with a fixed key, a random IV is generated for each encryption. The IV is not secret and is passed along with the ciphertext to the decryption side, typically concatenated in the order IV|ciphertext.

Therefore, the current Go code is a secure implementation (even more secure is authenticated encryption e.g. via GCM), while the C# code is not. So it would make more sense to modify the C# code to be functionally equivalent to the Go code.
However, since the C# code seems to be the reference, the following changes are needed in the Go code to make it functionally identical to the C# code:

• Instead of AES, Rijndael must be applied. In the following example, pkg.go.dev/github.com/azihsoyn/rijndael256 is used. To do this, import "github.com/azihsoyn/rijndael256" and formally replace aes with rijndael256. You can of course apply another implementation.
• The static IV is to be applied: bm := cipher.NewCBCEncrypter(block, IV). iv and its filling is to be removed together with associated imports.
• Only the ciphertext is returned in the enecrypt()-method: return ciphertext[rijndael256.BlockSize:].

The following Go code gives the result of the C# code: