Bugzilla attachments should live on GitHub

[JasonGross]

Description of the problem

Currently migrated bugs link to bugzilla attachments. GitHub supports uploading .txt, .log, and .zip files as attachments on issues. I propose that for all bugs with attachments on bugzilla, we archive the files in a .zip file, and attach that to the github issue.

One possible alternative is to special-case .txt, .log, and .v files, to rename foo.v to foo.v.txt, and upload these separately. However, I don't think there's any particular benefit to doing this, as I don't think you can view .txt or .log file attachments in the browser without downloading them.

[Zimmi48]

GitHub API doesn't support uploading attachments, so unless some people are willing to do this by hand, I guess this issue is going to be a "won't fix".

Note that currently the bugs link to attachments on Bugzilla but the plan is to preserve the attachments beyond the Bugzilla take-down (as static assets).

[Zimmi48]

Maybe though, I should have documented this in the blog post I published about the migration.

[JasonGross]

If we do want to migrate the attachments, rather than leaving them as static content elsewhere, if someone attaches to this issue a zipfile which contains, for each bug with attachments, a zipfile named <github issue number>.zip which contains the attachments, I can write an autohotkey script that uploads them to the correct issues. If there's a plan to preserve them elsewhere as static assets, though, is this desired?

[Zimmi48]

I'm going to leave it to @letouzey to decide what he thinks of this issue. Should we follow the initial plan of letting https://coq.inria.fr/bugfiles/ (where attachments live) survive the take down of https://coq.inria.fr/bugs/ as static assets or should we try the approach suggested by @JasonGross of uploading attachments on GitHub using a autohotkey script?

[letouzey]

Here come our 776 attachment numbers with their various metadata :
attachments.txt. It is actually a csv file with | as separator, and a header row. Beware that the bug_id fields refer to the bug number before the transition to github, so this should be combined with @Zimmi48 mapping.

If it is actually doable to upload all the corresponding files to github, I'm rather in favor of that. But beware of github : if you do something too automatic with their web interface, you'll probably be flagged as a spammer real quick...

As discussed with @Zimmi48 today, ideally the short .v attachments should rather be put into a code block inside an extra comment or be added as gist links. And it seems that .tgz are allowed, not only .zip files.

[letouzey]

I've put today the old bugzilla definitively offline. The attachments are now static files such as this one, with a redirect for compatibility urls such as this one. Mime type and download file name should be preserved thanks to an ad-hoc .htaccess.

[letouzey]

And if somebody wants to play more with these bug attachments, here comes the whole bunch of them :
bugfiles.zip (23Mb). The file names inside the archive are the attach_id, see above the attachment list.

[Zimmi48]

@letouzey You should change this page https://coq.inria.fr/bugs/ now that the old bugzilla is offline. Probably a simple redirect to https://github.com/coq/coq/issues would be enough.

[letouzey]

@Zimmi48 : done. I've also placed a redirect from https://coq.inria.fr/bugs/show_bug.cgi?id=NNN to http://github.com/coq/coq/issues/NNN, since there may remain some of these old urls in obscure places. For the moment this redirect is incorrect for bugs that were renumbered during the transition, I'll fix that later today.

[Zimmi48]

@vbgl It is possible that this issue becomes relevant with the website migration.

[Zimmi48]

With the GitHub Pages website migration, Bugzilla attachments are no longer available on the Coq website. It's time to decide whether to migrate them to GitHub attachments or to close this issue, based on the principle that, after many years, most of these issues have been solved and/or the attachments have become irrelevant, and that if they need to be retrieved, there is still the tarball provided by Pierre in this thread.

[JasonGross]

Does coqbot support uploading attachments to GitHub yet? I think it would be nice but not essential to get the attachments on GitHub, I expect it shouldn't be too hard to script if we already have code in coqbot for uploading attachments and commenting with them, and furthermore we'll want the ability to upload attachments for enhancing the minimizer comments, so I don't think adding this functionality to coqbot would be wasted effort. (It seems fine to go the route of making a new comment with "here's the attachment that was previously named ..." rather than editing existing comments, if that's easier to script.)

[Zimmi48]

No, GitHub still doesn't provide an official API for uploading attachment files. A comment from 2021 explained this. However, it seems that there exists an undocumented API that allows to do this. See: https://github.com/j178/github-s3. I'm not sure that abusing it in coqbot would be a good idea though.

[JasonGross]

However, it seems that there exists an undocumented API that allows to do this. See: https://github.com/j178/github-s3

Looking at the code, this is just some go code that pretends to be the browser doing the same thing that happens when you drag and drop a file