HG-Bridge disabled (Re: Mercurial connection refused)

[Christian Brabandt]

Hi,
just to let everybody know. Because of serious load issues, the HG
bridge is disabled for now.

Just for my reference, how many users are still using it hg.256bit.org?
If there are very many users, we should probably move it to the vim.org
domain.

Thanks,
Chris

On Tue, 19 Nov 2024, Tony Mechelynck wrote:

> On Tue, Nov 19, 2024 at 2:55 PM Christian Brabandt <cbl...@256bit.org> wrote:
> >
> >
> > On Tue, 19 Nov 2024, Tony Mechelynck wrote:
> >
> > > linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
> > > abort: error: Connection refused
> > > exit status 255
> > > Tue 19 Nov 14:48:32 CET 2024
> > > linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
> > > abort: error: Connection refused
> > > exit status 255
> > > Tue 19 Nov 14:48:50 CET 2024
> > >
> > > Let us hope this is only temporary.
> >
> > It was. Sometimes there is a bit of load on the server (for unknown
> > reasons).
> >
> > Thanks,
> > Christian

Mit freundlichen Grüßen
Christian
--
YOW!! Now I understand advanced MICROBIOLOGY and th' new TAX REFORM laws!!

[Marvin Renich]

* Christian Brabandt <cbl...@256bit.org> [241119 10:47]:

> Hi,
> just to let everybody know. Because of serious load issues, the HG
> bridge is disabled for now.
>
> Just for my reference, how many users are still using it hg.256bit.org?
> If there are very many users, we should probably move it to the vim.org
> domain.

I still use it once in a while. I mostly use the official Debian
packages, but I have a strong preference for hg over git, so that is
what I use when I want the latest source.

...Marvin

[Tony Mechelynck]

On Tue, Nov 19, 2024 at 4:47 PM Christian Brabandt <cbl...@256bit.org> wrote:
>
> Hi,
> just to let everybody know. Because of serious load issues, the HG
> bridge is disabled for now.
>
> Just for my reference, how many users are still using it hg.256bit.org?

I don't know how many are, but as I suppose you already know, I am one
of them. For some reason Mercurial feels congenial to me and git
doesn't.

My current Mercurial configuration includes the following remote
repository aliases, which I am listing alphabetically below with name,
URL, and current response to "hg in". Some of them may be obsolete.
bitbucket = https://bitbucket.org/vim-mirror/vim
Not found.
default = http://hg.256bit.org/vim
Not found.
osdn = https://hg.osdn.net/view/vim/vim
Certificate has expired.
In other words, the latter one is still responding, but rejecting the
request for lack of an up-to-date certificate.
I practically always pull from the "default" source unless, like now,
it really goes down.

> If there are very many users, we should probably move it to the vim.org
> domain.

If you could do that without too much hassle, for someone at the
receiving end like me it would just be a matter of adjusting the
source aliases (i.e. those displayed by "hg paths") to make sure that
the "default" source is the one we normally want to pull from. A piece
of cake.

>
> Thanks,
> Chris

My pleasure,
Tony.

>
> On Tue, 19 Nov 2024, Tony Mechelynck wrote:
>
> > On Tue, Nov 19, 2024 at 2:55 PM Christian Brabandt <cbl...@256bit.org> wrote:
> > >
> > >
> > > On Tue, 19 Nov 2024, Tony Mechelynck wrote:
> > >
> > > > linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
> > > > abort: error: Connection refused
> > > > exit status 255
> > > > Tue 19 Nov 14:48:32 CET 2024
> > > > linux-tuxedo:~/.build/vim/vim-hg # hg in || echo 'exit status' $? ; date
> > > > abort: error: Connection refused
> > > > exit status 255
> > > > Tue 19 Nov 14:48:50 CET 2024
> > > >
> > > > Let us hope this is only temporary.
> > >
> > > It was. Sometimes there is a bit of load on the server (for unknown
> > > reasons).
> > >
> > > Thanks,
> > > Christian
>
> Mit freundlichen Grüßen
> Christian
> --
> YOW!! Now I understand advanced MICROBIOLOGY and th' new TAX REFORM laws!!
>

> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/vim_dev/Zzyy/lTDSAwYqiH/%40256bit.org.

[Tony Mechelynck]

On Wed, Nov 20, 2024 at 2:10 AM Tony Mechelynck
<antoine.m...@gmail.com> wrote:
>
> On Tue, Nov 19, 2024 at 4:47 PM Christian Brabandt <cbl...@256bit.org> wrote:
> >
> > Hi,
> > just to let everybody know. Because of serious load issues, the HG
> > bridge is disabled for now.
> >
> > Just for my reference, how many users are still using it hg.256bit.org?
>
> I don't know how many are, but as I suppose you already know, I am one
> of them. For some reason Mercurial feels congenial to me and git
> doesn't.
>
> My current Mercurial configuration includes the following remote
> repository aliases, which I am listing alphabetically below with name,
> URL, and current response to "hg in". Some of them may be obsolete.
> bitbucket = https://bitbucket.org/vim-mirror/vim
> Not found.
> default = http://hg.256bit.org/vim
> Not found.
> osdn = https://hg.osdn.net/view/vim/vim
> Certificate has expired.
> In other words, the latter one is still responding, but rejecting the
> request for lack of an up-to-date certificate.
> I practically always pull from the "default" source unless, like now,
> it really goes down.

