llvm dev - Dec 2021 - [cfe-dev] Status of Bugzilla Migration

On Thu, Dec 2, 2021 at 12:47 PM Jeff Miller via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
>
> >- This has to be done via GitHub API and we're rate limited to
~5000
> requests per hour, so this means that the labelling will take ~20
> hours. I was told that there is no way for us to have the API rate
> limit increased.
>
> This 5000 request per hour limit, is that per repo or per access token?
> Could we potentially make a pool access token from multiple github accounts
> to sidestep the issue? Say 20 tokens to do the migration in 1 hour?
>
FWIW, "20 hours" or "11 hours" or "three days" is
like nothing, compared to
what the migration has already been doing. If it only requires taking
Bugzilla down for 24 hours to do it, IMO you should just do it already —
whatever "it" is.

Also, re timestamps: The choices seem to be
- Wait for GitHub to offer us some way of importing timestamps, *then* do
the migration; or
- Do the migration, *then* wait for GitHub to offer us some way of
retroactively changing some of the timestamps.
Neither is perfect, but the latter is clearly better for LLVM's purposes.

–Arthur
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211202/68e3e973/attachment.html>

Hello Arthur,
> FWIW, "20 hours" or "11 hours" or "three
days" is like nothing, compared to what the migration has already been
doing. If it only requires taking Bugzilla down for 24 hours to do it, IMO you
should just do it already — whatever "it" is.
Well, it's for single sweep. So, if we'd need to do this, say 5 times,
then everything starts to be very interesting.
> Also, re timestamps: The choices seem to be
> - Wait for GitHub to offer us some way of importing timestamps, then do the
migration; or
> - Do the migration, then wait for GitHub to offer us some way of
retroactively changing some of the timestamps.
> Neither is perfect, but the latter is clearly better for LLVM's
purposes.
Not the timestamps, the labels. And note that there is nothing in
general that could be done in GitHub retroactively. At least for us as
I've been told. If this would be possible we'd simply import into an
empty repo, add git repo, add releases (dating them into the past) and
we're done...

-- 
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University