Winsock module breaks WSL2

For an workaround provided by Proxifier, see https://github.com/microsoft/WSL/issues/4177#issuecomment-597736482
Please fill out the below information:

Your Windows build number:  10.0.18917.1000

What you're doing and what's happening:
After updating from 1903 to 18917, I upgraded to WSL2 and it works fine. Later, I enabled https://www.proxifier.com/'s winsock module in its "System Setting 64-bit" app, and WSL2 starting to fail with The attempted operation is not supported for the type of object referenced..

⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl
The attempted operation is not supported for the type of object referenced.
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl -l -v
NAME            STATE           VERSION
* Ubuntu-18.04    Running         2
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl --shutdown
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl -l -v
NAME            STATE           VERSION
* Ubuntu-18.04    Stopped         2
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl
The attempted operation is not supported for the type of object referenced.
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl -l -v
NAME            STATE           VERSION
* Ubuntu-18.04    Running         2
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl -l -v
NAME            STATE           VERSION
* Ubuntu-18.04    Stopped         2
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl
The attempted operation is not supported for the type of object referenced.
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl -l -v
NAME            STATE           VERSION
* Ubuntu-18.04    Running         2
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl
The attempted operation is not supported for the type of object referenced.

After uninstalling the winsock module, WSL2 launches again. And installing the winsock module won't cause running WSL2 console to fail.

What's wrong / what should be happening instead:

WSL2 should work even if there are other winsock modules installed.

Strace of the failing command, if applicable:  N/A

For WSL launch issues, please collect detailed logs.

lxcore.zip

Thanks for providing a trace, I will take a look.

I took a look at the trace and I'm not seeing any relevant events in the service etl.  If possible could you do the following?
wsl.exe --shutdown
start trace
launch distribuiton
stop trace

Steps I take (In a Chinese environment)
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ wsl.exe --shutdown
⚡ Liqueur Librazy C:\..\system32 ❯❯❯ cd 'C:\Users\Liqueur Librazy\OneDrive\桌面\'
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe create trace lxcore_kernel -p "{0CD1C309-0878-4515-83DB-749843B3F5C9}" -mode 0x00000008 -ft 10:00 -o .\lxcore_kernel.etl -ets                                                                       命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe create trace lxcore_user -p "{D90B9468-67F0-5B3B-42CC-82AC81FFD960}" -ft 1:00 -rt -o .\lxcore_user.etl -ets                                                                                命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe create trace lxcore_service -p "{B99CDB5A-039C-5046-E672-1A0DE0A40211}" -ft 1:00 -rt -o .\lxcore_service.etl -ets                                                                                命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ wsl                                                                                参考的对象类型不支持尝试的操作。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe stop lxcore_kernel -ets
命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe stop lxcore_user -ets
命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯ logman.exe stop lxcore_service -ets
命令成功结束。
⚡ Liqueur Librazy ~\..\桌面 ❯❯❯

lxcore.zip

same question,proxifier winsock installation, wsl2 can not work.

Same issue of WSL 2 on my Win10 laptop.

Sorry for a useless comment.
Developers in China highly rely on proxies due to poor network condition. I do hope this issue will be resolved soon.

