WSL | Weakly Supervised Object Localization with Progressive | Internationalization library

In my opinion, the CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE setting seems to be wrong.
you can check docker-compose.yaml or core.yaml

• I will explain fabric-samples/test-network as targeting according to your current situation.
• You can check in CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE in docker-compose.yaml
• Perhaps in your case(fabric-samples/test-network), the value of ${COMPOSE_PROJECT_NAME} was not set properly, so it was set to _test.
• Make sure the value is set correctly and change it to your network name.

Replace python==X with python=X (where X is the version) and for the version from 2.7.12 to 2.7

conda create --name tst python=2.7

Inside your /lib/modules has no entry with WSL2 "uname -r" output

Although WSL2 has /lib/modules/5.4.72-microsoft-standard-WSL2 (as a softlink), this soft link does not appear in the container.

The solution is adding this line to the Dockerfile*:

So, apparently the problem lies with windows, or the WSL to be precise. WSL does not seem to support the set termguicolors which is responsible for the weird colors appearing on screen. And because this is essential for several colorschemes (otherwise they look very different). So unless WSL2 provides this feature I don't think it is possible for windows to have any of the fancy colorschemes. The best option is to probably use a virtual machine and run linux or dual-boot your device.

Asking for a directory that does not exist throws this error.

In my case, I tried

There are two ways to go about this:

1. You can change your working directory to that of your shell script and execute it normally. To do so, follow these steps:

• Mount the relevant drive cd /mnt/c/.
• Change directories according to the path of the script.

1. This approach is more of a hack that I use for the sake of convenience. I have created a folder in my Windows storage wherein I store all Ubuntu WSL related files. Say, D:\Ubuntu. To avoid changing the working directory every time you open WSL, you can modify the shell profile file (bashrc, zshrc etc.) to load the relevant directory at the end.

• i.e., Add cd /mnt/d/Ubuntu/ at the end of your ~/.zshrc file if you use zsh or the relevant profile file otherwise.

This is indeed a shortcoming of Get-Clipboard. The HTML format is documented to support only UTF-8, regardless of the source encoding of the page, so the cmdlet should interpret it as such, but it doesn't.

I'm speculating as to the encoding PowerShell is going to be using when decoding the data, but it's probably whatever the system default ANSI encoding is. In that case

Based on our comments exchange, the problem is that the directory in which the pipenv executable is located - /home//.local/bin/ - isn't present in the PATH environment variable when invoking a command non-interactively.

This suggests that it is an initialization file that extends PATH, and it seems that it is ~/.bash_profile in your case; to force a non-interactive invocation to source this file, the -l option must be passed.

You report that the following command ultimately worked for you:

If you're able to use the WSL terminal with kafka-console-consumer, then running Python code there should work the same.

If you're connecting to a remote Kafka server, chances are the WSL2 network settings are simply not able to reach that address. (multiple issues elsewhere talk about WSL2 and not having external internet access) . Therefore, you should really consider running Python code on the Windows host itself. Otherwise, sounds like you'll need to adjust your network configurations.

The for loop will wait for new messages to a topic, not read existing data until you add another parameter to the consumer to tell it to

FWIW, you can use kafka-console-consumer ... >> file.txt to write out to a file