-
Notifications
You must be signed in to change notification settings - Fork 125
add .git extensions to dependency URLs #770
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
add .git extensions to dependency URLs #770
Conversation
@swift-server-bot test this please |
I am very surprised to learn this has an impact. Are you using package mirroring? |
No. |
Hmm, do you have a Feedback Assistant report for this? I'm trying to work out why Xcode would behave this way, as I've never seen it before. |
I have not filed a feedback. I'm happy to if that helps. And, if you have any suggestion on what would be relevant to include please let me know. I can make sure to include it. |
I don't remember if this issue started for me before or after I started using Xcode 16. I could try it in Xcode 15 to see if it happens there too. (I don't know if the Xcode version would/could impact this) |
Would it be possible to file a Feedback Assistant report? My recommendation would be to see if you can reproduce this in a small workspace that you can attach to the report, along with information about the Xcode version. |
I'm definitely having difficulty figuring out how to reproduce this in a small project at the moment, but I have also figured out how to solve my immediate issues. If I do the following I can get Xcode to fetch new package versions:
I'll keep looking to see if I can reproduce the issue with a small sample project. |
That's an interesting data point. If you do that series of steps you should end up with a new Package.resolved file: what does it look like? |
I was the one who suggested trying adding .git to those repo urls (and subsequently suggested a PR), and I'm not surprised that it worked, although it certainly shouldn't work. I had heard about some repo/url handling behavior differences/problems when using .git or not using .git in SwiftPM before, so I gave it chance that adding .git might have an effect on this new bug. I understand and appreciate if anyone wants to find the root of the problem and I'm not trying to stop that discussion, but generally speaking, as far as this PR goes, I think this is still mergable even assuming it doesn't actually fix any Xcode problems. |
Can we open an issue on SwiftPM for this. We can certainly make sure that all of our repos are using |
Does the same thing happen from the swift command line? |
This does not happen on the CLI. This seems to be isolated to the Xcode workspace only for me. |
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.
Approving this to get it aligned with our other dependencies here
@swift-server-bot test this please |
@swift-server-bot add to allowlist |
@swift-server-bot test this please |
@swift-server-bot add to allowlist |
This PR adds .git extensions to the Swift Package Manager dependencies that didn't include them. For me, this resolves issues that I have had with an error produced by Xcode when updating to the latest package versions if I'm editing the project which depends on AHC in an Xcode Workspace.
The complete error is:
github.com: https://github.com/apple/swift-algorithms: The repository could not be found. Make sure a valid repository exists at the specified location and try again.
Based on conversations in the Vapor Discord server, adding these extensions "shouldn't" make a difference to the dependency resolution done by swift package manager, however adding them resolves the error. 🤷