The same issue. After running a game speed VPN (https://uu.163.com), WSL2 cannot running.
Reset winsock can fix it.
PS C:\WINDOWS\system32> wsl.exe --shutdown
PS C:\WINDOWS\system32> wsl.exe
The attempted operation is not supported for the type of object referenced.
PS C:\WINDOWS\system32> netsh winsock reset

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.

PS C:\WINDOWS\system32> wsl.exe
root@TIGERHOMEPC /mnt/c/Windows/System32
  # exit

The same issue. After running a game speedup VPN (https://uu.163.com), WSL2 cannot running.
Reset winsock can fix it.
PS C:\WINDOWS\system32> wsl.exe --shutdown
PS C:\WINDOWS\system32> wsl.exe
The attempted operation is not supported for the type of object referenced.
PS C:\WINDOWS\system32> netsh winsock reset

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.

PS C:\WINDOWS\system32> wsl.exe
root@TIGERHOMEPC /mnt/c/Windows/System32
  # exit

Build 18922.1000.

I encounter this problem and use this method to solve.  But my proxifier can't be used.

So the problem is, after using any kinds of vpn (such as shadowsocks or whatever), wsl2 will crash when users try to start it. So I think it needs to be compatible with vpns in the future.

Still reproducible on recent insider version

windows10 18941.1001，this problem is still not fixed。

Still relevant. 10.0.18945.1001

The problem exists on build 18950.1000.

still 18956

windows10 18956.1000，this problem is still not fixed。

reproducible in 18963

18963.1000，this problem is still not fixed。

I don't think it makes any sense to keep reporting the bug is still not fixed, because there hasn't been any claim from Microsoft that it's fixed. It's pretty obvious that the issue is universal and easily reproducible, and it's very likely that Microsoft is already aware of it. So such comments only spam this issue and and the email inbox of those who have subscribed to this issue.

I took a look at the traces and unfortunately there really isn't much to go on other than WSAEOPNOTSUPP being returned when trying to call into the Service com interface.  There are no errors originating from our service itself, so I suspect something outside of WSL components is causing the issue.
For people that are hitting this issue, I would suggest looking in the Windows event log or using https://docs.microsoft.com/en-us/sysinternals/downloads/procmon to help track down what is returning the error.  Honestly this seems like an error in https://www.proxifier.com/

As many other winsock modules breaks wsl2, I think it is not Proxifier's fault. It is likely that the communication between wsl2 and other components (likely hyperv?) is broken.
I captured events from wsl.exe using procmon when reproducing the issue
Logfile.zip

@Librazy - Thanks for the additional logs. Unfortunately as I mentioned before, wsl.exe is not where the errors are coming from.  I suspect proxifier and other winsock modules are not correctly handling the Hyper-V socket address family (AF_HYPERV).  I would strongly suggest reporting the issue to them.

If you're still seeing this error, could you help us diagnose it by collecting networking logs?
Instructions on how to do so are here. Thanks!

@craigloewen-msft Thanks for the instructions and here is the log! https://aka.ms/AA5zzk7

@craigloewen-msft - I am not seeing logs attached to @Librazy's feedback hub issue.  Can you investigate?

@benhillis Yup! I'll look into it.

Perhaps worth mentioning that a similar tool, ProxyCap, suffers from the same issue. I forwarded benhillis's comment from before https://github.com/microsoft/WSL/issues/4177#issuecomment-523566234 to them.

I found a workaround. Start proxy client in wsl2, and change windows default route to it.

19008.1 the problem is still not fixed

in 19018.1 it's still there. I can start wsl only after reseting winsock using powershell with administrative privilege. And I noticed that an opened wsl.exe won't crash after starting use vpn.

in 19033.1 this problem is still not fixed.
I didn't use any vpn software.(maybe WeGame network speedup)

windows10 19041.21，this problem is still not fixed。

windows 10 19041.113, this problem is still not fixed, hope it can be fixed.

For anyone using Task Scheduler to run Privoxy or Sockscap on startup, the following event filter seems to fix this issue:
<QueryList>
  <Query Id="0" Path="System">
    <Select Path="System">*[System[Provider[@Name='Microsoft-Windows-Hyper-V-VmSwitch'] and Task=1019 and EventID=102]]</Select>
  </Query>
</QueryList>

Three months, so far so good.

The problem is still not fixed. I need to reset the winsock everytime. winver: 19041.113

Still relevant. 19577

When I use shadowsocksr, I find it can run normally as usual, but there are errors in it's log.
[2020-03-11 17:37:01] [Error] System.Net.Sockets.SocketException (0x80004005): 由于目标计算机积极拒绝，无法连接。 <IP_ADDRESS>:9410
   在 System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
   在 System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   在 Shadowsocks.Controller.Socks5Forwarder.Handler.ConnectCallback(IAsyncResult ar)

[2020-03-11 17:40:28] [Error] System.NullReferenceException: 未将对象引用设置到对象的实例。
   在 Shadowsocks.Util.Utils.QueryDns(String host, String dns_servers, Boolean IPv6_first)
   在 Shadowsocks.Controller.Socks5Forwarder.IsHandle(Byte[] firstPacket, Int32 length, Socket socket)
   在 Shadowsocks.Controller.Socks5Forwarder.Handle(Byte[] firstPacket, Int32 length, Socket socket, String local_sendback_protocol)
   在 Shadowsocks.Controller.ProxyAuthHandler.Connect()
   在 Shadowsocks.Controller.ProxyAuthHandler.HandshakeReceive3Callback(Int32 recv_size)

Maybe this can help you to locate the bug.

Developers of Proxifier told me the reason and gave me a solution.

Thanks for the info.
We have reproduced this issue.
Apparently, wsl.exe displays this error if Winsock LSP DLL gets loaded into its process.
The easiest solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to prevent this.
Under the hood the call creates an entry for wsl.exe at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog
This tells Windows not to load LSP DLLs into wsl.exe process.
We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe
Please just run as admin with the full path to wsl.exe as the parameter:
NoLsp.exe c:\windows\system32\wsl.exe
This has fixed the problem in my case.
Please let me know how it works for you.

And it works well for me!

Developers of Proxifier told me the reason and gave me a solution.

Thanks for the info.
We have reproduced this issue.
Apparently, wsl.exe displays this error if Winsock LSP DLL gets loaded into its process.
The easiest solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to prevent this.
Under the hood the call creates an entry for wsl.exe at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog
This tells Windows not to load LSP DLLs into wsl.exe process.
We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe
Please just run as admin with the full path to wsl.exe as the parameter:
NoLsp.exe c:\windows\system32\wsl.exe
This has fixed the problem in my case.
Please let me know how it works for you.

And it works well for me!

Thanks you! It works for me (19564.1005).

When I run this command  netsh winsock reset and restart my PC, it can be resolved temporarily. But next time when I use WSL, it doesn't work for me.

When I run this command netsh winsock reset and restart my PC, it can be resolved temporarily. But next time when I use WSL, it doesn't work for me.

me too. Windows OS build 19041.173.
And it does not need to restart the OS.

Developers of Proxifier told me the reason and gave me a solution.

Thanks for the info.
We have reproduced this issue.
Apparently, wsl.exe displays this error if Winsock LSP DLL gets loaded into its process.
The easiest solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to prevent this.
Under the hood the call creates an entry for wsl.exe at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog
This tells Windows not to load LSP DLLs into wsl.exe process.
We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe
Please just run as admin with the full path to wsl.exe as the parameter:
NoLsp.exe c:\windows\system32\wsl.exe
This has fixed the problem in my case.
Please let me know how it works for you.

And it works well for me!

@1160300208 Thanks you! It works for me (19564.1005).

Works for me, steps:

Run powershel as Administrator.
Run command .\NoLsp.exe c:\windows\system32\wsl.exe
Then you well see return:  Success!

When I run this command netsh winsock reset and restart my PC, it can be resolved temporarily. But next time when I use WSL, it doesn't work for me. The problem still had happend.

the problem is still not solve, the windows build 19041.246

i cannot use WSL 2 and proxifier at the same time,
netsh winsock reset
will fix it temporarily.

t solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to preven

are you able to connec to internet/network still from WSL after this?

Developers of Proxifier told me the reason and gave me a solution.

Thanks for the info.
We have reproduced this issue.
Apparently, wsl.exe displays this error if Winsock LSP DLL gets loaded into its process.
The easiest solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to prevent this.
Under the hood the call creates an entry for wsl.exe at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog
This tells Windows not to load LSP DLLs into wsl.exe process.
We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe
Please just run as admin with the full path to wsl.exe as the parameter:
NoLsp.exe c:\windows\system32\wsl.exe
This has fixed the problem in my case.
Please let me know how it works for you.

And it works well for me!

Are you able to connect to internet/network still from WSL after doing this?

Proxifier的开发人员告诉了我原因，并给了我一个解决方案。

谢谢（你的）信息。
我们已转载此问题。
显然，如果Winsock LSP DLL被加载到其进程中，则wsl.exe将显示此错误。
最简单的解决方案是对wsl.exe使用WSCSetApplicationCategory WinAPI调用来防止这种情况。

这告诉Windows不要将LSP DLL加载到wsl.exe进程中。
我们有一个可以进行此调用的工具：
www.proxifier.com/tmp/Test20200228/NoLsp.exe
请以管理员身份运行，并以wsl.exe的完整路径作为参数：
NoLsp.exe c：\ windows \ system32 \ wsl.exe
这已经解决了我的问题。
请让我知道它如何为您工作。

它对我来说很好！

Developers of Proxifier told me the reason and gave me a solution.

Thanks for the info.
We have reproduced this issue.
Apparently, wsl.exe displays this error if Winsock LSP DLL gets loaded into its process.
The easiest solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to prevent this.
Under the hood the call creates an entry for wsl.exe at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog
This tells Windows not to load LSP DLLs into wsl.exe process.
We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe
Please just run as admin with the full path to wsl.exe as the parameter:
NoLsp.exe c:\windows\system32\wsl.exe
This has fixed the problem in my case.
Please let me know how it works for you.

And it works well for me!

It‘s the best way to solve this!!! It's works! Even don't need a reboot! Thank you !

For the people using Proxifier like me and if you don't want to do weird stuff on your register,
I had a response from the support of Proxifier, and they responded that their new version still in beta support wsl 2,
I had no issue with my Docker on wsl 2, or on my ubuntu,
www.proxifier.com/beta

Just to let you know that same thing happens with Microsoft Forefront TMG.

Developers of Proxifier told me the reason and gave me a solution.

Thanks for the info.
We have reproduced this issue.
Apparently, wsl.exe displays this error if Winsock LSP DLL gets loaded into its process.
The easiest solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to prevent this.
Under the hood the call creates an entry for wsl.exe at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog
This tells Windows not to load LSP DLLs into wsl.exe process.
We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe
Please just run as admin with the full path to wsl.exe as the parameter:
NoLsp.exe c:\windows\system32\wsl.exe
This has fixed the problem in my case.
Please let me know how it works for you.

And it works well for me!

It saved me. Thanks!

Developers of Proxifier told me the reason and gave me a solution.

Thanks for the info.
We have reproduced this issue.
Apparently, wsl.exe displays this error if Winsock LSP DLL gets loaded into its process.
The easiest solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to prevent this.
Under the hood the call creates an entry for wsl.exe at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog
This tells Windows not to load LSP DLLs into wsl.exe process.
We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe
Please just run as admin with the full path to wsl.exe as the parameter:
NoLsp.exe c:\windows\system32\wsl.exe
This has fixed the problem in my case.
Please let me know how it works for you.

And it works well for me!

After following the prompts, an error will still be reported

As per @Mehdi13k8 comment, after installing the Proxifier v4.01 Beta 2, WSL 2 works as expected.

https://github.com/microsoft/WSL/issues/4177#issuecomment-597736482
This way I was able to launch it from the command prompt with wsl.exe.
However, I can't seem to start wsl from wsltty, wsl-terminal or windows terminal.

Developers of Proxifier told me the reason and gave me a solution.

Thanks for the info.
We have reproduced this issue.
Apparently, wsl.exe displays this error if Winsock LSP DLL gets loaded into its process.
The easiest solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to prevent this.
Under the hood the call creates an entry for wsl.exe at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog
This tells Windows not to load LSP DLLs into wsl.exe process.
We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe
Please just run as admin with the full path to wsl.exe as the parameter:
NoLsp.exe c:\windows\system32\wsl.exe
This has fixed the problem in my case.
Please let me know how it works for you.

And it works well for me!

Doesn't solve my problem with Windows version 19042.630.

Developers of Proxifier told me the reason and gave me a solution.

Thanks for the info.
We have reproduced this issue.
Apparently, wsl.exe displays this error if Winsock LSP DLL gets loaded into its process.
The easiest solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to prevent this.
Under the hood the call creates an entry for wsl.exe at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog
This tells Windows not to load LSP DLLs into wsl.exe process.
We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe
Please just run as admin with the full path to wsl.exe as the parameter:
NoLsp.exe c:\windows\system32\wsl.exe
This has fixed the problem in my case.
Please let me know how it works for you.

And it works well for me!

This works to start WSL, but because of the winsock shutdown, it won't connect to the internet. local network works fine.

I have 2 company computers. Only one has trouble with WSL. So far as I know, computers are same Windows 10 image.  When I try to run wsl, the "bad" computer says
The attempted operation is not supported for the type of object referenced.
Press any key to continue...

If I have an administrator around, they can open PowerShell and run
netsh winsock reset

That solves the problem until the system is forced to reset.
I want to understand why the problem only affects on computer.  Both of them have Cisco VPN, but the problem happens whether or not I'm connected to VPN.  The versions of Cisco AnyConnect Secure Mobility Client are slightly different, thought. The trouble computer has Cisco 4.9.05042.
I don't have a web proxy, that I know of, but if you tell me what to look for, I can try. I don't have admin authority, hence, I'm totally stuck!
It is possible that the corporate IT applied slightly different security policies on the 2 computers. On the new one, but not the old, I could not get the Ubuntu apps to display onto X11 server without a battle with the firewall.  We had to open up both the public and private channels for X410 and Vcxrv to get to the desktop.
Can you help me understand if I have same winsock problem and what program is causing it?

I have 2 company computers. Only one has trouble with WSL. So far as I know, computers are same Windows 10 image. When I try to run wsl, the "bad" computer says
The attempted operation is not supported for the type of object referenced.
Press any key to continue...

If I have an administrator around, they can open PowerShell and run
netsh winsock reset

That solves the problem until the system is forced to reset.
I want to understand why the problem only affects one computer. Both of them have Cisco VPN, but the problem happens whether or not I'm connected to VPN. The versions of Cisco AnyConnect Secure Mobility Client are slightly different, thought. The trouble computer has Cisco 4.9.05042.
I don't have a web proxy, that I know of, but if you tell me what to look for, I can try. I don't have admin authority, hence, I'm totally stuck!
It is possible that the corporate IT applied slightly different security policies on the 2 computers. On the new one, but not the old, I could not get the Ubuntu apps to display onto X11 server without a battle with the firewall. We had to open up both the public and private channels for X410 and Vcxrv to get to the desktop.
Can you help me understand if I have same winsock problem and what program is causing it?

Thanks, this command netsh winsock reset also solves docker/for-win#7208 and docker/for-win#7919

Looks like this magic registry stuff keeps WSL2/winsock combo happy, for at least three of us at work so far.
Disclaimer: works fine for me with no apparent side-effects, but I don't entirely know what it's doing. Use at your own risk...
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0408F7A3]
"AppFullPath"="C:\\\\windows\\\\system32\\\\wsl.exe"
"PermittedLspCategories"=dword:80000000

Same issue and it solves with the winsock reset.  This is another proof that Microsoft is a noob in writing proper software.
"In computing, the Windows Sockets API, later shortened to Winsock, is a technical specification that defines how Windows network software should access network services, especially TCP/IP."  A linux shell should run without using tcp/ip communication.

I encountered the same problem, I deployed Docker with WLS2 at VDI environment, It could be work at the Golden image, but when use the golden image provision bulk of vms, the docker couldn't work.  I searched a lot of info and try to fix the problem. it couldn't work.

I encountered the same problem, I deployed Docker with WLS2 at VDI environment, It could be work at the Golden image, but when use the golden image provision bulk of vms, the docker couldn't work. I searched a lot of info and try to fix the problem. it couldn't work.  Now I do the following processes, It 's fine.

Fixes # I encountered the same problem, I deployed Docker with WLS2 at VDI environment, It could be work at the Golden image, but when use the golden image provision bulk of vms, the docker couldn't work. I searched a lot of info and try to fix the problem. it couldn't work. Now I do the following processes, It 's fine.

Authorize the domain user to control  the folder (C:\program files\Docker)
add domain user to a local group ( docker-users)

I wonder why Winsock LSP DLL gets loaded into wsl.exe when proxy software (proxifier, game accelerator, whatever) work and what does it mean by.
Can we solve the problem simply by blocking Winsock LSP DLL without any side effect?

Proxifier的开发人员告诉了我原因，并给了我一个解决方案。

谢谢（你的）信息。
我们已转载此问题。
显然，如果Winsock LSP DLL被加载到其进程中，则wsl.exe将显示此错误。
最简单的解决方案是对wsl.exe使用WSCSetApplicationCategory WinAPI调用来防止这种情况。

这告诉Windows不要将LSP DLL加载到wsl.exe进程中。
我们有一个可以进行此调用的工具：
www.proxifier.com/tmp/Test20200228/NoLsp.exe
请以管理员身份运行，并以wsl.exe的完整路径作为参数：
NoLsp.exe c：\ windows \ system32 \ wsl.exe
这已经解决了我的问题。
请让我知道它如何为您工作。

它对我来说很好！

Developers of Proxifier told me the reason and gave me a solution.

Thanks for the info.
We have reproduced this issue.
Apparently, wsl.exe displays this error if Winsock LSP DLL gets loaded into its process.
The easiest solution is to use WSCSetApplicationCategory WinAPI call for wsl.exe to prevent this.
Under the hood the call creates an entry for wsl.exe at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog
This tells Windows not to load LSP DLLs into wsl.exe process.
We have a tool that can make this call:
www.proxifier.com/tmp/Test20200228/NoLsp.exe
Please just run as admin with the full path to wsl.exe as the parameter:
NoLsp.exe c:\windows\system32\wsl.exe
This has fixed the problem in my case.
Please let me know how it works for you.

And it works well for me!

It‘s the best way to solve this!!! It's works! Even don't need a reboot! Thank you !

Win10/WSL2 不管用啊

2021 年了，这个问题还没解决，不愧是你，微软

The same issue. After running a game speedup VPN (https://uu.163.com), WSL2 cannot running.
Reset winsock can fix it.
PS C:\WINDOWS\system32> wsl.exe --shutdown
PS C:\WINDOWS\system32> wsl.exe
The attempted operation is not supported for the type of object referenced.
PS C:\WINDOWS\system32> netsh winsock reset

Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.

PS C:\WINDOWS\system32> wsl.exe
root@TIGERHOMEPC /mnt/c/Windows/System32
  # exit

Build 18922.1000.

I encounter this problem and use this method to solve. But my proxifier can't be used.

This help for me

Create one file named wsl2.reg (or any other filename with .reg suffix)
Open this file in notepad.exe, pase text below to it.
Save file.
Double click this file, give it Administrator permission
Open wsl.exe

wsl2.reg code, I copied from this issue
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0408F7A3]
"AppFullPath"="C:\\\\windows\\\\system32\\\\wsl.exe"
"PermittedLspCategories"=dword:80000000

Or you can download my wsl2.reg directly:
https://baijifeilong.github.io/wsl2.reg

创建一个名为wsl2.reg（或任何其他带有 .reg 后缀的文件名）的文件
打开这个文件notepad.exe，将下面的文本粘贴到其中。
保存存档。
双击这个文件，给它Administrator权限
打开wsl.exe

wsl2.reg 代码，我从这个问题复制
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0408F7A3]
"AppFullPath"="C:\\\\windows\\\\system32\\\\wsl.exe"
"PermittedLspCategories"=dword:80000000

或者你可以wsl2.reg直接下载我的：
https://baijifeilong.github.io/wsl2.reg

Create one file named wsl2.reg (or any other filename with .reg suffix)
Open this file in notepad.exe, pase text below to it.
Save file.
Double click this file, give it Administrator permission
Open wsl.exe

wsl2.reg code, I copied from this issue
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0408F7A3]
"AppFullPath"="C:\\\\windows\\\\system32\\\\wsl.exe"
"PermittedLspCategories"=dword:80000000

Or you can download my wsl2.reg directly:
https://baijifeilong.github.io/wsl2.reg

work for me thx!!

2021 年了，这个问题还没解决，不愧是你，微软

22年了（update）

创建一个名为wsl2.reg（或任何其他带有 .reg 后缀的文件名）的文件
在 中打开此文件notepad.exe，将下面的文本粘贴到其中。
保存存档。
双击这个文件，给它Administrator权限
打开wsl.exe

wsl2.reg 代码，我从这个问题复制
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0408F7A3]
"AppFullPath"="C:\\\\windows\\\\system32\\\\wsl.exe"
"PermittedLspCategories"=dword:80000000

或者你可以wsl2.reg直接下载我的：
https://baijifeilong.github.io/wsl2.reg

解决了，感谢

WSL2 wont start if I have Sangfor EasyConnect connected. I have to run netsh winsock reset after vpn start to use wsl.exe.
Adding reg key does not resolve the issue.

Not working anymore. I'm using Win11 version 22H2

又不能用了，不亏是你，微软

又不能用了，不亏是你，微软

这个问题有啥前人的研究思路吗？每天都在winsock reset有点受不了，想抽空看看能不能自己尝试解决一下

no work when update to win11 22H2

又不能用了，不亏是你，微软

这个问题有啥前人的研究思路吗？每天都在winsock reset有点受不了，想抽空看看能不能自己尝试解决一下

this issuse may help: https://github.com/microsoft/WSL/issues/7570

!! proxifier 4.x version will not confilct with wsl2.

Instead of C:\windows\system32\wsl.exe, the new path is under windows apps, which for me is C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe. You may also need to add wslservice.exe.
If you don't want to reboot, use taskkill -IM "wslservice.exe" /F to kill all wsl stuff.

How I managed to solve the problem:
> cd "C:\Program Files\WindowsApps\"

Search for some folder that looks like "MicrosoftCorporationII.WindowsSubsystemForLinux ... x64 ...". For me, it was "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe"

Go in and list its files. It should contain "wsl.exe" and "wslservice.exe".

Download https://web.archive.org/web/20220728095911/http://www.proxifier.com/tmp/Test20200228/NoLsp.exe

Open a windows terminal with admin priviledge.

Kill WSL with
> taskkill -IM "wslservice.exe" /F

Run NoLsp.exe on both "wsl.exe" and "wslservice.exe". For me, it was like
> .\NoLsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe"

> .\NoLsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wslservice.exe"

I have Windows 11 21H2 and added the following to registry and it doesn't work :(
Two entries are created:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\04C4CA21
AppFullPath C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe
and
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0E1558B0
AppFullPath C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wslservice.exe
both with PermittedLspCategories 80000000

How I managed to solve the problem:
> cd "C:\Program Files\WindowsApps\"

Search for some folder that looks like "MicrosoftCorporationII.WindowsSubsystemForLinux ... x64 ...". For me, it was "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe"

Go in and list its files. It should contain "wsl.exe" and "wslservice.exe".

Download https://web.archive.org/web/20220728095911/http://www.proxifier.com/tmp/Test20200228/NoLsp.exe

Open a windows terminal with admin priviledge.

Kill WSL with
> taskkill -IM "wslservice.exe" /F

Run NoLsp.exe on both "wsl.exe" and "wslservice.exe". For me, it was like
> .\NoLsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe"

> .\NoLsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wslservice.exe"

I have Windows 11 21H2 and added the following to registry and it doesn't work :(
Two entries are created:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\04C4CA21
AppFullPath C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe
and
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0E1558B0
AppFullPath C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wslservice.exe
both with PermittedLspCategories 80000000

can confirm that the solution @lingsamuel  posted https://github.com/microsoft/WSL/issues/4177#issuecomment-1336406826
is working

Thank you! This is very important. My previous reg file also didn't work because of the version change

can confirm that the solution @lingsamuel posted #4177 (comment) is working

don't work still

There are some caveats for NoLsp.exe.

Full path must be specified. It doesn't check if wsl.exe exists or not.
Every time Microsoft Store version WSL updates, you'll need to run it manually.

So I created this script to run on boot. I have tested and now it works without issue. (Please remember to kill wslservice.exe if it doesn't work)
#Requires -RunAsAdministrator
# Fix for https://github.com/microsoft/WSL/issues/4177

$MethodDefinition = @'
[DllImport("ws2_32.dll", CharSet = CharSet.Unicode)]
public static extern int WSCSetApplicationCategory([MarshalAs(UnmanagedType.LPWStr)] string Path, uint PathLength, [MarshalAs(UnmanagedType.LPWStr)] string Extra, uint ExtraLength, uint PermittedLspCategories, out uint pPrevPermLspCat, out int lpErrno);
'@

$Ws2Spi = Add-Type -MemberDefinition $MethodDefinition -Name 'Ws2Spi' -PassThru

$WslLocation = Get-AppxPackage MicrosoftCorporationII.WindowsSubsystemForLinux | Select-Object -expand InstallLocation

$Executables = ("wsl.exe", "wslservice.exe");

foreach ($Exe in $Executables) {
    $ExePath = "${WslLocation}\${Exe}";
    $ExePathLength = $ExePath.Length;

    $PrevCat = $null;
    $ErrNo = $null;
    if ($Ws2Spi::WSCSetApplicationCategory($ExePath, $ExePathLength, $null, 0, [uint32]"0x80000000", [ref] $PrevCat, [ref] $ErrNo) -eq 0) {
        Write-Output "Added $ExePath!";
    }
}

@mariotaku Out of curiosity, how do you run this script as an Administrator on boot up?

@mariotaku Out of curiosity, how do you run this script as an Administrator on boot up?

Windows Task Scheduler

@mariotaku Out of curiosity, how do you run this script as an Administrator on boot up?

When I add it to the task scheduler, I configured it to use the highest privilege.

如果应用商店安装了Windows Subsystem for Linux

首先找到安装位置，最简单的方法是，打开应用商店，找到应用Windows Subsystem for Linux，点击应用详细介绍页面的打开按钮，会新打开一个terminal窗口，窗口的标题上面有所安装的wsl.exe的全路径。

或者也可以手动搜索，由于目录C:\Program Files\WindowsApps是保护文件夹，没法直接在资源管理器中搜索，可以管理员打开powershell
cd "C:\Program Files\WindowsApps"
ls

找到对应版本的wsl目录，例如MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe

下载nolsp.exe

管理员打开powershell，执行以下命令：
# 打开nolsp.exe所在目录
cd E:\Downloads\Other\nolsp.exe

# 该步骤就相当于添加注册表
.\nolsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe"
.\nolsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wslservice.exe"
# 注意：这里的wsl.exe以及wslservice.exe，必须是全路径，不能是相对路径。

打开注册表regedit，找到\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog，依次点击此目录的各项，可以找到两项：
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\2BB0D7FB]
"AppFullPath"="C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe"
"PermittedLspCategories"=dword:80000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\2FB92E99]
"AppFullPath"="C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wslservice.exe"
"PermittedLspCategories"=dword:80000000

