Closed Toshik1978 closed 5 years ago
This is happening to me as well, running pod outdated
with jsDelivr, and was occurring in 1.7.0 and 1.7.1 too. I was just about to open an issue when I saw that this one was just opened.
I've just found interesting workaround for my case. I've added to Podfile pod 'Firebase'
and all works!
But w/o CDN I had no this issue. At this moment I'm far away from fast internet, so CDN the only chance for me.
Looks like CDN has some problems with not explicit dependencies (like Firebase).
UPDATE. It works not stable... 2 calls to pod outdated
gives 2 different results. Success then fail (
cc @igor-makarov
This seems to be what I was talking about in Core#551.
I've manually integrated patch above. So, now I have much better error description. I have errors like
[!] CDN: jsdelivr-cocoa Relative path couldn't be downloaded: Specs/3/6/0/Crashlytics/3.8.5/Crashlytics.podspec.json, error: execution expired
or
[!] CDN: jsdelivr-cocoa Repo update failed - 2 error(s):
CDN: jsdelivr-cocoa Relative path couldn't be downloaded: Specs/0/3/5/Firebase/2.1.0/Firebase.podspec.json, error: execution expired
CDN: jsdelivr-cocoa Relative path couldn't be downloaded: Specs/1/f/6/SnapKit/0.13.0/SnapKit.podspec.json, error: execution expired
So, looks like it's always network issue. I don't know is it CDN-specific issue or my internet issue (it's actually bad at this moment)...
@igor-makarov should we add retries? are those intermittent network issues?
This occurs with https://cdn.cocoapods.org/
as well.
@dnkoutso It's not a network issue, the code spawns too many threads.
As for retries, I thought about it but didn't reach any solid opinions.
I’ve tried to add patch to cocoapods-downloader. In http.rb I’ve modified retry count to 5 and added connect-timeout as 300s. This way I’ve got stable behaviour. But I’m not sure, that it’s valid solution. What is more it can be random success due to current internet state... I’ll try to investigate it today.
@igor-makarov from what @Toshik1978 mentions though https://github.com/CocoaPods/Core/pull/551 does not seem to fully fix the issue. Am I understanding it right?
@dnkoutso as I was saying, there's the thread exhaustion issue which happens regardless of network, and there's the question of retries which needs to be discussed separately.
It seems two things are getting mixed in one issue.
Yeap, IMHO @igor-makarov is right. With integrated fix I’ve got much more useful error reporting. And this error gives me information about reason of pod failing - execution timeout. And this issue should be fixed separately.
Sounds good I will ship 1.7.3 with the fix in the following few days (hopefully tomorrow)
Merged the PR.
Issue still exists in 1.7.4 release(xx/xx/.rvm/gems/ruby-2.6.3/gems/cocoapods-1.7.4/lib/cocoapods.rb). The following is stack info,
Resolving dependencies of Podfile
CDN: jsdelivr-cocoa Relative path couldn't be downloaded: all_pods_versions_3_6_2.txt Response: 404
The jsDelivr URL is no longer supported or maintained. Please use the official URL at https://cdn.cocoapods.org/
.
For more info: https://blog.cocoapods.org/CocoaPods-1.7.2/
@igor-makarov thanks a lot, it works. And you save me more time, thanks again!
[!] CDN: cocoapods- Relative path couldn't be downloaded: Specs/0/3/5/Firebase/3.15.0/Firebase.podspec.json Response: 503
Got this error
We just added retries for this https://github.com/CocoaPods/Core/pull/573
This will definitely work for you.
https://github.com/CocoaPods/CocoaPods/issues/9319#issuecomment-561249605
Report
Command
Report
I've updated project to use CDN jsDelivr (added source to Podfile and updated .lock). Then call
pod update
Update of my pods.
I've got error message. It can be reproduced with
pod outdated
too...Stack
Plugins
Podfile
Error