Earlier quoted context omitted.
Pitty its licensing cost will go up ten fold next year.
How so? Pics or it didn’t happen.
Gitlab.com was experiencing elevated error rates for Git, Web, and API
41–50 of 94 posts
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#42Earlier quoted context omitted.
Hi, what could be improved in GitLab's code base in your opinion? :)
In the past people have suggested we rewrite GitLab in Scala, Haskell, Node.js, and IIRC also regular Java. I think it mostly comes down to "I didn't write it, so it's bad" :)
Suprised no rust or elixir there.
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#43Earlier quoted context omitted.
Github seems to be doing worse
Yes. They (GitHub) have been doing a lot worse. Last time I checked, they where completely down 2 days ago. [0] Before that, GitHub Actions was down 14 days ago: [1]. At least with GitLab, you can set up a self-hosted solution for free as a backup, unlike GitHub (Unless you want to pay a lot for GH Enterprise) where some have 'gone all in on GitHub Actions' and then some couldn't push that critical change [2] before…
> Maybe its time to setup a self-hosted backup VCS and not depend entirely on GitHub/GitLab web.
I've been wanting to do this for some time purely for git hosting (don't care about CI at all) but wasn't sure about how to make it failover...
Personally i'd be happy with a headless git server, but that's not fair on everyone else who wants the GUI to browse and organise stuff, so I want gitlab etc to deal with that. What would be nice is to have a headless backup server that allowed everyone to continue pulling/pushing from the CLI with their existing repos when gitlab is down. I can't see a smooth way of doing that since it would require messing with the git remotes, unless the solution is inverted and uses a single remote pointing at the "backup" server which then replicates to gitlab, but I don't think gitlab can be configured to change the default remote when people clone it from the UI.
I suppose this is why people just end up self hosting gitlab instead.
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#44This status page is weird, it says that there is an active incident and that there is a databate latency issues, but everything is green:
https://i.imgur.com/oXSiyTG.png
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#45Earlier quoted context omitted.
Well, they are stretching and extending gitlab with more and more functions.. With a... Not so great code base..
Is there any code base in this world that developers would not complain about? ;)
The only perfect code is the one you write, all others are crap
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#46Hi, GitLab team member here. Heads-up: GitLab.com appears to be stable again. Our engineers are monitoring and investigating the root cause of the incident.
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#47Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#48Earlier quoted context omitted.
It is usually their shared runners. I experience outages with them a couple times a month. It isn't a big deal since we maintain our own private pool, so I just move jobs to them. (They make you pay for CI minutes so we use them for certain jobs.)
For me even our private runners stopped worked over the last few weeks
Ouch. We haven't seen that, but we don't run them all the time either.
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#49Earlier quoted context omitted.
Hi, what could be improved in GitLab's code base in your opinion? :)
In the past people have suggested we rewrite GitLab in Scala, Haskell, Node.js, and IIRC also regular Java. I think it mostly comes down to "I didn't write it, so it's bad" :)
Nah, i don't care which language. Like, at all. I just think that gitlab outgrow ruby.
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#50Hi, GitLab team member here. Heads-up: GitLab.com appears to be stable again. Our engineers are monitoring and investigating the root cause of the incident. https://twitter.com/gitlabstatus/status/1371443832865222658
Out of curiosity, why does your "about" page vouch for a suspended Twitter account? Is @GitLab -> @GitLabs a typo?
https://about.gitlab.com/handbook/marketing/community-relati...
@GitLab