You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NetMQ Version: latest at 6 Aug (probably 4.0.0.0 as *.csproj says).
Built from sources for .NET FW 4.8 Operating System: Win7 x64 SP1 .NET Version: Framework 4.8
Unexpected null of type AsyncSocket
at NetMQ.Assumes.NotNull[T](T o) in C:\PRG\NetMQ_project\NetMQ\Utils\Assumes.cs:line 12
at NetMQ.Core.Transports.Tcp.TcpListener.SetAddress(String addr) in C:\PRG\NetMQ_project\NetMQ\Core\Transports\Tcp\TcpListener.cs:line 126
at NetMQ.Core.SocketBase.Bind(String addr) in C:\PRG\NetMQ_project\NetMQ\Core\SocketBase.cs:line 569
at NetMQ.NetMQSocket.Bind(String address) in C:\PRG\NetMQ_project\NetMQ\NetMQSocket.cs:line 188
at NetMQ.NetMQSocket..ctor(ZmqSocketType socketType, String connectionString, DefaultAction defaultAction) in C:\PRG\NetMQ_project\NetMQ\NetMQSocket.cs:line 65
at NetMQ.Sockets.ResponseSocket..ctor(String connectionString) in C:\PRG\NetMQ_project\NetMQ\Sockets\ResponseSocket.cs:line 17
...
If you look at SetAddress(TcpListener.cs line 121), it's smth strange: the only place where m_handle is initialized is line 130:
What?? How you can check it's not null if you never initialized it? Seems somebody too anxious for "null" value that forgot business logic - main thing he should worry about.
After elementary fix (remove illogical Assert) server at least started.
The text was updated successfully, but these errors were encountered:
Environment
NetMQ Version: latest at 6 Aug (probably
4.0.0.0
as *.csproj says).Built from sources for .NET FW 4.8
Operating System: Win7 x64 SP1
.NET Version: Framework 4.8
Sample is:
Fails with error:
If you look at
SetAddress
(TcpListener.cs line 121), it's smth strange: the only place wherem_handle
is initialized is line 130:...but immediately before this line you check:
What?? How you can check it's not null if you never initialized it? Seems somebody too anxious for "null" value that forgot business logic - main thing he should worry about.
After elementary fix (remove illogical Assert) server at least started.
The text was updated successfully, but these errors were encountered: