llvm dev - Dec 2021 - [cfe-dev] Bugzilla migration is stopped again

This may be a dumb question, but could this just be an issue of forward
references (i.e. issue A references B, but B has not been transferred yet
so doesn't exist)?
If so, could the transfer be split into a two step process:
1. Open all issues with summaries only
2. Populate description, comments, labels, etc.

Please note that I have no idea how any of this GitHub or Bugzilla stuff
works, so this suggestion may be completely absurd.

On Fri, Dec 3, 2021 at 7:19 PM Anton Korobeynikov via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> Dear All,
>
> I hate to say this, but the migration was stopped again. Now it seems
> that GitHub does not rewrite issue references properly during the
> transfer (sick!). Let me show what the problem is exactly:
>
> Consider two issues: A and B, where A will reference B and B will
> reference A. In our case this is used to model various relations like
> "duplicates / is duplicated by", "blocks / is blocked
by", "depends on
> / required by". So, in bz archive A will reference B as #B and B
> will reference #A.
>
> Now, let's migrate A. The references will be rewritten. #B =>
> bz-archive#B and #A => llvm-project#A. However, after migration of B
> only one reference is rewritten llvm-project#A => #A, the bz-archive#B
> link in the issue A will not be rewritten and therefore a dangling
> reference will appear.
>
> For us this means that we will lose all links to duplicate issues, and
> (more important!) to linked issues in the meta bugs.
>
> I informed GitHub about the bug and I am waiting for their answer.
>
> --
> With best regards, Anton Korobeynikov,
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211203/d5b8c2bd/attachment.html>

Hello
> This may be a dumb question, but could this just be an issue of forward
references (i.e. issue A references B, but B has not been transferred yet so
doesn't exist)?
> If so, could the transfer be split into a two step process:
It cannot, sorry

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

On Sat, 4 Dec 2021 at 00:54, Nemanja Ivanovic via cfe-dev
<cfe-dev at lists.llvm.org> wrote:
>
> This may be a dumb question, but could this just be an issue of forward
references (i.e. issue A references B, but B has not been transferred yet so
doesn't exist)?
> If so, could the transfer be split into a two step process:
> 1. Open all issues with summaries only
> 2. Populate description, comments, labels, etc.
>
> Please note that I have no idea how any of this GitHub or Bugzilla stuff
works, so this suggestion may be completely absurd.
>
This would seem like a sensible approach to me.
I have worked with many different graph databases, and it is quite
normal to load the nodes or entities first, and then add the
relationships or links second.
Maybe one can add all the bugs first, without any relationships/links.
Then build up a map of github IDs vs bugzilla IDs, and then use that
map to then add all the relationships afterwards using the learnt
bugzilla IDs.
Or, alternatively, use your current method, and then scan over
everything at the end, to add in any relationships that got missed
using the above approach.

Kind Regards

James