finalizers | Stupid Finalizers | Machine Learning library

First, I should note that "destructors" are now more commonly referred to as "finalizers", as the former term implies these special methods work like destructors in C++, but they really don't. So you might have better luck searching if you use the newer term.

To your question, yes, there is evidence that .NET has a time limit on finalizers during shutdown - common quotes say one finalizer taking more than 2 seconds, or all finalizers taking 40 seconds - will cause the runtime to give up and just shutdown without continuing to let finalizers run.

I would recommend looking into implementing IDisposable to handle cleanup deterministically. C# has syntax sugar - the using statement - to help make this easier on the consumer's side.

Where did I go wrong here?

Short version:

The important thing to realize here is that C# is not like C++ where } means "we must run destructors of locals now".

C# is allowed to increase the lifetime of any local variable at its discretion, and it does so all the time. Therefore you should never expect a local variable's contents to be collected just because control enters a region where the variable is out of scope.

Long version:

The rule that { } defines a nested local variable declaration space is a rule of the C# language; it is emphatically NOT a feature of the IL that C# is compiled to!

Those local variable declaration spaces are there so that you can organize your code better and so that the C# compiler can find bugs where you used a local variable when it was not in scope. But C# does NOT emit IL that says "the following local variables are now out of scope" at the bottom of your { } block.

The jitter is allowed to notice that your second myClass is never read from and therefore could be removed from the root set after the final write. But the fact that it is allowed to do so does not require it to do so, and typically it will not.

That "typically" is doing some heavy lifting there because, of course, the jitter is allowed to shorten the lifetime of a local. Consider this bad situation:

I have installed using instructions at this link for the Install NGINX using NodePort option.

The problem is that you are using outdated k0s documentation: https://docs.k0sproject.io/v1.22.2+k0s.1/examples/nginx-ingress/

You should use this link instead:
https://docs.k0sproject.io/main/examples/nginx-ingress/

You will install the controller-v1.0.0 version on your Kubernetes cluster by following the actual documentation link.

To make this simpler, since you're only calling your function to get the size of the current folder (zip), you can use a Calculated Property for this:

If you would like to create a client for custom object follow the following steps:

1. Describe the custom resource for which you would like to create a rest client:

I really hope nobody else runs across this, but finally I found the problem and for once it was not only between the chair and the monitor, but also RTFM was involved.

As mentioned I am using minikube to run my k8s cluster which provides PVs stored on the host disk. Where it is stored you may ask? Exaclty, here: /tmp/hostpath-provisioner/default/data-sessiondb-0/data/. You find the problem? No, I also took some time to figure it out. WHY ON EARTH does minikube use the tmp folder to store persistant volume claims?

This folder gets autom. cleared every now and so on.

SOLUTION: Change the path and DO NOT STORE PVs IN tmp FOLDERS.

They mention this here: https://minikube.sigs.k8s.io/docs/handbook/persistent_volumes/#a-note-on-mounts-persistence-and-minikube-hosts and give an example.

But why use the "dangerous" tmp path per default and not, let's say, data without putting a Warning banner there?

Sigh. Closing this question ^^

--> Workaround: https://github.com/kubernetes/minikube/issues/7511#issuecomment-612099413

Github issues to this topic:

• https://github.com/kubernetes/minikube/issues/7511
• https://github.com/kubernetes/minikube/issues/13038
• https://github.com/kubernetes/minikube/issues/3318
• https://github.com/kubernetes/minikube/issues/5144

My Github issue for clarification in the docs: https://github.com/kubernetes/minikube/issues/13038#issuecomment-981821696

mode may not work in some cases.

Try changing

Problem

Author of the question made some changes in his Job. After the update he got a "field is immutable" error.

This is caused by the fact that .spec.template field in Job is immutable and can not be updated.

Solution

Delete the old Job and create a new one with necessary changes.

This issue is commonly caused because the cattle-cluster-agent cannot connect to the configured server-url. Plus, let me inform you that from Rancher 2.5 and newer versions, cattle-node-agents are only present in clusters created in Rancher with RKE. You can visit the following URL which has the Official Rancher’s Documentation regarding to your issue and follow the instructions there to solve it:

Rancher Registered clusters