help / color / mirror / code / Atom feed
From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: gitlab out of sync with sourceforge and github repositories
Date: Sun, 18 Dec 2022 19:42:14 +0000	[thread overview]
Message-ID: <bc9307eb-bab4-4b26-900b-8fe2bb6a2270@app.fastmail.com> (raw)
In-Reply-To: <CA+rB6GJkWGesbHp4fx6QeLxb0xXWPbrCmjGTin2NnDo6rp5DyQ@mail.gmail.com>

Jim wrote on Sun, 18 Dec 2022 01:58 +00:00:
> On Sat, Dec 17, 2022 at 2:14 PM Daniel Shahaf <d.s@daniel.shahaf.name>
> wrote:
>> Now, I'm not even sure whether the lag observed this week was a one-time
>> thing or not.  However, should we determine that the GitLab mirror's
>> settings need to be changed, Oliver and I can effect such changes.
>> Daniel
>  I have noticed this lag multiple times before, so it's not a one off.
>  Generally GL catches up with the others within 24 to 48 hours
>  AFAICT(don't have actual numbers). But since I manually update, and
>  not every day, I really couldn't tell you how often this occurs or if
>  there is some pattern.

More interestingly, the last commit on gitlab as of this writing is
67d4bf5bb936a5b95160410b4790f2bf4113c75f, even though another commit was
pushed on the 14th at 05:06Z.  (I'm basing this date on the sourceforge
commit emails rather than on author dates or committer dates.)

I'm not sure what does the pushes.  It doesn't seem to be documented in
the infra repository either.  Oliver, any idea why gitlab hasn't updated in 4.5 days?



> Regards,
> Jim

  reply	other threads:[~2022-12-18 19:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 13:47 Jim
2022-12-15 19:01 ` Jim
2022-12-15 21:26   ` Daniel Shahaf
2022-12-16 21:04     ` Jim
2022-12-17 19:57       ` Bart Schaefer
2022-12-17 20:14         ` Daniel Shahaf
2022-12-18  1:58           ` Jim
2022-12-18 19:42             ` Daniel Shahaf [this message]
2022-12-18 23:40               ` Oliver Kiddle
2023-03-06 13:42                 ` Jim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bc9307eb-bab4-4b26-900b-8fe2bb6a2270@app.fastmail.com \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).