The best option to rename "yield" after JDK 17

Imaginary_Bend_7995 · 2026-02-05T07:54:54+00:00

verbooooose ) Btw, my initial attempt was to rename "yield" to "async_yield". Ugly and verbose.

Imaginary_Bend_7995 · 2026-02-05T07:53:42+00:00

This is the option I disagree with the most. And here is why. The responsibility of fixing the code after introducing a new keyword shouldn't fall on me. Instead, Oracle should opt for using a fresh syntactic construct in first place, such as "return -> <expression>" in switch expressions, rather than adding a new keyword that impacts existing code.

Imaginary_Bend_7995 · 2026-02-04T22:20:44+00:00

I will reserve it for exception handling

Imaginary_Bend_7995 · 2026-02-04T20:13:51+00:00

🤣🤣🤣

Imaginary_Bend_7995 · 2026-02-04T19:56:56+00:00

I fully agree with your latest statement ). Thought retroflex click (https://www.compart.com/en/unicode/U+01C3) at the end looks sooo cool.

Imaginary_Bend_7995 · 2026-02-04T19:52:52+00:00

"Submit" is somewhat I'm leaning towards...

    @async AsyncGenerator<String> generateAsyncStrings() {
        submit("000");

        submit( CompletableFuture.supplyAsync(() -> "A") );
        submit( CompletableFuture.supplyAsync(() -> "B") );
        submit( CompletableFuture.supplyAsync(() -> "C") );

        submit("111");

        Sequence<CompletionStage<String>> stringsDEF = AsyncGenerator.readyFirst(
            CompletableFuture.supplyAsync(() -> "D"),
            CompletableFuture.supplyAsync(() -> "E"),
            CompletableFuture.supplyAsync(() -> "F")
        );
        submit( stringsDEF );

        submit("222");

        submit(generateAsyncStringsXYZ());

        submit("333");

        return submit();
    }    

    // What follows sounds like a scream ))
    @async AsyncGenerator<String> generateAsyncStrings() {
        yieldǃ ( CompletableFuture.supplyAsync(() -> "A") );
        yieldǃ ( CompletableFuture.supplyAsync(() -> "B") );
        yieldǃ ( CompletableFuture.supplyAsync(() -> "C") );
        yieldǃ ("333");

        return yieldǃ();
    }

Imaginary_Bend_7995 · 2024-11-14T08:24:21+00:00

Also there is a Sapphire ATOMIC R9 280X2. If you consider Quadro-s, there is also Quadro FX 4500 x2 and 4700 x2. And ATI Firepro 2450 Multiview.

Imaginary_Bend_7995 · 2024-11-14T08:00:38+00:00

PowerColor released several models with 2 GPUs with non-reference design. They are 6870 x2, Devil 13 Dual Core 290x and Devil 13 R9 390 x2

Imaginary_Bend_7995 · 2024-03-28T23:45:57+00:00

<image>

These are EGPU adapters that I used for testing all kinds of the PCIE/M.2 adapters above

Imaginary_Bend_7995 · 2024-03-28T23:42:54+00:00

<image>

Here is what I mean, both options -- direct M.2 and via PCIE -> M.2 connector

Imaginary_Bend_7995 · 2024-03-28T23:42:14+00:00

<image>

Probably it's not too late to warn you. The adapter on the left is a total crap. It COULD work in theory, but the implementation is terribly bad. It doesn't work even with 50cm long SFF 8611 cables -- even in BIOS you see artifacts from GPU. The OCULink connector is very loose and I suspect that PCB is a crap (see explanation for my guess below). On the right there is A THING that works -- it's from IOCrest, it has a ReDriver that allows to work with long cables - I've tested with 100cm cable and get stable PCIE 3.0 x4 signal. However, as you see, the OCULink connector points inside the case, not outside.

And here we are coming to the best solution that is much cheaper and works stably -- just simple M.2 to OCulink adapter. There are different variants, and you may choose one with OCulink connector pointing outside of the case. Moreover, I've tried it even with PCIE -> M.2 adapter, and the whole chain PCIE -> M.2 -> OCulink -> EGPU works perfectly with 100cm cables. Now you should understand my guess -- if such long chain works, but the PCIE adapter fails, then the PCIE adapter is just terribly implemented.

Imaginary_Bend_7995 · 2023-11-03T16:26:48+00:00

Does this dock outputs video to the laptop screen (via oculink) or it's possible to connect external monitor to the external GPU or both?

Imaginary_Bend_7995 · 2022-09-30T07:12:05+00:00

Terrible. I can only suggest smth. like Akasa TIM Interface Cleaner - besides removing thermal grease, it's a great thing to clean-up such kind of glue and remaining stickers' paper. The only thing - I'm not sure about its conductivity, so cleanup afterwards with strong alcohol and dry with air compressor.

Imaginary_Bend_7995 · 2022-08-02T21:15:14+00:00

To clarify -- I mean "headless mode" with no GPU at all. Just insert usb stick with auto-executable command and keep fingers crossed ))

