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

Use correct url in metadata and mirrors #3816

Merged
merged 12 commits into from
Feb 21, 2025
Merged

Conversation

Hind-M
Copy link
Member

@Hind-M Hind-M commented Feb 11, 2025

@Hind-M Hind-M added the release::bug_fixes For PRs fixing bugs label Feb 11, 2025
@Hind-M Hind-M force-pushed the url_issue branch 2 times, most recently from 1146b9c to 18bf372 Compare February 17, 2025 09:24
@Hind-M Hind-M marked this pull request as ready for review February 17, 2025 09:24
Copy link
Member

@jjerphan jjerphan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @Hind-M.

Is it possible to have a slightly more precise and explicit PR title?

@Hind-M Hind-M changed the title Fix url Use correct url in metadata and mirrors Feb 18, 2025
Copy link
Member

@jjerphan jjerphan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for adding the tests on PackageFetcher directly, this is much clearer!

This LGTM modulo one last suggestion.


If we make some of PackageFetcher's const getters public (which I think they should independently from this PR), we can complete the tests as hinted.

See f493d46 as a suggestion.

@Hind-M
Copy link
Member Author

Hind-M commented Feb 20, 2025

If we make some of PackageFetcher's const getters public (which I think they should independently from this PR), we can complete the tests as hinted.
See f493d46 as a suggestion.

I don't think these methods should be made public as they are only meant to be used internally in package_fetcher.cpp. The PackageFetcher class itself is also only used in Transaction which doesn't need other functions to be exposed.

@jjerphan
Copy link
Member

I don't think these methods should be made public as they are only meant to be used internally in package_fetcher.cpp.

I think this is debatable1 but not a priority for now.

You can merge this PR.

Footnotes

  1. It would be useful to have a way to test some of those methods since some of them are not trivial (for instance url_path is not a getter returning const l-values of private members of an instance, but it conditionally constructing values at runtime). I cannot think of other simple way to test this than to change the access specifiers to public for now -- we could use some fixture friend (but that's far-fetch and overly complex) or we could #define private public at the beginning of this translation unit (but that's definitely evil). Opinions and ideas welcome!

@Hind-M Hind-M merged commit 8824be1 into mamba-org:main Feb 21, 2025
34 checks passed
@Hind-M Hind-M deleted the url_issue branch February 21, 2025 09:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release::bug_fixes For PRs fixing bugs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Redirection issues when using custom channels (e.g. https://repo.prefix.dev/emscripten-forge-dev)
2 participants