-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WouldBlock bubbling up to the calling code #31
Comments
How can I run tests on my own? I tried running tiberius tests but got errors like:
|
docker-compose.yml version: "3"
services:
mssql-2019:
image: mcr.microsoft.com/mssql/server:2019-latest
restart: always
environment:
ACCEPT_EULA: Y
SA_PASSWORD: "<YourStrong@Passw0rd>"
ports:
- "1433:1433"
networks:
- databases
networks:
databases: > docker-compose up
> export TIBERIUS_TEST_CONNECTION_STRING="server=tcp:localhost,1433;user=SA;password=<YourStrong@Passw0rd>;TrustServerCertificate=true"
> cargo test --all-features You can change async-std version from 1.6.3 to 1.6.4 to see some tests randomly failing to the WouldBlock. |
When I run
Is this normal? Do I just need to wait for a while for Also, if I run I'm using macos if that's relevant. |
Ah, yeah, the TLS certificate in the docker image will not work together with macOS Catalina. Damn, it's Linux/Windows only :( |
And, if you run |
We have the same issue with code that is basically |
Thanks for the help! This should be fixed in the latest release now, but let me know if you run into any issues. The problem was in that random yielding inside |
@tailhook Can you do |
Fixed in Tiberius too, no more errors bubbling up. Thank you @stjepang. |
Got |
* Gracefully handle the inability to spawn threads * Ensure the thread limit is never zero
I have an issue with async-native-tls together with async-std, and looking into the backtrace, it points to somewhere in this crate.
Our crate (tiberius) runs tests just fine with tokio and async-std 1.6.3, but updating async-std to 1.6.4 or later randomly throws
Io(Kind(WouldBlock))
. We have a few hundred tests, and 1-5 of them randomly fail into this error. The error happens when callingconnect
fromTlsConnector
(async-native-tls 0.3.3) and passing aTcpStream
to it from async-std 1.6.5 (or 1.6.4).As I said, when passing a
TcpStream
from async-std 1.6.3 or aCompat
version from tokio 0.2.x, the errors never happen. Hopefully this is the right crate to create the issue!Here's a full backtrace from one of the failing tests:
The text was updated successfully, but these errors were encountered: