[question] What is the expected behavior of `conan install --remote REMOTE`

I’m trying to understand the expected behavior of conan install --remote REMOTE. We have a local Artifactory server for our own packages, but still have conan-center as a remote, even though it is not really used.

Output of conan remote list:

virtual-remote: https://[...] [Verify SSL: True]
conan-center: https://conan.bintray.com [Verify SSL: True]

Whether or not I call conan install --remote virtual-remote or just conan install, I always get these “extra” calls in the trace log.

{"_action": "REST_API_CALL", "duration": 0.21838855743408203, "headers": {"User-Agent": "Conan/1.37.1 (Windows 10; Python 3.9.5; AMD64) python-requests/2.25.1", "X-Client-Anonymous-Id": "**********", "X-Client-Id": ""}, "method": "GET", "time": 1627460264.1806884, "url": "https://conan.bintray.com/v1/ping"}
{"_action": "REST_API_CALL", "duration": 0.016086578369140625, "headers": {"User-Agent": "Conan/1.37.1 (Windows 10; Python 3.9.5; AMD64) python-requests/2.25.1", "X-Client-Anonymous-Id": "**********", "X-Client-Id": ""}, "method": "GET", "time": 1627456231.6621335, "url": "https://conan.bintray.com/v2/conans/[...]/revisions/35c21a513276d9605b75da32df276b87/packages/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/latest"}

Is this to be expected and is there any way to avoid it (besides deleting the remote?)

Versions:

• Python 3.9.5 (tags/v3.9.5:0a7dcbd, May 3 2021, 17:27:52) [MSC v.1928 64 bit (AMD64)] on win32
• Conan version 1.37.1

• [y] I’ve read the CONTRIBUTING guide.

Edit: added Python and Conan version

[memsharded]

PR https://github.com/conan-io/conan/pull/9355 was merged, so this bug will be fixed and released in next 1.40

[memsharded]

Reproduced the behavior and checking in this PR https://github.com/conan-io/conan/pull/9355, if it can be changed and considered a bug, we better make sure that this change is not breaking other users that depend on this behavior.