# Pkg downtime incident

**URL:** <https://discourse.julialang.org/t/pkg-downtime-incident/44288>\
**Category:** Announcements\
**Tags:** package\
**Created:** [August 4, 2020, 9:58pm UTC](https://discourse.julialang.org/t/pkg-downtime-incident/44288 "2020-08-04T21:58:19Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [August 5, 2020, 4:11pm UTC](https://discourse.julialang.org/t/pkg-downtime-incident/44288/21 "2020-08-05T16:11:33Z")

</div>

People who already have a git cloned `~/.julia/registries/General` will continue to use git to update the registry, but only the registry. This should not make a significant difference and has no impact on this incident since registry updates were not broken. If you want to use Pkg protocol for General registry updates, you can delete `~/.julia/registries/General`.

---

<div class="post-metadata">

**Author:** ![stev47](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stev47/32/14090_2.png) [@stev47](https://discourse.julialang.org/u/stev47)\
**Post date:** [August 5, 2020, 4:55pm UTC](https://discourse.julialang.org/t/pkg-downtime-incident/44288/22 "2020-08-05T16:55:01Z")

</div>

> [@Keno](#):
>
> GitHub requests people don’t do this because the full clone path is special cased while the shallow clone case uses a slow path that causes lots of CPU load.

Do you have a reference for this? Since GitHub endorses shallow clones in their [GitHub actions](https://github.com/actions/checkout) where it is [implemented in that way](https://github.com/actions/checkout/blob/main/src/git-command-manager.ts#L171) I would totally have assumed it is fine. I could not find any official statement from GitHub for this.

---

<div class="post-metadata">

**Author:** ![Keno](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/keno/32/285_2.png) [@Keno](https://discourse.julialang.org/u/Keno)\
**Post date:** [August 5, 2020, 5:43pm UTC](https://discourse.julialang.org/t/pkg-downtime-incident/44288/23 "2020-08-05T17:43:15Z")

</div>

> [@stev47](#):
>
> Do you have a reference for this?

> <https://github.com/CocoaPods/CocoaPods/issues/4989#issuecomment-193772935>
>
> Note from @orta - 
> 
> If you are here because your Specs repo isn't updating, run:… \`cd ~/.cocoapods/repos/master && git fetch --depth=2147483647\` - this will convert your local repository of Podspecs to be a full clone, as opposed to a shallow copy.
> 
> \---
> \## What did you do?
> 
> Run \`pod setup\`
> \## What did you expected to happen?
> 
> Clone Spec repo master
> \## What happened instead?
> 
> It only downloads a few bytes and then throws error:
> 
> \> fatal: unable to access 'https://github.com/CocoaPods/Specs.git/': transfer closed with outstanding read data remaining
> \## Podfile
> 
> No Podfile yet
> 
> I also tried cloning the repo manually or with the githhub desktop app with no avail. 
> I´m having no issues cloning any other repo in github. Only with this one. Is it possible there is something wrong with it???
> 
> Thanks

They may have fixed it since.

---

<div class="post-metadata">

**Author:** ![stev47](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stev47/32/14090_2.png) [@stev47](https://discourse.julialang.org/u/stev47)\
**Post date:** [August 5, 2020, 5:59pm UTC](https://discourse.julialang.org/t/pkg-downtime-incident/44288/24 "2020-08-05T17:59:09Z")

</div>

> [Issues Cloning Spec repo - GitHub taking a very long time to download changes to the Specs Repo · Issue #4989 · CocoaPods/CocoaPods · GitHub](https://github.com/CocoaPods/CocoaPods/issues/4989#issuecomment-193772935)

Thanks! It seems they were talking 4 years ago about high-frequency  
(~10^6/week) fetches for a single repository consisting of a large amount  
(~10^4) of subdirectories and subsequent usage of non-shallow fetches that in  
total lead to more load than a full clone.

It is probably good to be cautious, but the reference does not seem to be  
general advice, especially since Julia is moving away from GitHub as a CDN  
anyway.

---

<div class="post-metadata">

**Author:** ![schlichtanders](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/schlichtanders/32/32145_2.png) [@schlichtanders](https://discourse.julialang.org/u/schlichtanders)\
**Post date:** [August 9, 2020, 4:16pm UTC](https://discourse.julialang.org/t/pkg-downtime-incident/44288/25 "2020-08-09T16:16:21Z")

</div>

Is it again possible/safe to register new packages using JuliaRegistrator?

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [August 9, 2020, 4:33pm UTC](https://discourse.julialang.org/t/pkg-downtime-incident/44288/26 "2020-08-09T16:33:47Z")

</div>

Yes

[Previous page](https://discourse.julialang.org/t/pkg-downtime-incident/44288.md?page=1)
