nanos | kernel designed to run

you can create a database with nano precision, then all the tables under this database will be using nano precision.

It's for sure something I do not like, but for images that have a cgroup v2, it seems like I will start it with:

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

Protobuf always includes fields on the wire; there's no (longer) an optional field setting.

Your code will need to use the default value as a signal of non-value.

JIT compilation in HotSpot JVM is 1) based on runtime profile data; 2) uses speculative optimizations.

Once the method is compiled at the maximum optimization level, HotSpot stops profiling this code, so it is never recompiled afterwards, no matter how long the code runs. (The exception is when the method needs to be deoptimized or unloaded, but it's not your case).

In the first case (SELECT_QUICK == true), the condition remaining > fBuffer1.length - fIdx is never met, and HotSpot JVM is aware of that from profiling data collected at lower tiers. So it speculatively hoists the check out of the loop, and compiles the loop body with the assumption that array index is always within bounds. After the optimization, the loop is compiled like this (in pseudocode):

the timestamp type is imported from a external definition, like import "google/protobuf/timestamp.proto";

BUT, Pub/Sub does not support external import for now, as you check here , so I'm afraid it's not going to work. The workaround would be change it to string type.

I could not find a way to enable imports or to use timestamp without it.

The definition you have created is actually validating a message like this:

PHP 7 >= 7.2.0 and PHP 8 do have a built-in crypto library "sodium" that let you derive the ED25519 public key from a given secret (private) key: https://www.php.net/manual/en/function.sodium-crypto-sign-publickey-from-secretkey.php

Below is a full runing example for this task:

So I figured it out, with the gracious help of Craig Estey and Amit (which you can see in the comments under the original post).

So in the end it was a Deadlock, because, as you can still see in the original post which I will not modify so anyone interested has a chance to gaze upon my folly.

This happened because at one point there will be 6 threads waiting to pull, the stack is empty, and the two remaining threads is one going into await, and the other just having fulfilled it's given function, which is one that didn't call another recursively (in our example one with fib(0) or fib(1)). Now that that is finished the thread, let's call it thread 7, going into fib_await() will check if the value that it is waiting for is fulfilled, which at this point it isn't yet, thus it checks if there are any other in the stack. As there are none, it is stuck in wait.

Now the other thread, thread 8, the one that just fulfilled it's given function marks it's future as fulfilled and tries to pull another future. As it is empty, it too will stay in pull.

Now all threads are stuck in pull and none can progress as the one that is waiting on another would first have to leave pull().

My only modifications came for pull(), push(), tpAwait(), tpInit(), and workerThread() as I also implemented a very simple ticket lock.

𝛿 threadpool.c

From the docs of UUID.randomUUID:

Static factory to retrieve a type 4 (pseudo randomly generated) UUID. The UUID is generated using a cryptographically strong pseudo random number generator.

A disadvantage of cryptographic RNGs is that they are slow. Because it is a pseudo-random number generator, the slowness of generating good random numbers only exists when crearing the random number generator.

If you take a look at the OpenJDK sources of UUID.randomUUID, you can see that the first random number generator is obtained using a simple but effective singleton that is loaded whenever it is called first (when the class Holder is loaded):