zk | Zettelkasten on the command-line 📚 🔍 | Text Editor library

Known bug on the Apache Kafka side. Nothing to do from Spring perspective. See more info here: https://github.com/spring-projects/spring-kafka/discussions/2027. And here: https://issues.apache.org/jira/browse/KAFKA-13391

You need to wait until Apache Kafka 3.0.1 or don't use embedded Kafka and just rely on the Testcontainers, for example, or fully external Apache Kafka broker.

Parsehub REST api wrapper class has solved the problem https://github.com/msankhala/parsehub-php

Just to make sure I've understood:

• You have some zul fragment (such as a reusable UI structure)
• This fragment uses the MVVM pattern, but you want to choose a viewModel object when you are instantiating that fragment, instead of declaring a class name in the zul viewModel="@id()@init()" attribute
• You want to initialize that fragment from a java class that has access to the UI (using Execution#createComponents to load the fragment and attach them to the page)

Does that sound correct?

If that's the case, you can make this way simpler The attribute can be written as viewModel="@id('yourVmId')@init(aReferenceToAnAlreadyInstantiatedObject)".

Important note here: Notice that I have NOT put quotes around the object in the @init declaration. I'm passing an actual object, not a string containing a reference to a class to be instantiated.

When you invoke execution.createComponents() you may pass a map of arguments to the created page. You can then use the name of the relevant passed object when you create bind the VM.

have a look at this fiddle (bit rough, but it should make sense): https://zkfiddle.org/sample/2jij246/4-Passing-an-object-through-createComponents-as-VM#source-2

The simple answer is use Plotly Express

I summed height of all elements in the design. It was 308. Then, I think 310 will be an ideal number. No problem, when I make it 310. Everything seems good.

1. When we take the trouble to initialize an nf structure with nfinit, we perform precomputations to speed up later work. Here, nfinit first computes the integer basis by calling nfbasis, which returns the (canonical) HNF basis, then LLL-reduces it with respect to the T2 norm. The LLL-reduced basis is usually different from the HNF one, but it usually have smaller elements.

2. This LLL reduction can be expensive (in particular when the degree is large) but it ensures that time complexities are bounded in terms of the field discriminant instead of the size of the input polynomial. I believe all polynomials defining number fields in the lmfdb were run through polredabs which ensures their coefficients are small (in terms of the field discriminant), but the HNF integer basis may still be much larger than the LLL one. Additionally, if an algebraic integer has small T2 norm, its expression in terms of the LLL-reduced basis is guaranteed to have small coefficients, whereas it can have much larger coefficients on the HNF basis.

3. In pari-2.14 (which is not released yet but available via git or through nightly snapshots on the PARI/GP website), you can use nfinit(, 4), which removes the LLL reduction step. This speeds up the initialization, but usually slows down every operation involving the resulting nf.

They are not implemented yet. There are plans to expose keeper metrics through Prometheus endpoint.

It looks like you are trying to use the forEach attribute. While it's a possible choice, I'd recommend against it because it's an older (and less wieldy) iteration option in ZK.

Your option are: ZUTI - forEach element (require ZK EE)

This is the easiest an most straightforward iterative template option. Collection and template goes in, templated result goes out.

The error shows that it can't find suitable table sink