scheduler | : watch : A fully managed cron job scheduler | Job Scheduling library

Support for _PIP_ADDITIONAL_REQUIREMENTS environment variable has not been released yet. It is only supported by the developer/unreleased version of the docker image. It is planned that this feature will be available in Airflow 2.1.1. For more information, see: Adding extra requirements for build and runtime of the PROD image.

For the older version, you should build a new image and set this image in the docker-compose.yaml. To do this, you need to follow a few steps.

1. Create a new Dockerfile with the following content:

with the hope that due to the Retain policy, the new pods (i.e. their PVCs would bind to the existing PVs (and data wouldn't get lost)

It is explicitly written in the documentation that this is not what happens. the PVs are not available for another PVC after delete of a PVC.

the PersistentVolume still exists and the volume is considered "released". But it is not yet available for another claim because the previous claimant's data remains on the volume.

I don't think MutableState is designed to be used in the ViewModel layer, since it's an observable integrated with the compose runtime. You could create a MutableStateFlow instead and use collectAsState() from the view layer.

In your case the issue is probably, because of the state is captured in a coroutine invoked outside composition.

How can I implement something like this in the best way? You don't appear to even need a numberOfTimesUpdated column as the number of days since the creationDate can be calculated when required.

• If the date/time were stored in a supported format (e.g. YYYY-MM-DD HH:MM) it is very simple.

For example consider this :-

This issue is solved after correcting up my code

In order to understand what's going on, I'll reformat the code a bit in order to make it more clear and explicit:

Your original code:

I am having difficulty placing the pragma correctly.

Focusing on correct placement, note that a Task_Dispatching_Policy pragma is a configuration pragma that must "appear before the first compilation_unit of a compilation."

at least according to GNAT.

As @egilhh comments, the GNAT User Guide describes how tp accomplish this in 3.4.1. Handling of Configuration Pragmas:

Configuration pragmas may either appear at the start of a compilation unit, or they can appear in a configuration pragma file to apply to all compilations performed in a given compilation environment.

In the case of a single compilation unit, simply place the pragma before the first context clause, as shown here:

From some research, it looks like computers have a hardware timer called a programmable interval timer (PIT), which the OS can use to set a time in the future to cause an "interrupt" in some milliseconds or nanoseconds in the future.

What about this solution? I removed parallel from Flux, in order to bufferize 10 elements. Each elements can be then handled in parallel