fresh | Preact , but super edgy | Frontend Framework library

From rails tailwind readme

Tailwind uses modern CSS features that are not recognized by the sassc-rails extension that was included by default in the Gemfile for Rails 6. In order to avoid any errors like SassC::SyntaxError, you must remove that gem from your Gemfile.

https://github.com/rails/tailwindcss-rails

The following works by subclassing the relevant class, and duplicating code with the relevant changes. We also have to subclass the Client class, to overwrite the place where the gateway/websocket class is used. This results in a lot of duplicated code, however it does work, and requires neither dirty monkey-patching nor editing the library source code.

However, it does come with many of the same problems as editing the library source code - mainly that as the library is updated, this code will become out of date (if you're using the archived and obsolete version of the library, you have bigger problems instead).

From the terminal messages, you are installing an old version of node-gyp (node-gyp@3.8.0). From a quick search, it seams that this version requires python 2. Python 2 should be present in Big Sur. Properly setting the path, should work:

Since you mention executing the same files (with proper performance) from within Git Bash, I'm going to make an assumption here. Correct me if I'm wrong on this, and I'll delete the answer and look for another possibility.

This would be explained (and expected) if your files are stored on /mnt/c (a.k.a. C:, or /C under Git Bash) or any other Windows drive, as they would likely need to be to be accessed by Git Bash.

WSL2 uses the 9P protocol to access Windows drives, and it is currently known to be very slow when compared to:

• Native NTFS (obviously)
• The ext4 filesystem on the virtual disk used by WSL2
• And even the performance of WSL1 with Windows drives

I've seen a git clone of a large repo (the WSL2 Linux kernel Github) take 8 minutes on WSL2 on a Windows drive, but only seconds on the root filesystem.

Two possibilities:

• If possible (and it is for most Node projects), convert your WSL to version 1 with wsl --set-version 1. I always recommend making a backup with wsl --export first.

  And since you are making a backup anyway, you may as well just create a copy of the instance by wsl --importing your backup as --version 1 (as the last argument). WSL1 and WSL2 both have their uses, and you may find it helpful to keep both around.

  See this answer for more details on the exact syntax..

• Or just move the project over to somewhere under the WSL root, such as /home/username/src/.

You can try disabling hardware acceleration using app.disableHardwareAcceleration() (See the docs). I don't think this is a fix though, it just makes the message go away for me.

main.js

I cannot reproduce your issue using:

1. openjdk:8-jre-alpine docker image
2. JMeter 5.4.1
3. Test plan Test.jmx from extras folder of JMeter

Demo:

If you cannot reproduce the above behaviour I think you made some changes either to Results File Configuration or to Reporting Configuration or both so you need to inspect all the JMeter Properties which differ from the defaults and restore their values to the original ones.

If you need further support you need to share at least first 2 lines of your outFilePath.jtl results file. Better if possible the full file and all the .properties files from JMeter's "bin" folder.

I found and tested in shorter toggle mechanism.

The configuration for Windows Feature:

• Windows Subsystem for Linux is installed.
• Windows Hypervisor Platform is installed.
• Hyper-V is installed.

If you need the Emulator, you only need to turn off Hypervisor + Restart. Run: bcdedit /set hypervisorlaunchtype off

If you need the Docker back, you can run the hypervisor hence disabling Emulator. Run: bcdedit /set hypervisorlaunchtype auto

You need to restart after setting Hypervisor

You cannot run both at the same time. Another forum worth checking in How about running docker? in my older answer below.

I think I solved this issue, tested to run from CMD / Android Studio and ran perfectly as before installing WSL. There are several step we go:

1. Removed Windows Subsystem for Linux
2. Removed Windows Hypervisor Platform
3. Removed Hyper-V

Here is my current setup:

I know after removing there are some odds because the AVD still get the same error as before and expected to get into WSL. I stumbled and found something when ran:

C:\Users\[NAME]\AppData\Local\Android\Sdk\emulator\emulator-check.exe accel

That command will check the current accel. It explains that the Hypervisor need to be set off and give specific help: run bcdedit /set hypervisorlaunchtype off.

After running the bcdedit, I restarted and all is reverted. Now I can run emulator both from CMD and Android Studio perfectly.

Sad truth, yeah you cannot run both pararel. There are several workaround in this forum:

How can I run both Docker and Android Studio Emulator on Windows?

Several option ranging from changing emulator, add & remove docker when in need using above step, created nested vm, etc. My personal choice right now is using another Emulator for the time being and removed docker for the latter.

remove the import line from your project and import it again by pressing Alt+Enter then inform me

My best solution so far is to create a shared folder.

I decided to make C:\Users\\AppData\Local\Temp\VSWebView2Cache\ shared. The "VS" prefix indicates that this is a Visual Studio-specific folder, and I think it is acceptable that my normal user can have access to that folder as it seems to contain temporary Visual Studio files.

To do so I logged in to Windows with the administrator account. I navigated to the folder and made it a shared folder. I added my no-admin user with "Read/Write" privileges. I then tested by logging out of the admin account and into my no-admin account. There I first tried the full path in File Explorer and was granted access to the folder. I then tested with VS2022 and during debugging no error box appeared and files were generated in the folder.

If anyone finds a better approach, I'd really like to hear about it. Also if you have knowledge to why this approach is either good or bad, that would be highly appreciated as well.