developers.redhat.com | Sources for developer.redhat.com

I read an article https://developers.redhat.com/articles/2021/07/16/whats-new-fabric8-kubernetes-client-version-550#new_features_in_fabric8_kubernetes_client_5_5_0, it mentioned in 5.5 release it adds "Certification management", however, seem I could not find any source codes related to it in fabric8 repo.

when I run a simple code like this

For a long time I thought that event loop implementation (libuv?) used in Chrome and Node.js used threads. But then I was reading this article on lightweight threads in Java that stated the following:

...instead of creating threads for each concurrent task (and blocking tasks), a dedicated thread (called an event loop) looks through all the tasks that are assigned to threads in a non-reactive model, and processes each of them on the same CPU core.

And the the book Computer Systems. A Programmer’s Perspective in the chapter on concurrent applications states that modern operating systems provide three basic approaches for building concurrent programs (3 approaches to implementing logic flows):

• Processes. With this approach, each logical control flow is a process that is scheduled and maintained by the kernel. Since processes have separate virtual address spaces, flows that want to communicate with each other must use some kind of explicit interprocess communication (IPC) mechanism.

• I/O multiplexing. This is a form of concurrent programming where applications explicitly schedule their own logical flows in the context of a single process. Logical flows are modeled as state machines that the main program explicitly transitions from state to state as a result of data arriving on file descriptors. Since the program is a single process, all flows share the same address space.

• Threads. Threads are logical flows that run in the context of a single process and are scheduled by the kernel. You can think of threads as a hybrid of the other two approaches, scheduled by the kernel like process flows and sharing the same virtual address space like I/O multiplexing flows.

So now I'm wondering now if the event loop falls under I/O multiplexing logical flow and doesn't use threads?

I'm trying to write a Rust module which can be called from Python. I'm following this page:

https://developers.redhat.com/blog/2017/11/16/speed-python-using-rust#edit_src_lib_rs

On cargo build --release I get this error:

= note: LINK : fatal error LNK1181: cannot open input file 'python39.lib'

This has come up before, and this seems the most recent and relevant answer.

I seem to have tried all the possible solutions in that answer, including locating and running vcvars64.bat, as detailed here. No joy.

I have MS Visual Studio (2019) installed, with the C++ and W10 SDK components.

Significantly, this error sometimes does not occur when I don't include the --release switch. Without it, the program (sometimes) compiles and runs OK. Given that one reason for wanting to make a Rust module is performance, however, I'd like to solve this problem. Also I have now found that this successul building of a "debug" build is a) intermittent and b) partial: when it fails, some of the desired output files are created but not others.

And...

According to the page at the first link, it seems that after build, I should then be looking for a file ending .so. In a W10 OS I'm looking for a .dll file.

If it builds completely successfully, under target\debug I have myrustlib.d, myrustlib.dll, myrustlib.dll.exp, myrustlib.dll.lib, myrustlib.pdb, pyext_myrustlib.pdb, pyext_myrustlib.d and pyext_myrustlib.exe. None of these, renamed and/or given an .dll extension as applicable, can be successfully imported as a Python module, at least as documented on that page.

I've also found this more recent page for doing the same thing. I get the same 1181 error.

python39.lib

I found out where this is located in my system, under ... Python\Python39\libs. I modified my PATH env var to specifically include this path (and rebooted). Still the same error.

According to this, I can specify system property KUBECONFIG to tell defaultKubernetesClient to use the specified kubeconfig file instead of the default ~/.kube/configfile.
What should I do that then I'm using fabric8io?
Tks in advance.

I just saw a college doing this optimization today:

i.e., change this:

I'm testing Hibernate Search 6 multitenancy with Hibernate (referred to this link) and got error message "HSEARCH000520: Hibernate Search encountered failures during bootstrap", with additional detail, "HSEARCH600029: Invalid backend configuration: index 'Users' requires multi-tenancy but no multi-tenancy strategy is set".

I apply to my Users entity. Here is the Users entity class.

I need to configure Keycloak to get a JWT token as in this blog post, but I have to do it with cUrl. They create a client and then update it setting access type to confidential, Direct Grant Flow to direct grant, and Browser Flow to browser. The PUT request from the web UI that does this has some uuids that they seem to have pulled out of nowhere. Here is the relevant part of the payload:

I have an Angular app deployed to kubernetes with the kubernetes ingress controller. There is one setup with a single-node cluster and one with a multi-node cluster. The MIME-Type problem occurs with both setups but the single-node can resolve it very quick while on the multi-node the latency is not acceptable.

On the multi-node cluster the Time To First Byte takes about 5 sec for:

• initial call to example.com
• runtime-es2015.js
• polyfills-es2015.js
• appConfig.json (custom config file)
• favicon.ico
• various png/svg files

What works within a normal timeframe are:

• main-es2015.js
• scripts.js
• styles.css
• ng-validate.js

My cluster setup is as following:

• 2 Control-Plane nodes
• 2 Worker nodes
• Cluster networking with canal
• The cluster was setup with RKE (if that matters)

The index.html in the Angular app contains:

I am working on an application that has a cluster of Artemis servers. Each live server is paired with a backup server for failover. I happened on an article by Bilgin Ibryam, and it has me wondering.

If the clustered live servers are running as containers, and the orchestrator restarts any containers that die, is the failover configuration necessary? The article says "no".

So if I understand correctly, running a cluster of Artemis brokers in an environment that detects and restarts failed brokers will provide the same semantics (and similar availability) as running a cluster where each live server is paired with a backup. Is that right?