Alex Veber
Alex Veber
> which apparently are still there on 1.0.61? I can't reproduce the issue with anyhow 1.0.61 on either stable or nightly.
I had this issue in the past. It's caused by some old rust-analyzer setting in settings.json that keeps reverting the change you do, however I don't remember what it is....
I am not sure I see the added value of this over just doing `#[deprecated(since = "3.8", note = "will be removed in version 4.0")]`
This is an old issue but if anyone encounters the problem the issue here is that `connectionPoolTimeout` is set to 0. For some reason this slows down pyvmomi, any other...
I did another test where I connect to 2 different hosts. Here is the code: ```python # ruff: noqa import ssl from threading import Thread import time from pyVim.connect import...
I did more tests and it looks like the performance issues are caused by python 3.7. Testing with python 3.11 and 3.12 the performance is much better.
I decided to reopen the issue after further testing. While the performance numbers with newer versions of python are better the trend is still the same. Connecting from multiple threads...
Is there anything new regarding this issue? I want to run cargo check with deny warnings as a precommit hook but the only way is to set RUSTFLAGS which causes...
I don't think using RUSTFLAGS here is the correct solution, clippy has the option to control the lints directly using `cargo clippy -- -Dwarnings`. You can also do this with...
I also have this issue in a very large repo but it happens even if I set: ``` "python.analysis.userFileIndexingLimit": -1 ```