10 ms·

Repos are disappearing from Gitlab

65 points by kaishiro 9y ago

DiabloD3 9y ago
Official response: https://twitter.com/gitlabstatus/status/897375110205722624 https://twitter.com/gitlabstatus/status/897375110205722624
deleted 9y ago
[deleted]
hardwaresofton 9y ago
Disclaimer: I don't work for Gitlab. The problem seems to be resolved now, seems like a problem with invalidated cache on a heavily loaded server ( official tweet: https://twitter.com/gitlabstatus/status/897375110205722624 https://twitter.com/gitlabstatus/status/897375110205722624) -- not data destruction. Gitlab Issue: https://gitlab.com/gitlab-com/support-forum/issues/2320 https://gitlab.com/gitlab-com/support-forum/issues/2320
cottsak 9y ago
Resolved https://twitter.com/gitlabstatus/status/897382564020793345 https://twitter.com/gitlabstatus/status/897382564020793345
laumars 9y ago
I really really want to like Gitlab, I love their openness and I love having the competition with Github. But it seems like every 6 months they have an issue of some description. It's unfortunate the expectations we place on cloud providers but my clients have similar expectations from me so I need to work with providers that can assure me they can offer the kind of uptime I'm expected to provide. Plus the modern way of pipelining code means git is seldom a static silo like it once was which only compounds things when one of your links in the chain has multiple glitches a year. edit: I thought I would get downvoted into oblivion for this but I felt it was a discussion worth having since they relate directly to my experiences with working at scale. So I "took one for the team" - so to speak. Anyhow to answer a few points: * Yes I'm aware git is a distributed VCS but like I said, git is seldom a silo so you'd need to reconfigure your pipeline to point to the new git origin or have your pipeline already configured to accept fallback systems. Quickly your configuration spirals in complexity. * Yes I'm also aware you can self host. This is actually what we did do before moving to a cloud hosted solution. This added complications with our AWS pipelining. Problems that were solvable but again, with additional complexity compared with cloud hosted solutions. At the end of the day all problems can be addressed with enough time and resources however the reason people typically opt for hosted solutions is to reduce complexity not increase it.
- amelius 9y ago
  But git is a decentralized system/protocol, so in theory if Gitlab is down, you could very easily resort to using a different origin.
  - omk 9y ago
    When you have CI/CD in place your central repo going down is a huge hassle.
    - Cthulhu_ 9y ago
      That's why you should make your CI / CD code-based, so you can recreate it from scratch within minutes. At worst you'd lose your previous build states.
      - trome 9y ago
        Might as well Ansiblize it :P
  - laumars 9y ago
    In theory yes. But in practice it's not quite so straightforward. If you're working to tight deadlines then having to reconfigure your pipeline because of an outage is both scary and a huge pain in the arse. The reason people opt for cloud solutions is to decrease complexity, not increase it. So if I'm having to run multiple git origins then I would be better off self hosting and just moving those complexities in house.
    - jacquesm 9y ago
      That's exactly why you can run your own gitlab instance. The thing to do when you don't want dependencies is to reduce your dependencies, not complain about a third party service that offers their software for free so you can run it yourself.
      - 9y ago
OskarS 9y ago
And now gitlab.com returns 403 forbidden for me. Wonderful!
- cmatija 9y ago
  Sorry about that. Could you provide more context about it? We'd love to help. Are you already logged in when that happens to you? If so, you should open an issue in https://gitlab.com/gitlab-com/support-forum/issues https://gitlab.com/gitlab-com/support-forum/issues with as much info as possible so we can look into it. If you're getting that when you're trying to log-in, then you're having trouble accessing your GitLab.com account, with which our support team can help you - https://support.gitlab.com https://support.gitlab.com
mrmondo 9y ago
Title reads as clickbait, while repos didn’t appear due to the caching issue it was quickly resolved and they didn’t disappear and it isn’t still happening.

65 points by kaishiro 9y ago

Official response: https://twitter.com/gitlabstatus/status/897375110205722624 https://twitter.com/gitlabstatus/status/897375110205722624

deleted 9y ago

[deleted]

hardwaresofton 9y ago

Disclaimer: I don't work for Gitlab. The problem seems to be resolved now, seems like a problem with invalidated cache on a heavily loaded server ( official tweet: https://twitter.com/gitlabstatus/status/897375110205722624 https://twitter.com/gitlabstatus/status/897375110205722624) -- not data destruction. Gitlab Issue: https://gitlab.com/gitlab-com/support-forum/issues/2320 https://gitlab.com/gitlab-com/support-forum/issues/2320

cottsak 9y ago

Resolved https://twitter.com/gitlabstatus/status/897382564020793345 https://twitter.com/gitlabstatus/status/897382564020793345

laumars 9y ago

I really really want to like Gitlab, I love their openness and I love having the competition with Github. But it seems like every 6 months they have an issue of some description. It's unfortunate the expectations we place on cloud providers but my clients have similar expectations from me so I need to work with providers that can assure me they can offer the kind of uptime I'm expected to provide. Plus the modern way of pipelining code means git is seldom a static silo like it once was which only compounds things when one of your links in the chain has multiple glitches a year. edit: I thought I would get downvoted into oblivion for this but I felt it was a discussion worth having since they relate directly to my experiences with working at scale. So I "took one for the team" - so to speak. Anyhow to answer a few points: * Yes I'm aware git is a distributed VCS but like I said, git is seldom a silo so you'd need to reconfigure your pipeline to point to the new git origin or have your pipeline already configured to accept fallback systems. Quickly your configuration spirals in complexity. * Yes I'm also aware you can self host. This is actually what we did do before moving to a cloud hosted solution. This added complications with our AWS pipelining. Problems that were solvable but again, with additional complexity compared with cloud hosted solutions. At the end of the day all problems can be addressed with enough time and resources however the reason people typically opt for hosted solutions is to reduce complexity not increase it.

amelius 9y ago
But git is a decentralized system/protocol, so in theory if Gitlab is down, you could very easily resort to using a different origin.
- omk 9y ago
  When you have CI/CD in place your central repo going down is a huge hassle.
  - Cthulhu_ 9y ago
    That's why you should make your CI / CD code-based, so you can recreate it from scratch within minutes. At worst you'd lose your previous build states.
    - trome 9y ago
      Might as well Ansiblize it :P
- laumars 9y ago
  In theory yes. But in practice it's not quite so straightforward. If you're working to tight deadlines then having to reconfigure your pipeline because of an outage is both scary and a huge pain in the arse. The reason people opt for cloud solutions is to decrease complexity, not increase it. So if I'm having to run multiple git origins then I would be better off self hosting and just moving those complexities in house.
  - jacquesm 9y ago
    That's exactly why you can run your own gitlab instance. The thing to do when you don't want dependencies is to reduce your dependencies, not complain about a third party service that offers their software for free so you can run it yourself.
    - 9y ago

OskarS 9y ago

And now gitlab.com returns 403 forbidden for me. Wonderful!

cmatija 9y ago
Sorry about that. Could you provide more context about it? We'd love to help. Are you already logged in when that happens to you? If so, you should open an issue in https://gitlab.com/gitlab-com/support-forum/issues https://gitlab.com/gitlab-com/support-forum/issues with as much info as possible so we can look into it. If you're getting that when you're trying to log-in, then you're having trouble accessing your GitLab.com account, with which our support team can help you - https://support.gitlab.com https://support.gitlab.com

mrmondo 9y ago

Title reads as clickbait, while repos didn’t appear due to the caching issue it was quickly resolved and they didn’t disappear and it isn’t still happening.