Closed danylaporte closed 5 years ago
That looks interesting, can you also reproduce with stable/beta?
It works using the stable toolchain. I will try the beta.
It does not work in the beta toolchain. Same as in nightly.
I can reproduce the issue locally.
Cannot produce a reduced testset so far. The error is triggered (but likely not caused by) in miow::CompletionPort::get_many. If I remove enough code from tiberius it isn't triggered anymore, leading me to believe we're dealing with a lower level issue here (possibly optimization).
A short workaround should be not using instance-lookups (specifying a TCP port).
Ok, thanks. I will try that. If I use a UDP socket to invoke the SQL Browser service just before Tiberius, I get it to work but the same call inside Tiberius is failing. I will bypass the SQL Browser service for now. Thanks again.
If I make the function parse_connection_str
in lib.rs public, the issue goes away.
Yeah sure anything that effects optimization will cause this to go away, upstream LLVM bug for the underlying issue has been filed.
Thanks for all your hard work on this bug! I saw the "regression in rust-nightly" issue.
@danylaporte Should work with the next nightly now.
@steffengy It works now in nightly. Thank you very much for all your hard work on this issue.
This is a weird behavior. When compiled in debug mode, the code is working but when compiled in release mode, it failed with the following panic:
It used to works in release mode but I cannot say when it started not working. Cargo.toml does not have any patch on the dependency. I am using the very latest nightly.