[bug] `conan search` broken
See original GitHub issueEnvironment Details (include every applicable attribute)
- Operating System+version: Windows 20H2
- Conan version: 1.51.0
- Python version: PyInstaller
- Artifactory EnterpriseX: 7.41.7
Steps to reproduce (Include if Applicable)
conan search
on a Artifactory repository gives unexpected results.
For some reason using the artifactory remote for conancenter
does work.
We updated to conan 1.51.0 yesterday but also upgraded Artifactory yesterday. See output below.
Logs (Executed commands with output) (Include/Attach if Applicable)
> conan search zlib -r artifactory-repository
Existing package recipes:
apr/1.7.0
autoconf/2.71
automake/1.16.3
automake/1.16.4
b2/4.5.0
b2/4.8.0
bison/3.7.1
bison/3.7.6
boost/1.72.0
boost/1.74.0
boost/1.76.0
brotli/1.0.9
bzip2/1.0.8
catch2/2.13.7
ccache/4.6
cmake/3.21.4
cppcheck/2.7.5
eigen/3.3.8
expat/2.4.1
ffmpeg/4.2.1
ffmpeg/4.3.2
flex/2.6.4
fmt/6.0.0
fmt/6.1.2
fmt/7.1.0
fmt/7.1.3
fmt/8.1.1
freetype/2.10.4
freetype/2.11.0
freetype/2.11.1
gmp/6.2.1
gnu-config/cci.20201022
gtest/1.10.0
gtest/1.11.0
gtest/1.12.1
hdf5/1.8.21
hdf5/1.12.0
hdf5/1.12.1
jansson/2.13.1
json-schema-validator/2.1.0
libiconv/1.16
libmp3lame/3.100
libpng/1.6.37
libpq/13.3
libsodium/1.0.18
libtool/2.4.6
libvpx/1.9.0
libvpx/1.10.0
libvpx/1.11.0
libwebp/1.2.0
libwebp/1.2.1
libwebp/1.2.2
libx264/20191217
libx265/3.4
lz4/1.9.3
m4/1.4.18
m4/1.4.19
matio/1.5.23
meson/0.59.2
minizip-ng/3.0.6
mpir/3.0.0
nasm/2.15.05
ninja/1.10.2
nlohmann_json/3.7.3
nlohmann_json/3.9.1
nlohmann_json/3.10.4
nlohmann_json/3.10.5
ogg/1.3.4
openh264/2.1.1
openjpeg/2.4.0
openssl/1.1.1l
openssl/3.0.1
opus/1.3.1
pcre/8.44
pcre/8.45
picojson/1.3.0
pkgconf/1.7.4
protobuf/3.11.4
protobuf/3.17.1
pybind11/2.5.0
pybind11/2.8.1
pybind11/2.9.1
rapidjson/cci.20200410
sml/1.1.4
spdlog/1.8.5
strawberryperl/5.30.0.1
swig/4.0.1
tinyxml/2.6.2
uriparser/0.9.6
vorbis/1.3.7
winflexbison/2.5.24
xerces-c/3.2.2
xerces-c/3.2.3
xz_utils/5.2.5
yaml-cpp/0.7.0
yasm/1.3.0
z3/4.8.8
zeromq/4.3.2
zlib/1.2.11
zlib/1.2.12
zstd/1.5.0
zstd/1.5.1
zstd/1.5.2
This works:
conan search zlib -r conan-io
Existing package recipes:
zlib/1.2.8
zlib/1.2.11
zlib/1.2.12
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Troubleshooting — conan 1.32.1 documentation
When installing packages (with conan install or conan create) it is possible that you get an error like the following one: WARN: Can't...
Read more >Conan search with channel broken (#326898) · Issues - GitLab
Searching for a conan package with a user and channel returns null instead of an empty list for results . When using conan...
Read more >[RTFACT-26310] Issue with the conan-search - Jira - JFrog
1ERROR: HTTPSConnectionPool(host='rt-artifactory.test.com', port=443): Max retries exceeded with url: ...
Read more >Qt Conan package troubleshooting - Qt Wiki
Here you can find causes for commonly encountered issues with Conan ... Unable to connect to conancenter=https://center.conan.io; ERROR: ...
Read more >conan C++ ERROR: Unable to find Package in remotes
The package reference in conanfile.txt is declared using its name, version, user and channel. Both user and channel are used as a namespace ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@czoido We just found out, that every
conan install
in our infrastructure is broken because of this bug. So this is very urgent for us!To paint the picture:
Expected behavior:
The package
bapdb
does not exist in remoteprod
and therefore conan should continue the search with other remotes.Actual Behavior:
Conan decides the package exists in
prod
but not with a correct version.Here is the trace file:
Here is the output of the API Call:
Hi @vectorsli,
Yes, It looks like something related to Artifactory. We are trying to raise the awareness of the Artifactory team on it and as far as I know they are working on it. Did you already comment to Artifactory support that you are having that issue or open a Jira ticket for this? That would help too. We’ll do as much as we can to keep track on this and make sure that things keep moving to solve this and I’m sure that the Artifactory team will solve this as soon as possible.