official | Website for Ruby no Kai

I've never used it. But, here's what Morgan's Library and Burleson Consulting say about it (didn't find any reference in "official" Oracle documentation).

AUTO_PURGE purges from the logs based on class and global log_history.

The AUTO_PURGE procedure uses the log_history values defined at the scheduler, job class and job log_history level to determine which logs should be purged. This procedure runs as part of the scheduled purge process, but it can also be run manually.

Generally, if there are any incompatibility between TF, CUDA and cuDNN version you can observed this behavior.

For GeForce RTX 3060, support starts from CUDA 11.x. Once you upgrade to TF2.4 or TF2.5 your issue will be resolved.

For the benefit of community providing tested built configuration

CUDA Support Matrix

Short answer: It's undefined behavior.

Most OpenAPI serialization styles are based on RFC 6570, which provides guidance only for:

• primitive values,
• arrays of primitives,
• simple non-nested objects (with primitive properties).

In case of other types of values (nested objects, objects containing arrays, nested arrays, arrays of objects) the behavior is undefined.

Similarly, OpenAPI's own deepObject style is currently defined only for simple objects but not for arrays or nested objects. Here are some related comments from the OpenAPI Specification authors/maintainers:

By the way, is there a reason we couldn't have deepObject work for arrays too? [...]

Darrel: Supporting arrays as you describe was my intent. I was supposed to find some canonical implementation to use as a guideline for the behavior, but didn't get around to it.

Ron: If we end up supporting the exploded array notation, it needs to be clear that the first index is 0 (or 1, or -1, or whatever).

(source)

Ron: when we defined deepObject in the spec, we explicitly chose to not mention what happens when the object has several levels in it, but in our conversations we went with 'not supported'. ​

(source)

There's an existing feature request to extend deepObject to support arrays and nested structures:
Support deep objects for query parameters with deepObject style

Kubernetes is a container orchestrator that may use Docker as its container runtime. So, they are quite different things—essentially, different levels of abstraction.

You could theoretically run an application at both of these abstraction levels. Here's a comparison:

Docker

You can run an application as a Docker container on any machine that has Docker installed (i.e. any OS or cloud provider instance that supports Docker). However, you would need to implement any operations-related features that are relevant for production, such as health checks, replication, load balancing, etc. yourself.

Kubernetes

Running an application on Kubernetes requires a Kubernetes cluster. You can run a Kubernetes cluster either on-premises, in the cloud, or use a managed Kubernetes service (such as Amazon EKS, Google GKE, or Azure AKS). The big advantage of Kubernetes is that it provides all the production-relevant features mentioned above (health checks, replication, load balancing, etc.) as part of the platform. So, you don't need to implement them yourself but just use the primitives that Kubernetes provides to you.

Regarding your two requirements, Kubernetes provides both of them, while using Docker alone does not provide easy production-readiness (requirement 2). So, if you're opting for production stability, setting up a Kubernetes cluster is certainly worth the effort.

The first example uses the CSS in the Antora UI, the second uses the standard Asciidoctor CSS. The HTML created in both scenarios is the same.

If you want the a similar styled HTML output as with the Antora UI, you'll need to borrow the necessary CSS from the Antora UI and integrate it into the theme you use for your HTML output.

Just do that and you will be fine (all external classes will be excluded):

The SAP IAS Tenant was configured with OpenID connect. For some reason, logout functionality is not working with OpenID Connect and there is not clear document on this. Once switched from OpenID Connect to SAML, logout functionality is working fine. This is a work around and may not be an actual solution. It's an issue with SAP CF. They have to solve it.

This Blog will help you configure your IAS Tenant.

Note: Logout is not working with default identity provider too. And IAS Tenant is not available for trial accounts.

No. It is fine to just have it in val.

The issue with fragments is that Fragment and its view have different lifecycles, so holding onto the binding in fragment between onDestroyView() and onDestroy() uses unnecessary memory.

In custom views, it has same lifecycle as any binding stored in a class property.

Your first query should be fine just adjusted to match the format that Django expects.

First, replace ? with %s to pass parameters to the query

Second, replace % with %% as a single percent is an "escape" character and you need to escape the escape char

DOCS

Here's your original query truncated to show an example of how it could work