至此，就可以打开wsl了。
如果商店更新了Windows Subsystem for Linux，需要重新执行一遍此流程

如果应用商店没有安装了Windows Subsystem for Linux
直接在注册表regedit添加项即可：
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0408F7A3]
"AppFullPath"="C:\Windows\System32\wsl.exe"
"PermittedLspCategories"=dword:80000000

临时解决办法：
管理员打开powershell，运行netsh winsock reset，不用重启，就可以打开wsl了。
但是每次重新启动电脑时，都要重新运行一次此流程。

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\

原来是自动的，我之前还费劲去手动添加注册表呢。

Still reproducable in year 2023. The solution is already provided in comments, not sure why its still not fixed.
Windows 11 build 22621.1413

如果应用商店安装了Windows Subsystem for Linux

首先找到安装位置，最简单的方法是，打开应用商店，找到应用Windows Subsystem for Linux，点击应用详细介绍页面的打开按钮，会新打开一个terminal窗口，窗口的标题上面有所安装的wsl.exe的全路径。

或者也可以手动搜索，由于目录C:\Program Files\WindowsApps是保护文件夹，没法直接在资源管理器中搜索，可以管理员打开powershell
cd "C:\Program Files\WindowsApps"
ls

找到对应版本的wsl目录，例如MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe

下载nolsp.exe

管理员打开powershell，执行以下命令：
# 打开nolsp.exe所在目录
cd E:\Downloads\Other\nolsp.exe

# 该步骤就相当于添加注册表
.\nolsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe"
.\nolsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wslservice.exe"
# 注意：这里的wsl.exe以及wslservice.exe，必须是全路径，不能是相对路径。

打开注册表regedit，找到\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog，依次点击此目录的各项，可以找到两项：
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\2BB0D7FB]
"AppFullPath"="C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe"
"PermittedLspCategories"=dword:80000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\2FB92E99]
"AppFullPath"="C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wslservice.exe"
"PermittedLspCategories"=dword:80000000

至此，就可以打开wsl了。 如果商店更新了Windows Subsystem for Linux，需要重新执行一遍此流程
如果应用商店没有安装了Windows Subsystem for Linux
直接在注册表regedit添加项即可：
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\AppId_Catalog\0408F7A3]
"AppFullPath"="C:\Windows\System32\wsl.exe"
"PermittedLspCategories"=dword:80000000

临时解决办法：
管理员打开powershell，运行netsh winsock reset，不用重启，就可以打开wsl了。 但是每次重新启动电脑时，都要重新运行一次此流程。

This workaround must be applied every time after the wsl app (app store version) updated, since the versioned path keeps changing. But it's hard to tell when or even whether the app was updated. So ... still quite a mess.

@pnck
Attempted to change the WSL startup command from C:\WINDOWS\system32\wsl.exe -d Ubuntu-20.04 to just bash.
Yes, that's right, just one word: bash. It worked for me.
Alternatively, you could try downloading and installing a different Linux distribution from the Microsoft Store, such as Ubuntu 22.04 LTS. I have tried this myself and it also works.

heroes who are digging to this issue, let me summarize the problem for you:

if you're having issue launching docker, or wsl, AND you're using proxy app the same time, you may encounter this problem, the wsl won't launch.
this is probably your proxy app is using lsp to take control of wsl network automatically for convenience(my guess), which is deprecated already since windows 8, but wsl does not support this, and it will not fix it, so we're having this issue for years.
one recommend work-around is to use @mariotaku 's script to add wsl entry to your registry.
run the exe as admin is not recommended, an anonymous exe should not be trusted for security concern.

but if you're curious about how the appid catagory hash is decided (as i do), here's a demo to show how the catagory is calculated，so you can write code to do the job for yourself, completely independent to ws2_32.dll, here's some note for the demo:

the path is using wide char.
the drive letter is ignored.
path capitalized during hash calculation
L'\0' should not be calculated, if you're using c string.

case close, studied this for a week.

My computer updated to WSL <IP_ADDRESS> today and this broke again. I had previously set up the Powershell script mentioned in https://github.com/microsoft/WSL/issues/4177#issuecomment-1359200646 but that wasn't fixing it this time. I had to use NoLsp.exe again and run the following commands to get it working again:
taskkill -IM "wslservice.exe" /F
NoLsp.exe "C:\Program Files\WSL\wsl.exe"
NoLsp.exe "C:\Program Files\WSL\wslservice.exe"
NoLsp.exe "C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_<IP_ADDRESS>_x64__8wekyb3d8bbwe\wsl.exe"

@RichardDavies Thank you, worked for me.
I have used @mariotaku script successfully until now, but i also needed to execute NoLsp.exe.
Here is aadjusted script, that first executes the NoLsp.exe and afterwards the registry fix:
#Requires -RunAsAdministrator
# Fix for https://github.com/microsoft/WSL/issues/4177

$MethodDefinition = @'
[DllImport("ws2_32.dll", CharSet = CharSet.Unicode)]
public static extern int WSCSetApplicationCategory([MarshalAs(UnmanagedType.LPWStr)] string Path, uint PathLength, [MarshalAs(UnmanagedType.LPWStr)] string Extra, uint ExtraLength, uint PermittedLspCategories, out uint pPrevPermLspCat, out int lpErrno);
'@

$Ws2Spi = Add-Type -MemberDefinition $MethodDefinition -Name 'Ws2Spi' -PassThru

$WslLocation = Get-AppxPackage MicrosoftCorporationII.WindowsSubsystemForLinux | Select-Object -expand InstallLocation

# Specify paths to all wsl locations

#since WSL Version 2.X.Y.Z also neccessary to execute fix in the "Program Files" locations https://github.com/microsoft/WSL/issues/4177#issuecomment-1817216126
$WslLocations = @(
    (Get-AppxPackage MicrosoftCorporationII.WindowsSubsystemForLinux | ForEach-Object { $_.InstallLocation }),
    "C:\Program Files\WSL"
)

$Executables = ("wsl.exe", "wslservice.exe", "wslg.exe", "wslhost.exe");

foreach ($WslLocation in $WslLocations) {

	Write-Output "Looping trough path:  $WslLocation";
	Write-Output "==========================================";

    foreach ($Exe in $Executables) {
        $ExePath = Join-Path $WslLocation $Exe

		# Test if exe exists in the path (not all exe's are in all locations)
		if (-not (Test-Path $ExePath -PathType Leaf)) {
			Write-Output "Path not found:  $ExePath!";
			continue;
		}

	# First execute NoLsp.exe fix
        & ".\NoLsp.exe" $ExePath

		# Second execute registry fix
		$ExePathLength = $ExePath.Length;
        $PrevCat = $null;
        $ErrNo = $null;

        if ($Ws2Spi::WSCSetApplicationCategory($ExePath, $ExePathLength, $null, 0, [uint32]"0x80000000", [ref] $PrevCat, [ref] $ErrNo) -eq 0) {
            Write-Output "Added $ExePath!";
        }
    }
	Write-Output "";
}

I'm running this script as suggested above with highest priviliges via the Task Scheduler on every startup.
The NoLsp.exe needs to be in the same folder as this script.

@RichardDavies Thank you, worked for me. I have used @mariotaku script successfully until now, but i also needed to execute NoLsp.exe.
Here is a adjusted script, that first executes the NoLsp.exe and afterwards the registry fix:
#Requires -RunAsAdministrator
# Fix for https://github.com/microsoft/WSL/issues/4177

$MethodDefinition = @'
[DllImport("ws2_32.dll", CharSet = CharSet.Unicode)]
public static extern int WSCSetApplicationCategory([MarshalAs(UnmanagedType.LPWStr)] string Path, uint PathLength, [MarshalAs(UnmanagedType.LPWStr)] string Extra, uint ExtraLength, uint PermittedLspCategories, out uint pPrevPermLspCat, out int lpErrno);
'@

$Ws2Spi = Add-Type -MemberDefinition $MethodDefinition -Name 'Ws2Spi' -PassThru

$WslLocation = Get-AppxPackage MicrosoftCorporationII.WindowsSubsystemForLinux | Select-Object -expand InstallLocation

# Specify paths to all wsl locations

#since WSL Version 2.X.Y.Z also neccessary to execute fix in the "Program Files" locations https://github.com/microsoft/WSL/issues/4177#issuecomment-1817216126
$WslLocations = @(
    (Get-AppxPackage MicrosoftCorporationII.WindowsSubsystemForLinux | ForEach-Object { $_.InstallLocation }),
    "C:\Program Files\WSL"
)

$Executables = ("wsl.exe", "wslservice.exe", "wslg.exe", "wslhost.exe");

foreach ($WslLocation in $WslLocations) {

    Write-Output "Looping trough path:  $WslLocation";
    Write-Output "==========================================";

    foreach ($Exe in $Executables) {
        $ExePath = Join-Path $WslLocation $Exe

	# Test if exe exists in the path (not all exe's are in all locations)
	if (-not (Test-Path $ExePath -PathType Leaf)) {
		Write-Output "Path not found:  $ExePath!";
		continue;
	}

	# First execute NoLsp.exe fix
        & ".\NoLsp.exe" $ExePath

	# Second execute registry fix
	$ExePathLength = $ExePath.Length;
        $PrevCat = $null;
        $ErrNo = $null;

        if ($Ws2Spi::WSCSetApplicationCategory($ExePath, $ExePathLength, $null, 0, [uint32]"0x80000000", [ref] $PrevCat, [ref] $ErrNo) -eq 0) {
            Write-Output "Added $ExePath!";
        }
    }
    Write-Output "";
}

