On Mon, Jan 16, 2023 at 3:34 PM Dima Pasechnik <dimp...@gmail.com> wrote: > > I don't know. Perhaps Matthias changed something in the setup of the repos.
I doubt it's some sort of metadata poisoning that happened in the latest iteration so that the search broke - it's probably general flakiness of setup. We can, potentially, ask GitHub support for help. However, the Enterprise Server version we're using is not the very latest - but I don't want more hours of banging my head on the keyboard to upgrade it to the next minor version (as they'd probably 1st thing ask for such an update...) > > On Mon, Jan 16, 2023 at 3:26 PM Aram Dermenjian <> wrote: > > > > Hey Dima, > > > > I'm confused by what you mean by "The search on issues is currently not > > working, but it's probably a limitation of > > our trial setup." > > > > When I tried the search on the earlier version it was working fine, but > > it's not working on this new version. > > https://34.105.185.241/sagemath/sage-all-2023-01-12-003/issues?q=34782+ > > vs > > https://34.105.185.241/sagemath/sage-all-2023-01-14-004/issues?q=34782+ > > > > -Aram > > > > On Mon, 16 Jan 2023 at 11:56, Dima Pasechnik <dimp...@gmail.com> wrote: > >> > >> On Mon, Jan 16, 2023 at 9:07 AM John Cremona <john.crem...@gmail.com> > >> wrote: > >> > > >> > > >> > > >> > On Mon, 16 Jan 2023 at 07:45, Matthias Koeppe <matthiaskoe...@gmail.com> > >> > wrote: > >> >> > >> >> Next iteration: > >> >> https://34.105.185.241/sagemath/sage-all-2023-01-14-004/issues > >> >> with much improved labels > >> > > >> > > >> > The label component: elliptic curves is empty, which does not seem > >> > right. On trac there are 64 open elliptic curve tickets. One currently > >> > active example is #34782. What is the best way to look for the new > >> > issue corresponding to a trac ticket number? > >> > > >> > Currently the only authors on issues are Dima and Matthias. > >> > >> No, why? See e.g. > >> https://34.105.185.241/sagemath/sage-all-2023-01-14-004/issues/21093 > >> (author: you, John :-)) > >> https://34.105.185.241/sagemath/sage-all-2023-01-14-004/issues/34898 > >> (author: fchapoton) > >> https://34.105.185.241/sagemath/sage-all-2023-01-14-004/issues/34905 > >> (author: tscrim) > >> > >> > >> > >> > Will it be possible to make the issue authors match the ticket creator > >> > on trac? > >> the plan is that for everybody with a github account the trac tickets > >> acct names are mapped to > >> these account names. For the rest, they are mapped to some aliases. > >> > >> The search on issues is currently not working, but it's probably a > >> limitation of > >> our trial setup. > >> > >> > >> > > >> > John > >> > > >> >> > >> >> > >> >> > >> >> On Friday, January 13, 2023 at 11:26:50 AM UTC-8 Matthias Koeppe wrote: > >> >>> > >> >>> We have just completed the first full trial migration of all ~35000 > >> >>> open and closed Trac tickets (as of late December) into a temporary > >> >>> GitHub Enterprise Server instance. > >> >>> > >> >>> Please take a look at: > >> >>> https://34.105.185.241/sagemath/sage-all-2023-01-12-003/issues > >> >>> (accepting the self-signed server certificate) > >> >>> > >> >>> The README of https://github.com/sagemath/trac-to-github explains some > >> >>> of the principles of the migration. It takes about 12 hours to get all > >> >>> data from Trac and to write a migration archive, and then about 20 > >> >>> hours to import it into our server. In the final migration (planned > >> >>> for Feb 1), our contact at GitHub.com will import a freshly generated > >> >>> migration archive into GitHub.com, and we will take down our temporary > >> >>> GitHub Enterprise Server instance. > >> >>> > >> >>> Questions regarding the migration are very welcome. Please report any > >> >>> errors or wishlist items regarding the conversion here or at > >> >>> https://github.com/sagemath/trac-to-github/issues > >> >>> > >> >>> > >> >> -- > >> >> You received this message because you are subscribed to the Google > >> >> Groups "sage-devel" group. > >> >> To unsubscribe from this group and stop receiving emails from it, send > >> >> an email to sage-devel+unsubscr...@googlegroups.com. > >> >> To view this discussion on the web visit > >> >> https://groups.google.com/d/msgid/sage-devel/ee8d93b2-afe8-411a-b1ac-51586c0dc1d4n%40googlegroups.com. > >> > > >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups "sage-devel" group. > >> > To unsubscribe from this group and stop receiving emails from it, send > >> > an email to sage-devel+unsubscr...@googlegroups.com. > >> > To view this discussion on the web visit > >> > https://groups.google.com/d/msgid/sage-devel/CAD0p0K4NYBt_p8xcdFY4xn-T4wBUUfMsGFNaDFKFawHv_EObkw%40mail.gmail.com. > >> > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "sage-devel" group. > >> To unsubscribe from this group and stop receiving emails from it, send an > >> email to sage-devel+unsubscr...@googlegroups.com. > >> To view this discussion on the web visit > >> https://groups.google.com/d/msgid/sage-devel/CAAWYfq1YHtUty5UjJo-LPzvLRQ04d1NF071oupre1h_gCsY9MA%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq2Sp6_sh%2B488jj%3D-_t3Mrgp9%3DODTmyw5i2PGd2X%2B4QV-g%40mail.gmail.com.
