Skip to content
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

art:build info upload fails to upload build info where a (python) dependency is located on a different remote #132

Open
schwaerz opened this issue Jun 6, 2024 · 3 comments

Comments

@schwaerz
Copy link
Contributor

schwaerz commented Jun 6, 2024

We are using a python dependency (base class) in our conanfiles, which is located on a generic publicly available conan repo (conan-remote-a).
The package to be created will be uploaded to a different remote (conan-remote-b).

When trying to upload the build info, I will get an error '400' complaining that the properties for conan_base cannot be set currectly. Which is understandable as it searches (according to the error message) in the wrong remote (conan-remote-b).

Interestingly art:build_info create will always add the dependency of the python base class into the build info json file - even if I don't specify --with-dependencies. Maybe a bug there as well?

@schwaerz
Copy link
Contributor Author

schwaerz commented Jun 7, 2024

Please note that I tried with and without --with-dependencies. Reading the source code it seems that --with-dependencies is supposed to disable dependency processing?

@schwaerz
Copy link
Contributor Author

schwaerz commented Jun 7, 2024

Did some further digging in the source code.

in the input json (from conan create) I found the following:

{
    "graph": {
        "nodes": {
            "0": {
                "ref": "conanfile",
...
            },
            "1": {
                "ref": "foo/1.2.3",
...
                "python_requires": {
                    "conan_base/0.1.3": {
                        "remote": null,
                        "recipe": "Cache",
                        "path": "/workspaces/foo/.conan2/p/conan3f0fc0e0fabee/e"
                    }
                },
...
                "info": {
                    "python_requires": [
                        "conan_base/0.1.Z"
                    ]
                },
...
}

However I was not able to find any specific handling for a python_requires in the source code. However if I simply rename it to something like _python_requires it will no longer get included in the build_info.json

@schwaerz
Copy link
Contributor Author

Some update:
Stangely enough, I did not face this issue in another project. Usign the same base class there, but no such issues.

Will try to get some more insights.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant