Gitlab 13.1
about.gitlab.com
Gitlab 13.1
1–10 of 90 posts
Re: Gitlab 13.1
#2"This month's Most Valuable Person (MVP) is Jacopo Beschi
"
What a cool company culture. telling people they are doing good in person is nice, telling it to them and also sharing it with the world is great
Re: Gitlab 13.1
#3If anyone from GitLab is reading this, these pages are locked in a refresh loop. I can't read the content because it is scrolling/moving slightly with every refresh which is happening constantly.
Latest version of Chrome stable, uBlock Origin in default config, HTTPS Everywhere, React/Redux devtools are the extensions I have installed.
I let the page run for 30 seconds and:
* CPU usage on two cores was at 100%
* 2,943 requests were made for 319 MB of resources over 30.06 seconds
A staggering rate of 100 requests per second that persists indefinitely - I have no reason to believe the refresh loop is broken at any point.
Re: Gitlab 13.1
#4With every release I wonder why our team is even paying for Gitlab Bronze. It seems to offer no value at all, might as well go for the free tier and save a thousand dollars a year.
Re: Gitlab 13.1
#5With every release I wonder why our team is even paying for Gitlab Bronze. It seems to offer no value at all, might as well go for the free tier and save a thousand dollars a year.
I'm not saying they should remove any free features, but now and then it'd be nice seeing a Silver feature come to Bronze.
Re: Gitlab 13.1
#6If anyone from GitLab is reading this, these pages are locked in a refresh loop. I can't read the content because it is scrolling/moving slightly with every refresh which is happening constantly. Latest version of Chrome stable, uBlock Origin in default config, HTTPS Everywhere, React/Redux devtools are the extensions I have installed. I let the page run for 30 seconds and: * CPU usage on two cores was at 100% * 2,94…
GitLab technical evangelist here.
I can't seem to reproduce this - maybe it's uBlock Origin? Are you sure it's the default configuration? What were the requests to - just to the main HTML page?
Re: Gitlab 13.1
#7If anyone from GitLab is reading this, these pages are locked in a refresh loop. I can't read the content because it is scrolling/moving slightly with every refresh which is happening constantly. Latest version of Chrome stable, uBlock Origin in default config, HTTPS Everywhere, React/Redux devtools are the extensions I have installed. I let the page run for 30 seconds and: * CPU usage on two cores was at 100% * 2,94…
@AaronFriel try deleting your cookies for the website and see if that resolves it. I recall someone at GitLab having that problem the other day and think I recall that clearing their cookies fixed the issue for them. Either way I'll notify our marketing website team to have a look at this.
Re: Gitlab 13.1
#8With every release I wonder why our team is even paying for Gitlab Bronze. It seems to offer no value at all, might as well go for the free tier and save a thousand dollars a year.
Merge Request Reviews was moved to core as part of this release.
Re: Gitlab 13.1
#9If anyone from GitLab is reading this, these pages are locked in a refresh loop. I can't read the content because it is scrolling/moving slightly with every refresh which is happening constantly. Latest version of Chrome stable, uBlock Origin in default config, HTTPS Everywhere, React/Redux devtools are the extensions I have installed. I let the page run for 30 seconds and: * CPU usage on two cores was at 100% * 2,94…
GitLab technical evangelist here. I can't seem to reproduce this - maybe it's uBlock Origin? Are you sure it's the default configuration? What were the requests to - just to the main HTML page?
[deleted]
Re: Gitlab 13.1
#10If anyone from GitLab is reading this, these pages are locked in a refresh loop. I can't read the content because it is scrolling/moving slightly with every refresh which is happening constantly. Latest version of Chrome stable, uBlock Origin in default config, HTTPS Everywhere, React/Redux devtools are the extensions I have installed. I let the page run for 30 seconds and: * CPU usage on two cores was at 100% * 2,94…
@AaronFriel try deleting your cookies for the website and see if that resolves it. I recall someone at GitLab having that problem the other day and think I recall that clearing their cookies fixed the issue for them. Either way I'll notify our marketing website team to have a look at this.
One thing to look at is that the page does at least one whole page refresh by default, even an incognito window.
If I open up the page in incognito, I see two requests in the network tab for https://about.gitlab.com/releases/2020/06/22/gitlab-13-1-rel...