I'm running this script as suggested above with highest priviliges via the Task Scheduler on every startup. The NoLsp.exe needs to be in the same folder as this script.
Tested with WSL 2 v<IP_ADDRESS> and ProxyCap 5.38

I spent days struggling with it and now it's working again. Thanks!

@craigloewen-msft @OneBlue
Hey guys
I saw the AMA and your help to fix the issue https://github.com/microsoft/WSL/issues/10812.
So i hope you might also help us here out :D.
The summary of this issue (iirc):
It seems that some proxy tools (like proxifier or proxycap) interfere with the socket communication between the wsl instance and the host.
The solution for this was at the begining to "deactivate"/"unload" a DLL called "Lsp" from the wsl.exe.
For that, proxifier has build a small tool called NoLsp.exe, which did this "unloading" of the lsp dll.
Then the changed happened, that wsl gets automatically updated from the windows store.
After this, I had to execute the NoLsp.exe fix after every update (because every update had a new wsl.exe in an other path)
AND additionaly also had to do some registry fix.
To somehow automate this fixes, i've used successfully @mariotaku script (https://github.com/microsoft/WSL/issues/4177#issuecomment-1359200646) and adjusted it, so that also the NoLsp.exe fix was executed.
This worked for me since January 2023 until now til WSL v1.2.5.
Since the last WSL Update (2.0.X.Y) i also had to execute the fix at the wsl.exe, that's in "Program Files" Folder, in addition to the Microsoft Store Location. (The script automaticaly find's the path to the wsl.exe's that are updated by the Microsoft Store).
Here is the complete script : https://github.com/microsoft/WSL/issues/4177#issuecomment-1822438206
Now everything is working again fine.
I can't find any more the official link to the NoLsp.exe, but here is the one from the wayback machine: https://web.archive.org/web/20220728095911/http://www.proxifier.com/tmp/Test20200228/NoLsp.exe
I think the NoLsp.exe does only a registry entry, to unload the dll and therefore this fix could also be done without the .exe
(Maybe somone can post the manual registry fix).
My complete setup is :

ProxyCap 5.38
Citrix Secure Acces <IP_ADDRESS> (for VPN)
WSL vpn-kit (without it, i don't have internet acces inside the wsl instance)

tldr:
Would it be possible to remove this Lsp DLL from WSL AND also implement the second registry fix in an upcoming WSL Update ?
I don't know for what this DLL is, but everything is working fine without it.
Or make it an wsl config, so that we need to opt in for this fix.
Thanks in advance for your help !

Fixed with https://github.com/microsoft/WSL/releases/tag/2.1.0

I'm also using a VPN (Citrix Secure Access).
And now with the automatic enablement auf DNS tunneling in 2.1.0, i now don0t have internet/intranet access inside the wsl.
The fix for me is now to disable that via the .wslconfig file, e.g.
[wsl2]
dnsTunneling=false

And internet/intranet access works again.


Obfuscator misses nested variables

e.g.
Dim cFruits as New Collection
cFruits.Add "Apple"
cFruits.Add "Cherry"
Debug.Print cFruits(cFruits.Count)

=> cFruits.Count doesn't get obfuscated, so the code breaks!
Possible Fix in the Obfuscation Module:
There is this line with sPattern... I added a loop to get it work:
sPattern = "([\*\.\^\*\+\#\(\)\-\=\/\,\:\;\s])" & sFinde & "([\*\.\^\*\+\!\@\#\$\%\&\(\)\-\=\/\,\:\;\s]|$)"
Do 'Recognize nestings like "cRels(cRels.Count)"
	sCodeTemp = RegExpFindReplace(sCode, sPattern, "$1" & sReplace & "$2", True, False, False)
	If sCodeTemp = sCode Then Exit Do
	sCode = sCodeTemp
Loop

Obsolete, with the more performant change of #8


dxvk_2: 2.4 -> 2.5

https://github.com/doitsujin/dxvk/releases/tag/v2.5
https://github.com/NixOS/nixpkgs/issues/355254

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@LovingMelody Pinging you to test since you opened the issue for the update.

Tested by a quick play though of Star Citizen. Appears to be working correctly.


SCRAM-SHA-1 auth mechanism is only supported in single mongod instance, not yet in replication set instances.

When I test SCRAM-SHA-1 auth mechanism in single mongod instance, it seems everything goes well. But when I setup a replica set cluster and connect one member in the cluster, it report  "not authorized on xxx collection to execute command xxx" when I issue a COUNT command.

I'll check it.

I'm experiencing the same issue:
** exception error: {bad_query,{'$err',<<"not authorized for query on ppns2.apps">>,
code,13}}
in function  mc_connection_man:process_error/2 (src/connection/mc_connection_man.erl, line 57)
in call from mc_action_man:read_one/2 (src/core/mc_action_man.erl, line 22)

Could you please try mongodb java driver with your configuration?

I'm using it with a Ruby driver 2.0.5 and it works fine:
DEBUG -- : MONGODB | COMMAND | namespace=ppns2.$cmd selector={:saslStart=>1, :autoAuthorize=>1, :payload=><BSON::Binary:0x70222595582220 type=generic data=n,,n=wri...>, :mechanism=>"SCRAM-SHA-1"} flags=[] limit=-1 skip=0 project=nil

It seems that I hit all the walls. I try to insert some data to collection to the replica set of mongod 3 and I get

mongo:insert(Conn3, <<"aux">>, bson:document( Data )).
** exception error: {bad_query,{write_failure,13,
<<"not authorized for insert on mi-aux.aux">>}}
in function  mc_connection_man:process_error/2 (src/connection/mc_connection_man.erl, line 56)
in call from mongo:insert/3 (src/api/mongo.erl, line 86)
in call from mongo:insert/3 (src/api/mongo.erl, line 83)

For now I advice you to use 2.6 auth in 3 mongo set. I have lack of time, so I can't fix it immediately.

fixed in https://github.com/comtihon/mongodb-erlang/pull/82


Document MatchOnMetadata

closes #6846

@cdmihai : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@cdmihai : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Suggestion - A Friendly Introduction to the Fediverse

Section: Documentation
Title: A Friendly Introduction to the Fediverse
https://drwho.virtadpt.net/archive/2019-01-04/a-friendly-introduction-to-the-fediverse

I simplified the list's intro to only keep the official doc which contains a clear explanation, but thank you!


fix: fixed button UX issue

Description
This PR fixes the UX issue with color change on hover and adds supporting text on hover for the Run, Variables, and Settings buttons. Additionally, it changes the run icon from a stick figure to Iconplayerplay.
Fixes #1895
##How should this be tested
-[ ] Open CollectionToolBar
-[ ] Check the color change on hover , supporting text on hover, and change of run icon
Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x]  The pull request does not introduce any breaking changes
[ ] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[x]  Create an issue and link to the pull request. ( issue was already created ).

Hey @vaib1610 ! Thank you for the time and effort you've dedicated to this PR.
This tooltips has been delivered as a part of https://github.com/usebruno/bruno/pull/2812


Make spawn pass worker options again

When https://github.com/ManageIQ/manageiq/pull/16130 was merged, it revealed that spawn was not properly passing worker_options, specifically, the ems id needed by provider workers.
That PR was reverted and now we need to get spawn working properly again.
This PR adds the --ems-id option to run_single_worker.rb, updates the Procfile example to leverage this instead of the QUEUE environment variable, removes support for that env variable and the now unused MIQ_GUID environment variable.
There's still some bugs to fix with spawn + BUNDLER_GROUPS excluding ui-classic for all non-ui workers but those can be done as follows up while fork is still the default (report_formatter in ui repo being used by our reporting code, ick).
We also want to support passing multiple ems id values for amazon workers cc @juliancheal @agrare but that will be done also as a followup to this PR.
To test this PR as is, you'll need to enable spawn workers locally:  MIQ_SPAWN_WORKERS=true bin/rake evm:start or use the Procfile via bin/rake evm:foreman:start and make sure your provider workers get the proper ems_id passed down.

@agrare according to a link @juliancheal sent me here, we shouldn't need to pass multiple ems_ids to the runner initialize.  It sounds like as long as you have an amazon ems with many managers, it should automatically, pickup the managers in the refresh worker.

@agrare Or, more importantly, if we need to have multiple ems_id's passed to the runner initialize, what is the proper queue name for that worker?

@jrafanie hm well amazon workers weren't starting up so there is something else up.
@juliancheal can you help debug this?

Not at work today. But can look tonight.
Sent from my iPhone

On 17 Oct 2017, at 15:01, Adam Grare<EMAIL_ADDRESS>wrote:
@jrafanie hm well amazon workers weren't starting up so there is something else up.
@juliancheal can you help debug this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I need to see what's going on, as so far with Amazon we get as far as this
 321 | ManageIQ::Providers::Amazon::CloudManager::RefreshWorker  | 12426 | ["ems_12", "ems_13", "ems_14"] | creating |

@juliancheal I added a commit to address @carbonin's concern about YAOH (yet another options hash)

Fixed the Amazon provider issue over here https://github.com/ManageIQ/manageiq/pull/16297


HttpCommandExecutor stuck

My acceptance test sometimes stuck for unlimited time > 30mins event the default timeout settings just 30secs.

HipHop VM 3.14.5 (rel)
Compiler: tags/HHVM-3.14.5-0-gc6bf714e6468213eed377527b431e9cd4cec1432
Repo schema: 9ab3fe4281c731189b558d921eb7317b0eb2b2e6
selenium-server-standalone-2.53.1.jar
ChromeDriver 2.23.409687 (c46e862757edc04c06b1bd88724d15a5807b84d1)
Google Chrome 53.0.2785.116
Codeception 2.2.3
All inside Vagrant Box with Ubuntu 14.04, with Xvfb

It is trapped on curl_exec at https://github.com/facebook/php-webdriver/blob/community/lib/Remote/HttpCommandExecutor.php#L309
I checked the selenium still running. If I abort with Ctrl+C and re run the tests then the stuck removed by itself without touching(restarting) the selenium.
Does anyone have some problem? Thanks

@firodj Do you know what is the command that is stucked?

DriverCommand::NEW_SESSION when called from RemoteWebDriver::create.
I am using Codeception. Let say I am running tests in a row like these:
./codecept.phar run tests/acceptance/folder1
./codecept.phar run tests/acceptance/folder2
./codecept.phar run tests/acceptance/folder3

The stuck at sometimes happens when testing folder3, never at folder1.
Maybe has correlation when selenium just have closing the google chrome browser.

I guess this could be some problem with ChromeDriver. I've read similar reports of ChromeDriver being stucke, which were solved by using latest version of ChromeDriver... Thats my only idea, sorry.

Sorry, there is no way I can help... If you find any way how to reproduce the issue, please feel free to open new issue.


AssertionError: decrunch .dist-info directory not found

Hi!
$ pip3 install decrunch || pip3 --version && python --version
Collecting decrunch
Installing collected packages: decrunch
Exception:
Traceback (most recent call last):
  File "c:\users\nicofisi\appdata\local\programs\python\python36\lib\site-packages\pip\basecommand.py", line 215, in main
    status = self.run(options, args)
  File "c:\users\nicofisi\appdata\local\programs\python\python36\lib\site-packages\pip\commands\install.py", line 342, in run
    prefix=options.prefix_path,
  File "c:\users\nicofisi\appdata\local\programs\python\python36\lib\site-packages\pip\req\req_set.py", line 784, in install
    **kwargs
  File "c:\users\nicofisi\appdata\local\programs\python\python36\lib\site-packages\pip\req\req_install.py", line 851, in install
    self.move_wheel_files(self.source_dir, root=root, prefix=prefix)
  File "c:\users\nicofisi\appdata\local\programs\python\python36\lib\site-packages\pip\req\req_install.py", line 1064, in move_wheel_files
    isolated=self.isolated,
  File "c:\users\nicofisi\appdata\local\programs\python\python36\lib\site-packages\pip\wheel.py", line 347, in move_wheel_files
    assert info_dir, "%s .dist-info directory not found" % req
AssertionError: decrunch .dist-info directory not found
pip 9.0.1 from c:\users\nicofisi\appdata\local\programs\python\python36\lib\site-packages (python 3.6)
Python 3.6.3

Windows 10 pro btw
What can I do? :heart: Need it for your other tools

This is on WSL?
Completely untested on Windows so, uh, I think you'll have to debug this one yourself most likely. Maybe @Mischanix can help.

I fixed it after an hour, IIRC I deleted the whole c:\users\nicofisi\appdata\local\programs\python\python36\lib\site-packages, installed pip again, and then either I downloaded and installed it from here or a simple pip3 install unitypack worked.
I don't really use Python for anything else so it's not a problem for me that I lost previously downloaded packages ;)
Thanks for the great tools and Marry Christmas anyways!

Cool!


Semantics of exact size vs lower bounded size?

Another small example where I'm unsure if this is intended behavior or a minor bug. It is about the usage of an exact size like .width(Px::new(100)) vs a lower bounded size like .width(Px::new(100)..). Consider the following example:
use cushy::animation::ZeroToOne;
use cushy::figures::units::Px;
use cushy::figures::Zero;
use cushy::value::Dynamic;
use cushy::widget::MakeWidget;
use cushy::widgets::progress::Progressable;
use cushy::Run;

fn content() -> impl MakeWidget {
    let progress = Dynamic::new(ZeroToOne::ZERO);
    progress
        .clone()
        .progress_bar()
        .width(Px::new(100)..) // using just `Px::new(100)` works
        .contain()
        .centered()
        .expand()
}

pub fn main() -> cushy::Result<()> {
    content().run()
}

Using an exact size, the widget renders as:

Using a lower bounded size, the widget renders as:

For some reason, the progress bar got shrunken down to less then the 100 pixels in this case. Intuitively I would have expected that the range syntax would express 100 pixel or more, so I'm a bit surprised that it can shrink now. Interestingly, it still has a width of 100 to the outside (barely visible by the container size) -- only the inner widget seems to have lost its minimum width constraint?

Thank you for reporting this! This looks like it only affected the Slider widget, which is what the progress bar uses under the hood.


Monthly ESMValTool meeting - August 2020

The next monthly ESMValTool meeting will be in August. The result of the poll is that it will be on
Monday August 3 at 14:00 CEST (13:00 BST).
The duration will be one hour. Join the zoom meeting here.
@ESMValGroup/esmvaltool-developmentteam
Format and agenda

We start the meeting by doing a round where everyone gets one minute to introduce themselves and tell what they will be working on in the next month or what they would like help with.
Using the input from the introduction round, we can decide to talk about specific topics with the entire group or make smaller breakout groups to continue the discussion there.
If you already know that you would like to bring up a particular topic in the meeting, you can link the GitHub issue to this issue so it's easy to find for other people in the meeting and we can already start discussing there before the meeting. Just create a new GitHub issue if there is no open issue yet.
GitHub issues are our preferred way to communicate outside the meeting and keep track of work, so any feature requests/action items/etc discussed in the meeting should ideally result in a GitHub issue.

Notes from the previous meeting can be found here: https://github.com/ESMValGroup/ESMValTool/issues/1670#issuecomment-656133884

@ESMValGroup/esmvaltool-developmentteam The meeting will take place on Monday August 3 at 14:00 CEST (13:00 BST).

Thanks for attending everyone!
Here is a summary with some news:

@katjaweigel Submitted the new paper on diagnostics for extreme events, regional and impact evaluation
@SarahAlidoost Reported that there has been a lot of progress on the new tutorial (source repository) in tutorial sprints that many members of the @ESMValGroup/esmvaltool-developmentteam joined and that it is now ready to be used
@sloosvel Mentioned that many new users are now up and running with ESMValTool at BSC and they plan to use the tutorial mentioned above when they give another course this autumn
@nielsdrost Announced that we now have a machine at DKRZ for running automatic tests of recipes and diagnostics and hope to set it up for usage in the next month #316
@valeriupredoi mentioned he was making good progress on testing multiple OSs and Python versions with GitHub Actions  https://github.com/ESMValGroup/ESMValCore/issues/731
@mattiarighi said that all recipes were tested successfully #1697 (apart from two which were fixed in the meeting #1742)
@bouweandela Mentioned that we will release v2.0.0 later today
@bascrezee said it would be nice if releases would be announced to the wider community and that he hoped the new testing infrastructure would also be able to catch issues like ESMValGroup/ESMValCore#710 before users run into them
@bouweandela said that we will discuss the release strategy and schedule with the core development team and hope to publish the result on the website


Support for right-to-left (RTL) texts

Validations