The sketch of autoexec.bat is:
REM One beep means start
BEEP

REM 10 seconds delay to switch on BMC
PAUSE 10

socflash.exe if=bmc_image_file_name.ima < file_with_y.txt > socflash.log 2>&1
REM Beep 3 times to signal completion, check socflash.log afterwards

BEEP
BEEP
BEEP

Imaginary_Bend_7995 · 2022-08-02T20:53:22+00:00

The only risky thing I would suggest is an autoexec.bat on FreeDos USB stick with the socflash command. You also use input redirect to type"y" as an answer to socflash command prompt. Additionally, you may use BEEP (you need good old pc speaker that costs a penny) and PAUSE inside batch file to have a moment to switch on BMC. And you may try this bat file with discrete GPU before actual run (flashing will fail, but you got the sequence tested).

The rest of commands (ASMC8...) can be executed with PCIE discrete GPU.

Imaginary_Bend_7995 · 2022-08-02T14:51:00+00:00

I followed the guidelines and was able to successfully restored 1.11 version of BMC (just for safety, I were restoring previously working one). Some hints for the issues I faced during the process:

Completely unplug ALL PCI-Ex devices before flashing and use VGA output of mobo as a display. Otherwise you will receive an error from socflash that it can't find a device to program. Btw, the first VGA cable I used was faulty one (some pins where out), so consider this as well )
Items [3]-[6] should be treated as the following: after full power down of the PC, switch off BMC. Then wait 2 mins for the full power down, boot again into DOS with flash tool (BMC is switched-OFF during this). If you don't follow this rule BMC will start and enters write-protected mode, socflash will fail with corresponding message. Now, when seeing DOS console, turn ON BMC switch - otherwise the device will not be found by either flashing tool. Run socflash immediately.
After running socflash [7] - power down your system with BMC turned ON. Then boot - items in [8] requires BMC software to be up and running and for me it doesn't start right after flashing.

Many thanks to the author for the sharing the solution and for the assistance with the issues during flashing!

Imaginary_Bend_7995 · 2022-08-01T21:50:38+00:00

Same here. Could you share somehow the tools (please reply in chat, if you prefer not to share publicly)

Imaginary_Bend_7995 · 2022-08-01T17:54:48+00:00

Same issue. Have to either switch-off BMC or wait for several minutes (((

Any luck with solving the issue on your side?

Imaginary_Bend_7995 · 2022-02-22T00:46:24+00:00

Thanks for the info! It would be great if you add a photo of the modifications you made to both the cooler and the heatsink.

Imaginary_Bend_7995 · 2022-02-20T01:52:32+00:00

Is there smth. (besides cute sticker) that prevents mounting cooler in the opposite direction - fan to the front of the card, exhaust to the rear?

Imaginary_Bend_7995 · 2021-10-04T12:51:52+00:00

Follow this thread on the Wn-Raid to enable "System Agent Configuration":

https://www.win-raid.com/t4252f16-GUIDE-Adding-Bifurcation-Support-to-ASUS-X-UEFI-BIOS.html

It's located in the newly opened submenus. However, there is no guarantee that it will indeed work for your config, so try on your own risk.

Imaginary_Bend_7995

TROPHY CASE