-
Notifications
You must be signed in to change notification settings - Fork 178
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
fix: do not always request for prefix mapping #1300
fix: do not always request for prefix mapping #1300
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a question
// we have only packages that are contained in custom mapping | ||
// so we don't requests our prefix.mapping | ||
// this will allow us to not fail in case of running | ||
// under corporates firewalls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// we have only packages that are contained in custom mapping | |
// so we don't requests our prefix.mapping | |
// this will allow us to not fail in case of running | |
// under corporates firewalls | |
// When all requested channels are present in the custom_mapping, we don't have to request from the prefix_mapping. | |
// This will avoid fetching unwanted URLs, e.g. behind corporate firewalls |
Is this correctly understood from the comment?
My questions would be what happens with packages that are non pypi packages? E.g. pandoc
is not in the mirrored custom mapping. Will it then still fetch the prefix mapping?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry - my comment was not 100% accurate - I meant packages channels. Let me update it
…ttps://github.com/nichmor/pixi into fix/conda_pypi_name_mapping_honor_mirror_middleware
fixes: #1048