[X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that requests the same enhancement

Problem
Please add a possibility to chat texts and their replies if they are, for example, Persian(Farsi) or Arabic. Display them right to left (RTL).
Solution
Maybe like this:
.thread-message {
    direction: rtl !important;
    text-align: right !important;
}

Can I work on this ?


Is CUDAGraph generation available during PPO training time？

Thanks for the great work! I saw that you support CUDA graph generation for fast inference. Is this effective during the PPO training time? Because PPO generation is really costly. or is there any fast generation method used in RealHF for training?

Yes. We didn't perform an ablation, but it can lead to about 4x accelearation in our use cases (2048 prompt + 2048 gen).
We get results in our paper without CUDA graph. We will update the paper recently.

Yes. We didn't perform an ablation, but it can lead to about 4x accelearation in our use cases (2048 prompt + 2048 gen).
We get results in our paper without CUDA graph. We will update the paper recently.

That's great! Is this CUDA graph auto applied now or I need to enable it use certain args?

Try setting ppo.gen.use_cuda_graph=True as in this example. And you may want to set ppo.gen.force_no_logits_mask=True as well.
Please see the doc for detailed explanations.

And you should use a proper docker image version according to your hardware. We've tested 24.03 for A100 and 24.07 for H100. Other combinations are not ensured to work well thanks to Nvidia.

Thanks for all the helpful information!


Consider using Memory/GC benchmarking

Consider following to apply some memory/GC benchmarking:

Benchmark Dot Net - investigate this blog post if this library can be used for this purpose
DotMemory Unit - after initial tests it's quite hard to filter out a set of objects as the query is passed to a proxy project, so one cannot adjust test to measure only allocations connected with a test. Additionally, it looks that the measurements performs some allocations on its own, lowering the possibility of getting a measured region without allocations at all.

Closed by #21

It's cool to see that you are using BenchmarkDotNet, I've added you to our list!


Incompatible shapes

Hi,I try to using this repository to train our 1-label custom dataset,and then I encounter some porblem to convert the xml to tfrecord. So,I decided to use the Vott to label my image dataset and export to tfrecord .(dataset is 320240 jpg files , I tried to resize to square 320320 ,but it fails too.)
When I run the train.py with below command:
python train.py --dataset ./DATA/annotations-TFRecords-export/*.tfrecord --val_dataset ./DATA/val/*.tfrecord --mode eager_tf
I also change the flag in train.py to reach our need :
flags.DEFINE_string('dataset', '', 'path to dataset')
flags.DEFINE_string('val_dataset', '', 'path to validation dataset')
flags.DEFINE_boolean('tiny', False, 'yolov3 or yolov3-tiny')
flags.DEFINE_string('weights', './checkpoints/yolov3.tf','path to weights file')
flags.DEFINE_string('classes', './data/mk100.names', 'path to classes file')
flags.DEFINE_enum('mode', 'fit', ['fit', 'eager_fit', 'eager_tf'],                   'fit: model.fit, '                   'eager_fit: model.fit(run_eagerly=True), '                   'eager_tf: custom GradientTape')
flags.DEFINE_enum('transfer', 'none',                   ['none', 'darknet', 'no_output', 'frozen', 'fine_tune'],                   'none: Training from scratch, '                   'darknet: Transfer darknet, '                   'no_output: Transfer all but output, '                   'frozen: Transfer and freeze all, '                   'fine_tune: Transfer all and freeze darknet only')
flags.DEFINE_integer('size', 320, 'image size')
flags.DEFINE_integer('epochs', 2, 'number of epochs')
flags.DEFINE_integer('batch_size', 2, 'batch size')
flags.DEFINE_float('learning_rate', 1e-3, 'learning rate')
flags.DEFINE_integer('num_classes', 1, 'number of classes in the model')
Finally , I got these error message:
root@b01c606d1cf2:/workspace/yolov3-tf2# python train.py --dataset ./DATA/annotations-TFRecords-export/*.tfrecord --val_dataset ./DATA/val/*.tfrecord --mode eager_tf 2019-11-21 10:07:18.116670: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA 2019-11-21 10:07:18.138229: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz 2019-11-21 10:07:18.138665: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x5733040 executing computations on platform Host. Devices: 2019-11-21 10:07:18.138706: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): Host, Default Version 2019-11-21 10:07:18.142559: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcuda.so.1 2019-11-21 10:07:18.219906: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.220363: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x57f9c50 executing computations on platform CUDA. Devices: 2019-11-21 10:07:18.220392: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): GeForce RTX 2060, Compute Capability 7.5 2019-11-21 10:07:18.220642: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.221165: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1618] Found device 0 with properties: name: GeForce RTX 2060 major: 7 minor: 5 memoryClockRate(GHz): 1.71 pciBusID: 0000:01:00.0 2019-11-21 10:07:18.221446: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0 2019-11-21 10:07:18.222726: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0 2019-11-21 10:07:18.223907: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10.0 2019-11-21 10:07:18.224237: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10.0 2019-11-21 10:07:18.225756: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10.0 2019-11-21 10:07:18.226967: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10.0 2019-11-21 10:07:18.230745: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7 2019-11-21 10:07:18.230986: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.231531: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.231867: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1746] Adding visible gpu devices: 0 2019-11-21 10:07:18.231918: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0 2019-11-21 10:07:18.232620: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1159] Device interconnect StreamExecutor with strength 1 edge matrix: 2019-11-21 10:07:18.232637: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1165]      0 2019-11-21 10:07:18.232644: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1178] 0:   N 2019-11-21 10:07:18.232756: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.233152: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.233514: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1304] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 3089 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2060, pci bus id: 0000:01:00.0, compute capability: 7.5) 2019-11-21 10:07:18.253259: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.253679: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1618] Found device 0 with properties: name: GeForce RTX 2060 major: 7 minor: 5 memoryClockRate(GHz): 1.71 pciBusID: 0000:01:00.0 2019-11-21 10:07:18.253732: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0 2019-11-21 10:07:18.253748: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0 2019-11-21 10:07:18.253762: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10.0 2019-11-21 10:07:18.253775: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10.0 2019-11-21 10:07:18.253788: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10.0 2019-11-21 10:07:18.253797: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10.0 2019-11-21 10:07:18.253807: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7 2019-11-21 10:07:18.253886: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.254297: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.254633: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1746] Adding visible gpu devices: 0 2019-11-21 10:07:18.255208: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.255584: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1618] Found device 0 with properties: name: GeForce RTX 2060 major: 7 minor: 5 memoryClockRate(GHz): 1.71 pciBusID: 0000:01:00.0 2019-11-21 10:07:18.255630: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0 2019-11-21 10:07:18.255647: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0 2019-11-21 10:07:18.255661: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10.0 2019-11-21 10:07:18.255672: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10.0 2019-11-21 10:07:18.255683: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10.0 2019-11-21 10:07:18.255696: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10.0 2019-11-21 10:07:18.255708: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7 2019-11-21 10:07:18.255773: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.256161: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.256497: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1746] Adding visible gpu devices: 0 2019-11-21 10:07:18.256524: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1159] Device interconnect StreamExecutor with strength 1 edge matrix: 2019-11-21 10:07:18.256532: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1165]      0 2019-11-21 10:07:18.256540: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1178] 0:   N 2019-11-21 10:07:18.256633: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.257023: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero 2019-11-21 10:07:18.257374: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1304] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 3089 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2060, pci bus id: 0000:01:00.0, compute capability: 7.5) 2019-11-21 10:07:26.820447: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7 2019-11-21 10:07:28.100940: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0 2019-11-21 10:07:28.318568: I tensorflow/stream_executor/cuda/cuda_driver.cc:830] failed to allocate 2.00G<PHONE_NUMBER> bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory 2019-11-21 10:07:28.735538: W tensorflow/core/common_runtime/bfc_allocator.cc:239] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.15GiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2019-11-21 10:07:28.735590: W tensorflow/core/common_runtime/bfc_allocator.cc:239] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.15GiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2019-11-21 10:07:28.765140: W tensorflow/core/common_runtime/bfc_allocator.cc:239] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.15GiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. 2019-11-21 10:07:28.765191: W tensorflow/core/common_runtime/bfc_allocator.cc:239] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.15GiB with freed_by_count=0. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available. Traceback (most recent call last):   File "train.py", line 193, in <module>     app.run(main)   File "/usr/local/lib/python3.6/dist-packages/absl/app.py", line 299, in run     _run_main(main, args)   File "/usr/local/lib/python3.6/dist-packages/absl/app.py", line 250, in _run_main     sys.exit(main(argv))   File "train.py", line 139, in main     pred_loss.append(loss_fn(label, output))   File "/workspace/yolov3-tf2/yolov3_tf2/models.py", line 309, in yolo_loss     tf.reduce_sum(tf.square(true_xy - pred_xy), axis=-1)   File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/ops/math_ops.py", line 899, in binary_op_wrapper     return func(x, y, name=name)   File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/ops/gen_math_ops.py", line 11085, in sub     _six.raise_from(_core._status_to_exception(e.code, message), None)   File "<string>", line 3, in raise_from tensorflow.python.framework.errors_impl.InvalidArgumentError: Incompatible shapes: [1,13,13,3,2] vs. [1,10,10,3,2] [Op:Sub] name: sub/
So,I trace the code in model.py,and I find pred_xy is in shape [1,13,13,3,2] and true_xy is in shape with  [1,10,10,3,2]
,but I don't know what the problem is .

You may try to resize your image data  to 416*416

@lazerliu  It's works . thanks you

Sorry this is a bit late but I just fixed training for custom size, either 320, 640 or 416 should work now


HDDGURU.HDDRawCopyTool version 1.10

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

I'm not sure if I'm doing something wrong but I cant get winget to use any local manifests, if I try to validate it complains that the multi-file manifest is incomplete, and if I try to install it says that the manifest could not be opened

I'm not sure if I'm doing something wrong but I cant get winget to use any local manifests, if I try to validate it complains that the multi-file manifest is incomplete, and if I try to install it says that the manifest could not be opened

Are you sure you did winget install --manifest "manifests/h/HDDGURU/HDDRawCopyTool/1.10"?

I'm not sure if I'm doing something wrong but I cant get winget to use any local manifests, if I try to validate it complains that the multi-file manifest is incomplete, and if I try to install it says that the manifest could not be opened

Are you sure you did winget install --manifest "manifests/h/HDDGURU/HDDRawCopyTool/1.10"?

I just did now and it worked fine, my issue was I was pointing it to a specific file, was unaware it was supposed to be the entire folder, thank you


feat(@angular/cli): support subresource integrity validation

Closes #5839

Sorry, need to cherrypick / PR master into 1.1.x :( BRB

CLA bot acted out when changing the base as there was multiple PRs missing in 1.1.x. @clydin already signed the CLA, so it's all good.

This is a great feature! Happy to see it being added.
Clarification question (hope it's the right place to ask) - will this allow to add integrity validation to external scripts as well? (e.g. loading an external library via CDN, which requires to add the crossorigin and integrity tags to the script / link tags)? webpack has the "external" attribute but I understand this is not currently supported in angular cli (And that there are no plans to support exposing the internal webpack config).

@hansl basic test added and description updated.
@eranation If the feature request supporting the use of CDN vendor assets is implemented, I would envision subresource integrity would be fully supported.

Please rebase on top of master.

@hansl can you re-review?

Does any further work need to be done to accept this PR?

I guess this is missing in Wiki documentation. How can I add it?

Probably it was answered elsewhere, but still, for those who will get here to find out how to use that option, here is a hint:
ng build --subresource-integrity=true


Concurrency settings should be 'persistent' in interface

If you edit an existing LES, the concurrency settings are always set as the default (although that might not reflect the actual allocation of the profiles).

Will deploy tomorrow.


How can I get my country time?

I need to get my country time, so how can I change String lookUpAddress: 'pool.ntp.org', so gets my country time? Thanks

Hi,
You can use this method to get current ntp time, this will return your local time with ntp offset, so this time will be same on every device (maybe ~50ms difference):
    final DateTime ntpTime = await NTP.now();

and you can change lookup address by passing a new address like this:
int _offset = await NTP.getNtpOffset(lookUpAddress: 'some.new.address');

But pool.ntp.org is most widely used and it is available everywhere


Contributor names and type in the filter dropdowns are being translated

Overview
Contributor names and types in the filter dropdowns are being translated. The translate library tries to translate all text on a page unless it encounters a a notranslate class.
Expected Behavior
Contributor names and types are not translated in the map page filter dropdown.
Actual Behavior
Contributor names and types are translated in the map page filter dropdown.
Steps to Reproduce

Browse the map page
Choose a non-English language
Open the contributor filter dropdown
Open the contributor type dropdown

Demo

Additional context
It looks like setting the notranslate class on parent element applies to all child elements, so this should be a relatively simple fix.

Shares points with https://github.com/open-apparel-registry/open-apparel-registry/issues/569


Add Age to the Asset List

Summary

Add time since last transaction to the asset list, like in the admin asset list.

For Admin Use

[x] Not duplicate issue
[x] Appropriate labels applied
[x] Appropriate contributors tagged
[x] Contributor assigned/self-assigned

fast follow of #60


:seedling: Detect more information about runtime

This introduces a system and a kairos block available in kairos-agent get state.
This allows for instance to query the agent for the kairos version as such:
kairos-agent get state kairos.version
Part of #755

Codecov Report

Merging #956 (cc1cb26) into master (da68d7b) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master     #956   +/-   ##
=======================================
  Coverage   22.79%   22.79%
=======================================
  Files          22       22
  Lines        1610     1610
=======================================
  Hits          367      367
  Misses       1179     1179
  Partials       64       64

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add Peer Service to Cilium DS Port List

For the sake of documenting the Peer Service port.
Signed-off-by: Nate Sweet<EMAIL_ADDRESS>

Yikes, to the silly mistakes I made! Thanks for the reviews!

/test


Unable to override error S00011:15404

Which version and edition of Flyway are you using?
5.2.4 Pro
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using (type & version)?
MSSQL 2017 Linux Docker Container:latest
Which operating system are you using?
Linux Alpine:5.2.4-alpine
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
flyway migrate with a migration containing EXECUTE AS USER = '[SOME DOMAIN USER]' with the following errorOverrides:
 flyway.errorOverrides=S0001:15151:I,S0001:15401:I,S0011:15404:I
# S0001 - 15151: Cannot alter the login '', because it does not exist or you do not have permission.
# S0001 - 15401: Windows NT user or group '' not found. Check the name again.
# S00011 - 15404: Could not obtain information about Windows NT group/user '', error code 0x4bc.

What did you expect to see?
An informational message in regard to S0011:15404.
What did you see instead?
 Changes successfully rolled back.
ERROR:
Migration [MIGRATION_FILE] failed
-----------------------------------------------------------------------
SQL State  : S00011
Error Code : 15404
Message    : Could not obtain information about Windows NT group/user '[USER_NAME]', error code 0x4bc.
Location   : /flyway/sql/test/stored-procedures/R__z_dbo.[MIGRATION_FILE] (/flyway/sql/test/stored-procedures/[MIGRATION_FILE])
Line       : 1
Statement  : EXECUTE AS USER = '[USER_NAME]'

Domain users are not yet supported on Linux SQL so we are on a trial for PRO only to take advantage of this feature locally to see if it will allow us to ignore these errors locally.  For whatever reason, Flyway doesn't like this one.

We have now loosened the rules for this as a workaround. I still believe this is an issue in the Microsoft driver and have filed an issue with them as well to get this issue's root cause resolved eventually.


Like with hostname: user and password can be passed via msg.payload

hostname can be sent to the node during runtime when the field is left empty in the configuration.
The same should be possible for user and password.

supported in 4.8.0


Add ttl to SOA records in builds

It seems like SOA records have two different ways of being built... the usual bind_render_record, and zone_builder.render_soa_only. This adds the TTL to the latter.
Resolves https://github.com/OSU-Net/cyder/issues/930

Is this supposed to be reviewed or not?

i'll deal with this one.


Can't create my own DB Trigger

Can't create my table base own trigger according to my use , can't import export as well.. can we accept this to be done ✅ in future?

@danielprrazevedo  Hi, yes i know that we cannot import/export trigger yet. It was on the list of ToDos, but i decided as know one where asking to prioritize the move to Capacitor3 which took me much more time that foreseen. that will be the first on the list except if there are other bugs requiring my attention. Is it something blocking for you?
can you more descriptif on Can't create my table base own trigger according to my use, do you mean with standard sql statements and execute or just import/export?

@danielprrazevedo  Hi, yes i know that we cannot import/export trigger yet. It was on the list of ToDos, but i decided as know one where asking to prioritize the move to Capacitor3 which took me much more time that foreseen. that will be the first on the list except if there are other bugs requiring my attention. Is it something blocking for you?
can you more descriptif on Can't create my table base own trigger according to my use, do you mean with standard sql statements and execute or just import/export?

@danielprrazevedo Hi, yes i know that we cannot import/export trigger yet. It was on the list of ToDos, but i decided as know one where asking to prioritize the move to Capacitor3 which took me much more time that foreseen. that will be the first on the list except if there are other bugs requiring my attention. Is it something blocking for you?
can you more descriptif on Can't create my table base own trigger according to my use, do you mean with standard sql statements and execute or just import/export?

Thank's for your reply...
I mean to say that I have created my project  required own trigger , its working fine in my DB sqlite , but i don't know how to add that trigger to specific table , as u have it for last_modified

@danielprrazevedo Hi, yes i know that we cannot import/export trigger yet. It was on the list of ToDos, but i decided as know one where asking to prioritize the move to Capacitor3 which took me much more time that foreseen. that will be the first on the list except if there are other bugs requiring my attention. Is it something blocking for you?
can you more descriptif on Can't create my table base own trigger according to my use, do you mean with standard sql statements and execute or just import/export?

Thank's for your reply...
I mean to say that I have created my project  required own trigger , its working fine in my DB sqlite , but i don't know how to add that trigger to specific table , as u have it for last_modified

@deepakjsr7979 ok so you do not know how to add it to a specific table in the json object to import i assume

@deepakjsr7979 ok so you do not know how to add it to a specific table in the json object to import i assume

@deepakjsr7979  Which release of the plugin are you using?

@deepakjsr7979  Which release of the plugin are you using?

I m using 2.9.6

I m using 2.9.6

@deepakjsr7979 i am working on it, it will be on the next release

@deepakjsr7979 i am working on it, it will be on the next release

@deepakjsr7979 i am working on it, it will be on the next release

Thanks man☺ really appreciate your effort..

@deepakjsr7979 i am working on it, it will be on the next release

Thanks man☺ really appreciate your effort..

@deepakjsr7979 this has been fixed in 2.9.8

@deepakjsr7979 There were a small issue for  Android export 'Partial' triggers which is fixed in 2.9.9

@deepakjsr7979 There were a small issue for Android export 'Partial' triggers which is fixed in 2.9.9

Great 👌 I will check it and reply you soon 🙂.

@deepakjsr7979 There were a small issue for Android export 'Partial' triggers which is fixed in 2.9.9

Can you please give  an example of Json structure  to create UUID and trigger ?

@deepakjsr7979 The doc was updated so look at https://github.com/capacitor-community/sqlite/blob/2.9.x/docs/ImportExportJson.md#full-mode-with-triggers-and-uuid


RecordsPermissionScope Requests must be scoped to a protocol

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.55%. Comparing base (661fad2) to head (0c57632).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #753   +/-   ##
=======================================
  Coverage   98.55%   98.55%
=======================================
  Files          73       73
  Lines       10910    10929   +19
  Branches     1571     1573    +2
=======================================
+ Hits        10752    10771   +19
  Misses        152      152
  Partials        6        6

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Authentication Sensor not available on RFID Stations

With the version 3.0.1 the Authentication sensors disappeared even though all the Charging Stations are equipped with RFID and they are enabled and in use.
Keba Charging Stations in use:
3x Keba P30 c-series RFID, eichrechtskonform
1x Keba P30 x-series RFID, eichrechtskonform
HA Version: 2023.3.3
Plugin Version: 3.0.3

I thought of only adding a lock sensor, if RFID is added to the configuration of the charging station. Without RFID configured, the lock is not working anyhow, at least with my BMW Wallbox Plus. Could you elaborate on how you use the lock?

Currently, I use the Lock to determine if the Charging Station (session) is authenticated or not. This allows me to only send the keba.start command to the charging stations that are locked and have an EV connected.

Good point, have not thought of that use case. I will re-add them tomorrow.

Quick fix: add a RFID to the configuration of the device. It should reload the component and add the missing locks.

Just as background info on the use case. Here we have an ekey xline Fingerprint sensor. That one sends a request to a webhook on HA. There I find the charging station that I just plugged in and authenticate that one with the RFID set by the finger that was used.


Migrate to native sliding sync

I've been running the sliding sync proxy for a few weeks now. My Element X says its my session is using native sliding sync, so I tried shutting down my sliding sync proxy and removed it from my well-known file.
After I removed my, all my matrix clients won't sync anymore, even those without sliding sync support.
How to migrate from the sliding sync proxy to native sliding sync?

I've just tested it with our deployment. Removed sliding sync proxy, dns entries and .well-known entries. Everything still works for us (tested with element-web and elementx on iOS).
synapse: v1.119.0
element: 1.11.86


revel package doesn't package all folders/files

The .tar file that the revel package command produces does not contain a number of folders/files in my project.  Entire folders of javascript files under my public folder are missing and the golang.org and gopkg.in folders in the project are also missing. My src folder looks like this (some folders left out for brevity):
/src
.. /myproject
..../public
....../myproject
......../models
........../component_modules
............/reporting_module
............/login_module
............/tickets_module
............/management_module
....../bower_components
.. /github.com
../golang.org
../gopkg.in
For example, the resulting .tar contains the reporting_module folder, but is missing the folders login_module, tickets_module, & management_module. These folders also contains more deeply nested folders of .js files (they are not empty).
I run:
revel package myproject
I'm running on Windows and using version v0.13.1 of revel. Using 7-zip to un zip it.
Is this a known issue?

Unzipping from the git bash resulted in the correct result:
tar -xvzf myproject.tar.gz


Deprecate StorageMetadata.downloadURLs

As per go/deprecate-download-url.

Mind running clang-format? I have a feeling it'll reformat the deprecated messages to be < 100 characters/line.

My update of clang-format just finished after 30 minutes. PR updated.


Leaderboard: Add radar chart

Not planned for the current release of the leaderboard, but it would be nice to have a radio chart for the plots. To make it clear where models excel. The radar plot could include task types, languages and/or domains.
It could either be placed where the description is now (moving the description up) or we could have it below the table.
Example of a radar chart

A critique of radar chart:
https://blog.scottlogic.com/2011/09/23/a-critique-of-radar-charts.html
There might be better plots available to access model capabilities quickly (though I think radar is a good fit on our case).

Would this chart be per-model? I'm trying to imagine where it would fit in the current layout. Maybe a separate tab as a single-model-view would fit this better

Yea, I also considered a tab where you compare models (e.g. 1-4) - otherwise it would get two crowded

I'm working on a prototype, will send screenshots once it gets neat enough

Whatcha think about this?

Looks great @x-tabdeveloping - is it possible to remove the shading i think that would make the plot more readable.
I would also change the tabs headers to:
"Performance by Size", "Performance by Task Category"
And then in the plot add "Performance by Task Category for the top-5 models."
Otherwise Wonderful addition.