Broken GitWeb

[M. GOUJON]

Hi everyone,

It appears Wine GitWeb 
https://source.winehq.org/git/wine.git/?a=shortlog page is broken 
since Monday, returning a 403 Forbidden error.
I know there is also the GitLab version 
https://gitlab.winehq.org/wine/wine/-/commits/master but I prefer the 
old one.

Can someone have a look and fix the (permission) issue?

Thanks in advance,
Regards

[Zhiyi Zhang]

Hi,

Quoting from winehackers IRC:
> <zhiyi> https://source.winehq.org/git/ shows forbidden to me, is this expected?
> <zf> zhiyi, yes, it's been discontinued
> <zhiyi> oh, okay.
> <zf> there wasn't an announcement, but basically, gitweb is poorly optimized on the server side and bots were causing a lot of load

So it seems deprecated now.

Thanks,
Zhiyi

On 7/18/24 04:11, M. GOUJON wrote:
> Hi everyone,
>
> It appears Wine GitWeb https://source.winehq.org/git/wine.git/?a=shortlog page is broken since Monday, returning a 403 Forbidden error.
> I know there is also the GitLab version https://gitlab.winehq.org/wine/wine/-/commits/master but I prefer the old one.
>
> Can someone have a look and fix the (permission) issue?
>
> Thanks in advance,
> Regards

[Jimi Huotari]

On Wed, 17 Jul 2024 22:11:02 +0200
"M. GOUJON"  wrote:
> Hi everyone,
>
> It appears Wine GitWeb 
> https://source.winehq.org/git/wine.git/?a=shortlog page is broken 
> since Monday, returning a 403 Forbidden error.
> I know there is also the GitLab version 
> https://gitlab.winehq.org/wine/wine/-/commits/master but I prefer the 
> old one.
>
> Can someone have a look and fix the (permission) issue?
>
> Thanks in advance,
> Regards

Since it seems to be intentional, and I'm not a big fan of certain things
regarding gitlab myself (infinite scroll, JavaScript requirement, ...),
I'll probably start making more use of a local clone for what I used
the gitweb instance for.

Additionally, I was informed/reminded of 'git instaweb', which will offer
a rather similar, if not identical experience while using a local clone,
which will also be free of any connection issues (if the clone is
acceptably up to date that is).  :]

[Hin-Tak Leung]

FWIW, github keeps many automated mirrors of open-source projects: https://github.com/wine-mirror/wine

On Thursday 18 July 2024 at 11:25:10 BST, Jimi Huotari  wrote:

On Wed, 17 Jul 2024 22:11:02 +0200
"M. GOUJON"  wrote:
> Hi everyone,
>
> It appears Wine GitWeb 
> https://source.winehq.org/git/wine.git/?a=shortlog page is broken 
> since Monday, returning a 403 Forbidden error.
> I know there is also the GitLab version 
> https://gitlab.winehq.org/wine/wine/-/commits/master but I prefer the 
> old one.
>
> Can someone have a look and fix the (permission) issue?
>
> Thanks in advance,
> Regards

Since it seems to be intentional, and I'm not a big fan of certain things
regarding gitlab myself (infinite scroll, JavaScript requirement, ...),
I'll probably start making more use of a local clone for what I used
the gitweb instance for.

Additionally, I was informed/reminded of 'git instaweb', which will offer
a rather similar, if not identical experience while using a local clone,
which will also be free of any connection issues (if the clone is
acceptably up to date that is).  :]

[Gabriel Ivăncescu]

Unfortunately, github has also been increasingly reliant on javascript 
and became very sluggish on less mainstream browsers, but it's still 
better than gitlab's UI.

gitweb was just on another level of convenience for me. Sad moment.

On 18/07/2024 19:26, Hin-Tak Leung wrote:
> FWIW, github keeps many automated mirrors of open-source projects: 
> https://github.com/wine-mirror/wine
>
> On Thursday 18 July 2024 at 11:25:10 BST, Jimi Huotari 
>  wrote:
>
> On Wed, 17 Jul 2024 22:11:02 +0200
> "M. GOUJON" <[e-mail] > wrote:
> > Hi everyone,
> >
> > It appears Wine GitWeb
> > https://source.winehq.org/git/wine.git/?a=shortlog page is broken
> > since Monday, returning a 403 Forbidden error.
> > I know there is also the GitLab version
> > https://gitlab.winehq.org/wine/wine/-/commits/master but I prefer the
> > old one.
> >
> > Can someone have a look and fix the (permission) issue?
> >
> > Thanks in advance,
> > Regards
>
> Since it seems to be intentional, and I'm not a big fan of certain things
> regarding gitlab myself (infinite scroll, JavaScript requirement, ...),
> I'll probably start making more use of a local clone for what I used
> the gitweb instance for.
>
> Additionally, I was informed/reminded of 'git instaweb', which will offer
> a rather similar, if not identical experience while using a local clone,
> which will also be free of any connection issues (if the clone is
> acceptably up to date that is).  :]

[Elizabeth Figura]

On Thursday, 18 July 2024 12:01:59 CDT Gabriel Ivăncescu wrote:
> Unfortunately, github has also been increasingly reliant on javascript 
> and became very sluggish on less mainstream browsers, but it's still 
> better than gitlab's UI.
>
> gitweb was just on another level of convenience for me. Sad moment.

Yeah, I'm also sad about this. gitweb was fast, it didn't have visual clutter, it was able to render several times as many commits as gitlab or github, it had a lot more intuitive UI and more links in convenient places...

Brendan suggested this off-list, but if gitweb is badly optimized on the server side, could we try cgit instead? It has a similarly nice experience to gitweb and might be more efficient.

--Zeb

[Jeremy Newman]

If someone wants to patch it so it doesn't eat up 100% cpu on all cores 
we could potentially put it back online. I also worry how it shells out 
to the command line git a bit too much. When the web server starts 
hitting 100 load average for extended periods I tend to notice.

As I stands now, I don't feel it is a safe tool to put up on a public 
website. Way too easy to DDOS with it.

On 7/18/2024 12:14 PM, Elizabeth Figura wrote:
> On Thursday, 18 July 2024 12:01:59 CDT Gabriel Ivăncescu wrote:
> > Unfortunately, github has also been increasingly reliant on javascript
> > and became very sluggish on less mainstream browsers, but it's still
> > better than gitlab's UI.
> >
> > gitweb was just on another level of convenience for me. Sad moment.
>
> Yeah, I'm also sad about this. gitweb was fast, it didn't have visual clutter, it was able to render several times as many commits as gitlab or github, it had a lot more intuitive UI and more links in convenient places...
>
> Brendan suggested this off-list, but if gitweb is badly optimized on the server side, could we try cgit instead? It has a similarly nice experience to gitweb and might be more efficient.
>
> --Zeb