P.S. I also install the vim executable from openSUSE Tumbleweed
(currently at version/patchlevel 9.1.836, and not with the same
+features as the Vim which I compile myself, or (if Mercurial
distribution never resumes) which I used to (currently at
version/patchlevel 9.1.873). This openSUSE vim is at /bin/vim and at
/user/bin/vim while mine is at /usr/local/bin/vim which is earlier in
the $PATH. Similarly for gvim, view, gview, etc. symlinks.

[Christian Brabandt]

On Wed, 20 Nov 2024, Tony Mechelynck wrote:

> On Tue, Nov 19, 2024 at 4:47 PM Christian Brabandt <cbl...@256bit.org> wrote:
> >
> > Hi,
> > just to let everybody know. Because of serious load issues, the HG
> > bridge is disabled for now.
> >
> > Just for my reference, how many users are still using it hg.256bit.org?
>
> I don't know how many are, but as I suppose you already know, I am one
> of them. For some reason Mercurial feels congenial to me and git
> doesn't.
>
> My current Mercurial configuration includes the following remote
> repository aliases, which I am listing alphabetically below with name,
> URL, and current response to "hg in". Some of them may be obsolete.
> bitbucket = https://bitbucket.org/vim-mirror/vim
> Not found.
> default = http://hg.256bit.org/vim
> Not found.
> osdn = https://hg.osdn.net/view/vim/vim
> Certificate has expired.
> In other words, the latter one is still responding, but rejecting the
> request for lack of an up-to-date certificate.
> I practically always pull from the "default" source unless, like now,
> it really goes down.

Oh, Apparently I am still pushing to osdn, I thought I had disabled this
long time ago. For the time being, you can continue to use that one.

> > If there are very many users, we should probably move it to the vim.org
> > domain.
>
> If you could do that without too much hassle, for someone at the
> receiving end like me it would just be a matter of adjusting the
> source aliases (i.e. those displayed by "hg paths") to make sure that
> the "default" source is the one we normally want to pull from. A piece
> of cake.

I think we can configure a vim.org subdomain hg.vim.org and move the
bridge over there. Shouldn't be too much effort I suppose. CC: @Marc for
your info (as he is taking care of the hosting)

@Sec: Is it possible to configure a new hg.vim.org subdomain and point
it to the vim.org domain please?

Thanks all,
Christian
--
Thank you for observing all safety precautions.

[Tony Mechelynck]

On Wed, Nov 20, 2024 at 10:34 AM Christian Brabandt <cbl...@256bit.org> wrote:
[…]

> Oh, Apparently I am still pushing to osdn, I thought I had disabled this
> long time ago. For the time being, you can continue to use that one.

[…]

I would, if it would let me ; but AFAICT Mercurial is adamant about
not letting me pull from a server with an out-of-date certificate.

Best regards,
Tony.

[Tony Mechelynck]

P.S.

P.S. Apparently you aren't pushing to it anymore, and since long ago
from the number of bytes hg says were exchanged (611 sent 525
received). I removed the s in https and tried the same URL ; it
answered "no changes found".
>
> Best regards,
> Tony.

[Christian Brabandt]

Hm, I can still pull using --insecure

But pushing is totally broken:
```
pushing to ssh://chrisbra@osdn//hgroot/vim/vim
remote: logger: socket /dev/log: Connection refused
searching for changes
remote: abort: No usable temporary directory found in ['/tmp',
'/var/tmp', '/usr/tmp', '/home/users/c/ch/chrisbra']
abort: unexpected response: empty string
```
and neither can I push using https urls, so this repository is at
```
changeset: 36245:368dd9765c4d
tag: tip
user: Christian Brabandt <c...@256bit.org>
date: Sat Oct 05 17:15:03 2024 +0200
summary: runtime(compiler): add cppcheck linter compiler plugin
```

We will setup a secondary vim.org mercurial mirror, but this will take
some time.

Sorry,
Christian
--
Bride, n.:
A woman with a fine prospect of happiness behind her.
-- Ambrose Bierce, "The Devil's Dictionary"

[Tony Mechelynck]

Take all the time you need ; in the meantime I have two temporary
solutions as I mentioned in another thread (1. keep using Vim 9.1.873
compiled from my own config options when hg.256bit.org/vim was still
online ; 2. fall back on the Vim from my Linux distro, which will
always be a little behind the times but not much and will never be
exactly what I would have configured myself, but it is usable ;
currently it is at 9.1.836, Huge, with GTK3 GUI).

Best regards,
Tony.