Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Connection time outs without any warning. An output about the reason is expected. #874
I use EntityFramework7.Npgsql 3.1.0-rc1-1 and ef rc1-final versions.
I can connect to the host using DbVisualizer with these params:
I run => dnx ef migrations add InitialMigration
When I change the username or password or server or port or databasename, it creates the same System.TimeoutException.
I think outputs such as "invalid user creditentals", "server doesn't exist" would be better.
It is the part of the NpgsqlConnector class, Connect() method.
After the following line is called:
So the problem seems to be at:
I don't have any idea why it behaves differently in Linux..
referenced this issue
Nov 23, 2015
@damageboy I use CoreCLR. It was 1.0.0-rc2-16177.
So developer will never know when there is a socket exception at the time Socket.DoConnect() method is called. Actually the exception takes place at there and this makes Socket.Select() method behave different. I think problem is System.Net.Sockets package just as you mentioned pure CoreCLR issue.
Should I close this issue ? ( I have already opened about this at dotnet/corefx#4631 )
dotnet/corefx#4631 => fixes select method but the problem still resists.
I have tested the new libraries (system.net.sockets version rc2-530) using coreclr runtime and got the same error (connection time out).
This bug blocks us using ngpsql with coreclr runtime. So I created an other issue here:
For those who want to use ngpsql in linux : dnx mono runtime version beta8 works.
got this when trying a dnx ef database update.
ubuntu server, 1.0.0-rc1-update1 coreclr
EntityFramework and Npgsql versions: