signature | Simple key/secret based authentication for apis | Authentication library

There are multiple potential places to measure execution time, first might be defining very specifically what is the intended measurement.

1. Measuring the training time of each client as proposed is a great way to get a sense of the variability among clients. This could help identify whether rounds frequently have stragglers. Using tf.timestamp() at the beginning and end of the client_update function seems reasonable. The question correctly notes that this happens in parallel, summing all of these times would be akin to CPU time.

2. Measuring the time it takes to complete all client training in a round would generally be the maximum of the values above. This might not be true when simulating FL in TFF, as TFF maybe decided to run some number of clients sequentially due to system resources constraints. In practice all of these clients would run in parallel.

3. Measuring the time it takes to complete a full round (the maximum time it takes to run a client, plus the time it takes for the server to update) could be done by moving the tf.timestamp calls to the outer training loop. This would be wrapping the call to trainer.next() in the snippet on https://www.tensorflow.org/federated. This would be most similar to elapsed real time (wall clock time).

I was able to get it resolved, but the solution is...hacky.

So, apparently, Google Apps Script exports only what is in globalThis of a project: just the functions and variables. No classes, no constants, ...

Probably has a lot to do with how ES6 works, with its globalThis behavior. One can see that in action, by creating a dummy function, a dummy variable, and a dummy class in their local developer console:

I answer by myself referencing this GitHub issue: https://github.com/psf/requests/issues/4775

I solved the problem using the code below:

Here I'm wondering about the line [in s_client]
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384

You're apparently using OpenSSL 1.0.2, where that's a basically useless relic. Back in the days when OpenSSL supported SSLv2 (mostly until 2010, although almost no one used it much after 2000), the ciphersuite values used for SSLv3 and up (including all TLS, but before 2014 OpenSSL didn't implement higher than TLS1.0) were structured differently than those used for SSLv2, so it was important to qualify the ciphersuite by the 'universe' it existed in. It has almost nothing to do with the protocol version actually used, which appears later in the session-param decode:

Ok, the signature container is embedded correctly.

But there are issues with the signature container itself:

• Both in the SignedData.digestAlgorithms collection and in the SignerInfo.digestAlgorithm value you have used the OID of SHA1withRSA, but that is a full signature algorithm, not the mere digest algorithm SHA1 expected there.

• Then the SHA1 hash of the signed bytes is BB78A402F7A537A34D6892B83881266501A691A8 but the hash you signed is 90E28B8A0D8E48691DAFE2BA10A4761FFFDCCD3D. This might be because you hash buffer2 and

  buffer2 has empty contents data (/Contents <>)

  The hex string delimiters '<' and '>' also belong to the contents value and, therefore, must also be removed in buffer2.

Furthermore, your signature is very weak:

• It uses SHA1 as hash algorithm. SHA1 meanwhile has been recognized as too weak a hash algorithm for document signatures.
• It doesn't use signed attributes, neither the ESS signing certificate nor the algorithm identifier protection attribute. Many validation policies require such special attributes.

I believe your goal as follows.

• You want to set the conditional format rules for each range with each formula.
• The range is created by the for loop of for (let i = 3; i < 25; i++) {,,,}.
• The formula is created by const formula = '=sum($' + columnStart[z] + '6:$' + columnEnd[z + 6] + '6)>=40';.

• When I saw your script, it seems that range of Logger.log(range) is the string value. But when setRanges(range) is used, range is required to be the Range object. I think that this might be the reason of your issue.
• And, in your situation, how about the following flow?
  1. Put each range to an array of rules of rules = sheet.getConditionalFormatRules().
     • For this, in my answer, I used RangeList.
  2. Use rules with sheet.setConditionalFormatRules(rules) put outside of the loop.

When above points are reflected to your script, it becomes as follows.

The answer is to bypass the empty-string test; the underlying protocol does not support region-less configuration, nor is there a configuration option to support it.

The trick is able to work because the use of 'endpoint' causes the 'region' to be ignored. With that, setting the region to something and forcing the endpoint allows it to work:

Sql server needs to set firewall policy be default, so I assume that after deploying app to azure web app, ip address must change and may lead to some error.

@Destroigo here met the firewall problem. Congratulations to solve it :)

Here's a way you could do it:

https://www.typescriptlang.org/play?#code/MYewdgzgLgBAZgQ2FEAnAlgUwjAvDAbwCgZ4QQAuGACgEo8A+GAcghAFtMZoMwBzZgBoSMAEYJUVOoxgBGAEwBmYQF8A3ESJQAngAcuAMSQpU2gDwAVJvmm4mFjVr2HjabQDUEAGwCu2S9aEIgDaANIw6GAwANaY2iBwMBYAulQWYckwmAAeUJhgACY4RshuZpFwmKgwAKpMAPy1MFRgmABuVRrqmqCQsG3efhBUJSYeg-46+gnwrhjYgcSkcORUzHnQQiLiknJKqhpAA