mather | zzllrr mather | Math library

You're looking for something like this:

Sure! Use a list comprehension and call the function inside of it, then compare the size of the result to what you had before. Given your example, you would replace existRule(rules[i]) with something like this:

With the help of split we can split the Yards for each Class.

fs.writeFile does not return a promise. fs.writeFileSync is a good synchronous alternative if you're OK with blocking the event loop.

It looks to me like your code isn't doing quite what you expect it to to. The saveFile function returns a Promise, and the result of the callback has nothing to do with the Promise that's returned, and you're not waiting for the write-function's work to happen. Working with callbacks & Promises in the same function can be a bit hairy, so Node comes with a util.promisify helper.

Problem Solved!

I think the round(microtime(true)) wasn't enough to generate unique names. I changed it to uniqid() and worked.

So the PHP code becomes:

You need to load the certificate with the MachineKeySet flag.

X509Certificate2 certificate = new X509Certificate2(certificateBytes, passphrase, X509KeyStorageFlags.MachineKeySet);

This will solve the problem in Azure but your local dev machine might have a problem after this change. You need to allow full access for the user running RavenDB to the MachineKeySet folder on your local machine.

"C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys"

Please also note that if you don't dispose the certificate afterwards, the private keys pile up in that folder (a key is written to that folder every time the X509Certificate2 constructor opens the certificate).

warning :

• on an empty directory du returns 4, your program will return 0 (no files)

• on a dir without file but containing an empty dir du -s returns 8 (4+4) and your program will return 0 (no files)

• etc

so du returns not only the size needed by the files but also by the dir(s), but your program only consider the files => your program computes less than du

It's the same as for synchronous iterators: generator functions are much easier to write, and easier to get correct, than implementing the iterator object manually. Do this only if you need some non-standard behaviour that cannot be achieved otherwise. With asynchronous generator functions specifically, you even get the proper queueing of next calls for free, which is a real headache to get right (your asyncIterable2 fails this¹).

The most common implementation of iterables is to make the Symbol.asyncIterator method an async generator method:

You can save defeated teams history in $result: