Debugger | just a log system for tolua

Javascript is case sensitive. I see that you used subreport and it should be subReport with a capital R.

Both Swing and JavaFX are single-threaded UI toolkits, and each has their own thread for rendering the UI and processing user events. Modifying Swing components and creating Swing windows (e.g. JFrames) must be done on the AWT event dispatch thread. Modifying JavaFX components must be done on the FX Application Thread.

Thus when you're working with both toolkits together, you have to be careful to delegate the appropriate actions to the appropriate threads. The Javadocs for JFXPanel have more details.

Here's a complete example which includes a slight re-working of your code and shows how to move the different parts of the code to the appropriate thread:

You should have a manifest.json looking like this

Please enable the quarkus-smallrye-jwt TRACE logging to see why the tokens are rejected. And indeed, as you have also found out, https protocol needs to be enabled in the native image, which can be done, as you have shown :-), by adding --enable-url-protocols=https to the native profile's properties in pom.xml.

This PR will ensure adding it manually won't be required.

thanks

Removing node_modules and lock file and reinstalling it fixed my problem.

No sequential-across-lanes pack until AVX-512, unfortunately. (And even then only for 1 register, or not with saturation.)

The in-lane behaviour of shuffles like vpacksswd and vpalignr is one of the major warts of AVX2 that make the 256-bit versions of those shuffles less useful than their __m128i versions. But on Intel, and Zen2 CPUs, it is often still best to use __m256i vectors with a vpermq at the end, if you need the elements in a specific order. (Or vpermd with a vector constant after 2 levels of packing: How do I efficiently reorder bytes of a __m256i vector (convert int32_t to uint8_t)?)

If your 32-bit elements came from unpacking narrower elements, and you don't care about order of the wider elements, you can widen with in-lane unpacks, which sets you up to pack back into the original order.

This is cheap for zero-extending unpacks: _mm256_unpacklo/hi_epi16 (with _mm256_setzero_si256()). That's as cheap as vpmovzxwd (_mm256_cvtepu16_epi32), and is actually better because you can do 256-bit loads of your source data and unpack two ways, instead of narrow loads to feed vpmovzx... which only works on data at the bottom of an input register. (And memory-source vpmovzx... ymm, [mem] can't micro-fuse the load with a YMM destination, only for the 128-bit XMM version, on Intel CPUs, so the front-end cost is the same as separate load and shuffle instructions.)

But that trick doesn't work work quite as nicely for data you need to sign-extend. vpcmpgtw to get high halves for vpunpckl/hwd does work, but vpermq when re-packing is about as good, just different execution-port pressure. So vpmovsxwd is simpler there.

Slicing up your data into odd/even instead of low/high can also work, e.g. to get 16 bit elements zero-extended into 32-bit elements:

Per the documentation for Canvg.from, you need to pass it your drawing context, not the canvas itself. So change this line:

It appears that azure is not connecting with your build either because you have it configured precariously or because of an over abundance of sql data you want it to work on so fast. My guess is the second.

Macro expansion happens at compile time. Your message indicates that the file that uses the macro was compiled when the macro was not defined, so the compiler assumed that the unknown name my-macro names a function (if you look at the compilation logs, you should see a message to that effect).

Solution: require the file containing macro definitions in files that use them.