You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that covers swift-log and all other github.com dependencies, I would hope that swift build never contacts github.com because the whole idea of the mirroring is that it never needs to reach out of say a company's network.
However:
$ swift build
Fetching https://internal/some_other_repo
Fetching https://github.com/apple/swift-log.git ## <<<<< BAD
Completed resolution in 4.33s
Cloning https://github.com/apple/swift-log.git ## <<<<< BAD
Resolving https://github.com/apple/swift-log.git at 1.1.0
Cloning https://internal/some_other_repo
Resolving https://internal/some_other_repo at 1.0.7
Updating https://internal/some_other_repo
Fetching https://internal/mirrors/swift-log.git
Completed resolution in 4.76s
Removing https://github.com/apple/swift-log.git
Cloning https://internal/mirrors/swift-log.git
Resolving https://internal/mirrors/swift-log.git at 1.1.0
So the good thing is that it converges to the right solution (using the mirrors instead of github.com) but in the intermediate steps, it does fetch from github.com, despite a mirror being configured.
Tested with:
$ jw-swift-5.1 swift -version
Apple Swift version 5.1-dev (LLVM 2238e51577, Swift 16859f1963)
Target: x86_64-apple-darwin19.0.0
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: 5072becf92410481f084ab50c44aab4c
Issue Description:
if I have a repository with the following dependencies (arrow means 'depends on')
This bug only manifests if the mirrored repository is a transitive and not a direct dependency.
Then running
swift build
will produce such aPackage.resolved
file:which is correct. If I now configure a mirror like so:
that covers
swift-log
and all othergithub.com
dependencies, I would hope thatswift build
never contactsgithub.com
because the whole idea of the mirroring is that it never needs to reach out of say a company's network.However:
So the good thing is that it converges to the right solution (using the mirrors instead of
github.com
) but in the intermediate steps, it does fetch from github.com, despite a mirror being configured.Tested with:
The text was updated successfully, but these errors were encountered: