10000 [question] Transitive headers not found when visible=False · Issue #18389 · conan-io/conan · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[question] Transitive headers not found when visible=False #18389

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.

Al 8000 ready on GitHub? Sign in to your account

Open
1 task done
db4 opened this issue May 30, 2025 · 2 comments
Open
1 task done

[question] Transitive headers not found when visible=False #18389

db4 opened this issue May 30, 2025 · 2 comments
Assignees

Comments

@db4
Copy link
Contributor
db4 commented May 30, 2025

What is your question?

I hope I've finally figured out the issue #18237. The attached archive demonstrates it for Windows. good.bat shows success when a dependency binary is already available and bad.bat shows a failure that when it's built while conan install.
conan_test.zip

Have you read the CONTRIBUTING guide?

  • I've read the CONTRIBUTING guide
@AbrilRBS AbrilRBS self-assigned this May 30, 2025
@AbrilRBS
Copy link
Member

Hi @db4 thanks a lot for providing a reproducible case, we have been able to reproduce it and are looking into ways to tackle it :)

@AbrilRBS
Copy link
Member
AbrilRBS commented Jun 2, 2025

Hi @db4 some updates, we're still looking into this.

For now we think that this might be a malformed graph, as it makes little sense for a conflict between pkg3/1.1 and pkg3/1.0 not to be reported in pkg1, as it can see both, so there would be no way to distinguish which one you would want to use.

This becomes a bit more evident because if you swap the order of any of the requirements in pkg1 or consumer, a conflict is reported, but we still haven't totally discarded whether this should be a supported graph configuration either.

We are working towards properly reporting this conflict in #18403

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

No branches or pull requests

2 participants
0